I have a VB6 program from many years ago. It has an 'out of process' COM exe that the main program starts and sends messages (API calls). The program and installer have worked fine for a number of years. The program works fine on Windows 7 and on Windows 10 64bit 2016 1607. We have recently received computers that are running Windows 10 64bit 2019 1809 and another one with Windows 10 64bit 21H2. None of these computers will allow the 'out of process' COM exe to start. I am getting the 430 'Class does not support Automation...' message or the 429 'ActiveX component can't create object'.
This feels like some sort of permissions issue. These PC's are single purpose PC. Only one user with Administrative rights. If I look in the registry on the PC's I see my EXE program with the correct GUID's. It looks like it is registered. I have the UAC set to the lowest level, as that has helped in past.
I have tried 'regsvr32 programName.exe' and 'programName.exe /regserver' . Some other stackOverflow answers indicated I should run 'regtlib msdatsrc.tlb', but I can not find 'regtlib' on the PC anywhere. I can find 'msdatsrc.tlb', but I'm not sure how that relates to my program. I also have a little helper program that will show the GUID and version information for any OCX or EXE. This program fails in the same way. Although the helper program runs ok on my company PC, which is Windows 10 21H2.
I just ran the program and noticed that the 'programName.exe' briefly appeared in the Task Manager. So, it is being started but then crashing or something is 'ending' it.
Thanks for any suggestions...