Start a Conversation

Unsolved

This post is more than 5 years old

4478

July 26th, 2018 08:00

Issue Windows Recovery Partition structure W10 1803 SP112

With Microsoft's Windows 10 build 1803 release 17134.112 the Windows Recovery Partition structure is inconsistent. Dell ImageAssist replicates this inconsistent partition attributes/files when capturing or restoring the Windows Recovery Partition.

Normally when you capture an image it should reflect the Recovery partition as UEFI / Recovery shown below:

1.jpg

And deploy it as a UEFI Recovery partition:

2.jpg

The updated Windows 1803 media will show the UEFI Recovery partition as Data when trying to capture:

3.jpg

During the restore, it will show that it is trying to apply a data partition. This partition will then be visible in the OS with a drive letter and the winre.wim does not get copied to this partition during OOBE since the id and attributes are not set correctly.

4.jpg

Running the following command line against the WIM image will show the incorrect volume description.

 dism /get-wiminfo /wimfile:

5.jpg

Please check back for updates. You can contact our regional OS Imaging support teams using the contact information here.

August 3rd, 2018 10:00

I'm having this exact issue. Is there a solution or workaround for this at the moment?

Thanks for posting this issue. I was worried I was messing up somewhere until I found this post.

Moderator

 • 

342 Posts

August 3rd, 2018 11:00

GELIANTORT -

Overview: Due to the inconstant partition structure created when installing using ≥ Windows 10 build 1803 release 17134.112, the following steps will work to capture / restore the recovery partition scheme when using ImageAssist with the current or previous release as of today's date. The WinRE.wim and folder structure will not be placed on the Recovery partition as documented in previous builds of Windows 10. They will instead reside in c:\Recovery.

Some additional information about this issue.

  • If Windows installation media is < .112 build and the OS is updated using KB’s provided by MS, this issue will not be present.
  • If Windows installation media is ≥ .112 and updated to the latest KBs, this issue will persist.

 

WORKAROUND: In this scenario you must interrupt the ImgaeAssist Auto-Capture process and create a folder named “Recovery” in the Recovery partition prior to capturing the image.

Click “Cancel” during the auto-capture countdown.

 1.png

Take note of the Data Driver Letter.

2.png

Press F7 (Function+F7 if your function key is not enabled) to open a Command Prompt. Execute the following two commands:

  • mkdir :\Recovery
  • exit

3.png

Click the ‘X’ in the upper right to close the Capture Tool.

4.png

Execute “capture.exe” to relaunch the Capture Tool.

5.png

Notice the correct UEFI Recovery Driver Letter versus the incorrect Data Drive Letter.

6.png

Click Capture.

August 3rd, 2018 15:00

This worked perfectly. Thank you for your quick reply and simple solution!

August 28th, 2018 11:00

Just as an update for future readers, this issue seems to have been resolved in ImageAssist v8.6.1.3 (released August 17, 2018).

No Events found!

Top