Open Menu
AllLocalCommunitiesAbout
lotide
AllLocalCommunitiesAbout
Login

Windows 11 25H2 Includes a Faster NVMe Driver Needing Manual Installation

⁨105⁩ ⁨likes⁩

Submitted ⁨⁨9⁩ ⁨hours⁩ ago⁩ by ⁨themachinestops@lemmy.dbzer0.com⁩ to ⁨technology@lemmy.world⁩

https://www.techpowerup.com/344348/windows-11-25h2-includes-a-faster-nvme-driver-needing-manual-installation

source

Comments

Sort:hotnewtop
  • FauxLiving@lemmy.world ⁨5⁩ ⁨hours⁩ ago

    I’d be wary of importing random unintelligible registry keys from sites purporting to increase system performance for free. Even if they’re posted on social media, the land of rigorous fact checking and rationality.

    source
    • SanctimoniousApe@lemmings.world ⁨4⁩ ⁨hours⁩ ago

      It mentions & includes a link to the NotebookCheck site as the source. It’s certainly NOT an unreliable site.

      source
  • kescusay@lemmy.world ⁨8⁩ ⁨hours⁩ ago

    Hmmm. The NVMe standard has existed since 2011, and Samsung released their first commercially-available drive with it in 2013. So Microsoft has had at least 12 years to make nvmedisk.sys the standard driver for these disks.

    source
    • finalarbiter@lemmy.dbzer0.com ⁨7⁩ ⁨hours⁩ ago

      Using this driver, however, is fraught with risks. Not all NVMe SSDs support it, and if incompatible, it could break Windows 11 boot.

      Probably why it isn’t standard, especially since there’s a driver that does work even if it’s suboptimal.

      source
      • deadcade@lemmy.deadca.de ⁨7⁩ ⁨hours⁩ ago

        And obviously, there’s been no possible way to try loading the modern driver and if that fails, falling back to the legacy one.

        This is once again Microsoft refusing to improve performance, because that doesn’t directly increase profits.

        source
        • -> View More Comments
      • pHr34kY@lemmy.world ⁨5⁩ ⁨hours⁩ ago

        So they can’t just write some probe code? It really can’t be that hard to determine if there’s support.

        source
      • DokPsy@lemmy.world ⁨6⁩ ⁨hours⁩ ago

        If only there was a way to do a check for compatibility on the os side for a standard that has been available since before the predecessor os was released and fall back to the older driver if it fails

        source
  • db2@lemmy.world ⁨6⁩ ⁨hours⁩ ago

    laughs in Linux

    source
    • spicehoarder@lemmy.zip ⁨4⁩ ⁨hours⁩ ago

      It certainly is, and when it breaks because it can’t handle some obscure use case, I won’t bat an eye

      source
  • adespoton@lemmy.ca ⁨8⁩ ⁨hours⁩ ago

    Interesting. I presume that over time, MS plans to tweak the driver, increasing safety and security, and then start transitioning known safe devices over. Seems surprisingly responsible.

    source
    • Poach@lemmy.world ⁨7⁩ ⁨hours⁩ ago

      Only like 10 years late

      source
  • ascendings@fedia.io ⁨8⁩ ⁨hours⁩ ago

    This is actually kinda cool! Hopefully it eventually becomes a "default" of some sort or at least has an easy toggle in compatible configs.

    source