Our work laptops are still on Windows 11 24H2, and I saw that it stops getting updates Oct 13. Do I have to upgrade them by that date, or does that only mean regular security and feature updates end?
I’m not clear on whether “unsupported” means the computers stop working normally or just become riskier to keep using. Is there any grace period for a small work team, or does the upgrade need to happen before Oct 13?
They will not stop working on October 13, 2026.
For Windows 11 Pro, that date means 24H2 reaches end of servicing. The laptops will still boot, run programs, access files, and connect to the network. What stops is Microsoft’s routine security fixes, bug fixes, and support for that release. The risk grows after the next newly discovered vulnerability goes unpatched, so “unsupported” is a security and compliance issue rather than a shutdown switch.
Check the Windows edition before planning anything. Work laptops often use Pro, but 24H2 Enterprise and Education remain supported until October 12, 2027. Enterprise LTSC has a different lifecycle again. You can confirm the edition under Settings > System > About, or run winver.
There is no normal small-business grace period for Pro. The October update should be the final scheduled update, but I would not wait until deadline day. Upgrade a couple of representative laptops first, test your VPN, security software, printers, and business apps, then roll it out to the rest. Keep backups and recovery keys handy.
So yes, plan to move Pro machines to a supported Windows release by then. Being a few days late will not break them, but deliberately leaving work systems unsupported is hard to justify, especially if they handle customer data or must meet insurance or compliance requirements.
Do not rely on company-laptops to upgrade themselves before cut-off date. Intune / Group Policy / WSUS may be holding them back on 24H2. Pro machines will continue to run, but monthly security and quality fixes for this release will end. Get the person responsible for update-checking to look at their target-version-policy instead of doing it manually for every pro-laptop.
A laptop you own personally can simply be upgraded when convenient, while a company-managed laptop may be held on its current release for a reason. That difference matters here. I would not run Microsoft’s upgrade assistant or install a newer release manually unless whoever manages the machines approves it.
For ordinary Windows 11 Pro, October 13, 2026 is the end of monthly servicing for 24H2. It is not an expiration date for Windows itself. The computers should continue operating, but that release will no longer receive the usual security patches, reliability fixes, time-zone changes, or Microsoft support after its final update.
So “have to” depends on what you mean:
The detail I would check is why they are still on 24H2. An update policy may intentionally keep them there while a newer release is tested against your VPN, disk encryption, endpoint security, accounting software, or other company tools. A compatibility hold could be involved too. Bypassing either can leave a laptop in the awkward position of running a supported Windows release while no longer matching company policy.
Ask whoever handles the devices which edition is installed and whether a feature-update deployment is planned. If there is no IT person, check the edition and management status before changing anything. Since the cutoff is only a few weeks away, this is the time to settle that question, but there is no need for everyone to panic-upgrade on the morning of October 13.
Some minor date correction: Microsoft currently has Home and Pro ending support on October 13, 2026, and Enterprise and Education ending the same on October 12, 2027. So the edition is more important than the fact that these machines are “work laptops.” A company owned machine could run Pro.
For Pro, it is about operational, not mechanical, deadlines. A fully patched laptop will not magic itself into being dangerous at midnight or refuse to sign in the next morning. It will simply miss out on future improvements. That might not come right away, but ultimately there will be a vulnerability, certificate switch, or reliability fix the old release just won’t see. Security audits and cyber-insurance questionnaires are often less forgiving of “it still turns on” than users are.
The good news is that transitioning from the release you have to the one you want is usually a small enablement package plus a reboot. It is not necessarily the giant reinstall project Microsoft’s version naming makes it seem like. Machines need recent cumulative updates before anything, and management policy or a compatibility hold can keep the feature update from ever coming up.
Be careful on the Windows Update screen after support ends. “You’re up to date” could simply mean Windows does not have anything it is currently allowed to offer for that machine. It does not confirm the installed release is still supported. Check the version after the rollout rather than trusting a green check mark to get everything sorted.
I would not have employees start beating their machines trying to force the upgrade. Whoever owns the laptops should approve and push the next supported release and confirm that every single machine went through with it. If no one owns the laptops, schedule the update rather than pretending October 13 is a ceremonial date that can be admired and ignored.
Realistically, a work laptop that slides a few weeks past that date won’t catch fire. The problem is that ‘a few weeks’ tends to quietly become ‘next spring’ because nobody actually owned the decision. That drift is the real risk, not October 13 itself.
@nodeguru nailed the part everyone skips: the machines probably aren’t going to move themselves, and there may be a policy pinning them to their current release on purpose. But here’s what nobody’s asked directly. You keep saying ‘our work laptops,’ which makes me wonder whether there’s a real IT setup behind them or whether you’re the closest thing your company has to one. That answer changes everything. If some MSP or internal admin manages these, your job is a two-line email asking which edition is deployed and whether a feature-update rollout is scheduled, then you sit back. If nobody manages them, you’re it, and forcing upgrades one laptop at a time is a bad way to find out your accounting software or VPN client hates the newer build.
Do the boring check first. Run winver on a couple of them and see if they’re Pro or Enterprise, because that alone tells you whether your deadline is next year or the year after. If they turn out to be Pro and it’s on you, don’t treat the update as a same-day emergency. Pick one non-critical machine, get its cumulative updates current, let the feature update land, and actually use it for a week against your real tools before touching the rest. Better to burn one test box than to brick a room full of them chasing a date that was never a hard shutoff to begin with.
The hidden failure point is the laptop that has never checked in. There is always a chance that a loaner in a cabinet, an employee’s rarely used spare, or an offsite machine is on the old release.
Nothing stops working at the cut-off – on Pro, that means Microsoft stops producing new monthly fixes for that release after the final servicing update and you want to avoid keeping machines on a release that will stop being supported. You need to get those machines forward – and the normal destination is 25H2, which is an enablement update from 24H2 (a restart, not a full reinstall). Do not try to target 26H1 for these laptops – that’s for newer devices and it is not offered as an in-place upgrade from 24H2.
I would pull an inventory listing edition, Windows version, last check-in, and pending-restart status, then upgrade the machines I can reach. Separately, I’d track down the missing ones. Then, confirm the reported version – do not consider a successful deployment command as proof of deployment if the version is still incorrect, because that will be the devices most likely to cause a support headache later.
First thing, figure out who signs off on these laptops before you run anything. If your company reimburses them or has any kind of managed setup, ‘do I have to upgrade by Oct 13’ isn’t really your call to make, and touching them could step on a rollout that’s already scheduled. @xrustylynxx is right that the ownership question decides everything else. Sort that out and half your worry disappears.
On the actual deadline: nobody has to do anything on the 13th. The Pro release just stops getting monthly fixes. Your machines boot the same on the 14th. The thing I’d push back on slightly is the framing that this is mostly a compliance headache. It is, but the more boring problem is drift. A machine that misses patches for six months isn’t dangerous because of one dramatic exploit, it’s dangerous because it quietly falls behind on a stack of small stuff and nobody notices until something else breaks.
Here’s a caveat I didn’t see raised. The enablement package to the next release isn’t guaranteed to show up just because you want it. Older or oddly configured laptops can sit under a compatibility hold, usually a driver or a storage/graphics thing, and Windows Update will happily say everything’s fine while never offering the feature update. If you’ve got a couple of machines that stubbornly won’t move, that’s usually why, not user error.
If it turns out these are yours to handle, my honest take is don’t overthink it. Pull one laptop that nobody would miss for a day, get it fully patched, let it move to the newer release, then actually open your accounting app, connect the VPN, print something, and log in with your normal account for a couple of days. If it survives that, roll the rest whenever suits you. The date on the calendar matters far less than confirming your real tools still work on the newer build.
And check the edition first, obviously. If these are Enterprise or Education you’ve got a whole extra year and this entire thread is a next-year problem.