The keys were listed in this thread, I didn't look for their origin I managed to test it with Vivetool. With the keys, need the new "component" added with a CU a few months ago and the WinCsFlags.exe executable
I know… I don’t know why I naïvely got my hopes up. But honestly, I’m a bit scared to try them on the Samsung 9100 Pro.
I have tried the driver with my samsung pro 9100Pro 2 Tb not realy a big gain and beside that samsung magician does not sees the nvme anymore.
Microsoft doesn’t recognize it, Samsung doesn’t recognize it, so I don’t know what we’re supposed to do with these Windows systems.
I defo need faster windows nvme but also sub system as with few project i had issue on storage system queue overload after longer uptime, but I am not ready to test my system with this yet, I hope they make more polished driver and way to enable it and revert more easy then now On linux I have no issue with deployment but it really hammer the disk subsystem with small read tasks where windows start to get unstable after a 3-4 weeks uptime
Uhhhh Microsoft recognizes the drive idk what ur talking about. The ssd programs will eventually because they will need to for enterprise server clients using the drivers. As always when something new is out it takes some software a few to catch up but Microsoft for sure sees and knows it's an nvme drive so idk what u mean or are talking about there
What do you need drive tools for? I do full discard/trim to clean-up SSDs from a Linux LiveUSB (blkdiscard/nvme-cli), then use it normally from the OS. Drive firmware updates are rare, and I check fwupd or WU for those. Drive health I've assumed fine for years (I check SMART occasionally but have plenty of health/provisioning left) My Samsung NVMe doesn't need to detect as anything specific under Windows as long as it works for the Windows install (RST or AHCI, RST v17.7 vs 17.11, random AHCI controller drivers), and the only realistic difference is slightly longer boot times AHCI.
We’re talking about drivers that were made back in 2006… okay, maybe it gets updated, but I still expected something newer and better. For example, when I connect a monitor, it has its own drivers, not just a plug-and-play option. The point is that, because of one program discussed in this thread, disk results or performance showed improvements of around 30%, and on some other forums even up to 80% if I’m not mistaken. For regular users this may not be that important, but for someone working in production, video editing, or photo processing, productivity can be significantly improved. I’ll write it again: I still haven’t dared to install the driver on the “Samsung 9100 Pro 4TB” for the simple reason that stability comes first, and speed comes after. That’s exactly why we buy expensive drives that promise higher speeds, not to experiment with drivers that, since 2006, should have changed or improved by now.
That might be Intel's thinking with their RST controller (I see a lot of RST-specific options in BIOS vs nothing special for AHCI)
That's fine, but I’m running a Ryzen 7 system, so Intel RST is not an option for me. On AMD platforms we rely on standard NVMe/AHCI drivers, and the core issue remains: NVMe driver maturity and behavior still affect performance and latency, regardless of how fast the storage hardware itself is.
It had better 4k by .2% which is well within margin of error. The other tests were better on native which is why I keep telling you to stop blanket posting it is better than the native which it is not and also that the native doesn't work with direct storage because it does.
That's why I initially said the modded Solidigm +tunings is "as fast or even faster" than Native NVMe. In RND4K Q1T1 (again, the most important metric for actual system responsiveness, boot times and game streaming) you had +1.1% in Read ("as fast") and +4% in Write ("even faster") Like also said: this while keeping full BypassIO compatibility while Native NVMe has not, as shown in the post above. That's also probably why it's being proposed for Servers only at the moment.
Looks like these settings have absolutely no effect on an ARM device (Surface Laptop 7th edition) running Win 11 26H1. Not sure if the architecture doesn't support it, the drive, the ARM64 version of Windows or all of the above.