An Anonymous Coward belatedly writes:
"Sandisk changed the configuration, beginning in 2012, for all USB drives they make so that in future external USB devices will be seen as physical hard drives. This has been done to meet requirements set by Microsoft for Windows 8 which states that all USB devices must be configured to be recognised as fixed drives (nb. this is possibly related to Windows-to-Go). This has caused havoc for many users as Sandisk drives can no longer be used with Windows Recovery or any program that will only write to USB External devices. Sandisk deleted the support page that described why Sandisk USB drives are now configured as fixed drives, although the blog author includes it in his blog.
Beware any USB pen drive which states it is "Windows 8 certified". The device will not be detectable as an external drive in Windows 8. The HP Recovery Disks page says to avoid any Windows-8-certified USB devices."
One comment on the blog suggests that Sandisk might have reverted to more conventional practices for subsequent USB devices.
(Score: 5, Insightful) by quitte on Monday March 03 2014, @11:48AM
Holy Shit. That explanation makes so much sense! Microsoft would rather talk all USB fob vendors into changing one bit than fixing their Partitioning tool.
(Score: 4, Interesting) by Vanderhoth on Monday March 03 2014, @11:55AM
That's what MS does. They have an overwhelming market share (especially in enterprise) so they can tell hardware companies how it is. If a hardware company wants their product to work on Windows, they'll do what MS tells them to. Otherwise a hardware company's competitor will be the choice product, and MS may decide to make "support" for company A's product difficult.
"Now we know", "And knowing is half the battle". -G.I. Joooooe
(Score: 5, Informative) by mojo chan on Monday March 03 2014, @02:01PM
Actually the problem is with BIOS vendor's code. If the disk appears as an external device the BIOS will try to boot it in a different want to a fixed disk. The BIOS expects external drives to have one partition in a very specific format, not suitable for Windows To Go.
Microsoft had two choices. They could hack around getting Windows To Go working with the old single partition system, but it is considered legacy and depreciated. Alternatively they could ask vendors to produce compatible drives and mark them as Windows 8 compatible, but in doing so break everyone else's code and violate the USB spec. I'd have preferred the former option.
const int one = 65536; (Silvermoon, Texture.cs)
(Score: 1, Interesting) by Anonymous Coward on Monday March 03 2014, @03:40PM
They could also have chosen a third route: Only certify computers as Windows 8 compliant if they can boot from multi-partition external disks.
(Score: 0) by Anonymous Coward on Monday March 03 2014, @03:00PM
I don't think it's so much they don't want to fix their partitioner as it is the UX-guys and the users causing problems. If multiple partitions could be created easily in Windows, hilarity would ensue, as the set of removable usb device owners, and Windows users, not actually trying to use WTG, intersected. I can see it now. 63 extended partitions, followed by a call for support for a "broken" flash disk.
(Score: 0) by Anonymous Coward on Monday March 03 2014, @03:09PM
s/extended/logical/g, because morning