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:

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend">
  <settings pass="specialize">
     <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <OEMInformation>
                <SupportURL>http://www.google.com/</SupportURL>
                <SupportPhone>123-123-1234</SupportPhone>
                <SupportHours>24/7</SupportHours>
                <Logo>C:\Windows\System32\oobe\skull.bmp</Logo>
         </OEMInformation>
         <CopyProfile>true</CopyProfile>
         <RegisteredOwner>My Name</RegisteredOwner>
         <TimeZone>Eastern Standard Time</TimeZone>
     </component>
  </settings>
 <cpi:offlineImage cpi:source="wim:c:/users/administrator/desktop/install.wim#Windows 10 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" /></unattend>

The first thing that strikes me is how devoid of information your unattend.xml is. It's almost empty. If you were following Kari's tutorial, there should be a lot more data in that file.

Second, could you describe the steps that you are taking and at what point you are trying to image this system with Macrium Reflect?

As a summary, here are basically the steps that you should be taking on the reference system (the system that will eventually be sysprepped). If you could note at what point you are trying to image the system with Macrium Reflect and how you are doing so, that would be appreciated.

1) Start installation of Windows and go to the point where region information is requested (not the one near the start of installation, but later in installation after all the Windows files have been copied from the source media and the the system has rebooted).

2) At that screen, press CTRL + SHIFT + F3 to reboot into audit mode.

3) When the system starts back up, select cancel in the sysprep dialog.

4) At this point you would perform all your customizations to Windows, install apps, etc. You can reboot as often as you wish, just cancel that sysprep dialog after each reboot.

5) When everything is setup as you want it, you get the system ready for sysprep by applying the runonce.bat file and the unattend.xml answer file, as well as the oemlogo.bmp (if you plan to use that). You also create \Image and \Scratch folders on the OS drive.

6) Now you run sysprep, after which the system will shutdown.

7) At this point, you want to boot the system from a thumb drive, DVD, etc. but NOT the HD. Once booted from that alternative media, you open a command prompt and run a DISM command to create an image of the reference system.

8) You then reboot the reference system system normally just for the purpose of retrieving and saving the image you just created.

hsehestedt said:

The first thing that strikes me is how devoid of information your unattend.xml is. It's almost empty. If you were following Kari's tutorial, there should be a lot more data in that file.

Second, could you describe the steps that you are taking and at what point you are trying to image this system with Macrium Reflect?

As a summary, here are basically the steps that you should be taking on the reference system (the system that will eventually be sysprepped). If you could note at what point you are trying to image the system with Macrium Reflect and how you are doing so, that would be appreciated.

1) Start installation of Windows and go to the point where region information is requested (not the one near the start of installation, but later in installation after all the Windows files have been copied from the source media and the the system has rebooted).

2) At that screen, press CTRL + SHIFT + F3 to reboot into audit mode.

3) When the system starts back up, select cancel in the sysprep dialog.

4) At this point you would perform all your customizations to Windows, install apps, etc. You can reboot as often as you wish, just cancel that sysprep dialog after each reboot.

5) When everything is setup as you want it, you get the system ready for sysprep by applying the runonce.bat file and the unattend.xml answer file, as well as the oemlogo.bmp (if you plan to use that). You also create \Image and \Scratch folders on the OS drive.

6) Now you run sysprep, after which the system will shutdown.

7) At this point, you want to boot the system from a thumb drive, DVD, etc. but NOT the HD. Once booted from that alternative media, you open a command prompt and run a DISM command to create an image of the reference system.

8) You then reboot the reference system system normally just for the purpose of retrieving and saving the image you just created.

I do steps 1-6. I place the RunOnce bat in the startup appdata folder (but I don't run the script, just place it there). I've never created \Image and \Scratch folders on the C drive, but I do have the unattend.xml answer file on the E: drive.


Step 7 I boot to a USB WinPE environment I got on this forum and run Macrium to take an image of the drive I just sysprepped, and then output/save it to an external hard drive. I've never had it fail on any other version of Windows 10 until now (1909).

I have no issue sysprepping and capturing with MDT and then deploying it with WDS. I just can't take it with Macrium now all of a sudden.


This is the tutorial I've been using for a couple years now: Customize Windows 10 Image in Audit Mode with Sysprep

I'll give it another go though.

-

Thanks for the clarification. I had thought that you were likely following another one of Kari's excellent tutorials, namely, this one:

Create media for automated unattended install of Windows 10

That accounts for the differences in the answer file and the creation of the image that you are performing.

I've not performed this same procedure myself, but now you have me curious as well. I may give it a shot and see if I run into the same issue. If so, I'll see if I can figure out what is wrong.

You may also want to see if @Kari has any thoughts on the matter. Kari is amazing with sorting out these issues and always extraordinarily helpful.

hsehestedt said:

Thanks for the clarification. I had thought that you were likely following another one of Kari's excellent tutorials, namely, this one:

Create media for automated unattended install of Windows 10

That accounts for the differences in the answer file and the creation of the image that you are performing.

I've not performed this same procedure myself, but now you have me curious as well. I may give it a shot and see if I run into the same issue. If so, I'll see if I can figure out what is wrong.

You may also want to see if @Kari has any thoughts on the matter. Kari is amazing with sorting out these issues and always extraordinarily helpful.

No problem, thanks for replying. If you try it out, let me know. Like I've said, I've never had an issue with this before 1909 so I wonder if it's something with this latest build release.

I haven't tried the other tutorial you just posted, but it looks like a good one. I've deploying with MDT and WDS more and more at home. I now need to work on install applications with MDT task sequences.

It may be this weekend before I have opportunity to try it, but I will make certain to take the time to do so.

That other tutorial is excellent. I use the sysprep image created with that tutorial to do completely unattended clean installs on all my systems whenever I reinstall on a system.

hsehestedt said:

It may be this weekend before I have opportunity to try it, but I will make certain to take the time to do so.

That other tutorial is excellent. I use the sysprep image created with that tutorial to do completely unattended clean installs on all my systems whenever I reinstall on a system.

Awesome. I do that with MDT and WDS now. Plug into my switch, PxE boot, get MDT going and go off to do other stuff. I'll check that other one though for sure.