I have repackaged WinPCap 4.1.1 with AdminStudio 8.0. When uninstalling, files in System32 and System32\Drivers folder do not get removed. I can go and remove these manually after uninstall without a problem so they do not appear to be in use. Why do these files not get removed? They are not shared and specific only to this application. When generating the MSI I unchecked the box for "Mark components destined for the System folder as permanent" but that did not make any difference. Files in Program Files do get removed during uninstall.
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
What are the settings on the components that these files are a member of? Are these components set to 'leave installed on uninstall' (that's Wise terminology, not sure what IS states)?

Try setting the comoponent attribute to 0 to see if this makes a difference, although this will remove any of the other settings on those components (e.g. increment dll count, never overwrite etc)
Answered 02/01/2010 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
The attributes were originally set to 8. I tried setting the attribute field for the components to 0 in the Component table but they are still getting left behind during uninstall. I have the Zenworks edition of IS which is very limited so I can't check to see what IS is doing. I have to use InstEdit or Orca to make changes.
Answered 02/02/2010 by: joedown
Second Degree Brown Belt

Please log in to comment
0
The attribute value 0 should work as I also faced same issue before and was solved.Hope you are running ur modified MSI on a clean machine.
Also, please check what log says..
Let us know the solution when solved..
Answered 02/04/2010 by: guy.forum
Orange Belt

Please log in to comment
0
the winpcap driver (file) may be in-use, is it deleted after a reboot?
Answered 02/04/2010 by: AngelD
Red Belt

Please log in to comment
0
I don't believe any files are in use since I can manually delete them all right after I uninstall. I did find something interesting in the uninstall log but I do not know what it means.

Sorry, the code tag does not work since the change.

MSI (s) (C4:94) [16:10:07:890]: Disallowing uninstallation of component: {7AC0BF29-78DD-437B-8BA3-2A12810BDA8F} since another client exists
MSI (s) (C4:94) [16:10:07:890]: Disallowing uninstallation of component: {F7E4E483-BFF4-4BE1-8CCB-8DABECBFE1B2} since another client exists
MSI (s) (C4:94) [16:10:07:890]: Disallowing uninstallation of component: {14B1021A-3C15-4553-AF21-B62993B5B647} since another client exists
Action start 16:10:07: CostFinalize.

The component ids match the three files that are getting left behind. What does "since another client exists" mean?
Answered 02/04/2010 by: joedown
Second Degree Brown Belt

Please log in to comment
0
Joe,

Long shot, but...

you might want to check if any shared DLL counters happen to exist for these files prior to your (un)installation. If this is the case Windows Installer will register an extra client for the components containing these DLL's at install time. (Component Attribute value of 8 would cause these to be increased too, and created if absent)

Have a look at HKLM\Software\Microsoft\Windows\CurrentVersion\SharedDLLs for the counters
Another place to look could be HKCR\Installer\Components and then look for the hashed up version of your component GUIDS

PJ
Answered 02/05/2010 by: pjgeutjens
Red Belt

Please log in to comment
0
PJ,

Not a long shot at all; there is another product that also installed these component(s)/file(s) which prevents the uninstall to remove them.
Answered 02/05/2010 by: AngelD
Red Belt

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