If you manage IT for an organization with legacy Office files, you already know what Windows 11 24H2 did. Macros silently blocked. Access databases that wouldn't open. ActiveX controls showing blank placeholders where buttons used to be. Support tickets from every department, all with the same root cause: a Windows update that nobody in IT was warned would break production files.
Windows 11 25H2 is on the horizon. This article breaks down what 24H2 actually broke, what patterns suggest 25H2 will change, and how to scope the migration work before the update lands on your fleet.
Before we can predict 25H2, we need to understand exactly what 24H2 did. The breakage fell into five categories, each with different fix complexity:
| Category | What Broke | Scope | Fix Complexity |
|---|---|---|---|
| Jet 4.0 Removal | .mdb databases couldn't open | All .mdb files on 64-bit systems | High (requires .accdb migration) |
| MOTW Expansion | Macros silently blocked in OneDrive-synced files | Any .xlsm from cloud-synced folders | Low (Trusted Locations fix) |
| API Deprecation | VBA Declare statements hard-blocked | .xls/.xlsm with 32-bit API calls | Medium (PtrSafe migration) |
| ActiveX Changes | Controls unregistered or broken | Files with non-Forms-2.0 controls | Medium-High (per-control fix) |
| COM Registration | Late-bound objects failed to create | VBA using CreateObject with legacy CLSIDs | Medium (registry investigation) |
The common thread: Microsoft didn't remove support for modern Office file formats. Every change targeted legacy formats, legacy runtime components, or legacy security models. The message is consistent — modern formats are the safe zone.
Microsoft hasn't published full 25H2 compatibility notes yet. But based on Insider Preview builds, Microsoft's published deprecation roadmap, and the trend line from 22H2 through 24H2, here's what IT teams should plan for:
Each update since 22H2 has expanded where Mark of the Web flags are applied and how strictly they're enforced. The 24H2 change that flagged OneDrive-synced files caught many organizations off guard. Expect 25H2 to extend MOTW to additional scenarios — possibly SharePoint-direct-access files, files opened from Teams channels, or files copied from external USB devices that were previously exempt.
For IT teams, this means your Trusted Locations policy needs to be comprehensive. Don't just add the folders that are causing problems today — add every location where your users store macro-enabled files.
The 24H2 update converted several VBA API deprecation warnings into hard blocks. This pattern is likely to continue. Functions that still work in 24H2 but generate logged warnings may become hard errors in 25H2. Particularly at risk:
SendKeys — already unreliable on Windows 11, may be blocked entirely in enterprise-managed environmentsShell — subject to Group Policy overrides; 25H2 may extend blocking to non-managed machinesCreateObject calls for objects with deprecated CLSIDsDeclare statements that slipped through 24H2's enforcementIn 24H2, several ActiveX controls were restricted — they stopped working but the OCX files were still present on the system. In 25H2, Microsoft may remove the underlying files entirely for controls that have been deprecated for multiple release cycles. The WebBrowser control (already non-functional since IE's retirement) and the FlexGrid control are the most likely candidates for complete removal.
The BIFF8 format handler (which reads .xls files) has been in compatibility mode for nearly two decades. Each update subtly changes how edge cases in the binary format are handled. Files that were created by third-party software using non-standard BIFF8 features are at increasing risk of rendering incorrectly or failing to open.
LegacyLeaps's batch scan mode lets you point at a network share and get a complete inventory of legacy files, VBA dependencies, and risk levels across your entire organization. Know the migration scope in hours, not weeks.
IT Team Bulk PricingFor IT teams, the migration isn't a single task — it's a project with discovery, prioritization, execution, and validation phases. Here's how to scope it:
Run a file inventory across all shared drives, user home directories, and cloud-synced folders. You need a count of:
This inventory is your migration scope. Without it, you can't estimate effort, timeline, or cost.
Not all files need to be migrated at the same urgency. Categorize by business impact:
For small environments (under 50 legacy files), self-service migration with LegacyLeaps is usually sufficient. One person can scan, convert, and test files in a day or two.
For larger environments (hundreds or thousands of files), bulk migration is more efficient. LegacyLeaps's batch processing handles the format conversion and VBA updates in one pass, and generates a per-file compatibility report that documents every change made.
For files with complex VBA — heavy API usage, external DLL dependencies, custom ActiveX controls — the done-for-you service provides human-reviewed migration with testing and a written compatibility report for each file.
After migration, every critical file needs to be tested by the person who uses it. Not by IT — by the business user who knows what "correct" looks like. The validation checklist:
IT teams sometimes defer migration because the current files "still work." This is a reasonable position — until the update lands and they don't. The cost comparison:
| Approach | Effort | Disruption | Risk |
|---|---|---|---|
| Proactive migration before 25H2 | Planned, scheduled | Minimal (done during maintenance windows) | Low (test before and after) |
| Reactive migration after 25H2 breaks files | Emergency, unplanned | High (users blocked until files fixed) | High (old format may not be readable) |
| Delay update indefinitely | Ongoing (security patches, workarounds) | Ongoing (unsupported OS version) | Critical (security exposure) |
Delaying the Windows update itself is technically possible but increasingly untenable. Microsoft's servicing model pushes feature updates aggressively, and running an unsupported build means missing security patches. The longer you delay, the harder the eventual migration becomes — because you're accumulating technical debt on a platform that's actively moving away from you.
If full migration before 25H2 isn't feasible, here are the partial measures that provide the most protection:
The 25H2 update is one event in a long trend. Microsoft has been deprecating legacy Office formats for nearly 20 years. The pace of deprecation is accelerating, not slowing. Every year that legacy files remain in their original format, the migration gets harder and the risk of sudden breakage gets higher.
The organizations that handle Windows updates smoothly are the ones that treat legacy file migration as infrastructure maintenance — something you do proactively on a schedule, not something you do reactively when an update forces your hand.
Download LegacyLeaps, run a batch scan across your file shares, and get a full inventory of what needs to be migrated. The scan is free. The report tells you exactly how big the project is.
IT Team Bulk PricingRelated: 24H2 Office Compatibility Guide • 24H2 Broke Your Excel Files • Windows Upgrade Survival Guide
Practical fixes for legacy Excel and Access problems. No spam.