Someone lit a 15-year fuse inside your computer in 2011

In 2011, someone at Microsoft signed a certificate and burned it into the firmware of millions of motherboards. It had a fifteen year lifespan. Nobody thought much about it, because 2026 was a very long way away.

It’s 2026. On 24 June, that certificate expired. On 27 June, so did the next one.

Nothing exploded. No screen went black. No alarm went off anywhere. That is exactly what makes this interesting.

The most expensive problems in IT rarely announce themselves. They sit on a calendar somebody forgot to keep, which is why IT lifecycle management is worth a lot more attention than it usually gets.

The clocks you cannot see

Your office is full of countdowns. Not the loud kind with a red display, the quiet kind written into firmware, certificates, licence files and support policies years before anyone bought the equipment.

Most of them do not fail dramatically. They fail by simply stopping: the thing that used to protect you quietly stops protecting you, and everything keeps working exactly as before.

That gap between “still working” and “still safe” is where most IT disasters are born. Good IT lifecycle management is the practice of closing it before it opens.

The fuse that went off this summer

Secure Boot is the mechanism that checks your computer starts with software it trusts. That trust rests on certificates baked into the motherboard firmware, and the originals date from 2011.

Three of them expire in stages. Two went in late June. The one that signs the Windows bootloader itself goes on 19 October 2026.

Devices that missed the newer 2023 certificates still switch on and still install regular Windows updates. What they can no longer receive are new protections for the boot process itself. Microsoft calls this a degraded security state. Your users will call it nothing at all, because they will never notice.

Machines shipped from early 2024 already have the new certificates. Older ones need Windows Update to have done the job, and some need a firmware update from the manufacturer that may never arrive.

So the honest question for any business right now is simple: do you know how many of your machines made the switch? That single number is a decent test of whether your IT lifecycle management is real or theoretical. Most companies cannot answer that, and it is checkable in an afternoon.

The deadline in October that gets expensive

Windows 10 lost standard support on 14 October 2025. Plenty of businesses bought themselves a year through Extended Security Updates and moved on.

That year ends on 13 October 2026. Year two costs double what year one cost, per device. Wait too long and you pay for the year you skipped before you get the year you need.

This is what makes IT lifecycle management so painful when it is left to chance. The technical problem is fixable. The financial penalty for noticing late is not.

The one right behind it

Windows Server 2016 reaches end of extended support on 12 January 2027. If that server still handles logins, files, printing or a line of business application, this is not a next-year problem. Server migrations are measured in months, not weekends.

Windows Server 2012 and 2012 R2 are further along the same road, with their final paid extension running out in October 2026.

Stack those three dates next to each other and you can see why sequencing matters. Companies practising real IT lifecycle management are already through the first one. Companies without it will meet all three at once, under pressure, in the same quarter.

The countdowns nobody owns

The famous deadlines get blog posts and vendor emails. The ones that actually take businesses down are smaller, and they fall through the cracks of most IT lifecycle management:

• Your domain name. Registered by someone who left in 2019, on a card that expired in 2023.
• Your TLS certificate. Ninety days of validity is becoming normal. Manual renewal is not a plan.
• The UPS battery. Three to five years of life. It reports itself as fine until the first real power cut.
• Your firewall subscription. The box keeps running. The threat intelligence behind it stops updating.
• The person. Somebody knows the password to the machine that runs payroll. Nobody wrote it down.

None of these are complicated. All of them are invisible until the day they are urgent.

And then there is 2038

Here is the one nobody has diarised.

Huge amounts of software count time as the number of seconds since 1 January 1970, stored in a 32-bit number. That number runs out on 19 January 2038, at 03:14:07 UTC. When it overflows, affected systems do not stop. They quietly decide it is 1901.

Your laptop will be fine. The question is everything else: the building access system, the camera recorder, the industrial controller, the machine on the factory floor with a serial port and a sticker from 2009. Equipment bought today can easily still be running in 2038.

It sounds absurd to plan for something twelve years out. It sounded absurd in 2011 too, and that fuse just went off.

Turning expiry dates into a calendar

The fix is not clever. It is boring, and boring is the point.

Start with an inventory that lists what you own, what version it runs, when its support ends and who is responsible for it. Add every renewal date you can find: domains, certificates, licences, contracts, warranties, batteries.

Then put those dates somewhere with an owner and a reminder that fires early enough to actually do something. Twelve months for a server migration. Ninety days for a certificate. A year for hardware you will need to budget for.

That is all IT lifecycle management really is. Knowing what you have, knowing when it stops, and deciding on your own schedule instead of somebody else’s.

Making IT effortless means watching the clocks for you

At EvolvingDesk we treat IT lifecycle management as part of the job, not a project you have to ask for. We keep the countdowns visible so you never meet one by surprise. We track support dates, certificates, licences and hardware age across your environment, flag what is coming, and plan the move while there is still time to plan it.

We work as your IT partner across the Netherlands, Belgium, Germany and Hungary, with teams nearby in Arnhem-Nijmegen, Eindhoven, Amersfoort and Apeldoorn. We think along, we take the work off your hands, and we make sure the deadlines in your building arrive as scheduled maintenance instead of emergencies.

No surprises. No firefighting. No expired certificates nobody knew about.

Want to know which clocks are already running in your office? Visit evolvingdesk.com and let’s take a look together.