Assume that you install Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 on a VMware virtual machine. However, if you run the Sysprep command just after you start the computer, you receive an error message that resembles the following:
Sysprep error Windows 2008 r2 and Windows 7
[0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\system32\msdtcprx.dll,SysPrepDtcCleanup', returned error code -2147024864[gle=0x000000b7][0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2147024864[gle=0x000000b7][0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80070020[gle=0x000000b7]
2012-02-02 07:29:14, Error [shsetup] CleanupAdministratorPassword: NetUserSetInfo(1003) failed (0x800708c5) [gle=0x000003e5]2012-02-02 07:30:39, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\System32\slc.dll,SLReArmWindows', returned error code -10734256572012-02-02 07:30:39, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -10734256572012-02-02 07:30:39, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize internal providers; hr = 0xc004d3072012-05-04 18:09:46, Error [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 312012-05-04 18:09:46, Error [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f2012-05-04 18:11:17, Error [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 312012-05-04 18:11:17, Error [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f2012-05-04 18:21:48, Error [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 312012-05-04 18:21:48, Error [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f
Has anyone ever had any luck with using something OTHER THAN sysprep to generate a new SID for Windows 7 / Server 2008 or newer machines? I know that there used to be something called NewSID but evidently that doesn't work anymore with newer OS'.
If you look at the sysprep log in the Panther folder (for whatever reason, Windows creates a Panther folder when you run sysprep), it actually lists the particular dll that it is having trouble loading during the process. The location of the folder is c:\Windows\System32\sysprep\Panther, and the log file is setupact.log. Here is the error message from the log:
2015-07-27 13:07:15, Error [0x0f0085] SYSPRP LaunchDll:Could not load DLL C:\Program Files\Microsoft Security Client\MSESysprep.dll[gle=0x0000007e]2015-07-27 13:07:15, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 126[gle=0x0000007e]
I did some research on that error, and it is caused by a piece of software not uninstalling cleanly and leaving some registry hooks that is tripping up sysprep. You have to use regedit to delete the entry to that particular piece of software in the cleanup folder, located here:
If you try to run Sysprep on Windows, more than three (3) times, then you will receive the following error message "A fatal error occurred while trying to Sysprep the machine" and the following explanation message is displayed inside the sysprep error log file (setuperr.log): "Date Time, Error [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 31".
Microsoft says that this error message "is designed to prevent the deployment of a corrupted image", but this is not true, because the error was caused when you reached the three rearm limit (you cannot run sysprep more than three times on the same machine).
I did all the steps up until, "part one fixing boot filenon MBR" (step 1)I cant find any file that says window in any disk. Does this means my windows really did gone missing?How do did it happen and how do i fix this?
Thanks, after trying everything this worked for me.The only extra thing I needed to do after following this tutorial to get it working was to disable windows media player through cmd (admin privs) with the command 'net stop WMPNetworkSvc'.
Hi James, the link to an older article of yours, you mention above ( -to-sysprep-windows-server-2008/2007/07/11/How-To-Sysprep-Windows) is broken. Obviously, it must be -To-Sysprep-Windows; hope you can fix it easily.
dear james, i need to ask you concerning my issue which is , i made installation for windows server 2008 on hp proliant BL 460 blades, but the problem i used the cloning method but i didnt take the CID for each blade which can and for sure affect on the active directory that will run soon on these blades, so what shall i do concerning that?i must run sysprep on each one or also by cloning method? please i need your help as soon as possible.
This error is caused by the Windows Media Player Network Sharing Service. There is a bug in Sysprep that will prevent it from running to completion if the Windows Media PLayer Network Sharing Service is running. To disable this service: 1. Click Start, type services.msc in the search box and press enter.2. Scroll down to the Windows Media PLayer Network Sharing Service and set it to disabled.3. Reboot the machine at try to run sysprep again.
After it finished the windows restart and it could be reboot. it says Windows prepared for the first time with error installation can not complete please restart and try againafter 2-3 times i have the same but without error but keeping restart without reboot 2ff7e9595c
留言