
Windows 11 installer for old VB6 Programme
- or -
Post a project like this- Posted:
- Proposals: 11
- Remote
- #4504296
- Open for Proposals



Description
Brett B.
0% (0)New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-

Hi Brett,
A few quick questions
1. Do you already have all compiled binaries + full VB6 source + any third-party OCX/DLL files, or would part of the task be to recover missing runtime dependencies?
2. Which database/backend does the VB6 application connect to (Access, SQL Server, Oracle, ODBC DSN, etc.)?
3. Do you want the final installer to support silent deployment / enterprise rollout, or only standard interactive installation?
Looking forward to your response. -

Can you confirm whether the VB6 application currently runs successfully on any Windows 11 machine, or only on older systems?
Brett B.3 hours ago
The programme works and downloads ok on Windows 10.
It also worls ok on windows 11 machines. Our problem is the installer wont install on windows 11, shows powershell problem and other permission problems. -

Has the application already been successfully tested on a completely clean Windows 11 machine, or is part of this engagement expected to uncover and resolve compatibility issues that may not yet be documented?
Brett B.3 hours agoThe programme works and downloads ok on Windows 10.
It also worls ok on windows 11 machines. Our problem is the installer wont install on windows 11, shows powershell problem and other permission problems.CYTNHIA W.An hour agoThanks Brett, that clarification helps. Since the programme itself already runs on Windows 11, this sounds more like an installer/UAC/permission and dependency-registration issue rather than a VB6 compatibility issue. I would focus on rebuilding the installer so it handles elevation correctly, avoids problematic PowerShell execution paths where possible, registers any required 32-bit DLL/OCX components properly, and installs cleanly on a fresh Windows 11 machine without manual fixes. The first step would be reviewing the current installer behaviour and error messages, then replacing or correcting the installer logic while keeping the working application unchanged.