Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

Unregistered packages do not restore file-type associations correctly

Details

Problem

If file type associations are created using Thinreg.exe version 4.0.1-2837, any pre-existing file type associations might not be restored correctly when the virtual package is unregistered.
 
This affects customers who:
  • Have an application installed natively, like Office 2003,
  • Have used Thinreg version 4.0.1-2837 on a system-wide basis (/a flag) to register a different version of the application, like Office 2007, or have installed a ThinApp-4.0.1-2837 created .msi of a different version of the application.

    In this case, when the virtual application is unregistered (thinreg /a /u ) or is uninstalled from the Add/Remove Programs control panel applet, file type associations are not restored correctly to point to the native version of the application.

Impact

After unregistration of the virtual package, double-clicking on a file with one of the affected file types does not launch the native application.

Solution

Mitigating factors

  1. If Thinreg.exe was not used, or if any version of Thinreg.exe besides 4.0.1-2837 was used, the problem does not occur.
  2. If Thinreg.exe was used without the /a flag, some registry values are left behind, but they do not impact file type associations.
  3. If no application was installed natively that handled the same file types as the virtual package, some registry values are left behind but they do not impact file type associations
  4. As long as the virtual package is not unregistered or uninstalled, file type associations work as expected.

Fix

Before unregistering a package that was registered with Thinreg.exe version 4.0.1-2837, download the updated ThinApp 4.0.1-2866 release. Use the updated Thinreg.exe version 4.0.1-2837 to re-register the package.

  • If the package was registered using thinreg /a <path\*.exe> , use thinreg /a /r <path\*.exe>
  • If the package was registered by installing a ThinApp-generated .msi , use thinreg /a /r /noarp <path\*.exe>
  • If the package was already unregistered, a reinstall of the native application may be required

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions
  • KB Article: 1007970
  • Updated: Aug 14, 2009
  • Products:
    VMware ThinApp
  • Product Versions:
    VMware ThinApp 4.x