[wix-users] Problem Updating

Thu Mar 1 10:33:18 PST 2018

Asking the naive question, would the driver be loaded by the kernel
requiring a reboot?

--
Edwin G. Castro

On Thu, Mar 1, 2018 at 10:31 AM, Jon Earle via wix-users <
wix-users at lists.wixtoolset.org> wrote:

> Yeah... So, I've been trying to narrow it down to which driver or sequence
> causes this.  I found that, I can Install (all) and Uninstall without
> issue... repeatedly.
>
> However, If I Install all (which generates log1 from the MSI), then Modify
> to remove the PCI driver (generating log2, which I posted), then it's
> already seeking a reboot.  If I Modify to add back PCI (log3), then
> Uninstall (log4), I get the log messages I posted previously.  So, to
> answer you question of what preceeded those lines:
>
> ....
> MSI (s) (F8:E4) [17:39:59:212]: Component: snmp_subagent_logs_dir;
> Installed: Absent;   Request: Null;   Action: Null
> MSI (s) (F8:E4) [17:39:59:212]: Component: snmp_subagent_settings;
> Installed: Absent;   Request: Null;   Action: Null
> MSI (s) (F8:E4) [17:39:59:212]: Note: 1: 2205 2:  3: BindImage
> MSI (s) (F8:E4) [17:39:59:212]: Note: 1: 2205 2:  3: ProgId
> MSI (s) (F8:E4) [17:39:59:212]: Note: 1: 2205 2:  3: PublishComponent
> MSI (s) (F8:E4) [17:39:59:212]: Note: 1: 2205 2:  3: SelfReg
> MSI (s) (F8:E4) [17:39:59:212]: Note: 1: 2205 2:  3: Extension
> MSI (s) (F8:E4) [17:39:59:212]: Note: 1: 2205 2:  3: Font
> MSI (s) (F8:E4) [17:39:59:212]: Note: 1: 2205 2:  3: Shortcut
> MSI (s) (F8:E4) [17:39:59:212]: Note: 1: 2205 2:  3: Class
> MSI (s) (F8:E4) [17:39:59:212]: Note: 1: 2205 2:  3: Icon
> MSI (s) (F8:E4) [17:39:59:212]: Note: 1: 2205 2:  3: TypeLib
> Action start 17:39:59: InstallValidate.
> MSI (s) (F8:E4) [17:39:59:215]: Note: 1: 2205 2:  3: _RemoveFilePath
> MSI (s) (F8:E4) [17:39:59:480]: PROPERTY CHANGE: Modifying CostingComplete
> property. Its current value is '0'. Its new value: '1'.
> MSI (s) (F8:E4) [17:39:59:480]: Note: 1: 2205 2:  3: BindImage
> MSI (s) (F8:E4) [17:39:59:480]: Note: 1: 2205 2:  3: ProgId
> MSI (s) (F8:E4) [17:39:59:480]: Note: 1: 2205 2:  3: PublishComponent
> MSI (s) (F8:E4) [17:39:59:480]: Note: 1: 2205 2:  3: SelfReg
> MSI (s) (F8:E4) [17:39:59:480]: Note: 1: 2205 2:  3: Extension
> MSI (s) (F8:E4) [17:39:59:480]: Note: 1: 2205 2:  3: Font
> MSI (s) (F8:E4) [17:39:59:480]: Note: 1: 2205 2:  3: Shortcut
> MSI (s) (F8:E4) [17:39:59:480]: Note: 1: 2205 2:  3: Class
> MSI (s) (F8:E4) [17:39:59:480]: Note: 1: 2205 2:  3: Icon
> MSI (s) (F8:E4) [17:39:59:480]: Note: 1: 2205 2:  3: TypeLib
> MSI (s) (F8:E4) [17:39:59:481]: Note: 1: 2727 2:
> MSI (s) (F8:E4) [17:39:59:503]: RESTART MANAGER: Did detect that a
> critical application holds file[s] in use, so a reboot will be necessary.
> MSI (s) (F8:E4) [17:39:59:503]: Note: 1: 1610
> MSI (s) (F8:E4) [17:39:59:519]: RESTART MANAGER: The user chose to go on
> with the installation, although a reboot will be required.
>
> If you like, I can post the whole Uninstall log, but I think the damage
> has already been done with the first removal of PCI drivers.
>
>
> ________________________________
> From: Hoover, Jacob <Jacob.Hoover at greenheck.com>
> Sent: Thursday, March 1, 2018 1:07 PM
> To: Jon Earle; WiX Toolset Users Mailing List; Nir Bar
> Subject: RE: [wix-users] Problem Updating
>
>
> And the lines in the previous message don’t appear in the logs.
>
>
>
> I did notice:
>
> DIFXAPP: A reboot is needed to uninstall the driver package
> '{21CC203C-C5CC-49BF-A858-2D44A4D79EDF}'.
>
> …
>
> DIFXAPP: A reboot is needed to uninstall the driver package
> '{6FE4BA08-7FEE-4746-9F9D-3539A236A109}'.
>
>
>
>
>
> From: Jon Earle [mailto:earlej at hotmail.com]
> Sent: Thursday, March 1, 2018 10:35 AM
> To: Hoover, Jacob <Jacob.Hoover at greenheck.com>; WiX Toolset Users Mailing
> List <wix-users at lists.wixtoolset.org>; Nir Bar <nir.bar at panel-sw.com>
> Subject: Re: [wix-users] Problem Updating
>
>
>
> Log file attached from the Modify action, removing the PCI drivers.
>
> ________________________________
>
> From: Hoover, Jacob <Jacob.Hoover at greenheck.com<mailto:
> Jacob.Hoover at greenheck.com>>
> Sent: Wednesday, February 28, 2018 5:33 PM
> To: WiX Toolset Users Mailing List; Nir Bar
> Cc: Jon Earle
> Subject: RE: [wix-users] Problem Updating
>
>
>
> What is in the log right before that line?
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf
> Of Jon Earle via wix-users
> Sent: Wednesday, February 28, 2018 4:27 PM
> To: Nir Bar <nir.bar at panel-sw.com<mailto:nir.bar at panel-sw.com>>; WiX
> Toolset Users Mailing List <wix-users at lists.wixtoolset.org<mailto:
> wix-users at lists.wixtoolset.org>>
> Cc: Jon Earle <earlej at hotmail.com<mailto:earlej at hotmail.com>>
> Subject: Re: [wix-users] Problem Updating
>
> We have a couple of system services that use the drivers in questions, so
> I tried forcing StopServices to occur right after InstallInitialize... no
> change.
>
> I noticed this in the log:
>
> MSI (s) (6C:5C) [17:20:57:973]: RESTART MANAGER: Did detect that a
> critical application holds file[s] in use, so a reboot will be necessary.
> MSI (s) (6C:5C) [17:20:57:973]: Note: 1: 1610 MSI (s) (6C:5C)
> [17:20:57:983]: RESTART MANAGER: The user chose to go on with the
> installation, although a reboot will be required.
> The setup must update files or services that cannot be updated while the
> system is running. If you choose to continue, a reboot will be required to
> complete the setup.
>
> Is there a way to determine exactly which "critical application" is
> holding which "files in use"?
>
>
> ________________________________
> From: Nir Bar <nir.bar at panel-sw.com<mailto:nir.bar at panel-sw.com>>
> Sent: Wednesday, February 28, 2018 2:15 AM
> To: WiX Toolset Users Mailing List
> Cc: Jon Earle
> Subject: Re: [wix-users] Problem Updating
>
> Seems like you shot yourself in the foot setting MSIRESTARTMANAGERCONTROL
> to DisableShutdown.
> The purpose of Restart Manager is to shutdown processes that are holding
> files in use so that system reboot will not be necessary. By setting it to
> DisableShutdown you prevent it from doing exactly that which ultimately may
> cause system reboot to be required.
>
> Instead, set MSIRESTARTMANAGERCONTROL to 0 or do not set it at all.
> Then, if you are aware of processes that hold files in use and are not
> part of your package, let Restart Manager control them by adding them with
> RestartResource elements.
>
>
> --
> Nir Bar, Independent WiX Expert. Creator of-
> JetBA: WiX WPF Bootstrapper User Interface Framework
> JetBA++: WiX Native Bootstrapper User Interface Framework
>
>
>
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>