Is Visual Basic 6.0 Still Supported? End-of-Life Dates (2026)
Short answer
The Visual Basic 6.0 IDE is no longer supported: vendor support ended on 8 Apr 2008 (18 years and 6 months ago).
The VB6 IDE is unsupported, but Microsoft supports the VB6 runtime on current Windows versions for the lifetime of those versions, limited to serious regressions and critical security issues.
Legacy Technology Tracker · Status as of 16 Oct 2026. Data checked 7 Oct 2026; refreshed monthly, with quarterly snapshots kept unchanged.
Risk rating
Elevated: support ended 8 Apr 2008; no entries on CISA's KEV list. How ratings work
Key facts
Every value links to its source and shows when we last checked or retrieved it. Data checked 7 Oct 2026; status as of 16 Oct 2026.
| Fact | Value | Source | Checked |
|---|---|---|---|
| Support status | UnsupportedThe Visual Basic 6.0 IDE (the development environment). Microsoft supports the VB6 runtime for the lifetime of supported Windows versions; that is a separate statement, noted but not used for status. | ||
| End of standard support (security updates) | |||
| Known exploited vulnerabilities (CISA KEV) | 0 CVEs all time; 0 added in the last 24 monthsMatched by vendor and product name in the KEV catalog. No CISA KEV entry names Visual Basic 6.0 (KEV lists VBA separately). | ||
| Job postings and salaries | Not published: the job-posting source is on hold pending a data licence. | — | — |
Versions in scope
The Visual Basic 6.0 IDE (the development environment). Microsoft supports the VB6 runtime for the lifetime of supported Windows versions; that is a separate statement, noted but not used for status. Dates per version, each with its source.
| Version | Status | Standard support ends | Extended support ends | Latest release | Source | Checked |
|---|---|---|---|---|---|---|
| Visual Basic 6.0 IDE | Unsupported | — | — |
If you still run Visual Basic 6.0
The IDE date, 8 April 2008, is not the one that matters. The VB6 runtime that your applications run on is supported for as long as the Windows version it runs on, so the deadline is that Windows version's end of support. Microsoft limits that support to serious regressions and critical security issues.
The realistic options:
- Keep running it on a supported Windows version. This works while the runtime files and any third-party controls hold up. Inventory the ActiveX controls and libraries: Microsoft supports only the runtime files it lists, and anything else carries its own vendor's terms.
- Rehost on a supported Windows Server. If the problem is an aging operating system, moving the application to a virtual machine on a supported version restores operating system support without changing code.
- Migrate to .NET. Microsoft publishes an upgrade guide, and tooling can help with conversion. The VB6 to .NET guide covers scope, cost ranges and risks.
- Rewrite. This suits small applications or ones whose users and workflows have changed.
Legacy system modernization companies lists suppliers for VB6 migrations, and modernization costs gives budget ranges.
Frequently asked questions
Is Visual Basic 6 still supported?
Partly. Microsoft's support statement says the VB6 IDE has been unsupported since 8 April 2008, but the VB6 runtime is supported for the support lifetime of Windows versions. The runtime bar is limited to serious regressions and critical security issues for existing applications.
Does VB6 work on Windows 11?
Microsoft lists the VB6 runtime files that ship in Windows 11 and Windows Server 2025 as supported, along with the extended runtime files you redistribute with your application. The IDE is not supported on any Windows version.
Is it safe to keep running VB6 applications?
The runtime is covered only while the Windows version under it is supported. Microsoft also lists some files, such as legacy VB4 and VB5 support files and third-party controls, as unsupported on Windows. There is no supported way to build or change VB6 applications, which Microsoft says is the reason to replace them.
What can replace Visual Basic 6?
Teams usually move to .NET, either by upgrading the code with tooling or by rewriting. The VB6 to .NET guide covers scope, cost ranges and risks.