Windows 10 Roaming Profile issue RRS feed

  • Question

  • I have created a Windows 10 WDS image, and it deploys fine. However domain user profiles don't work correctly.
     I have a domain user with no V5 roaming profile, log into Windows 10 and it creates the V5 profile on the server. If I log out of the machine and back into it, the account still works fine, but if I log on to another Windows 10 machine, or remove the users local profile (through System, Advanced, User Profiles) and then log back in, the Start menu or task bar don't work at all, the Edge icon is missing from the task bar and clicking the file explorer icon results in a permission error.

    After a lot of fiddling about with my completed Windows 10 image (all apps installed, unwanted Windows apps removed etc), I went back to basics to try and narrow down the problem.

     What I have tried:

     A clean install of Windows 10, configuring the default profile (unpinning apps from start menu), sysprep, capture and re-deploy the image with no group policies applied, log in with a clean user (no group policies).
     Log off, delete profile from local computer, attempt to log back in and the start menu is broken. So I know it is not a stray group policy, and after some investigating I see a lot of people having issues with the start menu.

     Another clean install, changed profile in audit mode (unpinned a couple of the apps and removed the search bar), rebooted the computer, joined to the domain, tested with clean user (no GPs or V5 profile), logged off, deleted the local profile, logged back in as domain user and the start menu doesn't work for that user.

     Yet another clean install, simply joined the flat Windows 10 install to the domain (this will basically be the same as above minus the profile changes) and the domain user works fine, I can delete the local copy of the profile and the start menu still works after login.
     Interestingly, if I then make changes to the domain user start menu (unpin a few apps), then repeat the process of delete local, log in again, all the apps I unpinned have returned. Please don't tell me that Start Menu configuration cannot be roamed?!

    It seems that making any changes to the default profile, particularly the Start Menu, seems to break the use of roaming profiles.
     Has anyone else experienced this yet? Is it a known bug in Windows 10? Or am I missing a step in the process somewhere?

    I have seen a solution involving a powershell command that re-installs all the windows apps, but this had no effect for my domain user, and I also saw that the All Application Packages group should have certain permissions, which it has.

     Also, the lack of group policies for controlling Edge is a real pain, how can you have a browser in an enterprise environment that you can't lock down?!

    Monday, October 19, 2015 9:14 AM

All replies

  • Have you used Windows ADK for creation Windows 10 image (and copyprofile parameter)?

    Monday, October 19, 2015 1:25 PM
  • I have yes. I believe the issue may be with the copyprofile parameter, as I have just been doing some more testing with a clean Windows image (literally just installing Windows 10, no WDS or anything) and using audit mode to modify the default profile - except this time I didn't change anything, just booted to audit mode, run sysprep with an unattend file that just says copyprofile, and the domain account still breaks after a second logon.

     So there seems to be an issue with doing a copyprofile at all.

    Monday, October 19, 2015 1:38 PM
  • I have the same issue


    Tuesday, October 20, 2015 8:23 AM
  • Hi,

    Windows 10 roaming profile use a new version of user profile called V5.

    And How about take out of the copyfile parameter?

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, October 22, 2015 7:26 AM
  • Hi

     As I said in my first post, the V5 profile is being created correctly, and it works without the copyprofile parameter. But I need to create a custom default profile, as I'm sure most enterprise users will want to do, and the only proper way to do that is with copyprofile.

     As linked in my last post, there is another thread with lots of people having issues with copyprofile breaking the roaming profiles in Windows 10 so there is clearly a bug with it.


    Thursday, October 22, 2015 8:06 AM
  • Hello ,


    Im created a Support Ticket on Microsoft.

    The Microsoft technician confirm mi that this problem is a bug on Windows 10.

    In November follows a update that fix this problem.


    • Edited by Pictop Monday, November 16, 2015 2:01 PM
    Monday, November 16, 2015 1:45 PM