Have you tried capturing an app on XP only to have it not work on Win 7?
As of the ThinApp 4.6.1 release you should not need to do this. Capturing of your application with 4.6.1 should no longer demonstrate the below issue.
For ThinApp 4.6 and Previous Versions…
If you captured an app on XP and it doesn’t run on Win 7, check for and remove OLEAUT32.DLL from %SYSTEMSYSTEM% and rebuild (don’t forget to clean the sandbox out first before testing).
If that gets it part way, watch the app errors. You may need to remove other things like:
- MSVCRT.DLL (from %SYSTEMSYSTEM%)
- OLEPRO32.DLL (from %SYSTEMSYSTEM%)
Rebuild of the project is needed after each removal (do one at a time). And, again, don’t forget to wipe the sandbox between each test.
So far I’ve seen this work for the following apps:
- Adobe CS5:
Removing OLEAUT32.DLL fixes launch errors on Win 7 and removing MSVCRT.DLL apparently makes it launch more quickly on Win 7.
- WordPerfect X5:
When captured on XP Pro it won’t launch on Win 7 – removing OLEAUT32.DLL fixes this. Capturing on Win 7 and then executing on Win 7 works fine.
- AutoCAD 2005:
Removing OLEAUT32.DLL fixes the major launch errors but my testing still shows other intermittent issues – but I suspect these are licensing errors. Also, I’m finding AutoCAD 2005 needs .NET FrameWork 1.1 packaged or AppLinked to it for running on Win 7.
- Oracle ADI:
Removing OLEAUT32.DLL and MSVCRT.DLL on the straight XP capture will get the ThinApp package to work on Win 7.