Hi,

Is there anyone of you knows how to resolved the issue regarding the deletion of an application specific registry upon launching the shortcut in administrator account? It is under HKCR\CLSID\<GUID>. The deletion of the said registry triggers the application not to function well.

Thanks in advance.

Note: setup captured
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
My guess would be that, during the capture, the vendor's set-up deleted the old CLSID and then created the new one and it is the latter part which you're missing. Perhaps you removed it in error? It should be simple enough to track that down.

As ever, what you should do with any captured package is:
- run your MSI
- If the app appears in Add/Remove Programs, delete the registry entry that indicates that the app is installed, in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall
- start up a lightweight snapshot tool (I use Ziff-Davis's In Control) and take a 'before' snapshot
- run the vendor's install over the top of yours
- take an 'after' snapshot
- carry over any relevant changes to your package.

By working through the process above, you can be pretty sure that your package does everything which the vendor's does.
Answered 01/26/2009 by: VBScab
Red Belt

Please log in to comment
0
[left][/left][left]Hi,

Is there anyone of you knows how to resolved the issue regarding the deletion of an application specific registry upon launching the shortcut in administrator account? It is under HKCR\CLSID\<GUID>. The deletion of the said registry triggers the application not to function well.

Thanks in advance.

Note: setup captured
[/left][left] [/left][left]Thanks for your suggestion VBScab. I really appreciate it. [/left][left] [/left][left]Just want to add this one. The issue is behavior of the legacy itself. [/left][left] [/left][left]After the installation, i lauched the shortcut in admin, it works fine. Then, I logged off and change the user to limited. In limited it also works fine. But, after launching the shortcut in limited and logging on back to the admin account, the deletion of the registry works there upon launching the shortcut. [/left]
Answered 01/26/2009 by: wilson
Senior Yellow Belt

Please log in to comment
0
Weird...

If you're sure that the deletion isn't occuring as part of a repair (do you see a Windows Installer progress dialog at all?) and you suspect that the app itself is responsible, then there's only one way to resolve what's going on - ProcMon (or your favoured process/file/registry monitor). That will identify the process which is performing the deletion. It's possible you could work around it by making the value a key path of a component (so that deletion of that key path would be repaired by the engine) but see if you can tie down what's happening first.
Answered 01/26/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity