I get a message that the file cant be registered because of error 80004005. So it seems the packaged VB6 app tries to register the OCX in the real environment and not in the virtualized environment.
I'm really running out of ideas here (and even worse: I'm running out of time. We really need the VB6 app).
Is there a way at all to register OCX files with the help of custom events within the virtualized environment?
If yes, what is the correct syntax? Have I done something wrong?
have you had the time to check the package from my PM?
I have done some further testing. When I create the package under Win8 or Win10 everything worked fine. Just under Win7 I cant get the package to work.
Please provide -Troubleshoot log and Process Monitor log for the new package that doesn't work after the Windows Updates, i.e. A and C from here. If you have a system that hasn't been updated, i.e. where the old package still works, we would appreciate logs from the old package, too.