Almost every month the workshop gets one call that goes the same way. A small office — often round the back of Haymarket, in Rutland Square, Torphichen Street or up towards the West End — came in on Monday morning, the desktop PC on the corner had installed an update overnight, and now Sage, QuickBooks or the till software will not open. The reception laptop is fine. The two other machines in the back office are fine. It is just this one, and it is the one the whole business runs on. If that is where your morning has gone, this is the pattern we work through when a same-day Haymarket business callout comes in for exactly this.
The reason it deserves its own walk-through and not just a “phone the software vendor” note is that the vendor is almost never the fastest way back to open. Their first-line script will ask you to reinstall, which on business software usually means a licence re-activation and a database restore, and that is a day of work you don’t need. Nine times out of ten the actual fix is smaller, faster and reversible — provided you get to it inside the ten-day rollback window Windows quietly gives you.
Why the Update Broke Only Your One Program
A Windows update is not really one thing. It is a bundle: the cumulative security patch, a serving-stack update, one or two component rewrites, occasionally a whole feature update like 24H2 or 25H1, and lately little servicing tweaks to .NET, the Visual C++ runtimes, WebView2 and the printer driver framework. Any of those components is a hard dependency for at least some business software. Change the plumbing behind an app that assumed a particular version of it, and the app can silently refuse to start, hang on a splash screen, or open with a blank main window and no error.
The reason your other office PCs are fine is usually that they are on slightly different Windows builds or slightly different app versions, and they got the same patch without touching the specific plumbing yours relied on. That doesn’t mean they are safe next month — it means today’s call is about this one machine, and next month it will probably be a different one unless the underlying policy is fixed. That is a wider theme we cover in the small-business IT guide for Edinburgh offices: the piece the business tends to skip is the update policy, and that is the piece that quietly generates most of the emergencies.
The First Thing We Check: Reliability Monitor
Before anything else, we open Reliability Monitor. It has been in Windows since Vista and hardly anyone knows it exists. Press the Windows key, type perfmon /rel, and press Enter. What comes up is a day-by-day timeline of every crash, every failed app, every Windows Update and every driver install, colour-coded with red crosses where things fell over.
On the morning the software stopped working, there is almost always a red cross on the day before — and on that same day, an entry that reads “Successful Windows Update” with a KB number attached. That KB number is the single most useful piece of information for the whole job. Everything else follows from it: whether it is a known bad update, whether the vendor has published a workaround, whether it is safe to roll back, and whether there is a policy setting that would have held it back long enough for the vendor to catch up. This is the same discipline we use on the wider Windows update errors and rollback guide, but the business case turns on identifying that KB fast because the rollback window has a clock on it.
Common Patterns We See on the Bench
Sage 50 hangs on the splash screen after a cumulative update. Nearly always a .NET Framework state problem — the .NET 3.5 optional feature has been switched off or partly stripped, and Sage’s older components can’t find their runtime. Turning “.NET Framework 3.5 (includes .NET 2.0 and 3.0)” back on under “Turn Windows features on or off”, then rebooting, brings it back inside ten minutes.
QuickBooks Desktop opens with a blank main window. The usual culprit is a Microsoft Edge WebView2 runtime version mismatch after a cumulative update. Reinstalling the Evergreen WebView2 runtime from Microsoft’s own download page — not from inside QuickBooks — sorts it, and it takes minutes rather than the hours a full QuickBooks reinstall and file rebuild would need.
An older EPOS or till program throws a “cannot connect to server” error, but the network is fine. This is very often SMB1 being disabled by an update on Windows 11 Pro or the older Home builds. The till software was talking to a legacy Linux samba share or an older Windows Server share using SMB1, and Windows has finally switched it off. Turning SMB1 client back on is a stopgap; the real fix is nudging the server side up to SMB2 or SMB3, which is a separate visit but not urgent.
Windows suddenly can’t see the office scanner or the network label printer. The 24H2 update tightened up WSD (Web Services on Devices) discovery, and older Brother, Kyocera and Zebra units drop off the list. Reinstalling the printer using its IP address rather than WSD auto-discovery gets it printing again in minutes and it doesn’t drop off next time.
A CRM or practice-management client fails with a TLS handshake error. Older business software still pinning TLS 1.0 or 1.1 will fail after a cumulative that hardened the SSL stack. The vendor almost always has a small registry fix or a client update to force TLS 1.2, and until they do, it is a one-line PowerShell that flips SchUseStrongCrypto for .NET.
None of those are guesses. They are the same five conversations we have on the phone before booking the machine in, and knowing which one you are looking at is what turns a two-day panic into a morning fix. This is the same “narrow the fault before touching the settings” discipline we walk through in the Windows update stuck guide.
Rolling Back One Specific Update
Once we have the KB from Reliability Monitor and we can see the software is genuinely on the wrong side of it, the cleanest first move is to remove just that update. Windows still allows this for ten days after install — the “previous version” files sit in C:\Windows.old and C:\Windows\SoftwareDistribution until then and are deleted afterwards, which is why we work fast.
For a servicing-stack or cumulative update the command is wusa /uninstall /kb:XXXXXXX in an elevated Command Prompt, where the number is the KB you identified. For a feature update, Settings → Windows Update → Update history → Uninstall updates offers a “Go back” button that reverts to the previous build. Either way, we then pause updates for at least a week under Settings → Windows Update to stop the machine reinstalling the same patch that afternoon while the vendor is still writing the fix.
What we do not do is roll back updates as a policy. This is a one-off tactical move to get a business open today, coupled with a proper update deferral on the way back out. If the same office needs a rollback every month, the answer is not more rollbacks; it is Windows Update for Business set up correctly, and that means being on Windows 11 Pro.
Home vs Pro: Why the Update Licence Matters for a Business PC
Windows 11 Home will let you pause updates for a maximum of five weeks and give you almost no control over which channel they arrive on. That is fine for a family PC. It is not fine for the machine that runs an accounting practice, a physio clinic, an insurance broker or a small serviced-office reception, because every feature-update window is a lottery on whether critical software still opens on Monday.
Windows 11 Pro gives you Windows Update for Business: defer feature updates by up to 365 days, defer quality updates by up to 30 days, target a specific servicing channel, and set the active-hours window so restarts never happen mid-day. It is a licence upgrade rather than a reinstall — Settings → System → Activation → Change product key — and it takes ten minutes if the machine is otherwise healthy. On any office PC where downtime costs a working morning, we suggest it before anything else.
Setting Update Policy Properly Once You’re on Pro
Once Pro is in place, the settings that actually stop this happening again live in one place: Local Group Policy Editor (gpedit.msc) → Computer Configuration → Administrative Templates → Windows Components → Windows Update → Manage updates offered from Windows Update. Set “Select when Preview Builds and Feature Updates are received” to defer by 90–180 days. Set “Select when Quality Updates are received” to defer by 7–14 days. Both of those windows are enough for Microsoft to catch the biggest issues and for vendors like Sage and Intuit to publish compatibility notes before the update hits the office.
On a two or three-PC office we set the same policy on each machine by hand, because a small business rarely wants the overhead of Intune or a domain controller. On a larger site we’d use Autopatch or a managed policy through our business IT support contract. Either way, the fix that stops the next 3am reboot is the policy, not the rollback. If you’d rather not touch Group Policy yourself, a short remote support session is enough to lock the settings down without a callout.
When It’s Not the Update — It’s a Vendor Bug
Occasionally the story looks like an update problem and isn’t. Sage and QuickBooks both push their own updates in the background, and it’s not unusual for a vendor update to install on Sunday evening and break the app long before Windows applies its own patch on Sunday night. Reliability Monitor will show that too — it lists application install and update events, not just Windows ones — and if the timeline shows a Sage or Intuit update the day it broke, the answer is on the vendor’s side, not Windows’. That’s a job for their support line with the exact version number, or for our software troubleshooting team if it needs sorting today.
Where it gets genuinely awkward is the overlap: a vendor update relies on a Windows component that a cumulative changed the day before. That is the case that actually needs someone comfortable in both worlds, and it is where an office ends up needing an on-site visit round Haymarket to look at the box in front of them rather than a phone-tree.
What To Do Right Now
- Open Reliability Monitor with Windows key → type
perfmon /rel. Find the day the software broke, look for the “Successful Windows Update” entry the day before, and write down the KB number. - Pause Windows Update under Settings → Windows Update for at least a week so the same patch doesn’t reinstall that afternoon.
- Check the vendor’s status page for that KB number. Sage, Intuit and most POS vendors post compatibility notices within a day or two, often with a small workaround.
- Turn .NET 3.5 back on under “Turn Windows features on or off” if Sage or an older Access-based tool is the affected app. This alone fixes a surprising share of splash-screen freezes.
- Reinstall the Edge WebView2 runtime from Microsoft if QuickBooks Desktop opens with a blank window. Do not reinstall QuickBooks first — that’s a much longer job.
- Roll back the specific KB with
wusa /uninstall /kb:XXXXXXXfrom an elevated Command Prompt inside the ten-day window. For a feature update, use “Go back” under Update history. - Upgrade to Windows 11 Pro if the machine is on Home. Ten minutes and it unlocks the deferral settings that stop the next update becoming another Monday morning.
- Set the deferral policy in Group Policy: 7–14 days on quality updates, 90–180 days on feature updates. That’s the setting that stops the whole pattern repeating.
- If it still won’t open, book a business IT support visit and we’ll bring the whole diagnostic kit to the office rather than talk you through it over the phone.
The through-line here is the one we come back to on every office callout: Windows updates are not the enemy, but on a business PC they need to arrive on your schedule, not Microsoft’s default one. Get the licence right, get the deferral policy right, and the “critical software won’t open” call goes from “once a month” to “once a year, and we knew it was coming”. That’s the difference between a Haymarket small business running on hope and one running on a plan.
Last updated: 15 September 2026