if I start Cameyo, there always shows up a messagebox with the error "Failed hooking CoCreateInstance". If I click OK, the programm runs without problems. I've also tried the -remove command but it didn't work.
I'm using the latest version of Cameyo and I'm running Win8 Pro.
1. When you say -remove didn't work, do you mean that Cameyo didn't remove successfully, or do you mean Cameyo removed successfully but you still get the Failed hooking error after launching Cameyo again?
2. Do you get the same error when running other Cameyo packages? (You can download from Cameyo Public Library for testing or for your own use.)
thank you for your response! -remove work, but it don't fix the error. I've downloaded a original Cameyo Package and I also get the error. I'm also running Cameyo in a Win8 VM, and there isn't the error. With a earlier version (2.0.832 or so) I don't get the error.
1. Is Win8 on VM the same as the Win8 on the host, i.e. is it also Professional?
2. If you build a package in the Win8 VM using version 2.0.834 and launch it on the host, do you get the same Failed hooking error as Cameyo gives you? In your reply, please also advise what software you virtualized.
the VM is a Win8 Enterprise with VMWare Player. If I build a package on the VM and try to launch it on the host, the menu to choose the right application appears. Only then the messagebox appears and if I click OK the app is running without any problems.
Last week, I set about testing Cameyo 2.0.834 in Win8 Pro, as well as several virtual pacakges. I was unable to reproduce the error in either an x86 or x64 system.
The only thing I can think of is that there is some program on your host that is interfering. What security software(s) do you have running?
Also, you said that an earlier version of Cameyo didn't give the error and you thought it might have been version 2.0.832 but didn't seem sure. Do you have a way of checking exactly which version it was? Thanks.
Okay, so you may have made changes between using Cameyo 2.0.832 and Cameyo 2.0.834. Please -Remove Cameyo 2.0.834 and try Cameyo 2.0.832 to see if build 832 still works without giving the error. Thanks.
It is really odd that build 832 produces no error but build 834 does. Even though I tested with a trial version of Norton 360 and was unable to reproduce the error, I guess we should have you try disabling Norton 360 to see if that produces any different results. Please -Remove Cameyo-2.0.832 and try Cameyo-2.0.834 after you have disabled Norton 360 and let us know if you still get the error. Thank you.
Thank you very much for your time and testing! I disabled Norton but it reproduce the error. But it removed all versions and started the latest build (which also gives out the error) and even 834 as admin and it works fine without the error. I think that I have a wrong system setting or program, which make that Cameyo has too less rights. (sorry for my bad english :) )
This type of error shouldn't occur even under Standard (or Limited) User or Guest. We don't believe there is a Win8 setting that should cause the error you're seeing, which makes it rather puzzling ... and now you have it working--puzzling again.
Thanks for your report and testing back and forth. I wish we came up with something conclusive.