How do I use REG DELETE within an msi package, Winzip 12?

Thanks vadimrapp1.

I´m a bit uncertain what to write and where to place it in the msi.
I would be very grateful for an example.

If I understand correctly, you want to create an msi that would remove registry keys left after winzip? It's technically possible, but usually msi represents an installation of some product, while this is actually one-time maintenance. For that, standalone script is the best, without any MSI.. Depending on your network, you can specify this script in group policy as logon script, so it runs for every user when he logs on. See examples at http://www.computerperformance.co.uk/Logon/logon_scripts.htm .

I´ve already made an functional mst/msi for Winzip12 for distrubution via SMS and now I want to make sure that the remainining regkeys also are deleted after an uninstall.
Could i use REG DELETE within the msi-script?
Just don´t know where in the script or what to write?

I´m not thinking about making a new msi for that purpose, sorry if I didn´t explain myself clear.

I see. If the MSI was made correctly, then it should clean everything up after itself, no need in any special effort.

Run your MSI through ICE validation and fix what it says. And/or  you can indeed upload it here (rename to .txt) and I'll take a look.

I´ve already run my msi trough ICE validation and fixed the problems except for some 33-errors.

So all errors exept the 33, see attachment are solved but I still got remaining regkeys after uninstall.

So I`ve come to a deadlock by now, I´m so grateful if there is a workaround/solution for this.

/ margeritha

then see the last sentence of my previous comment.

...you said "see attachment", but there's none.

Sorry, but I choose to attach my txt-file and it´s loading but obviously it`s never got attached.

So here are the ICE-errors.

Reg key registry431 is used in an unsupported way. Shell extension verbs info should be registered via the Verb table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry431
Evaluation: ICE33
Reg key registry439 is used in an unsupported way. ProgId should be registered via the ProgId table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry439
Evaluation: ICE33
Reg key registry438 is used in an unsupported way. ProgId should be registered via the ProgId table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry438
Evaluation: ICE33
Reg key registry431 is used in an unsupported way. ProgId should be registered via the ProgId table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry431
Evaluation: ICE33
Reg key registry369 is used in an unsupported way. Extensions should be registered via the Extension table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry369
Evaluation: ICE33
Reg key registry370 is used in an unsupported way. Extensions should be registered via the Extension table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry370
Evaluation: ICE33
Reg key registry431 is used in an unsupported way. Shell extension verbs info should be registered via the Verb table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry431
Evaluation: ICE33
Reg key registry289 is used in an unsupported way. ProgId should be registered via the ProgId table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry289
Evaluation: ICE33
Reg key registry291 is used in an unsupported way. ProgId should be registered via the ProgId table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry291
Evaluation: ICE33
Reg key registry290 is used in an unsupported way. ProgId should be registered via the ProgId table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry290
Evaluation: ICE33
Reg key registry369 is used in an unsupported way. ProgId should be registered via the ProgId table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry369
Evaluation: ICE33
Reg key registry370 is used in an unsupported way. ProgId should be registered via the ProgId table. This entry may overwrite a value created through that table. ice33.html Registry Registry registry370
Evaluation: ICE33
The File 'NTUSER.DAT' is explicitly marked compressed, but the Summary Information Stream already specifies that the whole install is compressed. This might not be the behavior you want. ice39.html File Attributes NTUSER.DAT
Evaluation: ICE39
The File 'NTUSER.DAT.LOG' is explicitly marked compressed, but the Summary Information Stream already specifies that the whole install is compressed. This might not be the behavior you want. ice39.html File Attributes NTUSER.DAT.LOG
Evaluation: ICE39
The File 'ntuser.pol' is explicitly marked compressed, but the Summary Information Stream already specifies that the whole install is compressed. This might not be the behavior you want. ice39.html File Attributes ntuser.pol
Evaluation: ICE39
The File 'WINZIP.WZMUL2' is explicitly marked compressed, but the Summary Information Stream already specifies that the whole install is compressed. This might not be the behavior you want. ice39.html File Attributes WINZIP.WZMUL2
Evaluation: ICE39
The File 'desktop.ini' is explicitly marked compressed, but the Summary Information Stream already specifies that the whole install is compressed. This might not be the behavior you want. ice39.html File Attributes desktop.ini
Evaluation: ICE39
Directory 'PrintHoodFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory PrintHoodFolder
Evaluation: ICE48
Directory 'System16Folder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory System16Folder
Evaluation: ICE48
Directory 'PersonalFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory PersonalFolder
Evaluation: ICE48
Directory 'MyPicturesFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory MyPicturesFolder
Evaluation: ICE48
Directory 'SendToFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory SendToFolder
Evaluation: ICE48
Directory 'TemplateFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory TemplateFolder
Evaluation: ICE48
Directory 'FavoritesFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory FavoritesFolder
Evaluation: ICE48
Directory 'CommonFilesFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory CommonFilesFolder
Evaluation: ICE48
Directory 'AppDataFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory AppDataFolder
Evaluation: ICE48
Directory 'RecentFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory RecentFolder
Evaluation: ICE48
Directory 'AdminToolsFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory AdminToolsFolder
Evaluation: ICE48
Directory 'LocalAppDataFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory LocalAppDataFolder
Evaluation: ICE48
Directory 'WWWROOT' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory WWWROOT
Evaluation: ICE48
Directory 'WinSxS' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory WinSxS
Evaluation: ICE48
Directory 'FontsFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory FontsFolder
Evaluation: ICE48
Directory 'NetHoodFolder' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory NetHoodFolder
Evaluation: ICE48
Directory 'GAC' appears to be hardcoded in the property table to a local drive. ice48.html Directory Directory GAC
Evaluation: ICE48
Mismatched component reference. Entry 'registry65' of the Registry table belongs to component 'LocalMachine'. However, the formatted string in column 'Value' references file 'WINZIP32.EXE' which belongs to component 'WINZIP32.EXE'. Components are in the same feature. ice69.html Registry Value registry65
Evaluation: ICE69
 

I meant, upload the msi file.

From what I see in the log you posted, you probably repackaged the installation. After you repackage, it's good idea to carefully review the result and remove the files and registry settings that are obviously not needed, such as example desktop.ini and NTUSER.DAT.LOG.