[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 578
  • Last Modified:

Uninstallation using msiexec /x has diferent results in laptop and PC using Vista home premium and ultimate respectively

Hi,
While uninstallaging our product in hp laptop with vista home premium using msiexec /x{Productcode} , the installation is proper but the same thing when i do in a pc with vista ultimate i  see that the files are not being removed from /windows/system32 ... i have attached the .msi file in

http://www.2shared.com/file/4290860/c7362e70/VFS201_DDK_2_7_0_39.html
0
prasant_hyd
Asked:
prasant_hyd
  • 2
1 Solution
 
Vadim RappCommented:
Produce log files in both cases and compare - find the place where it removes z file in one, and does not remove in another. If you don't find anything, upload the log files, and I will look.

But I'd note that best practices tell to "avoid installing non-permanent system components to the SystemFolder". If you run validation on your package, you will probably see this as ICE09.
0
 
prasant_hydAuthor Commented:
Hi,
I have put those logs here
http://www.2shared.com/file/4295717/2a919a1b/uninstall_39.html
http://www.2shared.com/file/4295721/e8df6ced/uninstall_HP_39.html

uninstall_39.html : its in a pc with vista ultimate, and its is not uninstallating properly , files are not being removed from windows/system32
uninstall_HP_39.html: working with vista home premium , the uninstallation is proper here
0
 
Rory de LeurCommented:
Try this:
Your logifle uninstall_39 notes "MSI (s) (1C:00) [12:55:51:723]: Machine policy value 'AlwaysInstallElevated' is 0", witch means that is using user privileges, the other log doesnt mention it at all and probably it's using system privileges. This will explain why the uninstall isn't doing it's job properly.

Change the next registry key on your Ultimate to change this behavior:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
AlwaysInstallElevated = 1

For more info about the key:
- http://msdn.microsoft.com/en-us/library/aa367561(VS.85).aspx 
0
 
Vadim RappCommented:
If you mean files such as vfsEMPIRE_2.DLL - the answer is in the word "PreviouslyPinned" in the log, for the component this file belongs to.

Most likely it's because of the shared count for this dll under  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs


0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now