Windows 10: How to Unmount or Discard failed WIMs in bulk on a Windows system

WIM or Windows Image is a file-based disk image format that was developed by Microsoft to deploy Windows. To understand it better, ISO or VHD […]

This article How to Unmount or Discard failed WIMs in bulk on a Windows system first appeared on TheWindowsClub.com.

read more...

 

Dreadful Windows Boot Manager message

Based on Internet search "opencl.dll" being corrupt is common on Windows 10, even on non-Microsoft hardware. sfc on my SP4 returned this error too. There were numerous suggestions out there on how to fix this error. This one works for me. Proceed at own
risk.

Step 1: Download a copy of Windows 10 ISO image from

http://www.microsoft.com/en-us/software-download/techbench. Pick the version that matches your current installation.

Step 2: Double-click the downloaded .ISO file. Windows will mount the .ISO file onto your D: drive. (Depending on your system, Windows may mount this on drive letter other than D:. Check File
Explorer to be sure.).

Step 3: Open a Command Window with Administrator privilege. Create a mount point.

mkdir C:\WIM

Step 4: Mount the WIM - assuming .ISO is mounted at D:

Dism /Mount-Wim /WimFile:\sources\install.wim /index:1 /MountDir:C:\WIM /ReadOnly

Step 5: Run Dism with following parameters.

Dism /Online /Cleanup-Image /RestoreHealth /Source:C:\WIM\Windows /LimitAccess

Step 6: When done, unmount the image and delete the folder.

Dism /Unmount-Wim /MountDir:C:\WIM /Discard

rmdir C:\WIM

Step 7: Restart PC.

Corrupt opencl.dll may not be the trigger to the Windows Boot Manager error I reported in this thread. But fixing corrupt system file is a good thing nonetheless.

 

After Windows 10 WIM deploy, system fails to boot

I have some brand new notebooks (they are HP Z Book G4 Studios). From the state I received the units, I wanted to deploy the company image, instead of using what came loaded by the factory.

Before posting, I did search this site and I did look at: Applied wim file does not correctly boot

No help.

Deploying the WIM failed. It's a Windows 10 WIM. The WIM had the HP drivers added to it... if there was a problem with the drivers, I would expect a BSOD. But that is NOT the problem as no BSOD is received.

Here are the steps I took:

1. Press F9 to access boot menu
   
2. Connect USB DVD drive with WinPE disc inserted
   
3. Boot to WinPE (created with the latest version of the AIK/ADK or whatever MS is calling it these days).
   
4. Run the following diskpart commands: select disk 0, clean, create partition primary, format fs=ntfs quick, assign letter=c:, and active
   
5. Run dism /apply-image /imagefile:e:\myWIM.wim /index:1 /applydir:c:\
   
6. Run bcdboot c:\windows /s c:
   
7. Exit WinPE and reboot.
   

After exiting and the subsequent reboot, I get an OS not found error right after POST.

I booted into the installation media, rescue mode, and ran:

bootrec.exe /fixmbr
bootrec.exe /fixboot
bootrec.exe /rebuildbcd

The bootrec.exe command returns:

Successfully scanned Windows Installations
Total identified Windows Installations: 1
Add installation to boot list? Yes/No/All:

So I enter Y

...and it fails!!!

I can go to c:\ and do a dir and see the file system as expected (so again, assuming so WIM integrity problems).

1. Is there anything special about doing this on Win 10 that is different (Win 10 does put a 100 MB and 450MB partition on the drive when it does a clean install right? Recovery areas and such?
   
2. When I do the diskpart clean, that wipes those two partitions out. How critical are they to run?
   
3. I've used the same process which worked on Windows 7 -- are there BIOS settings, partitioning, etc., which is preventing this from booting for me? I haven't had such problems before; just with Win 10.
   

The drive from the factory was gpt. I did run diskpart convert mbr. The whole process failed in the same way

Suggestions are greatly appreciated!

Thanks!!!

 

How to fix error unmountable boot volume

Hi James,

It is possible that you received the error UNMOUNTABLE_BOOT_VOLUME due to a damaged file system which failed to mount. This error also means that sub-system on machine failed to mount the boot volume. To efficiently assist you, we'd like
to gather more information:

• Have you made any recent changes prior to this issue?
• What is the exact error message you received?
• What troubleshooting steps have you done so far?

Meanwhile, we suggest that you you follow the steps shared by Michelle Her and
Billion Debbarma on this threads below to troubleshoot your concern:

• Windows 10 Unmountable Boot Volume Error Message And Automatic Repair
• Unmountable_boot_volume -Windows 10
  

Keep us posted if you need additional help.