Windows 10: Problems after sysprep Windows 10 Pro v1803

Windows 10 Pro v1803
After running sysprep and rebooted i get " Windows could not finish configuring the system. To attempt to resume configuration, restart the computer" and obviously restarting did not fix the issue. So i pulled the log file from C:\windows\panther\setup.etl converted it to a csv file so i can read it, but i dont understand what is failing. Here is a couple of repeated failures in the log:

<Data Name="Message">(c0000022): Failed call to SclProcessObjectSecurity().</Data>
<Message>SclRegProcessKeyRecursiveByHandle@298 : (c0000022): Failed call to SclProcessObjectSecurity(). </Message>
<Data Name="Message">(c0000022): Failed to process reg key or one of its descendants: [\REGISTRY\USER\.DEFAULT\Software\SetID]</Data>
<Message>SclRegProcessKeyRecursiveByHandle@341 : (c0000022): Failed to process reg key or one of its descendants: [\REGISTRY\USER\.DEFAULT\Software\SetID] </Message>
<Data Name="Message">(c0000022): Failed to process reg key or one of its descendants: [\REGISTRY\USER\.DEFAULT\Software]</Data>
<Message>SclRegProcessKeyRecursiveByHandle@341 : (c0000022): Failed to process reg key or one of its descendants: [\REGISTRY\USER\.DEFAULT\Software] </Message>
<Data Name="Message">(c0000022): Failed to process reg key or one of its descendants: [\REGISTRY\USER\.DEFAULT]</Data>
<Message>SclRegProcessKeyRecursiveByHandle@341 : (c0000022): Failed to process reg key or one of its descendants: [\REGISTRY\USER\.DEFAULT] </Message>
<Data Name="Message">(c0000022): Failed to process key [\REGISTRY\USER\.DEFAULT]</Data>
<Message>ProcessOnlineRegistryHives@301 : (c0000022): Failed to process key [\REGISTRY\USER\.DEFAULT] </Message>
<Data Name="Message">(c0000022): Failed to process registry</Data>
<Message>SclpExecuteRequestInternal@390 : (c0000022): Failed to process registry </Message>
<Data Name="Message">STAT: Number of $Secure security descriptors failed = 0</Data>
<Message>SclpStateRecordStatField@195 : STAT: Number of $Secure security descriptors failed = 0 </Message>
<Data Name="Name">FsSecureSDFailedUpdateCount</Data>
<Data Name="Description">Number of $Secure security descriptors failed</Data>
<Message>SetupCl statistic (FsSecureSDFailedUpdateCount): Number of $Secure security descriptors failed = 0. </Message>
<Message>SetupCl statistic (FsSecureSDFailedUpdateCount): Number of $Secure security descriptors failed = 0. </Message>
<Data Name="Message">STAT: Number of $MFT security descriptors failed = 0</Data>
<Message>SclpStateRecordStatField@195 : STAT: Number of $MFT security descriptors failed = 0 </Message>
<Data Name="Name">FsMftSDFailedUpdateCount</Data>
<Data Name="Description">Number of $MFT security descriptors failed</Data>
<Message>SetupCl statistic (FsMftSDFailedUpdateCount): Number of $MFT security descriptors failed = 0. </Message>
<Message>SetupCl statistic (FsMftSDFailedUpdateCount): Number of $MFT security descriptors failed = 0. </Message>
<Data Name="Message">(c0000022): Request execution failed</Data>
<Message>SclpExecuteRequestInternal@484 : (c0000022): Request execution failed </Message>


Is this the right info that is stopping windows from configuring? Anyone know what this means? Is there another log to look at?
Any help is appreciated, thank you.

:)

 

SysPrep Advice

Hi Joseph,

The topic that you raised is beyond the scope of support for this site which focuses more on home and personal end users. Here's what I found about SysPrep:

• What Is Sysprep?
• How To Sysprep – Sysprep is a Great And powerful tool And Easy
  Too If You Know How (Step-By-Step).

However these are old articles and the process may have been changed already. You may re-post this question in

TechNet Forums for further assistance.

All the best.

 

Windows 10 1709 sysprep fail

Hi,

I had the same problem, checked the logs and they basically said Windows was unable to remove the Miracast app.

Tried multiple suggestions, nothing worked until I found this:

Failed to sysprep and capture Windows 10 Fall Creators 1709

Basically Microsoft have pushed out their 1709 image without the Miracast app installed, to fix:

• Copy the C:\Windows\MiracastView folder from a working 1703 build into the C:\Windows directory on the 1709 machine
• Restart and then run sysprep

Sysprep should then run successfully!

Josh

 

Windows 10 1709 sysprep fail

Unfortunately this did not work for me.