The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Sysprep prepares a Windows 11 installation to become a reusable image. It removes computer-specific information, configures the next startup for Windows Out-of-Box Experience (OOBE), and shuts down the reference computer so you can capture its disk with DISM or another imaging tool.
Use it to create a standard Windows 11 image for multiple PCs or to prepare a virtual machine image. Do not use Sysprep to reconfigure an already deployed Windows installation. Microsoft requires /generalize before moving or copying an installation to another PC, even if the computers have identical hardware. See Microsoft’s Sysprep command-line options.
Before you run Sysprep
Sysprep is installed with Windows 11. Run the version included in the Windows installation you are preparing, from an administrator account. The executable is %WINDIR%\System32\Sysprep\Sysprep.exe.
Prepare the reference PC as follows:
- Install Windows 11 on the reference computer.
- Enter Audit mode before customizing the image.
- Install desktop applications, drivers, updates, and settings that should be part of the image.
- Do not install or update Microsoft Store apps through the Microsoft Store while building the image.
- Run Sysprep with /generalize /oobe /shutdown.
- After shutdown, boot Windows PE or other capture media and create the image.
Generalization is required even when the source and destination computers have identical hardware. It removes the computer SID, event logs, restore points, and other unique configuration data. Windows uninstalls configured Plug and Play devices during generalization but keeps their driver files, so it can detect destination hardware and install the appropriate drivers. See Microsoft’s generalization guidance.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Start Windows 11 in Audit mode
Audit mode lets you customize Windows before the normal first-run setup appears.
- Start the Windows 11 reference installation.
- When the Windows Out-of-Box Experience screen appears, press Ctrl+Shift+F3.
- Windows restarts and signs in with the built-in Administrator account.
- Use the System Preparation Tool window that opens, or close it and run Sysprep later from an elevated Command Prompt.
Avoid configuring a password-protected screen saver in Audit mode. The built-in Administrator account is disabled during a later configuration pass, which can prevent you from unlocking the desktop. The account is removed during generalization. See Microsoft’s instructions for starting Windows in Audit mode or OOBE.
Recommended command-line method
Open Windows Terminal (Admin) or Command Prompt (Admin), then run:
%WINDIR%\System32\Sysprep\Sysprep.exe /generalize /oobe /shutdown
If the current directory is already C:\Windows\System32\Sysprep, this equivalent command works:
Sysprep /generalize /oobe /shutdown
Each switch has a specific purpose:
| Switch | Purpose |
|---|---|
| /generalize | Removes computer-specific information so the installation can be moved or copied to another computer. |
| /oobe | Configures the next boot to start Windows Out-of-Box Experience. |
| /shutdown | Turns off the reference PC when Sysprep finishes. |
Do not restart the reference PC after Sysprep shuts it down. Boot it into Windows PE or another imaging environment and capture the prepared Windows partition. When the image is deployed, Windows runs the specialize configuration pass, detects the target configuration, and then displays OOBE.
Using the Sysprep window
The graphical interface still works, but Microsoft has deprecated it and recommends command-line Sysprep for new deployment workflows. See Microsoft’s Sysprep process overview.
- Press Win+R, type %WINDIR%\System32\Sysprep\Sysprep.exe, and press Enter.
- Under System Cleanup Action, select Enter System Out-of-Box Experience (OOBE).
- Select the Generalize checkbox.
- Under Shutdown Options, select Shutdown.
- Click OK.
The GUI selections correspond to /generalize /oobe /shutdown. Wait for the computer to power off before capturing its disk.
Sysprep with an answer file
An answer file automates Sysprep and Windows Setup settings. Run Sysprep with the file specified explicitly:
%WINDIR%\System32\Sysprep\Sysprep.exe /generalize /oobe /shutdown /unattend:C:\Path\Unattend.xml
Rank #2
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
Using /unattend: matters when a particular answer file must be used. Windows Setup can cache an earlier answer file, and that cached file may take precedence over one simply copied into the Sysprep folder. See Microsoft’s guidance on using answer files with Sysprep.
For identical hardware where you need installed device configurations to persist, an answer file can set Microsoft-Windows-PnPSysprep to <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>. The default is false. Do not enable this setting for a general-purpose image intended for different hardware; allowing Windows to redetect the destination hardware is normally safer.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Preparing a VHD for a virtual machine
For a VHD that will be deployed on the same type of virtual machine or hypervisor, you can use:
Sysprep /generalize /oobe /mode:vm
/mode:vm is valid only when Sysprep runs inside a virtual machine. The resulting VHD must use the same type of VM or hypervisor and a matching hardware profile. It is not a method for preparing one VHD for arbitrary physical PCs or different virtual hardware. See Microsoft’s command-line options.
Fixing common Sysprep failures
Microsoft Store or AppX package error
A common failure occurs when a Microsoft Store app was installed or updated for one user but was not provisioned for every user. The Sysprep log may report that a package was installed for a user but not provisioned for all users.
The supported way to avoid this problem is not to install or update Microsoft Store apps through the Store while preparing the reference image. Use offline provisioning or sideloading when appropriate, or let users update Store apps after deployment.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteDo not assume every built-in Windows app must be removed. The documented failure condition concerns a package registered for one user without being provisioned for all users.
Find the relevant logs
Review setupact.log and related files in these locations:
| Process | Log location |
|---|---|
| Generalize and Sysprep | %WINDIR%\System32\Sysprep\Panther |
| Specialize | %WINDIR%\Panther |
| OOBE and unattended Setup | %WINDIR%\Panther\Unattendgc |
Look near the end of setupact.log for the first package, driver, answer-file, or configuration error. Later messages often only describe the resulting failure. Microsoft’s Sysprep process overview documents these log locations.
Important limitations and edge cases
- Do not run it as SYSTEM. Sysprep cannot run under the System account, including through Task Scheduler or PsExec configured to use SYSTEM.
- Domain membership: Sysprep is intended for a workgroup reference computer. If the PC is domain-joined, Sysprep removes it from the domain. Domain Group Policy settings, including password requirements, can remain in effect.
- Encrypted files: Sysprep can make encrypted files or folders on an NTFS partition completely unreadable and unrecoverable. Back them up or remove them before generalizing.
- One instance only: Only one Sysprep process can run at a time.
- Run-count limit: Windows 11 supports up to 1,001 Sysprep runs on one image. After the 1,001st run, recreate the image. The historical SkipRearm advice is not required for current deployment guidance when using a retail or volume-license key.
- Upgrade installations: Microsoft supports preparing an installation upgraded to Windows 10 or Windows 11, but not using Sysprep to reconfigure an already deployed Windows installation.
Microsoft states that if Sysprep encounters an error, it cannot be run again on that same Windows image; the image must first be redeployed. Keep a clean reference snapshot or backup and resolve Store-app, driver, domain, encryption, and answer-file issues before the final run. See Microsoft’s Sysprep overview.
Recommended Free Tools
Rank #3
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
Useful command variations
| Command | Use |
|---|---|
| Sysprep /audit | Reboots the installation into Audit mode. |
| Sysprep /generalize /shutdown | Generalizes the installation and shuts down without explicitly selecting OOBE. |
| Sysprep /oobe /shutdown | Sets the next startup to OOBE and shuts down; used in specific workflows after an image has already been generalized. |
| Sysprep /audit /generalize /shutdown | Generalizes the installation and configures the next boot for Audit mode. |
For a normal Windows 11 image, use Sysprep /generalize /oobe /shutdown, capture the powered-off installation, and deploy that captured image rather than booting the reference PC again.
FAQ
Do I need Sysprep if the target PCs have identical hardware?
Yes. Microsoft requires /generalize before moving or copying a Windows installation to another PC, even when the hardware is identical.
Can I run Sysprep on a normal Windows 11 PC?
Sysprep is intended for preparing an image, not reconfiguring an already deployed installation for continued use. Build and customize a reference installation, then generalize and capture it.
What is the correct Windows 11 Sysprep command?
For a standard reference image, run %WINDIR%\System32\Sysprep\Sysprep.exe /generalize /oobe /shutdown from an elevated administrator Command Prompt or Windows Terminal.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why does Sysprep fail because of a Store app?
The app was usually installed or updated for the current user without being provisioned for all users. Avoid Microsoft Store installations and updates while building the image, then inspect %WINDIR%\System32\Sysprep\Panther for the package name.
Should I remove all built-in Windows 11 apps before Sysprep?
No. The documented problem is a package installed for one user but not provisioned for all users; removing every built-in app is not generally required.
What happens after Sysprep shuts down Windows?
Boot Windows PE or other capture media and capture the Windows partition. On the first boot after deployment, Windows runs its specialize pass and then presents OOBE.
Can I use /mode:vm for a VHD deployed anywhere?
No. /mode:vm must be run inside a VM, and the resulting VHD requires the same type of VM or hypervisor and a matching hardware profile.
The Bottom Line
For a standard Windows 11 reference image, customize the installation in Audit mode, avoid Microsoft Store app changes, then run:
%WINDIR%\System32\Sysprep\Sysprep.exe /generalize /oobe /shutdown
Once the PC powers off, capture it from Windows PE. Keep a clean backup of the reference installation because a Sysprep failure requires redeploying the image before trying again.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
