IT ISSUE · APPLICATIONS AND SOFTWARE
Application stopped working after an update
The update is a clue, not the whole answer. Often two vendors' products have stopped agreeing.An application that worked on Friday doesn't work on Monday, and an update landed in between. The timing is a useful clue and it doesn't prove the update caused the fault. What broke is usually a dependency between two products maintained by two companies who don't test against each other.
What you may notice
- The application worked yesterday and nothing else changed.
- It fails on updated machines and works on ones that lagged behind.
- A plug-in or add-in has disappeared.
- It opens but a specific feature now fails.
- The vendor's support page already mentions it.
Establish what changed, then who owns the fix
We identify which update landed, whether the fault is in the application, the operating system or something between them, and whether the vendor has acknowledged it.
Rolling an update back feels decisive and is usually the wrong move, unless the vendor itself advises it: it reintroduces whatever the update was fixing, and the machine stays behind until somebody remembers. Where a vendor has broken something, the honest answer is that the fix is theirs, and our job is a workaround you can live with until they ship it rather than a change to your systems that hides it.