sbaebler
Posts: 18
Joined: Wed Oct 08, 2008 10:15 am

For FileExtensions, cryptic registry entry is created

Hello

I use the File Extensions wizard of Advanced Installer to launch files with a specific extension with my application. When Advanced Installer then creates registry entries for my Application
I then find in HKCR\Application.Document\shell\open\command the two values

(Default) "C:\Program Files\CompanyName\ApplicationName\Application.exe" "%1"
and
command yj?=&Z7gw9jGorBmF5,{MainFeature>W7L.$^w5LAR'RPV4.A8U "%1"

Judging by the MainFeature substring I think that it must have been created by Advanced Installer.
What is this cryptic command value and what is it used for? Is it a bug? Can I somehow specify not to write the command value?

I have encountered another problem that may be related to that. For some Files, when I double click them, the Windows Installer is run and Updates my application for about one minute, without further specifying what is being done and requiring no user input. Do you know why it behaves like that?

Thank you
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: For FileExtensions, cryptic registry entry is created

Hi,
What is this cryptic command value and what is it used for?
This entry is created automatically by Windows Installer and it is used for the auto-repair feature:
- when the file association is used, Windows Installer verifies the integrity of the installation
- if something is missing or it's broken, it will be repaired automatically (a Windows Installer progress bar is shown after launching the file)
Can I somehow specify not to write the command value?
No, the value is managed by Windows Installer.
For some Files, when I double click them, the Windows Installer is run and Updates my application for about one minute, without further specifying what is being done and requiring no user input.
This happens because the auto-repair feature is used. Windows Installer detects that something created by the install process is missing and it reinstalls it. A method to determine the cause of the auto-repair is to open the Event Viewer ("Start -> Run", "eventvwr.msc") and look under the Application node for "MsiInstaller" log messages of the form:

Code: Select all

Event Type: Warning
Event Source: MsiInstaller
Event ID: 1001
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}', feature 'Example' failed during request for component '{00030829-0000-0000-C000-000000000046}'
The message and the GUIDs will of course be different on your machine. The component GUID in the message should be the GUID of a component in your package (in the Organization page).

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”