Mankalas

Hi!

I am some information in a registry key that does not disappear at rollback. Here it is:

---
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders\

C:\Program Files\DataKraft\ String
---

Our application doesn't deal with any registry key, so I suppose that comes from the tweak I did to pass the test case 19 :

---
Step 1) In the CustomAction table set the following row values:
(Action) (Type) (Source) (Target)
MyTargetDir 51 ARPINSTALLLOCATION [TARGETDIR]

Step 2) In the InstallExecuteSequence table set the following row values :
(Action) (Condition) (Sequence)
MyTargetDir ARPINSTALLLOCATION="" 798
---

The weird thing is that this rollback failure doesn't occur on 64-bit architecture. But our software doesn't depend on the architecture, neither does the installer (Visual Studio msi).

Do you have some idea

Thanks in advance.




Re: Application Compatibility for Windows Vista Test case 23 - Rollback and registry key

Bruce N. Baker - MSFT

What's in the MSI log related to this




Re: Application Compatibility for Windows Vista Test case 23 - Rollback and registry key

Mankalas

That's very strange because I didn't find any information in the log, no "SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders" nor any other information related to this registry.

I managed to solve this problem deleting manually this key during the rollback in my custom action.

I don't like this solution very much, but at least it works...




Re: Application Compatibility for Windows Vista Test case 23 - Rollback and registry key

Bruce N. Baker - MSFT

I don't think deleting this key is a good plan because it hold paths to other objects and was not explictly created by your custom action but I appreciate your deligence in trying to solve the issue.

It sounds like maybe it's trying to remove an entry from the folders regkey that isn't there anymore, try removing the exact key(s) that relates to your application instead of the entire folders registry entry. It looks like this holds paths to where your application install files and a quick guess makes me think it may be related to the files table. I'm sure more investigation in MSI design would turn up more info.