Started giving me blue/green/black screen.

I understand that pausing Windows Update does not necessarily cancel an update that has already been downloaded or staged. My concern is slightly different, though.

Windows Update has been paused on my system for roughly 2–3 months. I did not manually trigger this update, yet KB5129195 was released and subsequently pushed to my system in September. That is what I find difficult to understand. If an update is capable of being installed while Windows Update has been paused, then what exactly does “Pause updates” prevent?

More importantly, everything was working normally before I installed KB5129195 on September 20. Immediately after the installation, I started experiencing a very specific combination of problems:

CS2 performance dropped from around 200 FPS to frequently below 100–120 FPS under the same settings.

CPU usage is frequently around 100% and GPU usage is also above 90%.

• USB devices can simultaneously stop responding: keyboard, mouse, headset, camera, etc for few seconds (and sometimes my wireless usb like mouse and headset are completely stuck).

The display can freeze and turn grey, black, blue, or green depending on what application is running.

The freeze lasts 15+ seconds and then the system recovers without a reboot.

Disk usage can remain at 100% for extended periods.

Memory usage can jump to 60–70% even with no applications open, while Task Manager does not clearly show what is consuming it.

The C: drive had only around 17 GB free after the update, and the system appears to consume additional storage after these incidents.

I have already freshly reinstalled the NVIDIA driver, including a clean installation, and the behavior remains the same. That makes it difficult for me to simply assume this is an old graphics-driver problem that happened to appear at exactly the same time as the Windows update.

I also understand that Microsoft may not currently classify this as a confirmed general KB5129195 regression. I'm not claiming that the update is definitively the sole cause. What I am saying is that the temporal correlation is extremely strong: the system was stable before the update, and these problems began immediately afterward.

If Microsoft was already aware of issues associated with this update, why was it delivered through the normal security-update channel rather than treated like an optional/preview update where users can choose whether to install it? And if Microsoft was not aware of these problems, then I think it is still reasonable to investigate KB5129195 as the primary suspect before blaming unrelated hardware, firmware, or drivers.

I will test uninstalling KB5129195 as suggested. If removing it makes the system stable again, that would be a much stronger indication that the update is involved.

And honestly, this is where my frustration comes from. Microsoft used to have a reputation for making Windows feel like a stable operating system first. Lately, it feels like Windows is becoming increasingly packed with AI features and other changes that many users never asked for, while basic things like update control, stability, resource usage, and predictable behavior are becoming harder to manage.

I personally don't understand why I need AI integrated into places like File Explorer, and I certainly don't want to assume that these features exist for some hidden purpose such as training AI models on users' personal files. That's my personal opinion, and I understand that suspicion is not evidence. But when a major update causes unexplained system behavior immediately after installation, it makes users much less willing to trust what Windows is doing in the background.

Microsoft is still one of the biggest technology companies in the world. That's exactly why I expect Windows updates to be thoroughly tested and, when something goes wrong, investigated seriously rather than immediately attributing the problem to everything except the update itself.

Hi, Samir Neupane

You are right to question this. A genuine active pause should prevent new restart-requiring updates from downloading or installing until the selected pause date ends. However, the standard pause period is limited to 35 days, so a pause started 2-3 months earlier may have expired or resumed automatically. KB5129195 was an out-of-band cumulative security update, not an optional preview, and its support page states that it downloads and installs automatically through Windows Update.

Your before-and-after comparison makes KB5129195 a reasonable primary suspect, especially since a clean NVIDIA driver installation made no difference.

Uninstall the update, restart, and test the same CS2 match/settings and USB devices. Record FPS, CPU/GPU load, disk usage, memory usage, and whether another colored-screen freeze occurs. If stability returns, use Win + F to submit a Feedback Hub report under Install and Update > Downloading, installing, and configuring Windows Update, include “KB5129195 / build 26200.9457” in the title, and attach the diagnostic data.

The published known issues currently include domain trust and USB Audio Class 1.0 failures, but not the complete performance, storage, memory, USB, and display pattern described here.

Regarding AI, the update notes say its AI components apply only to Copilot+ PCs. They do not support the claim that personal files are used to train AI models.