I'm trying to set up a Windows 11 image for new users that includes a specific start menu layout, saved in a file called start2.bin. My current method involves copying this file to the location: C:UsersDefaultAppDataLocalPackagesMicrosoft.Windows.StartMenuExperienceHost_cw5n1h2txyewyLocalState. Unfortunately, during testing, the start menu is regenerated on the first login, and the default layout appears instead of my custom one. I can confirm that the file exists in the default location but it doesn't seem to transfer to the users' profiles. Does anyone have any solutions or tips for getting this to work?
4 Answers
We do something similar, and it works without issues. We have a startup script through GPO that checks the profile on first boot and copies the start menu template if it isn't there. Make sure to run gpupdate /force without any user logged in, then reboot. This ensures the group policies are applied properly before the first login.
Why not use the PowerShell command 'Export-StartLayout' and manage it through GPO? They’ve fixed the issue with it reapplying settings at every login. I'm implementing it myself but haven't rolled it out yet since I'm still customizing my setup. Check out the documentation for Windows 11 layouts.
Have you tried placing the start2.bin file in the Roaming folder instead of the Local one? Sometimes Windows is a bit finicky about which AppData folder it reads configurations from. Give it a shot!
You might want to add an empty settings.dat file in the settings folder. It doesn’t need to have any content, it just has to exist there. For reference: C:UsersDefaultAppDataLocalPackagesMicrosoft.Windows.StartMenuExperienceHost_cw5n1h2txyewySettingssettings.dat.
Are you suggesting this stops it from copying on new profiles?
Not yet. I’m going to try that path: C:UsersDefaultAppDataRoamingPackagesMicrosoft.Windows.StartMenuExperienceHost_cw5n1h2txyewyLocalStatestart2.bin.