STOP Error Message after deploying Sysprep Images
How can I fix STOP 0x7B Error Messages after deploying Sysprep Images?
When you prepare an image of a machine with the sysprep tool, the machine resets or you get the stop 0x7B error on the deployed machines even if you used the pnp switch.
The message is:
Say Goodbye to Traditional PC Lifecycle Management
Traditional IT tools, including Microsoft SCCM, Ghost Solution Suite, and KACE, often require considerable custom configurations by T3 technicians (an expensive and often elusive IT resource) to enable management of a hybrid onsite + remote workforce. In many cases, even with the best resources, organizations are finding that these on-premise tools simply cannot support remote endpoints consistently and reliably due to infrastructure limitations.
STOP 0x0000007B INACCESSABLE_BOOT_DEVICE
This is caused because of the difference between the IDE/SCSI controller at the master machine and the target machine. (Note that different chipsets have different controllers).
- Prepare the master machine: install software, updates, and hardware drivers, configure user setting etc.
- Using "Setup Manager", create a sysprep answer file and save it to %systemdrive%’sysprep folder as sysprep.inf.
- Copy the setupcl.exe and sysprep.exe to the same folder.
- Open the Sysprep.inf file and add these lines at the end of the file:
[Sysprep] BuildMassStorageSection=Yes [SysprepMassStorage]
Run sysprep.exe and mark the pnp and minisetup checkboxes and click on Reseal.
Note: You can also run sysprep.exe from the command prompt while using the correct switches.
The sysprep process will take longer than usual because of the new section that is being built.
This tip has been tested on Windows XP Pro, Windows 2000 Pro, Windows 2000 Server and Windows Server 2003, both on IDE and on SCSI Controllers.