[DISCUSSION] Windows 11 26x00 native Nvme driver discussion

Clean installed 26300, it activated just fine using reg keys, it even shows SN now, so hopefully not abandonware and MS will keep improving it.

 

Sorry for the wrong screenshot.
What I meant is: if you're using a non-Microsoft controller driver, revert it to the standard Microsoft one if Storage disks do not show up

 

I needed all 4 keys (rebooted after each 1 in order; only Storage disks after the last/4th) on 26100.7705 (LTSC 24H2):

Before:





After:





From W10 to W11, MySQL optimize takes longer (not sure if it's a general W11 thing, or file I/O specifically with W11 native NVMe)

 

Running Check Disk ("chkdsk /f C:") on boot switches OS from running native nvmedisk.sys to original legacy disk.sys driver after reboot and does not switch back to new nvmedisk.sys driver regardless of registry entries. How do I bring back nvmedisk.sys after running "chkdsk /f C:" ?

Also, deleting Bootstat.dat file from "C:\Windows" (must be done with image mounted offline) has the same.effect of switching back from nvmedisk.sys to disk.sys, but deleting that file does not actually harm booting or OS when legacy disk.sys is used. How I prevent this behavior?

EDIT: ViveTool can restore the native NVME driver once "ChkDsk/f C:" reverts to legacy after scanning.

 

Any clue why latest update revert back to stock driver, first time i see it with 26200.8106 update

 

MS updated nvmedisk.sys and magic numbers via registry and/or ViveTool stopped working... There are probably new magic numbers... 24H2 26100.8106 is also affected.

 

Updated override info is on Simon Macer GitHub page, but I get "Too Many Requests" error and I can't post links yet due to my low post count.

Someone should copy/paste the details here once links start working.

 

The override info currently shared on Github doesnt work sadly.

 

Yeah same here. Very sad.

 

Working Id for new nvme driver, tested with newest preview.

Spoiler: NVME support

vivetool.exe /enable /id:60786016

As earlier for safe mode to work u need to change value in these keys from "nvmedisk" to "Storage disks"

Spoiler: NVMe new driver SafeBoot fix

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\{75416E63-5912-4DFA-AE8F-3EFACCAFFB14}
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\{75416E63-5912-4DFA-AE8F-3EFACCAFFB14}

 

Thanks! It worked.

 

How to try this new driver on 28000?
I tested with Vivetool and several different reg tweaks posted in here but it's still using the old driver.
I have 2 x Kingston PCIe 4.0 nvme disks.

 

Why mess around with the registry?
Microsoft has been offering a patch since December that lets you enable it via Group Policy. This way, Microsoft can easily change the keys if necessary, instead of you having to set them manually!

h##ps://download.microsoft.com/download/123547b0-bff7-419d-96ba-d1cfee92f442/Windows%2011%2024H2,%20Windows%2011%2025H2%20and%20Windows%20Server%202025%20KB5066835%20251014_21251%20Feature%20Preview.msi

Plus, there’s been a tool on GitHub with a GUI for ages that sets all the keys, checks for compatibility beforehand, and creates backups, etc.
h##ps://github.com/SysAdminDoc/win11-nvme-driver-patcher

Both solutions have always supported NVMe and Safe Boot mode!

This whole thing has been censored off all major German forums for the past three months, and instead they’re relying on stupid keywords that you have to set manually—keywords they supposedly discovered themselves just to boost their click counts... Computerbase, Deskmodder... all these insular forums are just screwing their customers over!

 

=

group policy changes are registry changes, afaik.

 

All the GPO does is simply change one reg key (Feature ID 59254307).

Code:

  <policies>
    <policy name="KB5066835_251014_2125_1_FeaturePreview" class="Machine" displayName="$(string.KB5066835_251014_2125_1_FeaturePreview)" explainText="$(string.WUKnownIssue_Help)" key="SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides">
      <parentCategory ref="KnownIssueRollback_Win_11_24H2_25H2" />
      <supportedOn ref="SUPPORTED_Windows_11_0_24H2_25H2_Only" />
      <enabledList defaultKey="SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides"><item valueName="1176759950"><value><decimal value="1" /></value></item></enabledList>
      <disabledList defaultKey="SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides"><item valueName="1176759950"><value><decimal value="0" /></value></item></disabledList>
    </policy>
  </policies>

 

Why is it 183 MB? Ridiculous. A tool to do a few registry changes shouldn't be more then a few MB.

 

becorse its an full rewrite in .net from powershell

 

25H2 26200.8116 not work