Forum Discussion
Windows 10 start menu problems and copyprofile
- You can still use CopyProfile, but it's not required if all you want is a custom start menu layout - you can import that using the PowerShell "Import-StartLayout" command prior to a user logging onto the system, then they will pick up that layout as default.
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\*.*
How did you get the command to run. Are you able to add this to the unattended answer file from WDS?Hannah Walters
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.- Thank you Luis for this information. I will give it a shot and report back.
- I proofed this method works!
However, you need to delete at Administrator profile instead of Default if you are using Audit mode (Ctrl-Shift-F3 traditional method).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?
- I've spent the last 10 hours trying to find out why our newest 1709 image build has been having issues with searching and some start menu functionality with domain accounts. I saw the tons of WebCache errors produced, but I hadn't made the connection mentally that it could be related to the CopyProfile function, since it worked fine with the 1703 build. This turns out to be the appropriate solution (besides MS not breaking this mess repeatedly), and I'm a little flustered I had to dig so deep to find the one person who managed to make sense of something MS has failed to figure out. Thanks a ton for this info. You rock!
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.
Cheers,
Lain
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.
Cheers,
Lain
