OctopussYes but if I understand it correctly, this is internal Windows thing, not something that has anything to do with specific SSDs.

I thought the driver itself misbehaved with some important app functionality, which is why they were holding off on an official release. I'm just lumping that under the "reliability" umbrella.

Presumably storage is a touchy subject for them at the moment as I was again offered cloud storage after installing that recent out of band update. Ironically the cloud storage servers are probably running said nvme driver...

ShrekThe driver under 'Storage disks' still seems to be dated 6/21/2006

Ignore the date. Look at the version number. On my machine it's 26100.7019. Windows itself is 26200.8037

Jtuck9I thought the driver itself misbehaved with some important app functionality, which is why they were holding off on an official release. I'm just lumping that under the "reliability" umbrella.

Mostly in disk utilities that do not yet support the new driver. For example SSD manufacturer tools such as Samsung Magician. Tho i haven't used it for months so maybe they've added support in the mean time. For example AIDA64 added support. HwInfo64 has support etc.
Only deprecated or rarely updated utilities will end up missing support and thus simply dont display the drives in Windows.
Boot time utilities such as Clonezilla etc should be fine.

TomorrowMostly in disk utilities that do not yet support the new driver. For example SSD manufacturer tools such as Samsung Magician. Tho i haven't used it for months so maybe they've added support in the mean time. For example AIDA64 added support. HwInfo64 has support etc.
Only deprecated or rarely updated utilities will end up missing support and thus simply dont display the drives in Windows.
Boot time utilities such as Clonezilla etc should be fine.

Yea. I was wondering if we'd see it crop up when these Direct X enhancements arrive as bypassio was another question mark.

...aaand it's gone!
www.techpowerup.com/347650/microsoft-removes-registry-hack-for-faster-nvme-ssds-in-windows-11

How does that work, as I did the registry hack yesterday.

Ah, I see the block is for insider builds.

If anyone wants and easy automatic way to enable the Windows 24h2/25h2 nvme driver, attached is the script I created for it.
It will check if your system meets the criteria and auto enable, or if not, it stops at what doesn't match what microsoft has as requirement.
My github page for the microsoft nvme driver enablement
I also attached the file with this message.
Simply change the .txt extension to .bat and run it.
*Some have had to go to the file properties and choose unblock first before running it.
What it does:
The script will elevate as admin, and show the menu.
Start with the first option that runs the prerequisite checks and if all pass automatically enables the features and safe mode protections for the driver.
Yes, there is an UNDO option that you can run in safe mode.
I included all known compatibility issues in the disclaimer, so read that, dont skip it.
The second option is there because for some reason I still have some drive brands that show incompatible in my script but after enabling anyway, it works.
Don't ask me why, but I know I'm missing something in my logic checks for the drive being tied to the driver.
If anyone wants to look through it and give me feedback, I welcome it 1000%.
If you add a suggestion, obvious credit will be given in the updated script.
Also, (side note) if you need more drive space in windows... Feel free to also look through my repositories for Scripts from my videos and find yhe BeardSweeper. It my ultimate disk cleanup script I created for maximum junk / temp files cleanup.
BeardSweeper Disk cleanup

So the main benefit of this driver is that apparently the old driver which we all thought was native, is actually a scsi emulation layer? So this new one has much lower CPU overheads for threaded and particular random i/o?

That explanation seems to have a bit more meaning to it, but I think its best to wait until its made default by Microsoft.

But given all the vendor driver all only ever had improvements within margin of error margin's, does this mean they all have the same scsi emulation design? I am not fully convinced of the explanation, but at least it explains why people have been jumping on it.

chrcolukSo the main benefit of this driver is that apparently the old driver which we all thought was native, is actually a scsi emulation layer? So this new one has much lower CPU overheads for threaded and particular random i/o?

That explanation seems to have a bit more meaning to it, but I think its best to wait until its made default by Microsoft.

But given all the vendor driver all only ever had improvements within margin of error margin's, does this mean they all have the same scsi emulation design? I am not fully convinced of the explanation, but at least it explains why people have been jumping on it.

all vendor drivers are for the controller only, host > controller > disk(scsi/native)

Hello Fellow Windows Users.

Just now i see in Partition Control that there is a not initialized volume?
Trying to initialise the volume gives an I/O error?

Windows 11 Device Manager also shows that the NVMe Devices are set back to normal drives again?
In drive settings Both NVMe SSD are also set back to the normal windows disk.sys drivers ??

Is The 25h2 NVMe option taken out of Windows update or what?

Any Help apreciated.
grtz
Mr Jay Cee Corp!

JayCeeCorp!Hello Fellow Windows Users.

Just now i see in Partition Control that there is a not initialized volume?
Trying to initialise the volume gives an I/O error?

Windows 11 Device Manager also shows that the NVMe Devices are set back to normal drives again?
In drive settings Both NVMe SSD are also set back to the normal windows disk.sys drivers ??

Is The 25h2 NVMe option taken out of Windows update or what?

Any Help apreciated.
grtz
Mr Jay Cee Corp!

Screenshot Jay. We need to see what you're seeing.

lexluthermiesterScreenshot Jay. We need to see what you're seeing.

Sorry guys.
I Got Dutch W11 OS installed.

I did re-enter de Registrys Commands given here to activate the NVMe options in W11 update 25h2
Rebooted and again nothing changed to get older earlier succesfull settings back?
Checked for Viruses within Windows Security and Thirth Party AVIRA Prime.
Nothing came up??

All drives in Windows Explorer give no errors in accessing files or folders.

When Bedtime i wil do CHKDSK within CMD as adminstrator and see what this brings up?

Are there any other remarks about unstable NVMe or Drives when using the 25H2 option on NVMe SSD ?

Thanks for any help here, Me confused :)

do not checkdisk a raw volume before you've taken a sector by sector backup, you may lose everything on it.

use recovery tools to check the partition headers

Sorado not checkdisk a raw volume before you've taken a sector by sector backup, you may lose everything on it.

use recovery tools to check the partition headers

Thanks for the Tip.
I will do the recovery first.

Reading my systemerror log and the www.
Could This be that Windows 11 update KB5063878 bug?
As the system time log says, this happened just around i was transferring a big amount of Data from external USB drive to internal drive?
All info around this Windows Bug says it mostly occurs when transferring Big Data ?

Ik keep you Posted !
Thanks for any Help so far :)

Have a Nice Day.
Grtz
Mr Jay Cee

Hello Gentlemen.

I tried my Old Seagate Disc Wizard Software to Access not Initialized drive, no succes there.
I got a License for another Third party Software Called Mini Tool Partion Wizard.
That Tells me That a MBR of System Drive Got Faulty. Reason ???

Windows 11 probably went into safe Mode as everything still is running fine?
(more checks for this needed)

See if i Can recover any Data from Faulty MBR, If not no problem as
i can do a re-install if again probs occure.

Grtz
Mr Jay Cee Corp!
Netherlands

Hello Windows Users.

This New Software looks neat.
GUI shows lots of Possible Options Not seen in Olde Seagate Disc Wizard.
Partition Scan is in Progress now ( see attached scrn shot )
As is Big partition i guess this full scan will take a Couple of days to show up Report.
Further investigation in Event Logs en Windows 11 Settings about this occured " Not Initialized Drive " Fault is
probably a NVMe crash of some sort?
All parameters somehow lead to the KB Update bug causing Faulty NVMe Control Chip?
If So I Replace MBR OS NVMe with new one and do a " Clone Disc " with Seagate Disc Wizard.
using my USB Docking stations

Have fun this Weekend.
Grtz
Mr Jay Cee Corp.
Netherlands