[wix-users] Unable to upgrade per-machine driver package with burn bundle

[Steve Sanders]

Thanks for your reply, but this sequence did include a reboot. I have since
narrowed this down further to a problem in the driver package. Testing just
the driver msi separately, it works fine if I uninstall the old version and
install the new one separately, but updating, which does essentially the
same thing, fails. Comparing the logs line by line shows this in the
failing upgrade case:

DIFXAPP: ERROR:  Unable to start service 'dokan1' because of error 0x422

I assume this matches ERROR_SERVICE_DISABLED
1058 (0x422)
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it

I may be able to hack around this by repeating the driver installation
commands in a runonce registry entry or something, but why does the install
say it succeeded when the service couldn't be started? Log here:

https://gist.github.com/zanderz/e9882870a4b3ff4d0ba143ff724d7c56#file-dokan-log-L667


On Wed, Aug 3, 2016 at 1:00 AM, Jürgen Schäpker <Juergen.Schaepker at giepa.de>
wrote:

> Hi Steve,
>
> the uninstall of the Dokany driver requires a reboot as the driver file
> will only be removed then. Apparently it is not possible to upgrade file
> system drivers without intermittent reboot.
>
> -----Ursprüngliche Nachricht-----
> Von: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] Im Auftrag
> von Steve Sanders
> Gesendet: Mittwoch, 3. August 2016 00:35
> An: wix-users at lists.wixtoolset.org
> Betreff: [wix-users] Unable to upgrade per-machine driver package with
> burn bundle
>
> I've been trying to make a mixed bundle with a per-user application package
> and per-machine driver package. It seems to work fine on initial install,
> asking for elevation only when the drivers need to be applied. But when an
> upgrade is applied with newer driver package, it uninstalls the current
> driver without installing the new one, and I see a line like this in the
> log, which seems to explain what's going on:
>
> Skipping cross-scope dependency registration on package: Dokan_x64.msi,
> bundle scope: PerUser, package scope: PerMachine
>
> The UAC prompt does happen when running the updated bundle.
> I have seen other bugs and discussions around "mixed bundles", such as
>
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bundle-with-mixed-privilege-packages-td7601094.html
>
> Our fallback is to error out with a message to manually uninstall the
> existing driver package on update, but it would be nice to not have to do
> that.
>
> Bundle logs:
> https://gist.github.com/zanderz/efc710d9bf4e4099687b0edc056304b1
>
> The per machine package project file can be seen here:
>
> https://github.com/keybase/dokany/blob/zanderz/test_2016.08.02/dokan_wix/Dokan_x64.wxs
>
> Per user package:
>
> https://github.com/keybase/client/blob/zanderz/installer_2016.08.02/packaging/windows/WIXInstallers/KeybaseApps/KeybaseApps.wxs
>
> Burn bundle:
>
> https://github.com/keybase/client/blob/zanderz/installer_2016.08.02/packaging/windows/WIXInstallers/KeybaseBundle/Bundle.wxs
>
> Burn v3.10.2.2516
> Windows 10
>
> Am I correct in assuming that the per-machine package is gone after
> updating due to "Skipping cross-scope dependency registration", and if so,
> what can I do?
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> Email secured by Check Point
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>