Authenticode verification fails on clean Windows Xp sp3

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Authenticode verification fails on clean Windows Xp sp3

Sørensen, Rune
Hi All,

I'm having some issues with the following use case:  Some of our users install our product on a clean Windows XP SP3 which has never been connected to the internet (and might never be). When Burn tries to validate the authenticode of the packages, it fails. However, if the system is connected to the internet, the next installation attempt succeeds. After investigating the issue, I assume this issue is related to burn/WinVerifyTrust() being unable to download a certificate revocation list.
Another use case with the same result: Install on a clean windows xp sp3 WITH internet access. First installation attempt fails, second succeeds.

Since these use cases is pretty common I was hoping some of you have had similar issues. Could this be related to the certificate chain used when signing msi-packages?

Definition of "clean": The state just after installation of windows has been completed - no windows updates and no other programs installed.


Extract from the log file (the issue is the same on v3.7.1224.0):

[0634:04E8][2013-02-20T15:15:14]i001: Burn v3.7.1203.0, Windows v5.1 (Build 2600: Service Pack 3), path: Z:\BootStrapper\bin\Debug\ product .exe, cmdline: ''
...
[0634:07A0][2013-02-20T15:15:22]i338: Acquiring package: product_x86.msi, payload: product_x86.msi, copy from: Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed authenticode verification of payload: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed to verify signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e310: Failed to verify payload: product_x86.msi at path: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting file.
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed to cache payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:23]e314: Failed to cache payload: product_x86.msi from working path: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\product_x86.msi, error: 0x800b010a.
[0634:07A0][2013-02-20T15:15:23]e349: Application requested retry of payload: product_x86.msi, encountered error: 0x800b010a. Retrying...
[0634:07A0][2013-02-20T15:15:26]i338: Acquiring package: product_x86.msi, payload: product_x86.msi, copy from: Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed authenticode verification of payload: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed to verify signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e310: Failed to verify payload: product_x86.msi at path: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting file.
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed to cache payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:26]e314: Failed to cache payload: product_x86.msi from working path: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\product_x86.msi, error: 0x800b010a.
[0634:07A0][2013-02-20T15:15:26]e349: Application requested retry of payload: product_x86.msi, encountered error: 0x800b010a. Retrying...
[0634:07A0][2013-02-20T15:15:29]i338: Acquiring package: product_x86.msi, payload: product_x86.msi, copy from: Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed authenticode verification of payload: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed to verify signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e310: Failed to verify payload: product_x86.msi at path: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting file.
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed to cache payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:29]e314: Failed to cache payload: product_x86.msi from working path: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\product_x86.msi, error: 0x800b010a.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: Authenticode verification fails on clean Windows Xp sp3

Peter Shirtcliffe
You might be missing the necessary root certificate on those machines. I
think this is the link you need. Some certificates are updated by Windows
Update but not all so look at the certificate chain of the exe (right click /
properties) on an affected machine to see if it is installed.
http://www.microsoft.com/en-us/download/details.aspx?id=35945

-----Original Message-----
From: Sørensen, Rune [mailto:[hidden email]]
Sent: 21 February 2013 07:40
To: [hidden email]
Subject: [WiX-users] Authenticode verification fails on clean Windows Xp sp3

Hi All,

I'm having some issues with the following use case:  Some of our users
install our product on a clean Windows XP SP3 which has never been connected
to the internet (and might never be). When Burn tries to validate the
authenticode of the packages, it fails. However, if the system is connected
to the internet, the next installation attempt succeeds. After investigating
the issue, I assume this issue is related to burn/WinVerifyTrust() being
unable to download a certificate revocation list.
Another use case with the same result: Install on a clean windows xp sp3 WITH
internet access. First installation attempt fails, second succeeds.

Since these use cases is pretty common I was hoping some of you have had
similar issues. Could this be related to the certificate chain used when
signing msi-packages?

Definition of "clean": The state just after installation of windows has been
completed - no windows updates and no other programs installed.


Extract from the log file (the issue is the same on v3.7.1224.0):

[0634:04E8][2013-02-20T15:15:14]i001: Burn v3.7.1203.0, Windows v5.1 (Build
2600: Service Pack 3), path: Z:\BootStrapper\bin\Debug\ product .exe,
cmdline: ''
...
[0634:07A0][2013-02-20T15:15:22]i338: Acquiring package: product_x86.msi,
payload: product_x86.msi, copy from:
Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed authenticode
verification of payload: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed to verify
signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e310: Failed to verify payload:
product_x86.msi at path: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting
file.
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed to cache
payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:23]e314: Failed to cache payload:
product_x86.msi from working path:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\pro
duct_x86.msi, error: 0x800b010a.
[0634:07A0][2013-02-20T15:15:23]e349: Application requested retry of payload:
product_x86.msi, encountered error: 0x800b010a. Retrying...
[0634:07A0][2013-02-20T15:15:26]i338: Acquiring package: product_x86.msi,
payload: product_x86.msi, copy from:
Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed authenticode
verification of payload: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed to verify
signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e310: Failed to verify payload:
product_x86.msi at path: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting
file.
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed to cache
payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:26]e314: Failed to cache payload:
product_x86.msi from working path:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\pro
duct_x86.msi, error: 0x800b010a.
[0634:07A0][2013-02-20T15:15:26]e349: Application requested retry of payload:
product_x86.msi, encountered error: 0x800b010a. Retrying...
[0634:07A0][2013-02-20T15:15:29]i338: Acquiring package: product_x86.msi,
payload: product_x86.msi, copy from:
Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed authenticode
verification of payload: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed to verify
signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e310: Failed to verify payload:
product_x86.msi at path: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting
file.
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed to cache
payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:29]e314: Failed to cache payload:
product_x86.msi from working path:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\pro
duct_x86.msi, error: 0x800b010a.
-----------------------------------------------------------------------------
-
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK.


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: Authenticode verification fails on clean Windows Xp sp3

