Windows 10 V1803: Roaming profile not fully synchronized

[German]On Windows 10 version 1803 it is possible that server stored user profiles are not synchronized fully/properly. This results in error messages during shutdown and in event logs.


The problem with roaming profiles

The problem is a mentioned across the Internet. For example, I came across an article here about Windows 7 from 2015. Another forum post from 2011 is here. The latest post refers to Windows 10 version 1803, when shutting down Windows 10 V1803 systems the message ‘Your roaming user profile was not fully synchronized’ appears and a hint to look for details in the event log is given. Here is the German shutdown message.

Ihr Roamingbenutzerprofil wurde nicht vollständig synchronisiert

In the event display, the affected administrator found entries of the type:

Event-ID:   1509
Source:      Microsoft-Windows-User Profiles General
The file \\?\C:\Users\deepsys\AppData\Local\Microsoft\Windows\
UPPS\UPPS.bin could not be copied to \\?\UNC\server\profile\deepsys.V6\AppData\Local\Microsoft\ Windows\UPPS\UPPS.bin. Possible causes of errors are network problems or insufficient security rights. 

Event-ID:   1504
Source:       Microsoft-Windows-User Profiles Service
The roaming profile could not be fully updated. For details, see the previous events.

This can make an administrator desperate, as there will then be problems with the profiles.

Microsoft’s explanation: Changes in Windows 10 V1803

The affected administrator quoted above, finally found Microsoft’s KB article  KB4340390 “Roaming profile was not completely synchronized” error and logon, logoff delays on Windows 10 Version 1803 from June 20, 2018. Microsoft addresses the issue outlined above. The explanation:


This problem occurs because of a change that was made in Windows 10 Version 1803. This change inadvertently caused folders that are ususally excluded from roaming to be synchronized by roaming user profiles when you log on or log off. 

Microsoft is researching this problem and will post more information in this article when the information becomes available.

A workaround

If you have already upgraded to Windows 10 V1803, Microsoft suggests a workaround. To fix this issue, administrators must use the ExcludeProfileDirs registry key at

HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\

from a Windows 10 version 1709 machine and export it. Then import it on an affected Windows 10 version 1709 machine.


This entry was posted in issue, Windows and tagged , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *