06-08-2017 09:40 AM
06-08-2017 09:40 AM
1. I deploy Windows 10 enterprise in a lab environment where hundreds of unique domain users are logging in and using the computers every monthy. We've had a problem where after a few weeks the Start Menu (and cortana) will become unresponsive, leaving users without a working Start Menu. I've seen posts from other users running into the same issue and based on my own troubleshooting I suspect the problem happens after windows updates are applied. Is MS aware of this issue and are there any plans to address it?
2. When building my image for these lab environments, I like to create a custome default user profile so that anyone who logs in will have the same user experience, for example the same desktop icons in the same order. In order for this to work, I have to sysprep my gold system twice using the copyprofile flag in the unattend.xml file. From what I can tell, I have to do this because the copyprofile process doesn't actually take place until the system is booting back up from the first sysprep. So I have to perform a second sysprep to actually capture the image with customizations made from the first sysprep. Is there a better way to do this?
06-08-2017 09:43 AM
06-08-2017 09:46 AM
1. We have addressed a few issues in early Windows 10 releases like this, but this shouldn't be happening any more. This can also happen with older antivirus software packages - they interfere with the start menu (accidentally).
2. There is no need to sysprep twice to use CopyProfile. It just needs to be set in the unattend.xml used when deploying the image. (See https://deploymentresearch.com/Research/Post/415/How-CopyProfile-really-works-in-Windows-7-Deploymen... for a discussion around that.) If you manually sysprep and capture, then the unattend.xml that you used with sysprep becomes the one that is embedded in the deployment image, so they are sort of one in the same. But in MDT or ConfigMgr, they would be separate.
06-08-2017 09:53 AM
06-08-2017 09:53 AM
1. It was definitly a problem with the early releases of Windows 10 and I don't think it has been reported again since moving to the Creators Edition, so hopefully it's fixed for good.
2. I look forward to trying this with my next image, I've been using two syspreps since the Windows 7 days as it's always worked for me, but it never felt right.
06-08-2017 09:57 AMSolution
06-08-2017 09:59 AM
We had the same experience on Windows 10 machines you describe in #1. We also use Office 365 and download Office 2016 from the portal. We found Uninstalling Office 2016 and Reinstalling cured this issue. Not sure why Office 2016 impacted a Windows 10 update.
06-08-2017 09:59 AM
I've had success customizing the start menu using a default associations config .xml file and assigning it through Group Policy, but for getting other customizations such as aligning desktop icons along the right side of the screen in a particular order, or even to remove first-use dialogues from some apps (MS Edge and Reader DC for example) I've had to use this two sysprep trick.
06-08-2017 02:50 PM
I would like to set up some customizations for the look and feel of the image that I haven't been able to do other ways so being able to possibly copy the profile and set the start menu settings both would be great, I will see if it works.
06-08-2017 05:58 PM - edited 06-08-2017 06:04 PM
From what I can find online, this was fixed in 1607 but from our own testing where I work, it is DEFINITELY broken again in 1703 - with the same symptoms. We cannot use CopyProfile at all right now for deployment.
Can we expect a fix?
If not, how can we deploy an image with a customized/configured default profile? This is vital to us.
06-08-2017 08:29 PM
UPDATE - WORKAROUND:
Adding these lines to the SetupComplete script for Sysprep fixed the CopyProfile issues for us in 1703:
Add these to: %WINDIR%\Setup\Scripts\SetupComplete.cmd
del /F /Q C:\Users\Default\AppData\Local\Microsoft\Windows\WebCacheLock.dat del /F /Q C:\Users\Default\AppData\Local\Microsoft\Windows\WebCache\*.* del /F /Q C:\Users\Default\AppData\Local\Microsoft\Windows\INetCache\*.*
09-15-2017 03:16 AM
I can confirm that "copyprofile" is causing issues in the latest Windows 10 release from the Volume Licensing Service Center (SW_DVD9_WIN_ENT_10_1703.1_64BIT_English_MLF_X21-47750.ISO).
I found the same information as Hannah posted above just now but I've yet to try it myself and my symptoms were slightly different in any case. I'll likely forgo the batch file option though in favour of mounting the WIM and removing the content.
The primary issue we've observed isn't with Edge hanging, but rather not handling file downloads correctly. Using the F12 developer tools, we can see the MIME types in the reponse headers are coming through correctly, however, the app insists on treating the resulting file consistently as a TXT file and replaces the final period in the filename (which would normally denote the extension) with an underscore. For example ".msi" becomes "_msi". IE11 doesn't have this issue: it's strictly limited to Edge after being sysprep'd while using copyprofile.
09-15-2017 08:22 AM
Just a quick follow-up to provide some confirmation and clarification on the solution referenced by Hannah.
Firstly and most importantly, removing the two directories and file mentioned above resolved the faulty download behaviour.
Secondly - and this is only relevant if you're using vanilla WDS and looking to remove these folders and file from the WIM, you need to consider where you're using the CopyProfile=true directive. As we are using it in the WDS answer file, it meant that those same directories and file actually needed to be removed from the \Users\Administrator profile, not the \Users\Default profile.
In any case, this workaround has got the August 1703.1 build back into usable territory. Fingers crossed it's sorted out in the next build and ISO.
04-20-2018 10:54 AM
06-22-2018 03:53 PM
12-17-2018 12:13 PM
Is it possible to set up the admin profile with all the settings (desktop wallpaper, settings, etc.) then exporting and importing into the ntuser.dat default?
10-22-2019 05:32 AM
How did you get the command to run. Are you able to add this to the unattended answer file from WDS?@Hannah Walters
10-22-2019 08:43 AM - edited 10-22-2019 08:47 AM
I was able to get CopyProfile working the way I wanted in Windows 10 (including the latest Win10 Enterprise v1903) with the following steps...
1. Manually did a clean install of Windows 10 (as a VM) and only used the local account that was initially created during install to configure the OS.
2. Using this account, I applied updates, installed and configured apps, and configured Win 10 (such as settings, background color, desktop icons, etc) the way I wanted it to look for all future domain users who would eventually log into computers running this image.
3. Once finished configuring, I then sysprep the system using one unattend.xml file that contains basic settings such as language and locale, specialize settings for domain join and product key, oobe settings, etc.
4. After capturing the image and adding it to my WDS server as an install image, I then have a second unattend.xml file that I apply to the properties of the image under the Unattend File checkbox "Allow image to install in unattended mode". In this second file I have many of the same settings as the first file, including the CopyProfile setting. It's this second unattend file that performs the Copy Profile at imaging time, saving all of my setup work done from the local account into the default profile.
I'm currently not deleting those webcache files using the SetupComplete.cmd as described by Hannah, although that might still be a good option to include, but so far the Copy Profile has been working for me using those above steps. I've also been building my image in a VM for the last couple of years, as the ability to create multiple snapshots and revert back to correct any mistakes or make changes has proven to be extremely useful.
Hope this helps.