none
Sysprep Error 0x0f0043

    Question

  • While trying to run sysprep for a Windows 10 Enterprise 2016 LTSB image I keep getting this error that returns 0x0f0043. Here's the setupact.txt log:

    2017-04-19 11:02:40, Info                  SYSPRP MSS: MSSrch_SysPrep_Cleanup _DisableService returned successfully.
    2017-04-19 11:02:40, Info                  SYSPRP MSS: MSSrch_SysPrep_Cleanup _CreateBlockingRegKey returned successfully.
    2017-04-19 11:02:40, Info                  SYSPRP MSS: Stopping service WSearch and its dependents.
    2017-04-19 11:02:40, Info                  SYSPRP MSS: Service WSearch has no active dependents.
    2017-04-19 11:02:40, Info                  SYSPRP MSS: Stopping service WSearch.
    2017-04-19 11:02:40, Info                  SYSPRP MSS: _StopService status checking loop 0 round, QueryServiceStatus return TRUE, the status is 0x3
    2017-04-19 11:02:41, Info                  SYSPRP MSS: _StopService status checking loop 1 round, QueryServiceStatus return TRUE, the status is 0x1
    2017-04-19 11:06:45, Info                  SYSPRP ========================================================
    2017-04-19 11:06:45, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2017-04-19 11:06:45, Info                  SYSPRP ========================================================
    2017-04-19 11:06:45, Info       [0x0f004d] SYSPRP The time is now 2017-04-19 11:06:45
    2017-04-19 11:06:45, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\system32\sysprep\Panther
    2017-04-19 11:06:45, Info       [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine
    2017-04-19 11:06:45, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\system32\sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2017-04-19 11:06:45, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'REBOOT'
    2017-04-19 11:06:45, Info       [0x0f003d] SYSPRP WinMain:Displaying dialog box for user to choose sysprep mode...
    2017-04-19 11:16:34, Error      [0x0f0043] SYSPRP WinMain:The sysprep dialog box returned FALSE
    2017-04-19 11:16:34, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2017-04-19 11:16:34, Info       [0x0f004d] SYSPRP The time is now 2017-04-19 11:16:34
    2017-04-19 11:18:31, Info                  SYSPRP MSS: MSSrch_SysPrep_Cleanup _DisableService returned successfully.
    2017-04-19 11:18:31, Info                  SYSPRP MSS: MSSrch_SysPrep_Cleanup _CreateBlockingRegKey returned successfully.
    2017-04-19 11:18:31, Info                  SYSPRP MSS: Stopping service WSearch and its dependents.
    2017-04-19 11:18:31, Info                  SYSPRP MSS: Service WSearch has no active dependents.
    2017-04-19 11:18:31, Info                  SYSPRP MSS: Stopping service WSearch.
    2017-04-19 11:18:31, Info                  SYSPRP MSS: _StopService status checking loop 0 round, QueryServiceStatus return TRUE, the status is 0x3
    2017-04-19 11:18:32, Info                  SYSPRP MSS: _StopService status checking loop 1 round, QueryServiceStatus return TRUE, the status is 0x1

    So far I have tried running a registry cleanup with CCleaner. That didn't work. I have heard commonly that sysprep won't work on an "upgraded" install of Windows, but this shouldn't be the case because I performed a clean install. Any ideas?

    Thanks in advance!

    Wednesday, April 19, 2017 5:41 PM

Answers

  • Well, I tried everything and nothing seems to work. It seems like there's just something really wrong with the image that maybe happened as I installed all the software on this image, and it has A LOT of software. I'm just going to save the image and try just sysprepping a new one. I can always go back to the old one if all else fails. Thanks for your help!
    Thursday, April 27, 2017 7:49 PM

All replies

  • Hi nufsty,

    Are there any error messages recoreded in the Event Viewer(Windows Logs\Applications, System)?

    Before we do the sysprep, please ensure the machine is up to date.
    Open an administrator command line and run "sfc /scannow" or "dism /online /cleanup-image /restorehealth" to check the health of system files.

    Sysprep in a clean boot environment.
    How to perform a clean boot in Windows
    https://support.microsoft.com/en-sg/help/929135/how-to-perform-a-clean-boot-in-windows

    To troubleshoot the issue deeply, please upload the setupact.log to OneDrive and paste the link here.
    Best regards

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, April 20, 2017 2:32 AM
    Moderator
  • Thanks for the response!



    In the Application log, there are multiple instances of 4 consecutive error from "SideBySide":

    "Activation context generation failed for "C:\Program Files (x86)\National Instruments\DIAdem 2015\DIAdemStart.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.953_none_89c2555adb023171.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.953_none_42151e83c686086b.manifest."



    In the System log, there are 2 errors from "Service Control Manager" and 1 from "volmgr":

    "The MSSQL$TEW_SQLEXPRESS service failed to start due to the following error: 
    The service did not respond to the start or control request in a timely fashion."

    "Crash dump initialization failed!"



    sfc /scannow did not find any integrity violations.



    dism ran with no errors.



    When running sysprep in a clean boot environment I got the same errors.



    I can't post a link to the setupact.log yet because I guess Tech Net needs time to verify my email before it will let me post links but here is what the new log says:



    2017-04-21 13:43:22, Info                  SYSPRP MSS: MSSrch_SysPrep_Cleanup _DisableService returned successfully.
    2017-04-21 13:43:22, Info                  SYSPRP MSS: MSSrch_SysPrep_Cleanup _CreateBlockingRegKey returned successfully.
    2017-04-21 13:43:22, Info                  SYSPRP MSS: Stopping service WSearch and its dependents.
    2017-04-21 13:43:22, Info                  SYSPRP MSS: Service WSearch has no active dependents.
    2017-04-21 13:43:22, Info                  SYSPRP MSS: Stopping service WSearch.
    2017-04-21 13:43:22, Info                  SYSPRP MSS: _StopService status checking loop 0 round, QueryServiceStatus return TRUE, the status is 0x3
    2017-04-21 13:43:23, Info                  SYSPRP MSS: _StopService status checking loop 1 round, QueryServiceStatus return TRUE, the status is 0x1
    2017-04-21 13:46:37, Info                  SYSPRP ========================================================
    2017-04-21 13:46:37, Info                  SYSPRP ===          Beginning of a new sysprep run          ===
    2017-04-21 13:46:37, Info                  SYSPRP ========================================================
    2017-04-21 13:46:37, Info       [0x0f004d] SYSPRP The time is now 2017-04-21 13:46:37
    2017-04-21 13:46:37, Info       [0x0f004e] SYSPRP Initialized SysPrep log at C:\Windows\system32\sysprep\Panther
    2017-04-21 13:46:37, Info       [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine
    2017-04-21 13:46:37, Info       [0x0f007e] SYSPRP FCreateTagFile:Tag file C:\Windows\system32\sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
    2017-04-21 13:46:37, Info       [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'REBOOT'
    2017-04-21 13:46:37, Info       [0x0f003d] SYSPRP WinMain:Displaying dialog box for user to choose sysprep mode...
    2017-04-21 13:56:02, Error      [0x0f0043] SYSPRP WinMain:The sysprep dialog box returned FALSE
    2017-04-21 13:56:02, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
    2017-04-21 13:56:02, Info       [0x0f004d] SYSPRP The time is now 2017-04-21 13:56:02
    2017-04-21 13:57:05, Info                  SYSPRP MSS: MSSrch_SysPrep_Cleanup _DisableService returned successfully.
    2017-04-21 13:57:05, Info                  SYSPRP MSS: MSSrch_SysPrep_Cleanup _CreateBlockingRegKey returned successfully.
    2017-04-21 13:57:05, Info                  SYSPRP MSS: Stopping service WSearch and its dependents.
    2017-04-21 13:57:05, Info                  SYSPRP MSS: Service WSearch has no active dependents.
    2017-04-21 13:57:05, Info                  SYSPRP MSS: Stopping service WSearch.
    2017-04-21 13:57:05, Info                  SYSPRP MSS: _StopService status checking loop 0 round, QueryServiceStatus return TRUE, the status is 0x3
    2017-04-21 13:57:06, Info                  SYSPRP MSS: _StopService status checking loop 1 round, QueryServiceStatus return TRUE, the status is 0x1




    Thanks for the help!
    Monday, April 24, 2017 4:39 PM
  • Actually, here's the setupact.log:

    https://1drv.ms/u/s!AqfLdOpWqeP4gxboR2_UuoXcstTr

    Monday, April 24, 2017 4:40 PM
  • Hi nufsty,

    How did you perform the sysprep?
    First of all, please ensure the machine is up to date.

    Please run the "sysprep.exe" tool manually in C:\Windows\System32\Sysprep, ensure you have chosen the "Generalize" option. Try to sysprep in safe mode.

    Best regards


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    Tuesday, April 25, 2017 7:55 AM
    Moderator
  • Well, I tried everything and nothing seems to work. It seems like there's just something really wrong with the image that maybe happened as I installed all the software on this image, and it has A LOT of software. I'm just going to save the image and try just sysprepping a new one. I can always go back to the old one if all else fails. Thanks for your help!
    Thursday, April 27, 2017 7:49 PM