It will not install, or it will not update
Installers that stop partway, definition updates that never complete, and licence keys that are refused have a short and fairly predictable list of causes. Most of them are environmental rather than faults in the software.
The short version
Restart the device first, then check four things: the system clock, free disk space, whether the operating system version is still supported, and whether another security product is present. Those four account for the majority of installation and update failures. Download installers only from the vendor’s own website, and note the exact error code before you start changing anything.
Which failure are you looking at
The three symptoms look similar from the outside and have different causes, so it is worth being precise about which one you have.
| What you see | Most likely area | First thing to check |
|---|---|---|
| The installer starts, then rolls back or exits with a code | Leftovers from a previous product, or permissions | Whether another security product is still installed or partly removed |
| The product is installed but says definitions are out of date | Network, clock, or the update service not running | The system date and time, then the connection |
| A licence key or account sign-in is refused | The account or subscription state, not the software | The vendor’s account area, signed in through a browser |
| The download itself fails or the file will not open | A corrupted or incomplete download | Downloading again from the vendor’s own domain |
The checks that resolve most cases
- Restart, properly. On Windows, choose Restart rather than shutting down, because fast startup can carry the old state across. A restart clears file locks left by a half-finished installation and is genuinely the reason a second attempt often works.
- Check the system date, time and time zone. Secure connections depend on certificates that are only valid between two dates. A clock that is wrong by days, or set to the wrong year after a flat battery, will make update servers unreachable and produce errors that mention certificates or trust. Set the clock to update automatically and confirm the zone is your Australian one.
- Check free disk space. Installers need room for temporary files well beyond the final size of the product, and definition updates need working space too. A drive within a gigabyte or two of full will fail in ways that do not obviously mention space.
- Confirm the operating system version is still supported. Vendors drop support for old Windows and macOS releases, and the installer often refuses with a generic message rather than a clear explanation. The system requirements page on the vendor’s site is definitive.
- Look for another security product, including a removed one. Uninstallers leave drivers and services behind more often than they should. Check Installed apps on Windows or the Applications folder on macOS, and see the conflicts page for removing one properly.
- Download the installer again, from the vendor’s own domain. An interrupted download produces a file that looks complete and is not. Type the vendor’s address yourself or use a bookmark rather than following an advertisement or a search result.
- Try once on a different network. A mobile hotspot for ten minutes will show whether a home router, a school or workplace filter, or a DNS setting is blocking the update servers.
- Record the exact error code before going further. Vendors index their support articles by code, and a code is worth far more to their support team than a description of the screen.
Where the installer comes from matters
Search results and advertisements for popular security products attract impostors, because a person about to install security software is a person about to run an installer with high privileges. Sites that repackage other people’s installers with extras added are a long-standing nuisance, and some are worse than a nuisance.
The rule that avoids all of it is simple: go to the vendor’s own website by typing the address or using a bookmark, sign in to your account there, and download from inside the account area. If you were sent a link, do not use it — navigate to the vendor yourself and find the same thing. The Australian Cyber Security Centre’s guidance at cyber.gov.au covers this pattern in more general terms.
What to avoid while troubleshooting an installation
- Do not disable protection and leave it off overnight because an update failed. If you must pause it to complete an install, resume it as soon as the install finishes.
- Do not use a third-party removal or repair tool found through a search. Vendors publish their own removal utilities; use those or nothing.
- Do not allow anyone remote access to fix an update error, including people who contact you first. Legitimate support does not initiate contact about an error you have not reported.
- Do not buy a licence from a marketplace listing offering keys at an unusual price. Keys from those sources are frequently refused at activation, and there is rarely any recourse.
When it is the licence rather than the software
A refused key or sign-in is an account problem, and no amount of reinstalling changes it. Sign in to the vendor’s site through a browser and look at the subscription state directly: whether it is active, when it expires, how many device slots the licence includes, and how many are currently in use.
Device slots are a frequent and invisible cause. Licences are often tied to devices rather than to installations, and a replaced laptop, a reinstalled operating system or a sold phone can leave a slot consumed by a device that no longer exists. Most account areas allow you to release a device; doing that usually clears the activation failure.
If the account area shows a subscription you did not expect, or a charge you cannot place, the renewals and refunds page covers what to do, and the scam messages page covers the invoices that arrive for subscriptions that never existed.
Approaching the vendor’s support usefully
Support conversations go faster with a short factual summary prepared in advance: the operating system and version, the exact product name and version, the precise error code and message, what you were doing when it appeared, what you have already tried, and whether any other security product has ever been installed on the device. That paragraph saves a round of questions.
Ask for a reference number, keep the correspondence, and note the dates. If the problem eventually becomes a question of getting your money back rather than getting the software working, that record is the thing that matters, and the ACCC’s explanation of consumer guarantees sets out the framework it will be assessed against.
Phones and tablets fail differently
On mobile devices an installation rarely fails in the way a desktop one does, because the app store handles the install. What fails instead is activation: the app installs cleanly, then declines to sign in or reports that no subscription is attached.
Almost always the cause is an account mismatch. The subscription is held under one email address and the app has been signed in with another, or the licence was bought through a desktop purchase and the mobile app expects the vendor account rather than the app store account. Sign in to the vendor’s account area in a browser on the phone and confirm which address holds the subscription before reinstalling anything. The other recurring cause is an operating system version that has fallen below the app’s minimum, which the store listing will state.