VB6 won't die, but your business might: risks and exit paths
VB6 applications keep running because Microsoft ships the runtime inside Windows 11 under its "It Just Works" policy. That is also the trap: the development environment left all support on 8 April 2008, Microsoft says there is no supported way to maintain VB6 applications, and the successor language VB.NET was frozen in 2020. The risk is not that your app stops; it is that the first change you need becomes the day you discover nobody can safely make it.
VB6 is the survivor of the dead platforms, and that is precisely its danger. A FoxPro owner knows they have a problem. A VB6 owner has an application that installed fine on Windows 11, so the clock on the wall looks stopped. It is not stopped. It is just quiet.
The platform facts, with sources, live on the VB6 migration page. This note is about the shape of the risk and the three ways out.
Why VB6 apps keep working
Microsoft made VB6 a strange deal. The development side died young: mainstream support ended in March 2005 and the IDE left support entirely on 8 April 2008. But the runtime, the files an installed application needs, ships inside Windows itself under what Microsoft calls the “It Just Works” policy: supported for the lifetime of the Windows version it came with, for serious regressions and critical security issues only.
So your application runs, legitimately, on a supported runtime. What you do not have is any supported way to change it. Microsoft’s words: there is no supported method to create or maintain VB6 applications, and it strongly recommends replacement. The IDE was never supported on any 64-bit Windows at all.
The five risks, in the order they usually bite
- The first change request. A VAT rule, a new label format, a customer’s portal. The application did not break; the world moved. Now someone must run a 2008-era IDE on an OS it was never supported on, and edit code with no vendor behind it.
- The controls. Most real VB6 systems lean on third-party OCX and ActiveX controls for grids, reports and charts. Microsoft explicitly cannot support them, and many of the vendors no longer exist. One Windows update that breaks one control can take the whole application with it.
- The people. IT Jobs Watch counted three permanent UK job adverts citing VB6 in the six months to June 2026, at a £60,000 median. The market is telling you what emergency cover costs, when it exists at all.
- The operating system underneath. Windows 10 left support on 14 October 2025. Paid Extended Security Updates exist, with commercial pricing from 61 US dollars per device in year one and doubling each year for at most three years, but that is a countdown with an invoice attached, not a plan.
- The 32-bit ceiling. VB6 binaries run under WOW64 emulation and cannot load into 64-bit processes, which quietly rules out 64-bit Office add-ins and a growing share of modern integration points.
UK businesses carry one more: Cyber Essentials requires software to be supported, and unsupported software to be removed or isolated from the internet. A VB6 development machine on the network is exactly the kind of finding that stalls a certification.
The three exit paths
| Path | What it is | Where it leads |
|---|---|---|
| Machine conversion to VB.NET | Tools such as those Microsoft’s own partner page lists convert the code, then hand-finishing begins | A working .NET app in a language Microsoft froze in 2020. A sideways step that suits stable, rarely-changed systems |
| Replace with a package | Buy off the shelf, migrate the data | Right when the system was never very bespoke. Decades of custom logic rarely fit |
| Rebuild as a web application | Extract the data, rebuild the behaviour in a mainstream stack, run old and new in parallel | The expensive option once, then ownership and an ordinary hiring market forever |
The conversion row deserves one honest paragraph, because the tooling is real and sometimes right. Microsoft offers no first-party converter; its partner page points at third-party tools, and they do convert the bulk of straightforward code. What they cannot convert is the reason you wrote VB6 in the first place: control arrays, default properties, error handling by GoTo, and the thousand small Variant behaviours your business logic accidentally depends on. Budget for the hand-finishing, and ask the harder question first: do you want to arrive on VB.NET, a language with a stable design and no new workloads by Microsoft’s own strategy, or pay once more later to leave it too?
What to do this month
Copy the source tree somewhere safe, including the .vbp project files and every OCX the installer needs; the source is plain text and readable even where the IDE cannot run. List the third-party controls and check which vendors still exist. Then get the options priced against your actual system rather than in the abstract. The free Legacy Risk Audit does exactly that in 30 minutes plus a written one-pager, and the Rescue Roadmap turns it into a fixed-price proposal if you want one.
F5 still runs it. The question is who fixes it when F5 does not.