If you installed May 2016 update rollup 3156418 on Windows Server 2012 R2, the DFSRS.exe process may consume a high percentage of CPU processing power (up to 100 percent). This may cause the DFSR service to become unresponsive to the point at which the service cannot be stopped.

Resolution. To resolve this issue, we have released a hotfix for Windows Server 2012 or Windows Server 2008 R2, and we have released an update rollup for Windows 8.1 or Windows Server 2012 R2. Get the update rollup for Windows Server 2012 R2.

Symptoms. Consider the following scenario: You use the Distributed File System Replication (DFSR) service in a Windows Server 2012-based domain environment. You have a Distributed File System (DFS) replication group in the domain environment. You use the DFSR service to replicate files in the DFS replication group.

Distributed File System Replication (DFSR) no longer replicates files after restoring a virtualized server's snapshot - Microsoft Support. Symptoms. Using any virtualization product you create a guest snapshot of a server replicating files with DFSR. You later restore that snapshot, returning the server to an earlier point in time.

DFSR stops replication after an unexpected shutdown in a Windows 8.1 or Windows Server 2012 R2 environment - Microsoft Support. Windows 8.1 Windows 8.1 Enterprise Windows 8.1 Pro More... Symptoms. Consider the following scenario:

Symptoms. Assume that you have Windows Server 2012 R2 or Windows Server 2012-based servers that use the Distributed File System Replication (DFSR) service. You have a DFSR replication topology in your environment. In this situation, you experience a spike of backlogs on a daily or weekly basis.

Turn off scanning of the DFSR Staging folder as specified in the msDFSR-StagingPath attribute of the object CN=SYSVOL Subscription,CN=Domain System Volume,CN=DFSR-LocalSettings,CN=DomainControllerName,OU=Domain Controllers,DC=DomainName in AD DS. This attribute contains the path to the actual location that DFS replication uses to stage files.

Cause. The DFS Replication service incorrectly manages the DFSR database. This behavior causes an inconsistent status. Resolution. Hotfix information. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article.