Microsoft blocks trick to unlock native NVMe driver, but workarounds still exist

I don't mind Microsoft attempting to fuse off experimental features in builds of windows. That makes perfect sense. I don't want to accidentally fuck all my data either. What sends me into an unmitigated schizo frenzy is the part where they double down over and over like it's a game of competitive CTF.

Microsoft did the same thing with notepad.exe. At some point it apparently got so intense that they added code to make it possible to prevent association of certain executables with certain extensions (i.e., if you got cheeky and copied the old version over and tried to use it). I know Microsoft deals in a lot of unusual business, but I'd bet my life there is no rationale for deeply restricting the use case here, other than to be an antagonizing prick to the other team/tribe who simply seeks to use their computer freely.

If AI was truly profitable Microsoft wouldn't need to cover their expenses at every other corner.

Supposedly it requires additional workarounds to run in safe mode, and doesn't work if the NVMe drive is attached to a RAID controller (whether that's in use or not).

I also wonder whether this feature will be locked to server and the little-known "pro for workstations" variants.

> The native NVMe driver (nvmedisk.sys) replaces the legacy storage path that has routed NVMe commands through a SCSI translation layer since before NVMe SSDs existed.

What? What are Microsoft doing for a decade after NVMe available to consumer grade motherboard?

I mentioned this in the Scott Hanselmen trying to re-allow local-accounts for Windows thread. https://news.ycombinator.com/item?id=47498494

It just seems so beyond-belief that Microsoft keeps having such depraved anti-consumer behavior. Maybe perhaps this was just a not-ready-yet feature folks had enabled being moved around or shuffled. But it seems just as likely Microsoft intends to keep consumers using a decade and a half years old shitty NVMe-downcast-to-SCSI layer indefinitely, to upsell folks to fancier Windows versions or gaming systems. Microsoft intends to keep Windows consumer disk access slow and bad.

As a seasoned Linux veteran & believer, it's somewhat against my interest to share this view, to try to arouse the slumbering behemoth to action. Microsoft not getting the message and doing great misservice to their users is somewhat in my interest. The status quo of Linux being far better at everything is great: gaming is already much faster on Linux, & that should be no surprise, and disk io too. Just holding my tongue and letting Microsoft make a fool for themselves with absymal performance would be ideal. But I also believe in competition, and Linux is going to start slacking off if Microsoft can't be arsed to update a disk io subsystem that was a filthy pitiful hack when they slammed it into service a dozen years ago. We all need some pressure sometimes to get off our hinds, wake the frak up, and pay some attention.

And perhaps, maybe: even Windows users don't deserve this malpractice.

Much like oracle MS doesn’t have customers just victims that for whatever reason can’t escape

holy fuck, imagine segregating your customers' block layer

“NVME?? What’s NVME got to do with anything?

It’s the Task Bar!

For goodness sake can’t you see Windows users have lost faith because they can’t move the task bar!”

(Heard in meetings all over Microsoft campus recently).