DO NOT INSTALL THAT UPDATE!
(updated 12/10/2024 see at bottom of article)
At least on two of my computers, it completely disabled the USB ports, leaving me without mouse, keyboard, bluetooth and any way of giving any input to the computer to do anything.
Luckily I had Google Remote Desktop installed previously so I could take over the screen and fix the issue.
Not everyone, but others do have the same issue, see:
https://techcommunity.microsoft.com/t5/windows-insider-program/major-problem-with-version-23h2-for-x64-based-systems-kb5043145/m-p/4256541
I also posted my issue here:
https://www.elevenforum.com/t/kb5043145-windows-11-cumulative-update-preview-build-22621-4249-22h2-and-22631-4249-23h2-sept-26.28865/
So what happened:
Windows 11 23H2, automatically installs KB5043145 and after the reboot leaves you without any USB.
SPECS FOR MY PC
Device name ~
Processor Intel(R) Celeron(R) N4500 @ 1.10GHz 1.10 GHz
Installed RAM 16.0 GB (15.8 GB usable)
Device ID ~
Product ID ~
System type 64-bit operating system, x64-based processor
Pen and touch Touch support with 10 touch points
Edition Windows 11 Home
Version 23H2
Installed on 9/16/2023
OS build 22631.4169
Experience Windows Feature Experience Pack 1000.22700.1034.0
I first suspected a hardware failure, but since it was after a Windows update I started searching for the issue and found I was not the only person with a USB problem. A second PC (same specs) had the same issue after I executed the same update, so that ruled out a hardware issue for me.
So my question was, how to roll-back the update? Well:
so I found this:
then hit Uninstall …
…and was very happy I was able to solve this.
Now I have another computer (different specs) waiting on a reboot for the same update, so I wonder if that one will survive the update. I was lucky, however if you do not have a remote desktop installed, I have no idea how to get this update uninstalled and fixed!
So, except for whoever gave the okay for this update at Microsoft (because, yes, you did cost me three hours of my time trying to figure this one out…)
update 12/10/2024:
I had paused all updates, but got a message that the issue was solved. I received the update of KB5044285 (skipped KB5043145 completely) and that “works on my machine”. Problem solved!
Have a nice day everyone!