Skip to content
Home » Security Basics & Strategy » Why Regular Software Updates Are Your Best Defence

Why Regular Software Updates Are Your Best Defence

Laptop displaying a “Software Update” progress bar with a security shield and padlock, while cyber threats appear in the background, highlighting the importance of timely updates.

When the server asks to install software updates, it is tempting to click “remind me later”. Updates mean a restart, the restart means telling staff to save their work, and there is always the worry that Tally or the printer will misbehave afterwards. But most of what an update fixes is security holes, and attackers move faster than they used to. For a small office, keeping software updated, and keeping the server on a version of Windows that still gets updates, does more for security than almost anything else you can do for free.

What an update actually fixes

Updates (patches) fix bugs, sometimes add features, and close security holes: flaws that let an attacker run their own code, read data or take over an account. Once a fix is published, the flaw is public knowledge. Attackers study the patch, work out what it fixes and go looking for machines that have not installed it.

That gap is short now. Google’s Mandiant team analysed vulnerabilities exploited in 2023 and found the average time to exploit was five days, down from 32 days in 2021 to 2022. Waiting a month for a convenient weekend is no longer a safe habit.

Two lessons from two famous attacks

WannaCry: the patch was already there. Microsoft fixed the file-sharing (SMBv1) flaws that WannaCry used in security update MS17-010, published on 14 March 2017. The ransomware spread around the world in May 2017, two months later. Machines that had installed the March update were protected against its main way of spreading. Machines that had not were encrypted.

PrintNightmare: there was no patch yet. PrintNightmare (CVE-2021-34527), a flaw in the Windows Print Spooler service, is often told as a “should have patched” story, but it was the opposite. It was a zero-day: working exploit code was posted publicly in late June 2021, before any fix existed, and Microsoft shipped an emergency out-of-band update on 6 July 2021. Exploiting it needed a valid user account, but that account could then take full control of the machine. The lesson is that updating fast matters, and so do the things you do between patches: switching off services the server does not need (the advice at the time was to stop the Print Spooler on servers that do not print), keeping accounts few and passwords long, and watching for signs of trouble.

The bigger risk: a server that no longer gets updates

No patching routine helps if Microsoft has stopped writing patches for your version of Windows. This is common in small offices, where the Tally server is often the oldest machine in the building. Check your dates on Microsoft’s lifecycle pages:

Windows versionSecurity updates
Windows Server 2012 and 2012 R2Ended 10 October 2023. Paid Extended Security Updates, for organisations that bought them, run out in October 2026.
Windows Server 2016Extended support ends 12 January 2027.
Windows 10 (a PC used as the server)Support ended 14 October 2025 for Home and Pro.

To see which version you are running, open PowerShell on the server and type:

(Get-CimInstance Win32_OperatingSystem).Caption

If it says 2012, the server has been missing security fixes for years and needs replacing or upgrading now. If it says 2016, you have until January 2027: plan the move to Windows Server 2022 or 2025 this quarter, test Tally and your other software on the new version, and budget for the licence. A busy filing season is the worst time to discover the old server cannot be patched.

A patching routine that works in a small office

  1. Use Patch Tuesday as your calendar. Microsoft releases security updates on the second Tuesday of each month. Install them within a week, with the restart scheduled for the evening or a weekend.
  2. Back up first, and know the backup works. Keep three copies of your data on two kinds of storage, with one copy offline or immutable, and test a restore now and then. The Tally data folder is the first thing ransomware goes for, and the first thing you will want back.
  3. Do not forget the other software. TallyPrime, SQL Server, remote-support tools such as AnyDesk or UltraViewer, PDF readers and browsers on the server all get security fixes too. Keep a short list and check it monthly.
  4. Check that updates really installed. This shows the five most recent Windows updates and their install dates: Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5 HotFixID, InstalledOn. If the newest is more than a couple of months old, something is stuck.
  5. Switch off what you do not use. Old features such as SMBv1 file sharing, unused remote-access tools and the Print Spooler on a server that never prints are flaws waiting for a patch. Our five steps to secure your Windows server cover the basics.

Automatic or manual?

For staff PCs, automatic updates are the right default. For the server, many IT vendors prefer to let Windows download updates automatically but choose the install time, so the restart does not land in the middle of a GST deadline. Either way is fine. What is not fine is switching automatic updates off and then never getting round to installing them by hand. If “we will do it later” has become the routine, switch automatic installs back on.

Between patches

Even a well-patched server has gaps: the days between a fix being published and installed, and zero-days like PrintNightmare that have no fix yet. That is where monitoring helps. Prixl Warden‘s security audit includes a check on how recently Windows Update installed updates and whether Microsoft Defender is running, alongside 27 other checks on the server’s settings. Between audits, Warden watches the event logs and emails you about the signs that usually follow a break-in, such as new admin accounts, new services and a cleared audit log. Warden supports Windows Server 2016 or newer and Windows 10 or 11, so a 2012 server needs upgrading before it can be monitored.

See where your server stands across all 29 checks. Start your 30-day free trial.

Related reading

Leave a Reply

Your email address will not be published. Required fields are marked *