locked
sysprep fatal error, MDT2010, Windows 7 RRS feed

  • Question

  • Hi Guys

    right here goes with the info, i have made a basic image with windows 7 and office, now i need to make my staff and or student images so i bring the image down, install app's then sysprep the image, capture the image using mdt2010 all is fine, image comes back and because i have been having issues i try to sysprep the image again......but it comes back with fatal error so basicly if i want to use this image again for customizing its useless.

    i have killed the wmpnetwk as suggested in other posts

    i have uninstalled the sound driver as suggested in other posts, but to no avail

    here is the log from setupact: "had to cut alot of this out as the post went over 6000 letters"

    "2010-05-04 13:56:53, Info                  SYSPRP ========================================================
    2010-05-04 13:56:53, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2010-05-04 13:56:53, Info                  SYSPRP ========================================================
    2010-05-04 13:59:42, Info                  SYSPRP SPPNP: Reflected all boot critical driver packages (101806 ms).
    2010-05-04 13:59:42, Error                 SYSPRP SPPNP: Error 0x2 setting SDDL on driver file C:\Windows\system32\igfxpph.dll!
    2010-05-04 13:59:42, Error                 SYSPRP SPPNP: Error 0x2 enumerating locked down files!
    2010-05-04 13:59:42, Info                  SYSPRP SPPNP: Sysprep_Generalize_Pnp: Exit
    2010-05-04 13:59:42, Info       [0x0f0081] SYSPRP LaunchDll:Successfully executed 'C:\Windows\System32\sppnp.dll,Sysprep_Generalize_Pnp' without error
    2010-05-04 13:59:42, Info       [0x0f008b] SYSPRP RunRegistryDlls:Found entrypoint in registry at SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SysPrep\Generalize\{82468857-ad9b-1a37-533f-7db889fff253}; will try to launch 'C:\Windows\System32\slc.dll,SLReArmWindows'
    2010-05-04 13:59:42, Info       [0x0f0080] SYSPRP LaunchDll:Found 'C:\Windows\System32\slc.dll,SLReArmWindows'; executing it
    2010-05-04 13:59:42, Error      [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\System32\slc.dll,SLReArmWindows', returned error code -1073425657
    2010-05-04 13:59:42, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -1073425657
    2010-05-04 13:59:42, Error      [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize internal providers; hr = 0xc004d307
    2010-05-04 14:00:04, Info       [0x0f004c] SYSPRP WaitThread:Exiting spawned waiting thread
    2010-05-04 14:00:04, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2010-05-04 14:00:04, Info       [0x0f004d] SYSPRP The time is now 2010-05-04 14:00:04"

    now heres the log from setuperr:

    "2010-05-04 13:59:42, Error                 SYSPRP SPPNP: Error 0x2 setting SDDL on driver file C:\Windows\system32\igfxpph.dll!
    2010-05-04 13:59:42, Error                 SYSPRP SPPNP: Error 0x2 enumerating locked down files!
    2010-05-04 13:59:42, Error      [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\System32\slc.dll,SLReArmWindows', returned error code -1073425657
    2010-05-04 13:59:42, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -1073425657
    2010-05-04 13:59:42, Error      [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize internal providers; hr = 0xc004d307"

    any advise would be very welcome, trying to decide if i should pull the plug on going to windows 7 for the college this summer.

    Regards

    Dave

    Tuesday, May 4, 2010 1:28 PM

Answers

  • i think i have solved the issue

    Settings pass="generalize">
            <component name="Microsoft-Windows-Security-SPP" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SkipRearm>1</SkipRearm>

    i looked at the help in the image manager it pointed towards if you have a 1 in it halts it so it doesnt count anymore syspreps but once you are happy with that image and more more syspreps needed change back to 0

    just sent 2 images down and tried to sysprep soon as they came down and they both work with no errors....... so maybe 2 options do it with the apps or do it with the above code in.

    Dave

    • Marked as answer by dave-loucoll Wednesday, May 5, 2010 12:32 AM
    Wednesday, May 5, 2010 12:30 AM

All replies

  • If you are using MDT, then what you really should be doing is making a Task Sequence that starts from scratch and builds the entire OS from the beginning all the way to the creation of a WIM file in an unattended fashion each and every time.

    That way you do not run into this error that you are getting due to the fact that you are running sysprep too many times. (http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/9f327882-dcc0-4719-ace1-66ec058a224f)

    If you always start fresh, you'll never have to worry about this problem...and you'll deploy systems that are less prone to have things in them that you don't want to be there...  (Like apps installed and then uninstalled and upgraded, etc).

    So, my advice is to re-examine the way you use MDT to build your OS images and go about it differently so that you can start from scratch each time.  Once you have it automated all you ever have to do is start it...and let it run.  It might be more work to setup initially, but in the long run it is really worth it.

     

     


    Mike N.
    Tuesday, May 4, 2010 2:24 PM
  • Hi Mike

    thanks for the reply

    the way ive done it and done it again since posting, is get the wim from the windows 7 dvd inport it made a task sequence did all the changed needed to make it a T image so it could be staff or student.

    redeployed the T image made changes to make it staff apps etc imaged it then made new task sequence etc came down but i'm guessing it had a fatal error because administrator wasnt enabled, and when i went to sysprep to check it came up with the fatal error.

    in my unattend.xml files in the control part of the deploymentshare i have added the spp and set the rearm to 0 so i throught this would have sorted this out?

    are you suggesting i make deployable apps instead then add them to a basic image?

    is there no way round the syspreping?

    Regards

    Dave

    Tuesday, May 4, 2010 10:44 PM
  • i think i have solved the issue

    Settings pass="generalize">
            <component name="Microsoft-Windows-Security-SPP" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SkipRearm>1</SkipRearm>

    i looked at the help in the image manager it pointed towards if you have a 1 in it halts it so it doesnt count anymore syspreps but once you are happy with that image and more more syspreps needed change back to 0

    just sent 2 images down and tried to sysprep soon as they came down and they both work with no errors....... so maybe 2 options do it with the apps or do it with the above code in.

    Dave

    • Marked as answer by dave-loucoll Wednesday, May 5, 2010 12:32 AM
    Wednesday, May 5, 2010 12:30 AM