I have been working on creating an image of Windows 7 x86 Professional and I have had an issue with Sysprepping the computer recently where it looks like the /generalize command isn't working. I'm using the K2000 client to push the captured image. When the image gets applied it acts as if the image isn't generalized and prompts me with the error of "Windows Setup could not configure Windows to run on this computer's hardware."

The command that I use is as follows:
sysprep /generalize /oobe /unattend:unattend.xml /shutdown

2 Comments   [ - ] Hide Comments


  • That doesn't necessarily mean generalize isn't working. Have you checked these scenarios? https://support.microsoft.com/en-us/kb/2466753
  • I have tried both methods from the webpage. I'm using K2000 to deploy the image, I am using the Driver Feed to install the drivers. I verified I have the drivers for Windows 7 x86. The HDD connection was ATA so I did change it to AHCI and tried to reimage the computer. I still ended up getting the error.
Please log in to comment

Answer this question or Comment on this question for clarity


After you get the error press Shift-F6 (or maybe it's Shift-F10) to open a command prompt. From there you can browse to c:\windows\panther and check the logs to find the source of the problem. 
Answered 11/10/2016 by: chucksteel
Red Belt

  • Which .log file should I be looking into? There are several of them.
    • I can't remember the names but one of them should include errors.
      • The files that are in the folder are:
        setupact.log - Can't open says currently in use.
        setuperr.log - Can't open says currently in use.
      • Hmm. I can normally access the setuperr.log file. How are you trying to open it? I normally use notepad.
      • I'm trying to access it through the CMD window. when I try to have CMD open it it tells me that it is in use by another program.
      • In the command window, when you are in the c:\windows\panther directory type:
        notepad setuperr.log
        Does it open the file?
      • Here is what the file contains:
        2016-11-10 10:37:08, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize', returned error code 5[gle=0x000003e5]
        2016-11-10 10:37:08, Error [0x060435] IBS Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x5
      • After some Google searching it looks like C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize errors are generally related to hardware compatibility errors. Have you tried restoring the image on other hardware? Also, when you changed the drive type from ATA to AHCI you may need to rebuild the image, not sure on that (I didn't see that comment previously).
      • I have changed the drive type from ATA to AHCI, I also did reimage the computer while it was set to AHCI. I still got the error. I haven't tried pushing the image to on other hardware because I can push the pre-sysprepped image back down to the computer and it will load fine, its only after it is syspreped that I start getting the error.
Please log in to comment