Home > Blogs > VMware ThinApp Blog

Captured on XP – Running on Win 7

Have you tried capturing an app on XP only to have it not work on Win 7?

Updated 02/25/11!

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.

See the ThinApp Product Homepage or the VMware ThinApp Downloads site to obtain the latest version of ThinApp!

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:


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.
  • WordPerfect captured on XP running on Win 7
  • 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.
  • AutoCAD 2005 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.
  • Oracle ADI on Win 7
This entry was posted in Applications, Tips, Troubleshooting and tagged , on by .
Dean Flaming

About Dean Flaming

Dean is currently an EUC Architect and member of the VMware End User Computing Enablement and Lighthouse Support teams, working to develop communications and IP around VMware End User Computing products and solutions as well as support many various Lighthouse accounts with their own EUC practices. Prior to this, from 2008 through 2012 Dean was one of VMware's End User Computing Specialists. Throughout his time at VMware, Dean has also written and published various articles, videos, and podcasts regarding VMware's EUC Solutions.

14 thoughts on “Captured on XP – Running on Win 7

  1. Peter Björk

    More files to delete to make the package run on Windows 7..
    Located in: %SystemSystem%

  2. Thomas J

    I’m having trouble with the Japanese IME when running a thinapped English Office 2007 (captured with ThinApp 4.6 in an English XP SP3 VM) on Windows 7. The IME works fine when I run the package on XP, but I input only gibberish instead of Japanese when I use the Windows 7 IME. Everything else seems OK on both XP and Windows 7, even the Japanese MUI.
    Any ideas about this?

  3. Dean Flaming

    @Thomas J – This sounds as if it could be any number of things from isolation settings to potentially a glitch with double-byte characters. Please contact VMware support on the web at http://www.vmware.com/support or by phone at 1-877-4-VMWARE (1-877-486-9273) or 1-650-475-5345 and open a support ticket on this issue. If you have troubles doing so or are evaluating ThinApp (and don’t have a support agreement), please contact your VMware Account Rep or SE. If all else fails, please direct message me by clicking on my name and sending me an email so we can get you in contact with the proper person. Thanks!

  4. Mark

    The solution works for CA ERwin 7, but no good for IBM TestManager. Thanks.

  5. Tommaso Franceschi

    How you manage CA ERwin sequencing? I fixed W7 problems with this solution (Thanx!), but still got licensing errors.
    Everytime i start ERwin DM or MM it asks me for activation keys, even if they result activated.

  6. FukenGruven

    why not just build in Win7?

  7. FukenGruven

    are there advantages to building an App. in XP vs. Win7?

  8. Dean Flaming

    Keep in mind the following:
    1. ThinApp uses Delta technology.
    2. An application installation is nothing more than a package containing new or newer files than what exists on the end user system and new or different registry settings than what exist on the end user system.
    3. Newer Windows operating system contain additional and more components than older operating system – which means newer files, more files, and newer registry settings and more registry settings.
    Taking into account the above, this can mean applications captured on a newer operating system (i.e. WIn 7) will likely not work on an older operating system (i.e. Win XP).
    A good example is Win 7 has .NET FrameWork 3.5 embedded into the OS. Windows XP, on the other hand, does not come with any .NET FrameWork. If I capture an application which requires .NET FrameWork on a clean Win 7 OS and try and run that packaged app on a Win XP system, it’s not going to work unless .Net FrameWork is already installed natively. This ultimately means I must create two ThinApp captures – one for Win7 and one for Win XP. While this isn’t a big deal, it is more work.
    Conversely, if I capture on my lowest common OS (i.e. Win XP), then the app will work on XP, and be more likely to work on newer operating systems as well (i.e. Win 7).
    For discussions around setting up a Clean Capture and Build PC, see this blog article:

  9. Ken Kobori

    “Removing OLEAUT32.DLL and MSVCRT.DLL on the straight XP capture” means deleting OLEAUT32.DLL and MSVCRT.DLL under C:\WINDOWS\System32, correct? My Windows XP SP3 has “Windows File Protection” on and I cannot get rid of them. OS always brings the files back. How can I remove these files?

  10. Ken Kobori

    The files to remove was meant under captured application folder. I found it and trying this solution.

  11. Dean Flaming

    You got it on the second post. 🙂 The files are in the %SYSTEMSYSTEM% folder of the project.

  12. Dean Flaming

    You got it on the second post. 🙂 The files are in the %SYSTEMSYSTEM% folder of the project.

  13. Thomas

    I am working on an AutoCAD2006 install and the only issue I run into is that after the file is associated. If you File>Open the file it opens and displays properly. If you double click on a .dwg file to open it. It displays the generic drawing1.dwg. If anyone has any input this would be appreciated.

  14. Dean Flaming

    Before you complete the ThinApp post setup capture process (after installing the application) you need to ensure the file type is registered on the system or for the user.
    It sounds like you are doing this but in order to test this, I would suggest following the ThinApp Troubleshooting Procedure found here.
    This way you can isolate where the issue is (during or after capture, within the ThinApp package or in the native environment).

Comments are closed.