It typically indicates a problem with access to the folders within the boot.wim when it is mounted. If you look at the console.exe.log you may see errors indicating that it cannot find part of the path. In that case, cancel the edit window and from a command line run imagex /unmount. Imagex is in the C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot directory. That should list (I say should because if you have rebooted between mounting wims it may not be listed) the wim files that are currently mounted. Manually unmount the wim (Imagex /unmount yourwimdir) and try to edit the drivers through the gui again.
Running imagex shows that there are no additional .wim mounted on the local system.
If you manually try and mount it on the core, does it mount correctly or does it say it is in use?
Create a folder c:\mount
From command line in the C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot directory run imagex /mount boot.wim 1 c:\mount. See if you get an error. If not, unmount the image (imagex /unmount c:\mount).
We get this problem at our site. If you manage the Windows PE drivers on your local PC Landesk Management Console after you update and save, the progress bar will hang. Reopen Windows PE and it will show the blank screen. All work is lost. Very very frustrating.
Our fix for this problem is:
Go to \\<landesk server>\ldmain\ and copy bootmedia.wim.bak and put it in D:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot
You may have to rename the old bootmedia.wim to bootmedia.wim.old if it exists and then rename bootmedia.wim.bak to bootmedia.wim.
Close your management console and reopen. Drivers should appear.
My work around is I do the Windows PE update on the landesk server using the server Landesk Management Console. I have to RDC in as it is offsite. When done on the server I do not have the problem.
I then use my local PC Landesk Management Console to create the boot media.
Bootmedia.wim is designed for booting provisioning. I recommend grabbing the boot.wim from whatever most recent patch you installed that included a boot.wim file. The problem of everything being lost is actually indicating the boot.wim is still mounted. If you look at the console.exe.log, are there any errors during the unmount process?
Verify if C:\Users\%username%\AppData\Local\Temp\%number%\imgtmp\Apply exist, with all winpe folders when you are injecting drivers.
Each time you edit the WIM (to inject drivers, modify the picture), imagex deploy it in the folder given (usefull to know if you want to modify startnet.cmd script for example)
We use dism to mount the WinPE in C:\Users\%username%\AppData\Local\Temp\imgtmp\.
Some permissions issues can block the deletion of the mounted folder. Please manually delete the Apply folder under imgtmp then mount again the WinPE via the console and this should be fixed.