Easiest Way for Installing Filter Driver (cfadisk) within ' Boot.wim' On-the-FLY 1- First download ' Filter Driver On-the-Fly v1.0.zip ' file from 2- Extract ' Filter Driver On-the-Fly v1.0.zip ' to any location and double-click on ' CreateDesktopShortCuts.cmd' in order to create ' Mount_wim_2' Desktop shortcut Icon. 3- Drag-and-drop desired 'boot.wim' file onto the ' Mount_wim_2' Desktop shortcut in order to continue process. It will automatically mount the 'boot.wim' file and copy Filter Driver files to%SystemDrive% mount4 folder 4- You can cross-check mounted%SystemDrive% mount4 folder for changes (not required) otherwise Just C lose Explorer (Don't forget to Close Explorer, It's very Important)! 5- And then Enter C or D for Commit changes or Discard.

Hitachi Microdrive driver - cfadisk.sys is a filter driver that allows windows to see your USB Flash Drive as a Fixed Disk.This helps you to partition and access the various partitions of your USB.

6- Press any key to Continue. And now you can boot both 32 Bit 'Boot.wim' and 64-Bit 'Boot.wim' ('testsigning' option must be enable in BIOS BCD & UEFI BCD) within from any Partition ( PTN1/ PTN2/PTN3/PTN4) of your 'Removable USB Drive' in order to load 'install.wim' file within from any Partition ( PTN1/ PTN2/PTN3/PTN4 ) of your 'Removable USB Drive' in both BIOS and UEFI ( Secure Boot Disable ) mode. How do I do a 'Safely remove h/w' in WInPE?Try with RemoveDrive: or with the same devcon, it should be something *like* devcon remove 'USB VID_xxxx&PID_yyyy' Just tested in XP: devcon listclass USB devcon status *USB* Found ID: USB VID_058F&PID_6362 058F312D81B devcon disable '@USB VID_058F&PID_6362 058F312D81B'. Hi Wonko Thanks for the posts and tips. By experimenting with RemoveDrive and RestartStrDev, I have found out what the problem was. The drvload command (and RemoveDrive) did not work because the batch file it is running, is on the USB drive so Windows cannot lock and dismount the USB drive to remove it and re-enumerate the drives again.

To fix this, I copy a set of batch files + the driver files to the X: ramdrive and then run a batch file on drive X. This runs drvload fine but all drive letters are now changed because the USB drive is now a hard disk as seen by Windows and becomes C:! So I then have to look through all drive letters again to find the USB drive letter again, and then carry on with the rest of the batch file to load the ISO file from the USB drive using ImDisk. Anyway, the result is that Windows Setup can see all partitions on a Removable drive.

Just how useful this will be I am not sure. I guess the ISO file could be on the 2nd partition of a removable drive now. The drvload command (and RemoveDrive) did not work because the batch file it is running, is on the USB drive so Windows cannot lock and dismount the USB drive to remove it and re-enumerate the drives again. To fix this, I copy a set of batch files + the driver files to the X: ramdrive and then run a batch file on drive X. This runs drvload fine but all drive letters are now changed because the USB drive is now a hard disk as seen by Windows and becomes C:! So I then have to look through all drive letters again to find the USB drive letter again, and then carry on with the rest of the batch file to load the ISO file from the USB drive using ImDisk.

Anyway, the result is that Windows Setup can see all partitions on a Removable drive. Just how useful this will be I am not sure. I guess the ISO file could be on the 2nd partition of a removable drive now.

Kredo dat 41 s kryakom. I think I had already suggested exactly the same IDEA ( for copy a set of batch files + the driver files to the X: ramdrive and then run a batch file on drive X. )to you in mail. I was expecting for the success.

And Finally you got that point. Now It will be going be very useful for us (Specially for me). Thanks for your researching. Another idea: integrate the filter driver (cfadisk, dummydisk, diskmod) to boot.wim: dism /Add-Driver Thanks for the Tip. Actually we all already knew about this.

And I was also using this till now. But I had heard from somewhere that we can't do UEFI Booting (Secur Boot Enable) of unsigned driver integrated 'boot.wim'. And AFAIK, all filter drivers are unsigned. It's why I have to look for Filter Driver On-the-Fly. And I think now It should do UEFI Booting (Secur Boot Enable) of on-the-fly 'cfadisk' injected 'boot.wim'. No, that is not what devs mod does. If you look at the download, it just adds a winpeshl.ini file which runs a batch file when WinPE boots. So cfadisk driver is not installed until boot time (each and every time WinPE boots, drvload is run).