I noticed in BIOS its detected as 'USB Flash drive 0.00' its seems like there is some id info for USB devices that designers had to write, something like SPD for DIMM, and maybe A-Data didn't bother, so bios doesn't know how to interpret it. Bot both ST and A-Data detected in Hard drive section of my BIOS setup (Foxconn A690GM2A) Yea, I had to create a second file, I totally forgot about 4GB limit of FAT32, and it puzzled me how come there is lots of space but I can't copy a file of even less size (I also wanted to put an image for acronis) THANK YOU for a tip, it makes all the difference in the world, FAT32 text mode copy stage took ~ one _hour_ in NTFS I just plugged a stick at the back of computer and before I set down on my chair, it was done, ~2 min total crazy! Also creating a filler file with fsutil with fat32 takes ~20 min, with NTFS - instant! seems like it doesn't write 0 on actual media. Interesting, putting setup file on disk takes about the same type. I assume text mode setup uses kernel drivers to copy files not BIOS and the same drivers are used when windows fully installed? But with NTFS you can't put anything else, is it limitation of grub4dos? BartPE should be able to understand NTFS? Maybe as fix partition USB stick and make second partition FAT32 (or ext3) and put linux tools there? Grub4dos probably can see it. root (hd0,1) Also I assume WinSetupFromUSB should not interfere with RyanVM update packs and Nlite fixes? (speedUp - reducing numbers of drivers loaded in text mode) Also just, noticed, there is a lot of free spaces (several big gaps) in txtsetup.sif in the end portion, it make loading slower. Just tested on 8Gb stick, txtsetup.sif [DiskSpaceRequirements] FreeSysPartDiskSpace = 7024 UpgradeFreeSysPartDiskSpace = 7024 doesn't help.