Your workshop software may work while relying on an extension, an old computer or an access setup nobody knows how to recreate. I would review those dependencies before replacing the reception computer. The question is simple: if everything has to be reinstalled tomorrow, what is missing to resume booking appointments, checking records and invoicing?
There is no shared date when these five components will stop working. Each manufacturer maintains its own timetable, and each installation needs its own checks.
1. The extensions that help you work
Open the extensions section in the browser you actually use. Note which ones are involved in a workshop task, who maintains them and whether they show compatibility warnings. Having them installed is not enough: check the task that depends on them.
For Chrome, the Manifest V2 documentation places removal of the enterprise exception at Chrome 139. Chrome 138 was the last version that could support those extensions with the corresponding enterprise policy. For Edge, the timetable consulted on 10 October 2026 expects the phase-out for enterprise customers to begin in early 2027. These have different scopes; I would not apply one browser's timetable to the other.
If an extension is essential, ask the provider for a compatible version and a test of the task. Keeping an old browser to retain it leaves another dependency unresolved.
2. The operating system and devices
Note the exact Windows version and the management software version. Microsoft ended extended support for Windows 7 in January 2020 and Windows 8.1 in January 2023. That does not establish when a particular installation will fail.
Before replacing anything, ask for written compatibility confirmation for the devices you use: a printer, reader or diagnostic equipment, if applicable. I would not assume they have all stopped supporting the old system or will all work on the new one. Also prepare the licence, installer and a test of data recovery for the program.
3. Connections to other services
List what comes in and goes out: appointments, customer notifications, parts orders or invoices. For each connection, identify who maintains it and how you find out when it fails.
As a proposed test, I would send a test record and check that it reaches its destination, without accidentally creating a real order or notification. Ask the provider to organise that test and confirm the compatible version. An error-free screen does not establish that the data arrived. Write down a fallback procedure for any task that cannot wait.
4. Access that requires a legacy mode
If an application asks for Internet Explorer, Java or ActiveX, ask exactly which component it needs. I would not conclude that any update will disable it. Microsoft documents an Internet Explorer mode in Edge that supports certain ActiveX controls, including Java, for specifically configured sites.
The existence of that mode does not establish support for your application or its components either. Ask the manufacturer for current requirements, who is responsible for maintenance and an alternative way to consult records if access fails.
5. Connection warnings
On web portals, check the address and the browser's connection information. Do not look for a green padlock as a universal condition. Chrome's current help page explains indicators and warnings. Chromium explains that the HTTPS indicator does not establish a site's trustworthiness. Also check that the address belongs to the portal you want to open.
If a privacy warning appears, save its text and the address, and consult support before entering data. A warning can have different causes; it does not establish by itself that a certificate has expired. This check does not inspect the management software's internal connections either.
I would finish with a short sheet: dependency, affected task, person responsible and test still needed. Start with anything that would prevent you serving customers or invoicing. A list with owners and tests helps you decide what to review first.
Sources
- Chrome: Manifest V2 phase-out — Accessed on 10-10-2026.
- Edge: Manifest V3 timetable — Accessed on 10-10-2026; updated on 15-09-2026. Phase-out for enterprises expected to begin in early 2027.
- Microsoft: Windows 7 lifecycle — Accessed on 10-10-2026.
- Microsoft: Windows 8.1 lifecycle — Accessed on 10-10-2026.
- Microsoft: Internet Explorer mode in Edge — Accessed on 10-10-2026.
- Google Chrome: connection information and warnings — Accessed on 10-10-2026.
- Chromium: meaning of the HTTPS connection indicator — Published on 02-05-2023; accessed on 10-10-2026. A secure connection does not establish a site’s trustworthiness.
If you want to review a dependency that is holding up a workshop task, tell me which one through Let’s talk.