Microsoft officially ended support for Visual Basic 6 in 2008. That was eighteen years ago. And yet, if you walked into the back offices of businesses across the UK today — in manufacturing, logistics, finance, local government — you'd still find VB6 software quietly running the show.
So can VB6 still run in 2026? The short answer is yes. But the longer answer is: yes, with caveats. Here's what you need to know.
VB6 still runs on modern Windows
The VB6 runtime — the engine that powers VB6 applications — is still included in Windows 10 and Windows 11. Microsoft has never removed it, and has repeatedly stated they have no plans to do so. This is almost certainly because removing it would break too many systems that businesses depend on.
So if you have a VB6 application that worked on Windows 7 or Windows XP, there's a good chance it still runs today. Many do, without any modification.
The problems you might be running into
That said, running VB6 software on modern Windows isn't always completely smooth. The most common issues businesses encounter are:
- Compatibility issues with 64-bit Windows — VB6 applications are 32-bit. Most run fine, but some components and controls don't work properly on 64-bit systems.
- Deprecated or missing ActiveX controls — Some third-party controls used in VB6 applications are no longer supported or available, causing crashes on startup.
- Database connectivity — Older database drivers (particularly for Access and early SQL Server) can cause connection issues on newer Windows versions.
- Display scaling issues — High-DPI screens can make VB6 application interfaces look blurry or incorrectly sized.
- Administrator permissions — Modern Windows security settings can prevent VB6 applications from writing to certain folders they previously had access to.
Should you be worried?
If your VB6 system is running without problems today, you don't need to panic. The immediate risk isn't that Windows will suddenly stop supporting VB6 — Microsoft has given no indication of that.
The real risks are more gradual:
- The developers who originally built and know your system have retired or moved on
- Finding someone who can modify or fix the system becomes harder every year
- Modern integrations — connecting to cloud services, APIs, new databases — are increasingly difficult with VB6
- Security vulnerabilities in older components go unpatched
These aren't reasons to replace your system tomorrow. But they are reasons to have a plan.
What are your options?
Broadly speaking, UK businesses with VB6 systems have three choices:
- Keep it running — With the right support, most VB6 systems can be maintained and extended for years to come. If your system works well and does exactly what you need, this is often the right choice.
- Migrate to .NET — VB6 code can be migrated to VB.NET or C#, which preserves your business logic while moving to a supported, modern platform. This can be done in phases to spread the cost and risk.
- Replace entirely — In some cases, particularly where the software is very old and the business has changed significantly, a full replacement with off-the-shelf or bespoke software makes more sense.
Which is right for you depends on the size and complexity of your system, your budget, and your business plans. It's worth getting an honest assessment before deciding.
The bottom line
VB6 is not dead — it's just unsupported. The distinction matters. Unsupported means no new features, no security patches, and a shrinking pool of developers who know it. But it doesn't mean your software stops working tomorrow.
The businesses that get into trouble are the ones who assume everything will be fine indefinitely and have no plan for when something goes wrong. A broken VB6 system with no developer who can fix it is a serious operational risk.
If you're not sure where you stand, a free assessment is a good place to start.