Quote Originally Posted by dilettante View Post
None of the VB6 tool chain ships as part of Windows. You have to install the compiler, the linker, basically everything.

I just compiled 10 VB6 programs on Windows 11, copied the compiled EXEs to a Windows 10 machine, and all of them run perfectly.

Clearly what is going on above is some combination of improperly installed and updated VB6 and old Projects contaminated by being worked on under Windows 7, which has been known known to be problematic for a very long time. Contaminated Projects can be repaired, but you have to correct their type library references by hand.

There are three parts to these: a GUID, a type library version, and a locale ID (typically just a 0).
Hello,

do you use LoadPicture() in those programs?

That is good news that you are able to compile on 11 and run on 10, that gives me hope it is just my setup.

I will run more test tomorrow and report here

btw I installed vb6 enterprise and SP6