New
#1
Creating bootable USB 3.0 Flash Drive...
I have followed instructions to create my own Windows 10 To Go flash drive.
I have two suitable USB 3.0 flash drives: Corsair Voyager GTX and Super Talent RC4, both 128 GB versions. The Corsair Voyager GTX is not a certified Windows To Go drive, whereas the Super Talent RC4 is Windows To Go certified by Microsoft. Like all certified Windows To Go drives, the RC4 is significantly more expensive than the Corsair at equivalent storage capacities. The RC4 is generally at least twice the price of the Corsair.
The Corsair may actually be a bit faster than the RC4, but the RC4 feels a bit more "balanced" in its performance with large and small file sizes, and between read / write. That's my unofficial perception of the two; I haven't done any benchmarking to quantify performance differences.
Anyway, I started by installing Windows 10 to the Voyager GTX. And then I cloned that installation to the RC4.
Now here is where it gets interesting. Both drives work perfectly fine on my main desktop, booting from a USB 3.0 port. However, on another computer, only the RC4 will boot from USB 3.0. Attempting to boot the Corsair there produces an "Inaccessible Boot Device" Blue Screen. Now booting the Corsair from a USB 2 port actually does work on that machine, although one really only wants to use USB 2 as a last resort.
My theory at first was that the Corsair wouldn't boot [from USB 3.0] on the one machine because it lacked the correct drivers. However, the fact that a clone of that Windows 10 install on the Super Talent RC4 does boot from USB 3.0 pretty much invalidates that theory.
So does anyone have any idea what the "secret sauce" of the Super Talent RC4 may be? I'm quite sure its not that the Corsair Voyager GTX is too slow: I think it is actually a bit faster than the RC4 at least for large file reads. And also the fact that the GTX will boot through USB 2, tells me that its not related to being too slow... It also apparently isn't because my Windows 10 image lacks the appropriate USB 3.0 drivers for that computer, or why would the same image on the RC4 boot just fine through USB 3.0?
I have the drives formatted as MBR disks, not GPT disks. So these boot in legacy BIOS mode, not UEFI.
So this is a bit of an interesting mystery to me. For now, it appears it may be worth paying the premium for a certified Windows To Go drive as a non-certified drive may not work with all machines. Although I'm also not sure if the difference is due to something specified for Windows To Go certification. The only certified drive I've tested like this is the RC4. And it is entirely possible that certified drives from other brands may be more similar to the Corsair GTX, I don't know.
All of that said, I was wondering if anyone had any knowledge or theories to explain this phenomenon. Ideally, it'd be nice if I could get the Corsair to boot from a USB 3.0 port in the other machine. But maybe that just isn't possible due to a technicality in the hardware of that drive?
Thanks for any feedback.