If OneDrive is how your team keeps files available across laptops, desktops, and phones, it quietly becomes part of your business continuity plan. People don’t think about it until a laptop dies, a file goes missing, or sync starts behaving oddly.

On August 15, 2026, Microsoft stops providing updates (including security updates) for the OneDrive desktop sync app on Windows 10 version 21H2 and earlier. The app may still run, but it will be stuck on whatever version is installed that day.

What changes on August 15, 2026 (and what doesn’t)

This change is about the OneDrive sync app on older Windows 10 builds, not about OneDrive as a service.

Here’s the plain-English impact.

  • No more security updates for that OneDrive app. PCs on Windows 10 21H2 and earlier will stop receiving new OneDrive desktop app updates after August 15, 2026. Microsoft says the app may continue to function, but updates stop and compatibility is not guaranteed.
  • No more new OneDrive features or fixes on those PCs. Even if the rest of your environment is current, those older machines won’t pick up new OneDrive releases.
  • Windows 10 22H2 (and Windows 11) stays eligible for OneDrive updates. Microsoft’s current requirement to receive OneDrive sync updates is Windows 10 22H2 or Windows 11.

What does not automatically change on August 15:

  • Your OneDrive files don’t disappear. Your data in Microsoft 365 is still there. The risk is on the device side: an out-of-date sync client on an out-of-date OS is harder to trust.
  • Your users won’t all get kicked out of OneDrive that day. Microsoft’s wording is “may continue to function,” which usually means you will see a gradual increase in “weird” issues over time, not an instant shutdown.

Why you should care, even if “it still works”

When OneDrive sync is healthy, it’s invisible. When it isn’t, it shows up as lost time and messy recovery work.

A few real-world failure modes we see:

  • Silent non-sync. A user saves a file, assumes it’s in the cloud, then their laptop fails and the newest version never made it to OneDrive.
  • Conflicts and duplicates. Out-of-date clients can create “conflicted copy” files that waste time and create version confusion.
  • Support dead ends. When you call for help, the first answer is often “update Windows, update OneDrive.” If you can’t update, you’re stuck troubleshooting around the problem.

The goal here isn’t to panic-upgrade everything. It’s to find the handful of machines that are going to become exceptions, then make a clean plan.

Step 1: Find PCs that are at risk (Windows 10 21H2 and earlier)

Start with a simple inventory. You’re looking for any device still on Windows 10 version 21H2 or below.

  • Pull a device list from your management tool. If you use Intune, an RMM, or another endpoint tool, export device name, user, Windows version, and last check-in date.
  • Spot the stragglers, not the average. Most businesses have a “long tail” of older machines: a spare PC at the front desk, a warehouse workstation, a laptop that rarely comes online.
  • Confirm the version on the device (when in doubt). On the PC, go to Settings > System > About, and check the Windows specifications section for the Version.
  • Flag shared PCs. Kiosks and shared workstations are often the last to get upgraded, and they’re exactly where sync problems create confusion.

Deliverable for this step: a short list of affected devices, with an owner and a location for each.

Step 2: Reduce data loss risk before you touch upgrades

Before you upgrade anything, make sure you’re not relying on “sync” as your only safety net.

  • Check OneDrive sync status on each affected PC. Open OneDrive, confirm it says “Up to date,” and look for errors or paused sync.
  • Make sure the right folders are actually in OneDrive. If users keep important work on Desktop or Documents, confirm those locations are included in OneDrive (many businesses use Known Folder Move for this).
  • Verify free space and basic health. Low disk space, failing drives, or a PC that crashes mid-update is how you turn a routine upgrade into a recovery job.
  • Do a quick “can we restore a file” test. Pick one user, delete a harmless test file, and restore it from OneDrive. You’re proving the end-to-end loop works.

If you’re thinking, “We have backups,” that’s good. Still do the quick restore test. Backups and OneDrive solve different problems, and you want both to behave predictably.

Step 3: Choose the fastest upgrade path for each PC

Not every machine needs the same plan. The fastest path depends on what the hardware can handle and how critical the user is.

  • Best case: upgrade Windows 10 21H2 to Windows 10 22H2. If the PC is otherwise fine and you’re not ready for Windows 11, moving to 22H2 keeps the OneDrive sync app eligible for updates.
  • Better long-term: move to Windows 11 (if the device supports it). This is often the right call for laptops that will be in service another 2 to 3 years.
  • If the PC can’t upgrade cleanly: replace it. Old hardware is the hidden tax here. You’ll spend more in labour and downtime than the device is worth.
  • If the PC is “special purpose”: isolate the risk. For line-of-business systems that can’t be upgraded quickly, decide whether that device should be syncing business-critical files at all.

Deliverable for this step: a one-line decision per device (upgrade to 22H2, upgrade to 11, replace, or special handling).

Step 4: Run the upgrade in a way that doesn’t disrupt the business

Treat this like a small project, not a random Tuesday.

  • Schedule by role, not by device age. Upgrade the least disruptive users first, then do executives and customer-facing roles once you’ve proven the process.
  • Protect working hours. Most upgrades go fine, but you want a buffer for the 10 percent that don’t.
  • Have a rollback and recovery plan. Know how you’ll get the user working if the upgrade fails: spare laptop, loaner, or a quick reimage path.
  • After the upgrade, confirm OneDrive is updating. The whole point is to keep receiving OneDrive sync releases. Check that OneDrive is running and healthy.

Step 5: Prevent this from becoming next year’s scramble

Once you’ve cleaned up the current risk, make it harder for devices to drift.

  • Set an “oldest allowed Windows version” policy. Even a simple rule like “no devices more than one feature version behind” reduces surprises.
  • Track exceptions explicitly. If you must keep an older device, document why, who owns it, and what data it is allowed to access.
  • Review quarterly. A 15-minute quarterly check of device versions beats an urgent upgrade rush tied to a vendor deadline.

Want a hand getting this done quickly?

This is a very manageable fix when you treat it as inventory, risk reduction, then upgrades in batches. If you would like help identifying affected PCs and planning the fastest upgrade path with minimal downtime, the Flexnet Networks team can run the project with you.

Sources