General Random Write disk speed degradation in Windows 11.

Anonymous
2021-08-23T04:42:53+00:00

After updating several machines from Windows 10 to Windows 11 users have noticed a significant degradation on Disk Random Write speed. This is quite noticeable with NVMe SSDs benchmarks, it also seems to affect SATA SSDs even if it is not as significant. See 3 samples below with 3 different devices on Windows 10 and Windows 11:


Windows 10 19043.1165 NVMe SSD SK Hynix:

Windows 11 22000.160 NVMe SSD SK Hynix:


Windows 10 19043.1165 SATA SSD ADATA SU800:

Windows 11 22000.160 SATA SSD ADATA SU800:


Windows 10 19043.1165 Samsung NVMe SSD MZVLW:

Windows 11 22000.160 Samsung NVMe SSD MZVLW:

Windows Insider program | Windows Insider preview | Performance and maintenance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

60 answers

Sort by: Newest
  1. Anonymous
    2021-12-14T23:49:20+00:00

    This is a known issue which according to articles I have read is solved in KB5007262. I am running 22518 and I looked at my update history of Quality updates and I don't see it. I have another post right now where I asked the question, but one of the MVPs suggested that I shouldn't ask it here. Not sure why. I downloaded the KB, but it will not install on 22518. Is that the build you are testing on?

    Unfortunately, those articles are WRONG about KB5007262 -- this issue is NOT fixed. Some tech sites assumed that simply because MS added the term "NVMe" to its notes (after the fact by the way), they assumed it was the same NVMe issue being reported here and elsewhere -- where there is a 40% to 50% reduction in random write speed, as compared to Win 10, with an NVMe SSD running Windows 11.

    Rather, the "NTFS journaling" issue that MS "fixed" (in KB5007262) relates to ALL types of hard drives as set forth in the notes for that update (not just NVMe SSDs) and it results in some very MINOR improvement in random writes on SSDs. But not anywhere close to fixing the 40 to 50% difference between Win 10 and Win 11 with random write speeds and NVMe SSDs (and where the OS is on the SSD).

    So those sites made assumptions (without testing) and are incorrect. In fact, Neowin did test, and they also found KB5007262 did NOT fix this issue (it is build .348 by the way). I'm worried that now MS thinks it is fixed, when it is NOT, since a number of sites ran articles saying it was fixed (without any proof). Here are some threads, including what Neowin said about the alleged "fix":

    Microsoft's NVMe slow-down fix for Windows 11 didn't work according to our testing - Neowin

    https://www.reddit.com/user/gugu59/

    KB5007262 update may fix SSD performance issues in Windows 11 : Windows11 (reddit.com)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-12-14T23:31:48+00:00

    This is a known issue which according to articles I have read is solved in KB5007262. I am running 22518 and I looked at my update history of Quality updates and I don't see it. I have another post right now where I asked the question, but one of the MVPs suggested that I shouldn't ask it here. Not sure why. I downloaded the KB, but it will not install on 22518. Is that the build you are testing on?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-12-14T22:25:20+00:00

    I don't think today's update was meant to address any NVMe SSD issues (no mention in the notes I read). Hopefully some will be coming down the road though.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-12-14T22:18:14+00:00

    After the last update ((KB5008215), the situation is exactly the same. Very sorry to have upgraded from win10 to Win11 :(

    I hope you kept a backup of you Windows 10? 😉

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-12-14T22:11:11+00:00

    After the last update ((KB5008215), the situation is exactly the same. Very sorry to have upgraded from win10 to Win11 :(

    Was this answer helpful?

    0 comments No comments