If one Windows computer runs the only copy of a critical app, do not use it as the first place to discover whether an update causes trouble.
Updates still need to be installed because they fix security and reliability problems. Test them on a suitable device first, check the work staff actually do, then continue the rollout.
Know which systems matter most
Start with a list of the programs and equipment the business cannot operate without. Include accounting software, job management, point-of-sale systems, databases, printers, scanners and any custom applications.
Record the current software version, the computers that run it and the vendor's support details. Check whether the vendor supports your version of Windows and publishes update warnings.
Protect the data before testing
Confirm that important files and systems are backed up before making changes. A backup should be separate from the computer being updated, and someone should know how to restore it.
For critical systems, test a restore before the update. A successful backup message does not prove that the required data can be recovered.
Update a small group first
Choose one suitable computer to receive the update before the rest of the business. It should use the same Windows and application versions as the other machines, but it should not be the only computer capable of running a critical task.
A separate test environment may be appropriate for complex or custom software. Keep test data away from live customer records and make sure automated emails, payments or scheduled jobs cannot run by mistake.
Check real business tasks
Opening an application is not enough. Test the work staff actually do:
- open, change and save a common file
- create a sample quote or invoice without sending it
- connect to the required database or shared folder
- print, scan or run another important device-dependent task
Ask the staff who use the software to complete the checks. They are more likely to notice a missing button, slow process or unusual result.
Use a short, controlled delay
Windows may allow updates to be paused or scheduled. The available controls depend on your version and how the devices are managed.
Use a delay only long enough to test and respond to a known compatibility issue. Security updates should not be left unresolved without a clear reason and plan.
If an update causes a problem
Stop the wider rollout and record what failed. Check the software vendor's support information and contact them with the Windows version, update details and error message.
Do not rely on compatibility mode as a general fix. It may help with some older desktop programs, but it will not solve every driver, database or security problem. If software is no longer supported, plan its replacement rather than building the business around a temporary workaround.
An update can sometimes be removed or rolled back, but that also removes its fixes. Get advice before doing this on a critical system.
Make updates routine
Document who approves updates, which computer receives them first and what must be checked. Schedule the work when key staff are available and the business can tolerate a short interruption.
If updates are being delayed because nobody owns compatibility testing, book a Windows update planning consultation with JCPIT Support. We will identify the critical apps, nominate a safe test group and document the checks needed before the wider rollout.
