I have a few USB drives here of varying model. Using a script I compile my WinPE images and Windows installers onto them, add an NT6 MBR and bootsector using bootsect.exe, then set the drive as active. So they are all compiled in the same way.
Sometimes, after compiling, the WinPE images will work wonderfully - but installers won't work. They are mounted via ImDisk which is called from winpeshl.ini (a bit like the arrangement in the WinSetupFromUSB project)
I'm not sure if this is a bug with ImDisk, but what seems to happen is the mounted drive becomes inaccessible seconds after mounting. You can still view root folders but most of the time can't go inside them. This causes setup.exe to bug out in weird ways with various errors about not being able to install, sometimes even rendering artifacts.
a) Everything on these drives is MD5-hashed, and the working drives have identical contents to the non-working drives.
b ) Performing a diskpart clean on the non-working drives, then recompiling, will usually make them work properly again. However, the problem eventually seems to reoccur.
I don't think it's directly something with ImDisk, possibly some kind of weird MBR issue since the MD5s were the same? Has anyone ever had this problem?
Happens with the latest version of ImDisk and various older versions too.
Edited by spleenharvester, 27 June 2016 - 01:38 AM.