Test the complete operating envelope
- Install the application and prerequisites on a clean, non-developer machine.
- Map OCX/COM registration, native DLLs and 32-bit ODBC or OLE DB providers.
- Replace writes to protected program directories and machine registry locations with deliberate data/configuration paths.
- Test standard-user execution, UAC elevation boundaries and per-user state.
- Verify printers, serial adapters, vendor drivers and connected equipment.
The VB6 runtime being present does not prove that an application is compatible. Its installer, controls, database client, report engine or device driver may be the actual blocker.
Select containment deliberately
| Native deployment | Best when all dependencies work under controlled 32-bit installation and standard-user permissions. |
|---|---|
| Compatibility adjustment | Useful only when the exact filesystem, API or elevation assumption is understood. |
| Virtualization/isolation | Safer when an old driver or component cannot be responsibly installed on the target OS. |
| Subsystem replacement | Appropriate when one provider, printer or hardware boundary creates most risk. |
Use VB6 runtime compatibility for the runtime-specific question, installer modernization, hardware dependencies and the VB6 pillar.