Quantcast
Channel: Ivanti User Community : Document List - OS Deployment and Provisioning
Viewing all articles
Browse latest Browse all 639

"Manage Drivers in Windows PE image" Blank when trying to Add Drivers

$
0
0

Issue

 

On rare occasions, the "Manage Drivers in Windows PE Image" tool shows a blank list of drivers after selecting the desired boot.wim file.

 

This issue generally stems from the boot.wim file being improperly unmounted the last time it was used.

 

Manage Drivers Empty.png

Resolution

 

The first step to resolve this issue would be to verify the existence of the boot.wim file on the core. It'll be found at "C:\Program Files\LANDESK\ManagementSuite\landesk\vboot."

 

If the boot.wim is present, we'll need to run some DISM commands to verify if there are currently any WIM image files mounted on the core.


Open an administrator command prompt and rundism /get-MountedWimInfo. If there are currently any mounted files, you should see something like this.

    NOTE: There may be more than one mounted WIM file on the core. The one we're concerned with is going to be under the vboot directory, but all stray mounted WIM files should be dealt with.

getmountedwiminfo.png

From what we can see in the screenshot, we know that there is currently a WIM image file mounted. Its currently mounted to "C:\Mount" with an original file location being "C:\Program Files\LANDESK\ManagementSuite\landesk\vboot\boot.wim."

 

Note the Status. In this example, the status is listed as OK. This is usually best-case scenario; meaning the WIM file can be easily unmounted. Anything other than OK (Such as Needs Remount or Status Un-available) will likely result in needing to repair or revert the damage.

 

Its recommended to first try to unmount the WIM file gracefully so we don't lose any work done to the currently mounted WIM file. This is done by running the command "dism /unmount-Wim /MountDir:"Mount Dir" /commit."

Unmounting.png

If unmounting the WIM fails, or the Status is listed as something other than OK, there are a couple of things we can try. The first being Remounting the WIM file. This can be done by runningdism /remount-Wim /MountDir:"MountDir."

 

After successfully remounting the WIM, attempt to unmount it once more using the steps above. If remounting fails, the only option left is to run DISM Cleanup.

 

Run dism /cleanup-Wim. This will tell DISM to search for and "Clean up" any stale or corrupted image files on your core.

    NOTE: This will erase any previous work done to the Boot.WIM from the last time it was mounted. Any drivers or files added will have to be re-added after running this command.


Run dism /get-MountedWimInfoonce more to ensure there are no longer any mounted WIM files on the core.


The "Manage Drivers in Windows PE image" tool should now be showing the full list of drivers.

Manage Drivers Fixed.png


Viewing all articles
Browse latest Browse all 639

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>