Windows 10 Update Finds A Way To Make Gaming Worse

Windows 10 Update Finds A Way To Make Gaming Worse
Image: Kotaku

Ah, that old chestnut: a major Windows 10 update suddenly causing a bunch of video games to have issues out of nowhere.

If you’ve found yourself wondering why your gaming PC is suffering from a bunch of weird issues lately, you’re not alone. Users have been reporting a ton of supremely annoying issues after installing the KB5000842 Windows update — colloquially known as the April 2021 update, although some people got the patch at the end of March.

The issues are, to put it mildly, not great. Problems on AMD, Intel and Nvidia-based systems range from stuttering in games, instability with V-sync enabled, reduced FPS and intermittent lag elsewhere in Windows.

It’s such a persistent problem that even Nvidia is formally advising users to roll back the update if they’re noticing problems. (Naturally, Nvidia doesn’t want to cop flak for their latest driver if it’s actually Windows 10 that’s causing the issue.)

We’ve been down this road before, so if you don’t know how to put a block on forcing Windows 10 updates, here’s how you can do that. And with that information at hand, please enjoy some of the latest frustrations that Windows has manufactured for users out of nowhere:

kb5000842 update (March 29 – 2021) gives vsync issues from r/Windows10

If this sort of shit really annoys you, a great solution suggested by a Kotaku Australia reader is to limit feature updates to patch every 28 days, while allowing security updates through every day. You can hold feature updates back for 90 days as well, which might be best. The security updates are essential, but “feature” patches that send your FPS into the toilet? Not so much.


  • Unfortunately, the ability to set different delivery dates for feature and security updates doesn’t exist in 21H1 (and I think 20H2 either).

    You can use Local Policy I believe to still set the old cadence of 28 Days for feature updates {(Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business“.), and I’m unsure this will apply to Windows 10 or Windows 10 Pro SKU’s}, but the only GUI option you have is to pause updates. Which obviously leaves you without security updates.

  • The Supreme Commander 2 issues, on the other hand, definitely seem to be an Nvidia driver issue as my brother had to roll back to an earliar one to get the mouse to work properly.

  • I’ve been using Manjaro 99% of the time which is based on Linux arch distro for gaming. Its been pretty good escape from Microsofts grip, but some things still not quite ready such as anti-cheat api games (battleye/eac etc) so I still wouldn’t recommend it for casual gamers and non-power desktop users.

    You need to have some level of motivation to learn and change when moving to Linux, understanding it etc…

    Windows experience can only get worse from here on in, and Linux desktop experience can only get better 🙂

    • If I could get.

      A: A AMD softRAID driver for X570
      B: Nvidia to support Wayland properly rather than being petulant children about it (seriously, nvidia drivers in linux are as bad as how bad people think AMD drivers are in Windows).

      I’d probably shift over to Linux as my primary desktop and boot into Windows for anything that requires Anti-Cheat.

      • Nvidia is starting to support wayland now, but still lots of work to be done for wayland. Probably at least another year before I’ll consider using it over X11 (display server / window manager).

      • AMD has published drivers for their software raid, but have not pushed them upstream. So they aren’t there in the default install. Some people have put in some work to upgrade them to run with more recent kernels however:

        It’s probably easier to ignore BIOS level software RAID though. You’re probably better off using your operating system’s built-in software RAID or similar rather than limiting yourself to what the BIOS provides. At a minimum, it’ll make it easier if you ever need to transplant the disks to another machine to recover the data.

        As for Nvidia, I suspect they’ll release Wayland compatible drivers sooner or later. With the Xorg server going unmaintained and most distros signalling that they’re switching to Wayland by default, they can’t easily put this off much longer. But for now, most distros should automatically default you to an Xorg session if you’re on Nvidia hardware.

        • RCRAID is only useful for SATA, not NVMe

          And as for BIOS raid, I agree, except I’m using it as storage pooling preferably over multiple OS’s. Can’t run Storage Spaces in Linux, can’t run LVM on Windows.

          The shitshow over Nvidia is essentially every other manufacturer agreed on a standard way forward with Wayland, Nvidia decided to be different and pushed for another standard, and when the Nvidia proposal was dropped, essentially picked up their ball and went home for the next 5 years.

          • Fair enough. My reason for suggesting using OS level multi-volume solutions is that most of the recent improvements in handling multiple volumes have come from integrating it at the file system layer rather than the block layer underneath file systems. That lets you do interesting things like have different levels of redundancy for different types of data, and have knowledge of what parts of the disk are actually in use.

            As far as Wayland goes, Ubuntu 21.04 is shipping with the Wayland session by default, only falling back to X11 on Nvidia hardware. I expect it’ll be Wayland everywhere by the time the next LTS release is out.

    • I’d shift over to linux if I could figure out three things

      1. The linux alternative to mklink /j (cause with games, some things I throw onto an SSD and some things I throw onto a mechanical drive)

      2. The linux alternative to RivaTuner Statistics Server < this thing is the best global FPS limiter

      3. The linux alternative to control my GPUs inbuilt LEDs

      • Not sure about the other two, but (1) is pretty easy.

        If a standard symbolic link won’t do for some reason, a bind mount on Linux is probably the closest you’ll get to an NTFS junction point. Bind mounts won’t survive a reboot, but you can add an entry to /etc/fstab to set it up again on boot.

        In most cases though, a simple symlink will work just fine, and will persist over reboots.

Show more comments

Log in to comment on this story!