Sørensen, Rune
Installing the updated root certificates manually did indeed resolve the issue. The next issue is to determine how to install the root certificates using Burn before the other packages is verified??

-----Original Message-----
From: Peter Shirtcliffe [mailto:[hidden email]]
Sent: 21. februar 2013 11:38
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Authenticode verification fails on clean Windows Xp sp3

You might be missing the necessary root certificate on those machines. I think this is the link you need. Some certificates are updated by Windows Update but not all so look at the certificate chain of the exe (right click /
properties) on an affected machine to see if it is installed.
http://www.microsoft.com/en-us/download/details.aspx?id=35945

-----Original Message-----
From: Sørensen, Rune [mailto:[hidden email]]
Sent: 21 February 2013 07:40
To: [hidden email]
Subject: [WiX-users] Authenticode verification fails on clean Windows Xp sp3

Hi All,

I'm having some issues with the following use case:  Some of our users install our product on a clean Windows XP SP3 which has never been connected to the internet (and might never be). When Burn tries to validate the authenticode of the packages, it fails. However, if the system is connected to the internet, the next installation attempt succeeds. After investigating the issue, I assume this issue is related to burn/WinVerifyTrust() being unable to download a certificate revocation list.
Another use case with the same result: Install on a clean windows xp sp3 WITH internet access. First installation attempt fails, second succeeds.

Since these use cases is pretty common I was hoping some of you have had similar issues. Could this be related to the certificate chain used when signing msi-packages?

Definition of "clean": The state just after installation of windows has been completed - no windows updates and no other programs installed.


Extract from the log file (the issue is the same on v3.7.1224.0):

[0634:04E8][2013-02-20T15:15:14]i001: Burn v3.7.1203.0, Windows v5.1 (Build
2600: Service Pack 3), path: Z:\BootStrapper\bin\Debug\ product .exe,
cmdline: ''
...
[0634:07A0][2013-02-20T15:15:22]i338: Acquiring package: product_x86.msi,
payload: product_x86.msi, copy from:
Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed authenticode verification of payload: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed to verify signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e310: Failed to verify payload:
product_x86.msi at path: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting file.
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed to cache
payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:23]e314: Failed to cache payload:
product_x86.msi from working path:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\pro
duct_x86.msi, error: 0x800b010a.
[0634:07A0][2013-02-20T15:15:23]e349: Application requested retry of payload:
product_x86.msi, encountered error: 0x800b010a. Retrying...
[0634:07A0][2013-02-20T15:15:26]i338: Acquiring package: product_x86.msi,
payload: product_x86.msi, copy from:
Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed authenticode verification of payload: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed to verify signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e310: Failed to verify payload:
product_x86.msi at path: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting file.
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed to cache
payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:26]e314: Failed to cache payload:
product_x86.msi from working path:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\pro
duct_x86.msi, error: 0x800b010a.
[0634:07A0][2013-02-20T15:15:26]e349: Application requested retry of payload:
product_x86.msi, encountered error: 0x800b010a. Retrying...
[0634:07A0][2013-02-20T15:15:29]i338: Acquiring package: product_x86.msi,
payload: product_x86.msi, copy from:
Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed authenticode verification of payload: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed to verify signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e310: Failed to verify payload:
product_x86.msi at path: C:\Documents and Settings\All Users\Application Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting file.
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed to cache
payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:29]e314: Failed to cache payload:
product_x86.msi from working path:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\pro
duct_x86.msi, error: 0x800b010a.
-----------------------------------------------------------------------------
-
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.  Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK.


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: Authenticode verification fails on clean WindowsXp sp3

Wyrdfish
I would write a KB article that explains the issue and leave it as is.

Windows machines need updates installed whether it's via the internet or an
internal update server, it's not your installers job to do basic IT tasks for
an organisation.

Dave

-----Original Message-----
From: Sørensen, Rune [mailto:[hidden email]]
Sent: 21 February 2013 13:31
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Authenticode verification fails on clean WindowsXp
sp3

Installing the updated root certificates manually did indeed resolve the
issue. The next issue is to determine how to install the root certificates
using Burn before the other packages is verified??

