Failed to reboot after sysprep (deploying windows 7 x32 image)

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Professional x32
       #1

    Failed to reboot after sysprep (deploying windows 7 x32 image)


    I have created a base image of Windows 7 x32 to deploy to same systems.

    After a sysprep, with drivers and programs installed. I capture the image using Clonezilla and reboot.

    Once reboot occurs I get "Setup is updating registry settings" followed by the error message "Windows could not configur " I have checked the disk partitions and it keeps moving the system_drv to disk letter C:, windows to D: and the recovery disk to E:

    I tried renaming those and had no luck.

    I have recovered the setup.etl of the image and found variations of this registry error.

    <Data Name="Message">(80000005): Failed to process reg key or one of its descendants: [\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData]</Data>

    All errors have same path with variations of endings.

    I think it may be a progam on the image that may becausing this but I have no idea on how to find that program.

    I have also attempted to use Startup Repair from the Windows 7 Installation Media. I have run it several times an no difference.

    It says it will repair the boot manager and cannot find the windows partition.

    Any help would be greatly appreciated.

    I can specify more details if need be.
      My Computer


  2. Posts : 11,408
    ME/XP/Vista/Win7
       #2

    If all systems are the same, no need for sysprep.
      My Computer


  3. Posts : 7
    Windows 7 Professional x32
    Thread Starter
       #3

    But if we are adding these computers to our domain, won't we run across software issues, such as using the SCCM?
      My Computer

  4.    #4

    Try using Acronis True Image premium cloning/imaging program which comes free if you have WD or Seagate HD's.

    Or use free Macrium Reflect or Paragon 11.

    Clonezilla is recommended by no one here that I've come across.
      My Computer


  5. Posts : 1,426
    7 Pro
       #5

    sysprep is required, however maybe not to the extent that you're using it. No need to change drivers/applications if the systems are the same, but you should be changing SIDs.

    Do you have a working image at the moment, or is this your first sysprep adventure?
      My Computer


  6. Posts : 7
    Windows 7 Professional x32
    Thread Starter
       #6

    I have a backup/recovery image made. I keep restoring it after my failed trials of fixing my issue. I have not been changing drivers, I have used the command in building my answer file for sysprep to restore/keep current drivers.
      My Computer


  7. Posts : 7
    Windows 7 Professional x32
    Thread Starter
       #7

    Also, I do have a working image that was deployed to 3 computers already. That image was somehow corrupted on my extrernal drive and lost. That is why I am starting over. I had this issue however in the past with the first image, that is why I am led to believe this issue may be caused by a specific program on this new image that may/ may not have been on the older one.
      My Computer

  8.    #8

    Did you read my post?

    Change imaging programs.
      My Computer


  9. Posts : 7
    Windows 7 Professional x32
    Thread Starter
       #9

    thanks greg. I am in the process of trying your solution. I was just answering brady's post
      My Computer

  10.    #10

    Wasn't sure you saw it. Hope it helps as SysPrep is pretty reliable so it must be the imaging program, especially since images have already been corrupted.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:06.
Find Us