SoftDL

Windows 11 KB Update Broke Printing Again: How to Roll Back the Patch Before Monday

Review

The September 2026 Windows 11 security updates broke Always On VPN connections. Microsoft has confirmed it. If your users work remotely and connect through a VPN tunnel that’s supposed to come up on its own, some of them are going to open their laptops Monday morning and find nothing works. The tunnel just sits there. Maybe it connects and immediately drops. Maybe it never negotiates at all.

This is the third or fourth update in the past year that has caused problems for people I support. I’ve stopped being surprised. What I haven’t stopped doing is keeping a rollback plan ready before the patch lands. Here’s how to undo this one if it’s already on your machines, and how to buy yourself time if it isn’t.

First: figure out if you’re actually affected

Not every Always On VPN setup is going to fail. Microsoft hasn’t published a full list of which configurations are hit, but from what’s been reported, the failures are concentrated around device tunnels and user tunnels that rely on automatic connection triggers. If your VPN client connects manually and stays connected, you may escape.

Check the obvious things before you blame the update. Open Event Viewer and look under Applications and Services Logs, then Microsoft, then Windows, then the VPN client log if your vendor writes one. Most enterprise VPN clients (Fortinet, Palo Alto, Cisco AnyConnect, the built-in Windows VPN client) do log connection attempts somewhere. If the timestamp on the failure lines up with when the update installed, you’ve got your answer.

Also check the Windows Update history directly. Settings, Windows Update, Update history. Note the KB number and the install date. Write it down. You’ll need it in a minute.

Roll back the specific KB, not the whole update

You don’t want to uninstall everything. You want to remove one update. Here’s the sequence I use:

  1. Open Settings and go to Windows Update, then Update history.
  2. Click Uninstall updates. This opens the classic Installed Updates list.
  3. Find the KB from September 2026. It’ll be listed under Microsoft Windows.
  4. Select it and click Uninstall. The machine will reboot.
  5. After it comes back, immediately pause updates so Windows doesn’t reinstall the same patch overnight.

Pausing is the part people skip. If you uninstall and walk away, Windows Update will happily put it back within a day or two. In Settings, Windows Update, there’s a Pause updates option. Use it. The maximum pause varies by edition, but a few weeks is usually enough to wait for a fix.

If the GUI uninstall fails (it does, sometimes, especially on machines that have had several updates stacked), fall back to the command line. Open an elevated Command Prompt and run:

  • wmic qfe list brief /format:table to list installed hotfixes and confirm the KB number
  • wusa /uninstall /kb:XXXXXXX to remove it, replacing the Xs with the actual number

The wusa tool will prompt for a reboot. Let it. Don’t force anything.

If the uninstall won’t complete

Sometimes the rollback stalls at a certain percentage and then reports failure. When that happens, I go to the DISM route. From an elevated prompt:

  • dism /online /get-packages to list the package name associated with the update
  • dism /online /remove-package /packagename:PACKAGE_NAME to remove it

The package name is long and ugly. Copy it carefully. This method is slower than wusa but it tends to work when the standard uninstaller throws an error. I’ve used it on machines where the Windows Update database was corrupted from an earlier failed install.

One more option if DISM also refuses: System Restore. If the machine has restore points enabled (many do by default on Windows 11, but not all), rolling back to a point before the update is the cleanest path. It takes longer and you lose anything installed since, but it’s reliable. Check for available restore points before you start, not after you’re already in trouble.

Stop it from landing on the machines you haven’t touched yet

If you manage more than a handful of PCs, chasing each one after the fact is a waste of a weekend. Block the update at the source.

For domain-joined machines, use Group Policy or Intune to defer quality updates. In the Windows Update for Business settings, you can push the deferral out by a set number of days. Setting a 15 or 30 day deferral on quality updates gives you a buffer every month, not just this one. I’ve been running a 15 day deferral on most of my clients’ machines for over a year and it has saved me from at least three broken-update fire drills.

For standalone machines (the small office that has no domain, or the owner’s laptop), the Pause updates button is the only tool you’ve got, and it requires someone to click it. If you’re the one supporting those users, either remote in and pause it yourself or send them a short, plain instruction. Do not assume they’ll read a long email. Two sentences and a screenshot works better than a paragraph.

What about the VPN side?

Rolling back the update fixes the immediate problem. It doesn’t fix the underlying fragility. Always On VPN depends on a lot of moving parts (certificate trust, the NPS or RADIUS server, the client’s connection profile) and any one of them can break after a patch.

While you’re in there, verify the basics on one affected machine: that the VPN profile is still present, that the certificate hasn’t expired, and that the client service is running. If the update broke the connection, the rollback should restore it. If it didn’t, you’ve got a separate issue and you need to know that before you spend hours uninstalling patches for nothing.

Keeping a note for next time

Every time this happens, I add a line to a plain text file I keep on my own machine: the date, the KB number, the symptom, and the fix that worked. It’s not elegant. But when a user calls me six months from now with the same description, I can search that file and know in thirty seconds whether I’ve seen it before. The September 2026 VPN break is going in there. So is the next one, because there will be a next one.

If you haven’t already uninstalled it, do it now rather than waiting for Monday morning. The users who call you at 8 a.m. will not be patient, and you won’t want to be troubleshooting a rollback while they’re standing over your shoulder.