Member Avatar for zebnoon

Hello and Asslam o alekom!
I have problem to install my VB6 Application on Windows 8.First there is erorr when i start to install my Application.Please solve this problem?

  • 6 Contributors
  • 6 Replies
  • 298 Views
  • 2 Months Discussion Span
  • Latest Post Latest Post by IconKana

Dani AI

Generated

Thread shows a common pattern: VB6 apps can and do run on Windows 8, but installers fail when the runtime or COM/OCX pieces aren’t handled correctly. ’s caution about age is understandable, and ’s experience that VB6 programs run on Windows 8 is consistent with Microsoft’s support stance (the IDE is unsupported but key VB6 runtime files are shipped with and supported on current Windows releases). (learn.microsoft.com)

Most installer problems come from three things: missing/old VB6 runtime bits, unregistered ActiveX/OCX components, or 32-bit vs 64-bit redirection and UAC/permissions. Checklist to fix an installer build:

  • Identify every native dependency (use a dependency walker like the modern “Dependencies” tool).
  • Avoid shipping or overwriting OS-managed system DLLs; deploy only the VB6 runtime pieces your app truly needs.
  • Register 32-bit OCXs on 64-bit Windows with the 32-bit regsvr32 (run elevated). Example command:

%SystemRoot%\SysWOW64\regsvr32 "C:\Windows\SysWOW64\SomeControl.ocx"

See Microsoft guidance on using regsvr32 and troubleshooting registration. (github.com)

Use an installer engine that handles COM registration and elevation. Inno Setup (free) can register OCXs automatically; a minimal [Files] example:

[Files]
Source: "MyControl.ocx"; DestDir: "{syswow64}"; Flags: regserver 32bit sharedfile

The regserver and 32bit flags ensure proper registration into the 32-bit view on x64 Windows; sharedfile updates the SharedDLLs count instead of overwriting system files. Compile installers to require administrative elevation and test on clean 32‑bit and 64‑bit Windows 8 VMs to reproduce and fix problems reliably. (documentation.help)

Tying back to the thread: ’s pointer to Microsoft documentation is on the right track, ’s SysWOW64 note is the key practical detail, and tools like Inno or NSIS (or commercial setup builders) will work when the runtime/OCX registration and elevation are handled correctly.

Recommended Answers

All 6 Replies

Member Avatar for Ancient Dragon

What is the error? Most likely vb6 programs are just too old to run on windows 8, but that is just my guess.

Member Avatar for Mamoundi

I got same Problem ....!

Member Avatar for abelingaw

Try using Rose Setup Factory. Been using it in creating installers from VB6 projects.

Enables Serial Key for installer or even an Expiration date.

Member Avatar for IconKana

Try INNO. It's free and very good. Depending on the OCX files in your program, you will need to install them into the C:\Windows\SysWOW64 directory Windows 7 & 8, instead of the C:\Windows\System32 directory in XP. Not sure about Vista.

Member Avatar for IconKana

VB6 Programs run fine in Windows 8.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.