I've been encountering some serious problems with the KB5074109 update at my organization. A few computers are having trouble installing it, and so far, the only solution we've found is to reimage the devices. Trying to install the update from the catalog hasn't worked either, and I've attempted numerous other methods, including using the disk restore health command to fix corrupted files noted in the CBS logs, but nothing seems to help. My tier 1 support team is hesitant to reimage the computers, and now it's fallen on me as a tier 3 support, which feels a bit ridiculous. If anyone has experienced something similar or has suggestions, I'd really appreciate your insights!
3 Answers
Yep, our experience with patching has been both hilarious and fortunate. Anything that was deployed ended up getting pulled back in Intune, saving us from a lot of headaches.
Same here! I had to block the KB5074109 update for one user because it broke Adobe InDesign for them. The problems are pretty well documented, so I wasn't surprised to see it cause issues.
Oh man, dealing with the January 2026 cumulative updates was a nightmare for us too! We're still seeing Windows 11 machines randomly restarting instead of shutting down—super frustrating! Thankfully, we haven't had to deal with KB5074109 yet since we're on 23H2.
I get it! This is actually the first major issue we've faced since upgrading to Windows 11. Just a couple of months ago, one user reported the issue, and now we have six affected machines and even a VM. I’m using that VM for testing since the user hasn’t touched it.
Wow, I wish our company allowed us to delay updates for a bit. I only get a two-week window after Patch Tuesday to push everything!