It is the question every IT team asks before a hardware refresh or a server upgrade: will our Visual FoxPro application still run on Windows 11 or Windows Server 2022? The short answer is usually yes, for now. The longer answer is the one that matters, because "it runs" and "it is supported" are not the same promise.
Let us separate what is true today from what you are actually betting on.
What works today
Visual FoxPro 9.0 is a 32-bit application, and 64-bit Windows runs 32-bit software through its built-in compatibility layer. In practice, most VFP applications launch and run on current Windows 11 and Windows Server 2022 machines. Teams do it every day. So if the only question is "will it start," the answer is generally yes.
What tends to break
The trouble is rarely the core application. It is everything around the edges that a real-world FoxPro app leans on:
- ActiveX and OCX controls. Older third-party components, including some common controls, may not register or behave correctly on modern Windows.
- Printing and reports. Changes in printer drivers and the print subsystem are a frequent source of broken FoxPro reports and layout shifts.
- OLE and Office automation. Apps that drive Excel, Word, or Outlook often break as those products move forward and old automation interfaces change.
- Shared network data. DBF files over modern SMB shares and aggressive antivirus can cause locking and corruption issues that did not exist on older networks.
The pattern to notice: the failures almost never come from FoxPro itself. They come from the modern world changing underneath an application that can no longer be updated to keep up.
The bet you are actually making
Because Visual FoxPro has been unsupported since 2015, Microsoft makes no compatibility commitment to it on any current or future version of Windows. That means every Windows feature update is a roll of the dice. It might change nothing. It might quietly break printing, or a control, or a data driver, with no patch available and no vendor to call. You are not running supported software on a supported OS. You are running unsupported software that happens to still work, and hoping the next update keeps it that way.
Compatibility mode and VMs buy time, not safety
Running the app in Windows compatibility mode, or isolating it on an older OS inside a virtual machine, can keep a fragile system alive. These are legitimate stopgaps. But they are containment, not a cure. You are freezing the application in an aging environment to avoid the modern one, which only deepens the dependency on a platform the rest of the world has left behind.
The durable answer
The only way to stop gambling on each Windows update is to move the application to a platform that is actively supported. A modern web application runs in the browser, so it does not care whether the desktop is Windows 11, a Mac, or a tablet, and it is maintained on a stack that gets security updates. That is what turns "it still runs, we think" into "it runs, and it will keep running."
Bottom line: Visual FoxPro usually runs on Windows 11 and Server 2022 today, but it does so unsupported and unguaranteed. Each OS update is a risk you cannot patch your way out of. The fix is not a better workaround, it is a supported platform.
Want to know how cleanly your specific application would move to the web? Our free assessment tells you, with no obligation.