Windows 10: Macrium failing to capture sysprepped image after following tutorial

As the title says, Macrium is failing. I followed Kari's tutorial, as I have since 1607 but with 1909 I'm receiving this error:
Win 10 Enterprise 1909 is the version.
"Applying WinPE unattend settings failed with status 0x80070422; ignoring shutdown settings."

Here's my unattend.xml:

Code:

:)

 

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.

 

MDT: Capture and sysprepped reference image

Hello All,

This is my first post in this forum. However I have already followed the excellent tutorials about Windows 10 customization and used some tricks. Now I need some help.

I use MDT 8450 to create a reference image for Windows 10 Pro 1803 with Sysprep. After installing the reference image with a MDT deploy task sequence - task most things are automated.

I run sysprep /generalize /oobe /shutdown

Log in in audit mode and customize the Administrator profile. After that I run sysprep again.

sysprep /generalize /oobe /shutdown /unattend:C:\folder/copyprofile.xml

the unattend xml file has only the copyprofile true switch in it.

Once the system is shut down (VM) I boot into PXE and start the standard capture task of MDT. I switched off the Syspre section of the MDT task since I already ran Sysprep. The wim file is created fine.

After that re-start the VM (not the captured wim file) and now it comes what iritates me. Windows 10 starts a bit slower and ends up at the login screen and not with the OOBE process. I see the same if I replace instal.wim of the Windows 10 ISO with the captured WIM and start the ISO in a VM it installs Windows 10, but ends up at the login screen too and not going through OOBE process.

I would expect after I captured a WIM file, the VM would start with the OOBE process since sysprep run with shutdown option. The only thing between was I PXE booted and captured it. It seems during the capture process something has happened which might Windows think OOBE process is already done. I have to revert to last snapshot and then Windows does the OOBE process.

Thanks

Edy