How to fix January Updates for Windows Server 2012r2, 2016, 2019
The latest updates for Windows Server for January has caused multiple issues across the board for Microsoft’s brand of server software. Reports of crashes, loss of data and boot loops are the current talk of the town in the various subreddits and forums for system administrators as they try to recover things.
Luckily, the smart Alecs over at the SysAdmin subreddit has already gotten to the bottom of it and it appears to be centralised around three updates across each version. The affected versions are:
- KB5009624 or KB5009595 – Server 2012
- KB5009546 – Server 2016
- KB5009557 – Server 2019
The updates were just routine for the operating system, with Microsoft stopping the rollout of the updates before it hit all servers across the globe using these versions. If you have updated to these versions and are still experiencing issues, you might want to run the following commands and then redo the update at another point.
Deals season is here folks, and with it comes huge savings on some of the market's most popular hardware. Below, we be listing today's best PC hardware deals, including GPUs, CPUs, motherboards, gaming PCs, and more.
- ASUS TUF NVIDIA RTX 5080 Was $1599 Now $1349
- ASUS TUF RTX 5070 Ti Was $999 Now $849
- ASUS TUF ROG Strix XG27ACS Was $349 Now $329
- TCL 43S250R Roku TV 2023 Was $279 Now $199
- Thermaltake LCGS Gaming PC Was $1,799 Now $1,599
- Samsung Odyssey G9 (G95C) Was $1,299 Now $1,000
- Alienware AW3423DWF Was $699 Now $549
- Samsung 77-inch OLED S95F Was $4,297 Now $3,497
- ASUS ROG Strix G16 Was $1,499 Now $1,350
*Prices and savings subject to change. Click through to get the current prices.
Open the command line and then run these commands, followed by a restart. One user did report that it took 15 or so minutes for the server to allow them to get past the 100% mark on the uninstall and reload.
2012r2: wusa /uninstall /kb:5009624 or wusa /uninstall /kb:5009595
2016: wusa /uninstall /kb:5009546
2019: wusa /uninstall /kb:5009557
If you are currently in a bootloop, you’ll want to look into either disconnecting the Exchange Server or any affected DCs, which should allow you to load in without it continuing to reboot.