Does Visual Basic 6 work on Windows 11?

It is the question of anyone with a VB6 application about to change computers. The short answer: already compiled applications usually keep working. The real problem is not the runtime but everything around it.

What is supported and what is not

VB6 runtime

Microsoft has stated that the Visual Basic 6 runtime files remain supported on Windows 11 for the lifetime of the system.

Development environment (IDE)

Unsupported since 2008. It can be installed on modern Windows versions, but it is unsupported and causes problems.

Third-party controls (.ocx)

They are the weak point: many vendors disappeared and those controls may fail to register or work badly.

32-bit applications

VB6 produces 32-bit programs. They run on 64-bit Windows, but cannot load 64-bit components.

Where they usually fail

Component registration

.ocx and .dll files must be registered with administrator permissions and in the right system version.

Data access

Old ODBC, DAO or ADO drivers, and connections to Access or old databases, cause problems on new machines.

Printers and reports

Crystal Reports or old printer drivers tend to cause trouble every time the machine changes.

Office integration

Excel or Word automation depends on the installed version and whether it is 32 or 64-bit.

What to do so you are not left stranded

Take an inventory

List the executable, the .ocx files, the DLLs, the databases and the printers or machines it depends on.

Keep a working copy

A virtual machine with the system where it works today is the best insurance for going back.

Document what it does

Which business processes depend on the program. It is what will be lost if it fails and nobody remembers.

Assess the code

Analyse the executable to see whether its logic is recoverable, and decide whether to migrate in phases to a current application.

We only work on software you own or have the right to act on. This is not legal advice.

Frequently asked questions

Am I in a hurry to migrate my VB6 application?

It depends. If it works, has backups and lives on a controlled machine, there is no immediate technical urgency. There is urgency when it depends on one old machine, on unsupported components or on a mandatory change.

Can the code of a VB6 .exe be recovered?

It depends on how it was compiled. P-Code is fairly recoverable; native code only partially, and the logic must be rebuilt. The free analyser on this site gives a first estimate.

What do you migrate a VB6 application to?

To modern .NET or a web application, module by module, with the old system running in parallel until the new one proves it does the same.

Can I keep using the VB6 IDE?

It can be installed on modern machines, but Microsoft does not support it and it may give errors. To maintain the application in the medium term it is better to move it off.

Related

Contact

Email: jmoreno@stellariscode.com · Phone: +34 654 51 63 65