-----Original Message-----
From: Peter Shirtcliffe [mailto:[hidden email]]
Sent: 21. februar 2013 11:38
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Authenticode verification fails on clean Windows Xp
sp3

You might be missing the necessary root certificate on those machines. I
think this is the link you need. Some certificates are updated by Windows
Update but not all so look at the certificate chain of the exe (right click /
properties) on an affected machine to see if it is installed.
http://www.microsoft.com/en-us/download/details.aspx?id=35945

-----Original Message-----
From: Sørensen, Rune [mailto:[hidden email]]
Sent: 21 February 2013 07:40
To: [hidden email]
Subject: [WiX-users] Authenticode verification fails on clean Windows Xp sp3

Hi All,

I'm having some issues with the following use case:  Some of our users
install our product on a clean Windows XP SP3 which has never been connected
to the internet (and might never be). When Burn tries to validate the
authenticode of the packages, it fails. However, if the system is connected
to the internet, the next installation attempt succeeds. After investigating
the issue, I assume this issue is related to burn/WinVerifyTrust() being
unable to download a certificate revocation list.
Another use case with the same result: Install on a clean windows xp sp3 WITH
internet access. First installation attempt fails, second succeeds.

Since these use cases is pretty common I was hoping some of you have had
similar issues. Could this be related to the certificate chain used when
signing msi-packages?

Definition of "clean": The state just after installation of windows has been
completed - no windows updates and no other programs installed.


Extract from the log file (the issue is the same on v3.7.1224.0):

[0634:04E8][2013-02-20T15:15:14]i001: Burn v3.7.1203.0, Windows v5.1 (Build
2600: Service Pack 3), path: Z:\BootStrapper\bin\Debug\ product .exe,
cmdline: ''
...
[0634:07A0][2013-02-20T15:15:22]i338: Acquiring package: product_x86.msi,
payload: product_x86.msi, copy from:
Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed authenticode
verification of payload: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed to verify
signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:23]e310: Failed to verify payload:
product_x86.msi at path: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting
file.
[03DC:0644][2013-02-20T15:15:23]e000: Error 0x800b010a: Failed to cache
payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:23]e314: Failed to cache payload:
product_x86.msi from working path:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\pro
duct_x86.msi, error: 0x800b010a.
[0634:07A0][2013-02-20T15:15:23]e349: Application requested retry of payload:
product_x86.msi, encountered error: 0x800b010a. Retrying...
[0634:07A0][2013-02-20T15:15:26]i338: Acquiring package: product_x86.msi,
payload: product_x86.msi, copy from:
Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed authenticode
verification of payload: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed to verify
signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:26]e310: Failed to verify payload:
product_x86.msi at path: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting
file.
[03DC:0644][2013-02-20T15:15:26]e000: Error 0x800b010a: Failed to cache
payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:26]e314: Failed to cache payload:
product_x86.msi from working path:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\pro
duct_x86.msi, error: 0x800b010a.
[0634:07A0][2013-02-20T15:15:26]e349: Application requested retry of payload:
product_x86.msi, encountered error: 0x800b010a. Retrying...
[0634:07A0][2013-02-20T15:15:29]i338: Acquiring package: product_x86.msi,
payload: product_x86.msi, copy from:
Z:\BootStrapper\bin\Debug\product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed authenticode
verification of payload: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed to verify
signature of payload: product_x86.msi
[03DC:0644][2013-02-20T15:15:29]e310: Failed to verify payload:
product_x86.msi at path: C:\Documents and Settings\All Users\Application
Data\Package Cache\.unverified\product_x86.msi, error: 0x800b010a. Deleting
file.
[03DC:0644][2013-02-20T15:15:29]e000: Error 0x800b010a: Failed to cache
payload: product_x86.msi
[0634:07A0][2013-02-20T15:15:29]e314: Failed to cache payload:
product_x86.msi from working path:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{ee9f0de4-a315-4ed6-a2a5-a0dcee24ad78}\pro
duct_x86.msi, error: 0x800b010a.
-----------------------------------------------------------------------------
-
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without acting upon or copying any of its contents, and we
further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
7DY, UK.


-----------------------------------------------------------------------------
-
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

-----------------------------------------------------------------------------
-
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

CustomAction : FirstSequence/Rollback, OncePerProcess/Commit

Gabriel Ivanes
In reply to this post by Peter Shirtcliffe
Hello,

Anyone knows why does the bit FirstSequence automatically set Rollback's
bit ?
The same with OncePerProcess and Commit.
I made an immediat custom action with FirstSequence but i don't want
rollback's bit.
No problem in execution, but i'm just curious why.
Thanks.

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|

Re: CustomAction : FirstSequence/Rollback, OncePerProcess/Commit

Bob Arnson-6
On 21-Feb-13 09:13, Gabriel Ivanes wrote:
> Anyone knows why does the bit FirstSequence automatically set Rollback's
> bit ?
> The same with OncePerProcess and Commit.
Because they're the same bits. msidbCustomActionTypeFirstSequence and
msidbCustomActionTypeOncePerProcess are only valid for immediate custom
actions, so MSI reused them for deferred CAs.

--
sig://boB
http://joyofsetup.com/


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users