It’s a process I’ve done hundreds of times: wipe-and-load an existing device with a new Windows OS image, using USMT to capture documents and settings, migrating them forward to the new clean OS. It’s a process that’s worked well since the first time I tried it with Windows XP. So enter Windows 11 and the ADK for Windows 11, what can possibly go wrong?
As it turns out, the answer to that is simple: The new Start menu will be broken. SCANSTATE and LOADSTATE run fine, but when a user that previously had a user profile on the computer (hence has a new one that was recreated by LOADSTATE) signs in, you’ll see an error:
Well, at least it will fix itself if you sign out and back in again, right? Nope. It looks fine, but when you click the Start button you get the same error, which starts the cycle over again. Sometimes you’ll see a different look:
But that’s not really an improvement. The only real option appears to be deleting the user profile and then logging in to create a new one. Or just don’t use USMT in the first place…
Categories: Windows 11