Latest / The Windows Podcast with Fexingo: Microsoft, PC, and Enterprise Windows Conversations / How Windows 11 Is Killing Enterprise Legacy Apps
Transcript
- Lucas: There is a quiet war happening inside every Fortune 500 IT department right now, and most employees have no idea it's going on. It's about an invisible piece of infrastructure that has been running unchanged for decades. Luna: Are we talking about the 32-bit app problem? Lucas: Exactly. Windows 11 has a hard dependency on 64-bit processors and a 64-bit kernel. And while Windows 11 can run 32-bit applications through an emulation layer called WoW64, the bigger story is what Microsoft is doing on the driver side. Starting with a specific driver signing deadline in June of last year, and continuing with the phased removal of 32-bit driver support, Microsoft is essentially closing the door on a whole generation of legacy software that relies on kernel-mode components. Luna: So this isn't just about old applications—it's about the drivers those applications depend on, which often have no 64-bit replacement. Lucas: Right. A 32-bit application can still run, but if it needs a kernel-mode driver that's only available in 32-bit, it's dead. And according to a survey by Flexera from late 2025, roughly 15 million legacy applications are still in active use across Global 2000 companies. A huge chunk of those have driver dependencies. Luna: That number—15 million—is staggering. I've heard stories about banks running mortgage calculators written in COBOL that interface with a 32-bit print driver from 1992. Lucas: That's not apocryphal. I spoke with an IT director at a regional bank in Ohio last month. He told me their entire mortgage processing pipeline depends on a single 32-bit DLL that was compiled in 1997. It controls a signature-capture peripheral. That peripheral is no longer manufactured, the vendor went out of business in 2003, and the driver has never been ported to 64-bit. Luna: So what happens when they upgrade to Windows 11? Lucas: They either virtualise the entire application in a Windows 10 container, which is what many are doing, or they rewrite the integration. The bank chose to build a new signature-capture module using a modern web API. It cost them roughly 300,000 dollars and took eight months. And that's just one application. Luna: Eight months for a signature pad. Imagine what it costs for a hospital with dozens of legacy systems. Lucas: Hospitals are a perfect example. I was reading a case study from a health system in Texas. They had a patient scheduling tool written in 16-bit Visual Basic. That's right—16-bit. Windows 11's WoW64 doesn't support 16-bit at all. So they had to either find a 32-bit replacement or rewrite it entirely. They ended up migrating to a cloud-based scheduling platform, but the data migration alone took over a year. Luna: And the cost? Lucas: They wouldn't disclose a number, but analysts I've spoken with estimate that the average enterprise application modernization project costs between 200,000 and 500,000 dollars. For a company with a thousand legacy apps, you're looking at hundreds of millions. Luna: So Microsoft is essentially forcing a massive, expensive upgrade cycle. What's the counterargument? Why is this good for anyone? Lucas: The security argument is strong. Every 32-bit driver that runs in kernel mode is a potential attack surface. Microsoft's own Security Intelligence Report from early 2026 found that 68 percent of all kernel-mode exploits in the previous 18 months targeted legacy 32-bit drivers. By eliminating that entire class of drivers, you're removing a huge vector. Luna: So it's a trade-off: short-term pain for long-term security. Lucas: Exactly. And there's another benefit: performance. A pure 64-bit OS can address more memory, handle larger data sets, and run more efficiently. Even though 32-bit apps run in emulation, the overall system is leaner without the 32-bit kernel components. Microsoft's internal testing shows a boot time improvement of about 12 percent on average when the 32-bit subsystem is fully disabled. Luna: That's not negligible. But for IT managers, the real pain is the inventory problem. Most companies don't know how many legacy apps they have, let alone their driver dependencies. Lucas: That's exactly the issue. I talked to a consultant at a major systems integrator who told me that 40 percent of their Windows 11 migration clients discovered critical legacy applications during the compatibility testing phase that they didn't even know were running. Apps that were installed by a former employee years ago, never documented, and yet essential to a daily workflow. Luna: And those are the ones that break on upgrade day. That's the nightmare scenario—a hospital's scheduling system goes down because nobody remembered it needed a 32-bit printer driver. Lucas: Precisely. And Microsoft has been trying to push the industry forward for years. They announced the driver signing deadline for 32-bit drivers back in 2020. That gave companies five years of notice. But many simply didn't act. Now, with Windows 10 end of support looming in October 2025, the clock is really ticking. Luna: October 2025 is only about sixteen months away. That's not a lot of time for a full inventory and modernization cycle. Lucas: No, it isn't. And that's why we're seeing a surge in demand for application virtualization and containerization solutions. Microsoft's own App-V is being used heavily, and third-party tools like Cameyo and Turbo.net are seeing double-digit growth. The idea is to package the legacy app with its dependencies in a lightweight virtual environment that runs on Windows 11 without needing the actual 32-bit drivers. Luna: But that's a Band-Aid, not a cure. Eventually, those virtualized apps need to be replaced. Lucas: True, but it buys time. And for some apps, virtualization might be the permanent solution—especially if the app is too obscure or too expensive to rewrite. The key is that the driver dependency is removed. That's the hard requirement. Luna: If today's tech conversation gave you something usable—maybe a new perspective on the migration challenge, or a reason to check your own app inventory—that's exactly why we do this show ad-free. We deliberately don't run ads on these episodes because we want to keep the signal clear. Lucas: And that choice is only possible because of listeners who chip in. If you find value in the conversation, the link is buy me a coffee dot com slash fexingo. It's a simple way to support the work and keep it open for everyone. Luna: Yeah, no pressure. Just a quiet option if the show matters to you. Lucas: So back to that Texas hospital—they eventually virtualized the scheduling app using a Windows 10 container, but they also started a parallel project to replace it with a modern web-based system. The virtualization gave them a two-year bridge. Luna: That sounds like the smart play. But I wonder how many companies are just hoping their legacy apps will keep working after October 2025. Lucas: Too many. A Gartner survey from Q1 2026 found that 23 percent of enterprises have not yet started any legacy app remediation for Windows 11. That's nearly a quarter of the market. And for those companies, the upgrade will be a crisis, not a transition. Luna: So what's the first step an IT team should take today, specifically? Lucas: Inventory. Use the Microsoft Assessment and Planning Toolkit, or MAP, to scan every device for 32-bit applications and drivers. Then categorize them by criticality. Then test each one in a Windows 11 environment. That process alone will surface 90 percent of the problems before they hit production. Luna: And if they find a critical app with a 32-bit kernel driver that has no 64-bit version? Lucas: Then they have three options: find a modern replacement, virtualize the app, or isolate it in a dedicated Windows 10 VM that runs Windows 10 LTSC until 2032. That last option is technically possible, but it adds management overhead and security risk because Windows 10 LTSC still gets security updates, but not feature updates. Luna: It's a lot of complexity for what seems like a simple OS upgrade. Lucas: It is. But the alternative—sticking with Windows 10 past end of support—is far riskier. Unpatched systems are the number one entry point for ransomware. The Colonial Pipeline breach in 2021 started with a single unpatched VPN appliance. Imagine what a whole fleet of unpatched Windows 10 machines could do. Luna: So the legacy app challenge is really a security challenge in disguise. Lucas: Exactly. And Microsoft is betting that the short-term pain will be outweighed by the long-term security and performance gains. For once, I think they're right. Luna: I think so too. But I'd still hate to be the IT manager who discovers a critical 32-bit driver the day after the upgrade. Lucas: That's why we made this episode. If it helps even one listener start their inventory six months earlier, it's worth it.