We're trying to capture a 32bit application on Windows 7 SP1 using 5.1.0. During the capture we can install and run the application successfully. When we try to run the virtualised application on the captured machine (immediately after closing SetupCapture.exe following the build) it also works.
It's a fairly (I think) simple app that's loading a database from a mapped drive.
However when we try to run the captured application on a different machine it hangs on startup.... Like it's stuck in a loop with 100% CPU. If we then run the virtualised application again (without shutting down the hanging instance) the first process kicks into life and you get two running instances of the application.
What would the second launch do that the first launch couldn't? I can't think that there's anything created in the sandbox of relavence as if you repeat the process again, the first instance will again hang, even though there's now a complete sandbox from a previous successful launch. The fact the virtual app also runs on the capturing machine suggests there's something on that machine that has not been captured but then I don't know why if that's the case you can run the virtual app twice and have it work.
Any ideas?