Build 19045.4472, KB5037849 out to Release Preview.

2024-05 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5037849) broke my updates (couldn't get the security update 1.413.53.0) and made my keyboard act weird as heck, I am still not sure if this was exact root cause for sure though. All I know is that whenever I have this "Optional quality update" installed, it breaks my stuff.

Currently uninstalled the quality update using windows troubleshooter, and the issue has not occurred again since. I'm just putting this out there because it's my first time experiencing issues with the Optional quality updates and no one seems to be talking about it.

I just hope that when the final build gets pushed that it won't break my key inputs again. Also, I know for a fact that this is not a hardware or driver issue. I troubleshooted them accordingly and the only culprit I can find is KB5037849. It'd be funny if it's fine for now and it never was the updates' fault, but as of now that's not the case. I will provide an update if this happens.

My current Windows 10 is Build 19045.4474; I have no issues at all with Security updates nor with my keyboards.

Edition Windows 10 Pro

Version 22H2

Installed on ‎4/‎4/‎2024

OS build 19045.4474

Experience Windows Feature Experience Pack 1000.19058.1000.0

2024-05 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5037849) broke my updates (couldn't get the security update 1.413.53.0) and made my keyboard act weird as heck, I am still not sure if this was exact root cause for sure though. All I know is that whenever I have this "Optional quality update" installed, it breaks my stuff.

Currently uninstalled the quality update using windows troubleshooter, and the issue has not occurred again since. I'm just putting this out there because it's my first time experiencing issues with the Optional quality updates and no one seems to be talking about it.

I just hope that when the final build gets pushed that it won't break my key inputs again. Also, I know for a fact that this is not a hardware or driver issue. I troubleshooted them accordingly and the only culprit I can find is KB5037849. It'd be funny if it's fine for now and it never was the updates' fault, but as of now that's not the case. I will provide an update if this happens.