Re: [WiX-users] Reboot required during major upgrade in-between uninstall and re-install

2015-06-24 Thread Nir Bar
You may be able to schedule RemoveExistingProducts after InstallExecute if
you adhere to  component rules
https://msdn.microsoft.com/en-us/library/aa372795(v=vs.85).aspx  . This
will perform the uninstall after the reinstall and reboot on installation
end.



-
Nir Bar 
Freelance Developer 
Mail: nir@panel-sw.com 
Web: www.panel-sw.com 
   - C++ On Windows, Linux and Embedded Platforms 
   - WiX  InstallShield 
--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reboot-required-during-major-upgrade-in-between-uninstall-and-re-install-tp7600688p7600713.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical  virtual servers, alerts via email  sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Reboot required during major upgrade in-between uninstall and re-install

2015-06-23 Thread Phill Hogland
While doing other research I came across these threads, and made note of them
in the event that I might need them in the future.  They might be helpful to
you:

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Resume-Installation-Plan-td7579146.html

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-restore-after-reboot-not-working-td7585217.html#a7585250





--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reboot-required-during-major-upgrade-in-between-uninstall-and-re-install-tp7600688p7600690.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical  virtual servers, alerts via email  sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Reboot required during major upgrade in-between uninstall and re-install

2015-06-23 Thread Rami
Thank you, Phil.

Unfortunately, I only have one MSI that installs both my application and
ext2fsd.

Are you suggesting that I split them up into two MSIs and then bundle them
using Burn?

Thank you.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reboot-required-during-major-upgrade-in-between-uninstall-and-re-install-tp7600688p7600693.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical  virtual servers, alerts via email  sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Reboot required during major upgrade in-between uninstall and re-install

2015-06-23 Thread Phill Hogland
I guess I misread your question and assumed that you were using Burn.  Given
that I came across those posts I thought they might be helpful but if you
are not using Burn I can't really make any suggestion.

I have only used the approach of putting each app and each driver in a
separate UI-less MSI and then chaining them using Burn.  I have some bundles
which have several hundred msi packages in the chain and I find that this
approach works well for me. 



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reboot-required-during-major-upgrade-in-between-uninstall-and-re-install-tp7600688p7600695.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical  virtual servers, alerts via email  sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] Reboot required during major upgrade in-between uninstall and re-install

2015-06-22 Thread Rami Abughazaleh
Hi.

