Win10: Unattend.xml CopyProfile and OneDrive

You may find that OneDrive doesn’t work in Windows 10 after building a Custom Image and using the <CopyProfile> entry in the Unattend.xml. I detailed how CopyProfile works in my last post

The problem with Windows 10 is Copy Profile seems to break OneDrive

To get to this point, the following steps were done:

Create a Reference Image using a Build and Capture Task Sequence (Sysprep) in MDT. In my test there were no updates or customizations.
Deploy the Reference Image with CopyProfile set to True in the Unattend.xml
After deployment is complete, login as a New User
Run Regedit and search for ‘Administrator’

Registry Administrator Remnants

When reviewing the HKEY_CURRENT_USER of the New User, there were 50 remnants of the Administrator Profile. Most of these relate to OneDrive

Additional Administrator remnants seem to reference CD Burning and Internet Settings

Testing OneDrive

When logged in as Administrator, OneDrive opens as expected

When logging in as a New User and selecting OneDrive, nothing happens

Opening C:\Users\Administrator and selecting Continue to grant Permission

Allows OneDrive to work

The Real Solution

I believe the Solution would be to remove OneDrive and Reinstall, but I have not tested this at this time. Granting permissions to the Administrator Profile is not ideal for All Users, and quite possibly the Administrator Account should be removed or disabled. I will submit a Bug on Connect on this issue.

Pingback: Tool: OSConfig (Preview) Why? | David Segura
Matt 5:36 PM on May 23, 2016

Any updates on how to fix this? either via a first run script or some other method? I can verify it is still broken.

LikeLike
- segura 6:12 PM on May 23, 2016
  
  What is the issue?
  
  LikeLike
Craig 11:10 AM on August 22, 2016

A good way to fix this is to quickly start taskmgr and kill the onedrivesetup.exe before it deletes the run key from the registry. This is ofcourse taking into account you are running in audit mode.

Then delete the onedrive folder from Users\Administrator\AppData\Local\

Verify the key run key is still there under current_user Software\Microsoft\windows\currentversion\run

If it does not you can steal it from HKEY_USERS\S-1-5-20\SOFTWARE\Microsoft\Windows\CurrentVesion\Run

Now sysprep and future logons should have it setup correctly.

You can also correct it in the task sequence but you will need to make sure that the same version of the setup installer exists in C:\Windows\SysWOW64 as the one in the admin/default USER folder under AppData\Local\ if the version in the users folder is newer than the one in SysWOW64 it won’t work. you will need to copy out the onedrivesetup.exe form the update folder to the syswow64 folder then the key will work. You can use DISM to mount the image and do this offline…

Its best to do this before any update is applied and just have it in the image rather than try to fix it post capture in my opinion but it can be fixed during the imaging steps just would require some scripting logic.

LikeLike