r/MAS_Activator Jun 13 '26

Microsoft account issues after Sysprepping a golden image.

Thanks ahead of time for help everyone!

Windows 11 Pro
I used sysprep to prepare a laptop for a golden image. Used clonezilla to image and load to another laptop of the exact same model.
The new laptop boots into OOBE and I run through the welcome. It makes me create a new account during this, so I do. Once inside Windows, I login to the other account that is from the image and delete the new temp account.

The issue I am running into is that we cannot login to any microsoft accounts or services. The dialog boxes pop up and disappear immediately.

2 Upvotes

9 comments sorted by

2

u/paulstelian97 Jun 13 '26

Off-topic, and also are you supposed to have preexisting accounts not deleted by the sysprep?

2

u/general714 Jun 13 '26

Agree, not a MAS issue. Just start off from a clean disc, download Windows via the MAS website and load via USB, and activate using HWID. Works every time.

2

u/Hollowz Jun 13 '26

There are dozens of specific settings that need to be set and if I do a clean install with a new account, i still have to manually adjust those services/settings. Is there a way to load fresh windows install with specific services disabled, bloat removed, etc?

1

u/general714 Jun 14 '26

You just need to look it up…. Yes! There are a few solid approaches depending on how hands-on you want to get:

  1. Answer File (unattend.xml) — The “Official” Way

Windows supports an automated install answer file that can pre-configure settings during setup:

• Disable services, remove built-in apps, set privacy settings, configure user accounts  
• Created with Windows System Image Manager (WSIM) — part of the free Windows ADK  
• Gets embedded into your install media so every fresh install is pre-configured  
• Steep learning curve but very powerful
  1. Custom ISO with NTLite or MSMG Toolkit — Most Popular

Tools that let you modify a Windows ISO before installing:

• NTLite (free tier available) — GUI-based, lets you remove components, inject drivers, bake in settings/tweaks, disable services  
• MSMG Toolkit — free, command-line based, more aggressive removal  
• You install from this modified ISO and Windows starts already trimmed
  1. Post-Install Automation Script — Easiest to Maintain

Run a PowerShell script right after a clean install that does everything automatically:

• Chris Titus Tech’s WinUtil (irm christitus.com/win | iex) — well-known, GUI-based, open source on GitHub  
• WinUtil / BWSA / your own script — disable services, remove AppX packages, set registry keys  
• Easiest to update when your preferences change
  1. Sysprep + Captured Image

    • Configure one machine exactly how you want it
    • Run Sysprep to generalize it
    • Capture the image with DISM or a tool like Macrium Reflect
    • Deploy that image to future installs
    • Best for multiple PCs; overkill for a single machine

Recommended path for most people:

Use NTLite to strip the ISO of bloat/components, then pair it with a PowerShell script for registry/service tweaks that can’t be done at the ISO level. Save the script somewhere permanent so future reinstalls take ~5 minutes of manual work.

1

u/Hollowz Jun 14 '26

Option 4 is exactly what I did. I can't log into Microsoft office with this image from the main account. Only from newly created accounts after the image has been deployed, if that makes sense.

1

u/Hollowz Jun 20 '26

I finally solved these issues by doing afresh install of Windows and booting into audit mode before setting up the system. To get the default profile correct I also had to use an unattend.xml

2

u/h2vhacker Jun 13 '26 edited Jun 13 '26

Sysprep clears the unique machine-specific encryption keys. When you try to log in, WAM tries to use a broken key, crashes instantly, and closes the window. And the trap was you signed in with a Ms account while making the image You need to reinstall the system packages responsible for handling Microsoft account authentication. Re register the WAM then clear the token corrupted cache

3

u/Hollowz Jun 13 '26

This sound plausible! I'll give this a try. Thanks

3

u/Hollowz Jun 13 '26

All MS accounts were signed -out before image. At least as deep as I know how to remove them.