Autocheck Error After Sysprep
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business
Autochk Program Not Found Skipping Autocheck Fix
Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users autochk not found Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top sysprep'd Server 2008 R2 VMware autocheck BSODs up vote 0 down vote favorite I'm trying to set up a template Server 2k8 R2 (Standard) VM in our VMware ESXi environment, we'll need to deploy a whole lot of them and I want to (a) streamline and (b) standardise the server build process. Originally I built a sysprep answer file using WAIK and the Windows System Image Manager - once I'd run sysprep using this, restarting the machine resulted in a "autochk.exe not found - skipping autocheck" message, followed almost immediately by a BSOD. Rebooting just resulted in the same thing. I first assumed it was my answer file, but have now checked this on a physical machine and it works fine. I've reinstalled the OS on the machine (and NOTHING else), and run sysprep.exe (ticking Generalize) - this produces exactly the same result. I've also attempted to use the Customisation Wizard built in to VMware - again, the same autocheck message and BSOD is the result. Any ideas? Let me know any further information I need to provide... windows-server-2008-r2 vmware-esxi sysprep share|improve this question asked Jun 29 '11 at 6:29 slag 58129 What exact version of ESXi are you using and how (again as much detail as possible) is the VM defined? –Chopper3 Jun 29 '11 at 7:53 Thanks Chopper, –slag Jun 29 '11 at 22:12 Grr, shouldn't have pressed [Enter]! Using ESXi 4.1 381591 (multiple hosts clustered) & VSphere 4.1 build 345043. VM has 4GB RAM, single CPU, 40GB SCSI disk, guest OS is configured as Microsoft Windows Server 2008 R2 (64-bit). Have since discovered that others have successfully used the Guest Customisation Wizard in this environment on the same server version. Must be something amiss in my VM configuration? –slag Jun 29 '11 at 22:28 I've done the same thing, there is a prob
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 01 Oct 2016 17:42:28 GMT by s_hv987 (squid/3.5.20)
restart during 'sysprep' phase: "Windows could not finish configuring the system. To attempt to resume configuration, restart the computer". When you press 'OK', Windows restart but the same error appears again http://www.wintips.org/how-to-fix-windows-could-not-finish-configuring-the-system-error-after-running-sysprep/ without any details. After some research on the Internet I found that this error message occurs with Windows 7 and Windows Server 2008 R2 operating systems if the original operating system contains a registry key that is larger than 8 kilobytes (KB). A Hotfix for this problem is available from Microsoft here and must be applied before executing the 'sysprep' command. The hotfix is already included on Windows 7 not found SP1 systems. I write this article, because - in my case - I had not applied the available hotfix before "syspreping" the VM machine, but also because I discovered that the "Windows could not finish configuring the system" error can also occur in a clean install of Windows 7 OS. How to resolve the "Windows could not finish configuring the system" error. When the "Windows autocheck error after could not finish configuring the system" appears on your screen: 1. Hold down the SHIFT key and press F10 (SHIFT + F10). 2. At command prompt type: cd oobe (& press Enter) 3. Then type: msoobe (& press Enter) 4. At 'Set Up Windows' first screen, choose your Country/ Region, Time and currency & Keyboard layout settings & press Next. 5. Type a Username and a Computer Name & press Next. 6. Type a password (if you want) and press Next. 7. Accept the License Terms & Press Next. 8. Select how you want Windows to protect your computer. (e.g. "Use recommended settings") 9. Set the Time and Date settings & press Next. 10. Now wait until Windows finalizes your settings. 11. Finally Restart your computer. * * If after pressing Restart nothing happens, then close all open windows or perform a cold Shutdown by pressing the Power key for several seconds. Now Windows should boot normally. You 're done!
If you want to stay constantly protected from malware threats, existing and future ones, we recommend that you install Malwarebytes Anti-Malware PRO by clicking below (we do earn a commision from sales g