Using Ghost Solution Suite(GSS) 3.x to boot a Syspreped client to automation results in the client machine receiving a windows boot manager error when the client is booted back to production.
Windows Boot Manager
Info: Windows failed to load because the system registry file is missing, or corrupt.
The automation agent was hard set to log to the c:\windows\temp folder. In automation some times windows PE will assign drive letters differently than in production. If the OS drive was assigned a letter other than C the automation agent would create a windows folder on a non OS drive. Upon trying to boot to production the incorrect windows folder might then be used and the error would be triggered.