Document icon changes after first launch on Windows?

That would limit the shown icon to one single icon. Better would be to have an icon file which contains several icons (same icon UI but different sizes/color depths) - Explorer has different icon views! Try removing the ',0' if your icon file only has one icon in it.

It may be that the registry is written last in the installer, after the explorer got notified of updates? Make sure the registry entry is written after the icon file is stored on disk you should use the Wise installers own configuration to register the file type. Not sure, but I think explorer won't take any changes until the whole installation of an msi is finished, so calling SHChangeNotify() manually won't help.

The msi has its own table for this, which Wise will add if you use the right configuration. For Wise, do the following (instead of creating the registry keys on your own): Under the Feature Details page group, select the File Associations page. From the Current Feature drop-down list, select Core.

Click Add at the right of the window and select New. The File Association Details dialog appears. Click the Extension Details tab.

Browse to the QuickFacts directory, select the file QckFacts. Exe, and click OK.In Extension, enter: qft Leave the defaults for the rest of the fields and click OK. The extension .

QFT is added to the installation. When an end user double-clicks a file with this extension on the destination computer, the QuickFacts application launches. Save the installation Edit You may also missing required registry entries (the icon might not be enough for the shell to show it): HKEY_CLASSES_ROOT\.

Auz\(default) = auzfile HKEY_CLASSES_ROOT\. Auz\shell\open\command = C:\Path\To\App.exe.

Stefan, thanks for the input. The ",0" doesn't seem to be part of my problem, since the software writes that, and it works. Notifying Explorer after installation does not help either, so hypothesis 2 and 3 seem wrong as well.

But good points. – Carl Seleborg Jan 9 '09 at 15:31.

Here's the solution. Each file type (let's say ". Auz" in this case) was registered with: A DefaultIcon key with the path to the icon resource, and A value for the HKEY_CLASSES_ROOT\.

Auz\(default) value giving a description of the file type, e.g. "Foobar Document". In addition to this, there was an entry for the "Foobar Document" document type, or more specifically, a key for how to open such documents from the shell: HKEY_CLASSES_ROOT\Foobar Document\Shell\command\open\(default) = C:\Path\To\App. Exe "%1" Apparently, this key superceeds the value written for the specific file extension.

Because the icons are external to the . Exe file, Windows Explorer then used the first icon of the application to create an icon for all files of type "Foobar Document" (that "white sheet + application icon" icon I mentioned). Now, what I had wrong was that the application itself does change the value of HKEY_CLASSES_ROOT\.

Auz\(default) to a slightly different value when starting, say "Foobar 1.2 Document" (the problem with not being DRY). Thus, the link to "Foobar Document" was lost, and the . Auz files got their icons after the first launch.

So I fixed this all by simply removing the HKEY_CLASSES_ROOT\Foobar Document key altogether, and voilÃ!

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.