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

• 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

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

    That’s fair. I’m certainly not one to defend msoft, nor do I really have the technical knowledge to rebut. Is it possible that ‘trying’ the driver as you suggested could damage the drive or corrupt data? Just wondering if there’s a legitimate reason they wouldn’t go for a seemingly easy win aside from being a generally dumb organization.

    source

    • deadcade@lemmy.deadca.de ⁨6⁩ ⁨hours⁩ ago

      There’s always the option of gathering device info first, then using the appropriate driver. Either the SSD is in a “known supported models” list, or it reports support for whatever feature the new driver needs.

      It’s technically possible that straight up trying an unsupported driver can cause physical damage, but this can be avoided by carefully selecting the driver. From MS pov, they’d have to extensively test this driver on a bunch of SSDs and configurations, but it would lead to a performance improvement.

      source

      • finalarbiter@lemmy.dbzer0.com ⁨6⁩ ⁨hours⁩ ago

        Ah, any developer who suggested that probably got the same answer I get at work: “Testing costs money, so unless we absolutely have to, no.”

        source
• 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