Issues with Creating a Windows 11 Image Using Sysprep

0
27
Asked By TechieTurtle57 On

I'm facing a problem while trying to create a Windows 11 image for distribution using Clonezilla and Sysprep. I've installed all the necessary applications like Software Center, Office 365, and Teams, and I've made sure to push all Windows and BIOS updates. However, after running Sysprep to generalize the image, my machine enters a continuous loop, displaying a 'hi there' screen asking for preferences, followed by a 'why did my PC restart?' screen. Whenever I try to click next to reboot, it just goes back into the same loop. I've tried capturing the image with Clonezilla and restoring it on different machines, but I'm still encountering this issue. Can anyone help me understand what might be causing this?

3 Answers

Answered By ImageCreator77 On

I haven’t used Sysprep in a while, but it might be worth considering an alternative approach. Instead of capturing a static image, it's often more effective to create a task sequence for deploying software. When you capture an image, you're left with all the quirks and updates that have accumulated by the time you deploy it. Think of it like baking a cake in advance—it might be stale by the time you serve it. A task-sequence approach keeps everything fresh and ensures consistency.

Answered By SysPrepExpert42 On

This sounds like the classic Sysprep and Windows Store app loop. It usually occurs when certain built-in apps (like Teams, Store, or Edge) are provisioned or updated while Sysprep is in progress. Here are a few tips that might help:
- Make sure to remove or properly provision all store apps before running Sysprep. You can do this with commands like `Get-AppxPackage -AllUsers | Remove-AppxPackage` and `Remove-AppxProvisionedPackage`.
- Fully install updates and restart the system a couple of times before running Sysprep.
- Use `sysprep /generalize /oobe /shutdown` instead of restart.
- Check for any leftover pending updates or issues related to `Windows.old` that might be causing hang-ups.
- Avoid cloning immediately after Sysprep; it’s better to shut down cleanly first. Usually, the issue is more about Windows not liking something during the OOBE stage rather than anything wrong with Clonezilla itself.

ClonezillaFan22 -

I follow a similar process and rarely face issues with Windows 11. I use DISM instead of Clonezilla, and my deployments go smoothly.

TechieTurtle57 -

Yeah, Teams has been a nightmare for me too. Always seems to mess with Sysprep!

Answered By WindowsWizard33 On

Microsoft actually recommends using Autopilot for deployments instead of traditional imaging methods. They’ve phased out WDS. While you can still do flat imaging, it’s not the direction Microsoft is going anymore.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.