I still run W7 on a Ryzen gamer. I have SP1 installed and all of the update features are permanently turned off due to to that fact the MS doesn't like W7 running a modern Ryzen PC. I don't need any updates and only the Nvidia 1080 driver gets an update once in a while.
There's a project called Wufuc that fixes the "unsupported hardware" crap MS did for Windows Update.
Disables the "Unsupported Hardware" message in Windows Update, and allows you to continue installing updates on Windows 7 and 8.1 systems with Intel Kaby Lake, AMD Ryzen, or other unsuppo...
github.com
I used this back when I had to deploy some new Dell AIOs that had 7th gen Intel Core i5s, right around when MS first pushed out the update to break Windows 7 on newer hardware.
I don't use Windows 7 for internet anymore, but in the past my current Win7 system has experienced strange bugs like text glitches when I open notepad.
Plus, my CPU is AMD Bulldozer based, so it is sluggish for the first minute or two once the desktop loads - even on a clean install when I used to use Firefox and Avast antivirus. There are a couple of Windows updates to patch my CPU though, but I haven't tried them yet. I read online that the CPU patches don't help much.
I don't experience this level of bugs on other systems I used in the past which also had Win7 SP1 with no extra updates. So I'm hoping a large set of chronological updates will fix my problems.
The reason that Bulldozer CPUs suck is because of the "Cluster Multi-Thread" architecture. Each "module" has two integer units and one shared floating point unit. The FPU is "supposed" to be strong enough to feed both integer units, but in reality, it is anything but. If you have two resource heavy threads within the same module, you can expect performance degradation up to 50% since both threads have to share module resources. This can get worse if either or both threads need to make use of the FPU.
The "fix" that was released as a patch later in Windows 7's lifetime was to rewrite the thread dispatcher so it would keep resource intensive threads on different modules, and backfill the second thread with background or low resource usage threads to not degrade the performance of the first thread. All subsequent versions of Windows and Linux would have this behavior by default. Vista and XP never had their thread dispatchers fixed, so they remained with performance issues on Bulldozer CPUs.
I don't remember which patch changed the thread dispatcher behavior, but you'll be able to see it in resource monitor. If you have an 8000 series Bulldozer, you should see CPU 1, 3, 5 and 7 take the heavy loads, while 2, 4, 6 and 8 are backfilled with lower resource loads. It's easier to see on Linux using TOP in bash.