Photo by Devin Pickell on Unsplash
Every month, Microsoft releases a batch of security patches. Most slip through quietly in the background. Occasionally one of them breaks something, and this month that something is the connection between a Windows 11 machine and the network it is supposed to trust. For businesses where that connection is how staff start their working day, the failure lands at the worst possible moment.
What Actually Happened
Microsoft's latest Windows 11 security update is causing what is known as a domain trust failure on some business systems. A domain trust relationship is how a Windows computer identifies itself to the central server that manages your network. When it works, staff log in and get access to shared files, printers, and business software without any fuss. When it breaks, the computer and the server stop recognising each other. The result is staff hitting error screens or being unable to log in entirely, usually right at the start of the working day.
Microsoft has confirmed it is investigating and a fix will follow. That part will resolve. What is worth thinking through is the wider question this kind of incident raises for any UK small business running Windows devices.
Does This Affect My Business?
Not every business will feel this. The problem is specific to machines joined to a Windows domain, which typically means organisations running a Windows Server on-premises or a hybrid setup managed through Active Directory. If your business runs a straightforward Microsoft 365 arrangement where staff log into cloud services with an email address and password, this particular fault is unlikely to reach you.
If you have a traditional office network with a server in the building, or a setup where an IT provider controls a central domain, it is worth checking whether any machines are showing login or network access problems following a recent update.
The Real Issue: How Should Small Businesses Handle Patches?
The natural reaction when a patch breaks something is: hold off on updates until they are confirmed stable. That instinct is understandable. Acting on it without a proper process in place creates a different and often larger problem. Security patches exist because vulnerabilities are being actively exploited right now, and delaying them leaves a window open for attackers to walk through.
The answer is not to stop patching. The answer is to patch in a way that gives you control. For a small business without a dedicated IT team, that means three practical things:
- Know what is running on your network. You cannot manage what you cannot see. A clear picture of your devices, operating systems, and current update status is the starting point for any sensible approach to patching.
- Have a rollback option ready. Knowing how to reverse a bad patch quickly is worth far more than hoping this never happens. That relies on having current, tested backups that are separate from your main systems.
- Do not rely on manual or ad hoc updates. Staff applying updates whenever Windows prompts them, or machines left to update at random overnight, is not a patch management process. A structured approach tracks what needs updating, applies changes in a controlled window, and monitors for failures before they become a full outage.
This is exactly what Automated Patch Management does for businesses that do not have the time or resource to manage it themselves. When something like this month's update causes a fault on some machines, the right response is quick: identify what was affected, apply a workaround, and monitor for the vendor's fix. That response only happens fast when there is already a system watching your patch state in real time.
Backups Matter More Than Most Businesses Realise
A domain trust failure is recoverable. But if a patch causes deeper system damage, or if an attacker uses the gap between a new vulnerability and its patch to get into your network, how quickly you recover depends entirely on what you have backed up and how recently. If you are not certain your backups are current and have been tested recently, that is the thing to address alongside patching.
We have written before about why a backup alone may not be enough if it has not been set up with recovery in mind. It is worth a read alongside this one.
What to Do Right Now
If you manage your own Windows devices, check whether any machines received a recent update and whether staff are reporting login or network access problems. Microsoft's support pages carry the latest workaround guidance as the investigation continues.
If a managed IT provider looks after your systems, one question is all it takes: were any of our machines affected, and if so, what has been done? That should be a quick, clear answer.
For the longer term, this is a useful nudge to look at how patching is actually handled across your business. Vulnerability management is not a one-off exercise. It is an ongoing process of knowing what is running, what needs updating, and what your recovery options are when something unexpected happens. That process does not need to be complicated, but it does need to exist.
If you want to talk through what a sensible approach looks like for a business your size, get in touch with the team and we can walk you through the options.