I have a setup installer that installs ext2fsd v0.51 (a third party windows
file system driver found here: http://www.ext2fsd.com/) using the WiX
Toolset v3.5.2201 and DIFxApp:

difx:Driver PlugAndPlayPrompt=no AddRemovePrograms=no /

I basically followed the guide here:
http://kobyk.wordpress.com/2008/10/21/installing-filter-drivers-with-difxapp-and-a-wix-v3-msi/

Install and uninstall work without issues.

The uninstall detects a reboot is required because ext2fsd cannot be
stopped/unloaded on demand.

When asked about this behavior, the ext2fsd author indicated Ext2Fsd does
NOT support 'STOP' or 'UNLOAD' any more. There are various filters on the
top [and] below [the] file system driver. If you [forcefully] unload the
[files system driver], there might be unexpected NULL structures reference.
All known windows file systems are NOT supporting 'UNLOAD'.
See http://sourceforge.net/p/ext2fsd/discussion/143329/thread/d829b011/

And so the end-user is prompted to reboot after uninstall.

However, the problem occurs during a major upgrade where an uninstall of
the old version is scheduled before the re-install of the new version:

InstallExecuteSequence
...
RemoveExistingProducts After=InstallValidate /
...

The ext2fsd driver is uninstalled but is not re-installed.

Here are some relevant snippets from the upgrade MSI log file on Windows 7
x64:

...
MSI (s) (DC:78) [17:57:41:841]: PROPERTY CHANGE: Adding ADDLOCAL property.
Its value is 'ext2fsd'.
...
MSI (s) (DC:78) [17:57:57:503]: Feature: ext2fsd; Installed: Absent;
Request: Local;   Action: Local
...
MSI (s) (DC:78) [17:57:57:613]: Component: ext2fsd; Installed: Absent;
Request: Local;   Action: Local;   Client State: Unknown
...
MSI (s) (DC:20) [17:58:07:924]: Feature: ext2fsd; Installed: Local;
Request: Absent;   Action: Absent
...
MSI (s) (DC:20) [17:58:07:955]: Component: ext2fsd; Installed: Local;
Request: Absent;   Action: Absent;   Client State: Local
...
DIFXAPP: INFO: 'Component' is 'ext2fsd'
...
DIFXAPP: INFO: Component state 0x3 - 0x2
...
DIFXAPP: INFO: 'ComponentId' is {01234567-89AB-CDEF-0123-4567890ABCDE}
...
DIFXAPP: INFO: 'Flags' is 6
...
DIFXAPP: INFO: component path is
...
DIFXAPP: INFO: user SID of user performing the install is
'S-1-5-21-31901841-3674642990-1940449072-1000'.
...
DIFXAPP: INFO: creating
HKEY_USERS\S-1-5-21-31901841-3674642990-1940449072-1000\Software\Microsoft\Windows\CurrentVersion\DIFxApp\Components\{01234567-89AB-CDEF-0123-4567890ABCDE}
(User's SID: 'S-1-5-21-31901841-3674642990-1940449072-1000') ...
MSI (s) (DC!00) [17:58:09:250]: PROPERTY CHANGE: Adding MsiUninstallDrivers
property. Its value is '2.1.1 5 {01234567-89AB-CDEF-0123-4567890ABCDE}
6ProductNameCompanyName'.
MSI (s) (DC!00) [17:58:09:250]: Doing action: MsiUninstallDrivers
Action 17:58:09: MsiUninstallDrivers.
Action start 17:58:09: MsiUninstallDrivers.
MsiUninstallDrivers:
Action ended 17:58:09: MsiUninstallDrivers. Return value 1.
...
DIFXAPP: RETURN: ProcessDriverPackages() 0 (0x0)
...
Action ended 17:58:09: MsiProcessDrivers. Return value 1.
...
MSI (s) (DC:20) [17:58:10:249]: Executing op:
FeatureUnpublish(Feature=ext2fsd,Parent=ExtendedFileSystemDriver,Absent=2,Component=dJ8U!QpmK9lZUY0Nwo{I)
UnpublishFeatures: Feature: ext2fsd
MSI (s) (DC:20) [17:58:26:223]: Executing op:
FileRemove(,FileName=ext2fsd.sys,,ComponentId={01234567-89AB-CDEF-0123-4567890ABCDE})
RemoveFiles: File: ext2fsd.sys, Directory: C:\Program Files
(x86)\CompanyName\ProductName\ext2fsd\
MSI (s) (DC:20) [17:58:26:239]: Verifying accessibility of file: ext2fsd.sys
...
MSI (s) (DC:20) [17:58:32:104]: Executing op:
ActionStart(Name=MsiUninstallDrivers,,)
Action 17:58:32: MsiUninstallDrivers.
MSI (s) (DC:20) [17:58:32:104]: Executing op:
CustomActionSchedule(Action=MsiUninstallDrivers,ActionType=3073,Source=BinaryData,Target=UninstallDriverPackages,CustomActionData=2.1.1
5 {01234567-89AB-CDEF-0123-4567890ABCDE} 6ProductNameCompanyName)
...
MSI (s) (DC:24) [17:58:32:104]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSIAA6A.tmp, Entrypoint: UninstallDriverPackages
MSI (s) (DC:D4) [17:58:32:104]: Generating random cookie.
MSI (s) (DC:D4) [17:58:32:120]: Created Custom Action Server with PID 2172
(0x87C).
MSI (s) (DC:3C) [17:58:32:229]: Running as a service.
MSI (s) (DC:3C) [17:58:32:245]: Hello, I'm your 64bit Elevated custom
action server.
...
DIFXAPP: UninstallDriverPackages()
...
DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.1.
...
DIFXAPP: 'CustomActionData' property 'UI Level' is 5.
...
DIFXAPP: 'CustomActionData' property 'componentId' is
{01234567-89AB-CDEF-0123-4567890ABCDE}.
...
DIFXAPP: 'CustomActionData' property 'flags' is 0x6.
...
DIFXAPP: 'CustomActionData' property 'ProductName' is ProductName.
...
DIFXAPP: 'CustomActionData' property 'ManufacturerName' is CompanyName.
...
DIFXAPP: INFO: user SID of user performing the install is
'S-1-5-21-31901841-3674642990-1940449072-1000'.
...
DIFXAPP: INFO: opening