OneDrive.exe fails to load after Windows 10 v1803 in-place feature upgrade

C

Craigg B

We've just started to pilot the Windows 10 April 2018 Update (version 1803) at work, and found something peculiar...


After rolling out the update via ConfigMgr 1802, the pilot users (including myself) noticed that the OneDrive Next Gen Sync Client wasn't working properly and wasn't appearing in the system tray (notification area) any more. We had access to files from our OneDrive for Business, including those which we hadn't previously downloaded, but there was no way to sync a new library and no way to check the settings. My Personal OneDrive had also vanished from the navigation bar in Explorer and there was no way to access the OneDrive Settings panel.


We also had two users who had managed to install the feature update at home, over the weekend (the Group Policy Object which disable Windows Update this wasn't applied to their OU for some reason). They were also experiencing the same issues with OneDrive, so delivery mechanism doesn't seem to be the issue. What was an issue is the lack of any visibility of Personal OneDrive, as one of the users was a Director who needed access to data on his consumer OneDrive.


Cue lots of headscratching and WTFing...


Managed to find similar symptoms listed when the Group Policy setting "Computer Configuration\Administrative Templates\Windows Components\OneDrive\Prevent the usage of OneDrive for file storage" was enabled. We checked the GPRESULTS of all affected machines, and none of the machines were showing this setting as being configured through Group Policy or Local Policy. When we checked the registry however, this value set to 1, which effectively causes OneDrive.exe to quit immediately (the setting translates to the DisableFileSyncNGSC DWORD value under the HKLM\SOFTWARE\Policies\Microsoft\Windows\OneDrive key) when it's started.


Absolutely no idea where this came from, but we updated our OneDrive Baseline Settings GPO to Disable the "Prevent the usage on OneDrive for file storage" setting, which forces the registry value to 0, and everything seems fine now.


Just putting this up here to hopefully save others from spending an age trying to figure out what's going on...

Continue reading...
 
Back
Top Bottom