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.
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-Deployments 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.
Hi there,
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.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.
Thanks!
