Discussion:
[WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container
Neil Sleightholm
2014-08-18 17:51:35 UTC
Permalink
Has anyone seen the issue below?

We are deploying MSIs via a remote PowerShell script and last week it suddenly started failing with this error. We have tracked the problem down to Hotfix 2918614 (released 12 Aug 2014) but were curious if anyone else is experiencing the problem or know what is causing it.

MSI (s) (04:A0) [11:10:07:189]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{0853D2F3-3147-45BE-A153-23E5915150B3}
MSI (s) (04:A0) [11:10:07:189]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (04:A0) [11:10:07:221]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (04:A0) [11:10:07:314]: SECREPAIR: New Hash Database creation complete.
MSI (s) (04:A0) [11:10:07:938]: SECREPAIR: CryptAcquireContext: Could not create the default key container
MSI (s) (04:A0) [11:10:07:938]: SECREPAIR: Crypt Provider not initialized. Error:-2146892987
MSI (s) (04:A0) [11:10:07:938]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxxxxxxxx.msi: for computing its hash. Error: -2146892987
MSI (s) (04:A0) [11:10:07:938]: SECREPAIR: Failed to create hash for the install source files
MSI (s) (04:A0) [11:10:07:938]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (04:A0) [11:10:07:938]: SECUREREPAIR: SecureRepair Failed. Error code: 80090345F56034B8
Action start 11:10:07: ProcessComponents.
MSI (s) (04:A0) [11:10:07:938]:
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.

Neil

Neil Sleightholm
X2 Systems Limited
***@x2systems.com<mailto:***@x2systems.com>
Phill Hogland
2014-08-18 19:12:43 UTC
Permalink
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918614-causing-overlapped-i-o-operation-progress-errors.html




--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596418.html
Sent from the wix-users mailing list archive at Nabble.com.
Neil Sleightholm
2014-08-18 21:54:46 UTC
Permalink
Thanks, seen that one and this one https://community.logos.com/forums/p/87997/617278.aspx. Both look similar.

Neil

-----Original Message-----
From: Phill Hogland [mailto:***@rimage.com]
Sent: 18 August 2014 20:13
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918614-causing-overlapped-i-o-operation-progress-errors.html




--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596418.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Matt O'Connell
2014-08-26 10:05:42 UTC
Permalink
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of antivirus
and we presumed it's some kind of conflict with that but we've had no
success with disabling Anti-virus with msconfig. However removing the kb
update has fixed it for at least one customer. I'm hoping to find a
recipe to replicate it but we're not there yet.

I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one https://community.logos.com/forums/p/87997/617278.aspx. Both look similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918614-causing-overlapped-i-o-operation-progress-errors.html
--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596418.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Matt O'Connell
2014-08-26 10:35:12 UTC
Permalink
We get a slightly different error out of CryptAcquireContext, ours
follow this pattern:
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file
already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation
complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
CryptAcquireContext
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not
initialized. Error:0
MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running
CryptAcquireContext
MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not
initialized. Error:0
MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running
CryptAcquireContext
MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not
initialized. Error:0
MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running
CryptAcquireContext
MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not
initialized. Error:0
MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running
CryptAcquireContext
MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not
initialized. Error:997
MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to
CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its
hash. Error: 997
MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the
install source files
MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8

Error 997 being the Windows error 'Overlapped I/O operation is in
progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig. However
removing the kb update has fixed it for at least one customer. I'm
hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918614-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596418.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Rob Mensching
2014-08-26 15:15:15 UTC
Permalink
How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?

_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:***@gmail.com]
Sent: Tuesday, August 26, 2014 3:35 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

We get a slightly different error out of CryptAcquireContext, ours follow this pattern:
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Error: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8

Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig. However
removing the kb update has fixed it for at least one customer. I'm
hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb29186
14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPA
IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7
596414p7596418.html Sent from the wix-users mailing list archive at
Nabble.com.
---------------------------------------------------------------------
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------------------------------------------
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Matt O'Connell
2014-08-26 16:02:17 UTC
Permalink
Custom Autorun/Setup.exe (elevating) that's been working fine for years,
OR on the CMD line line msiexec /i path to msi (where it will prompt to
elevate as well).
Post by Rob Mensching
How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/
-----Original Message-----
Sent: Tuesday, August 26, 2014 3:35 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Error: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig. However
removing the kb update has fixed it for at least one customer. I'm
hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb29186
14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPA
IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7
596414p7596418.html Sent from the wix-users mailing list archive at
Nabble.com.
---------------------------------------------------------------------
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------------------------------------------
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Rob Mensching
2014-08-26 16:44:45 UTC
Permalink
Okay. That points to the fix having issues and not being isolated to Burn. Which, fortunately or unfortunately, means Microsoft probably needs to fix the fix.

_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:***@gmail.com]
Sent: Tuesday, August 26, 2014 9:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Custom Autorun/Setup.exe (elevating) that's been working fine for years, OR on the CMD line line msiexec /i path to msi (where it will prompt to elevate as well).
Post by Rob Mensching
How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/
-----Original Message-----
Sent: Tuesday, August 26, 2014 3:35 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Error: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig. However
removing the kb update has fixed it for at least one customer. I'm
hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb29186
14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPA
IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7
596414p7596418.html Sent from the wix-users mailing list archive at
Nabble.com.
---------------------------------------------------------------------
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------------------------------------------
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
K***@statcan.gc.ca
2014-08-26 19:52:29 UTC
Permalink
Has anyone with a support contract or the like with Microsoft asked about this? I've pre-emptively raised a concern with some of my colleagues but people don't know what to make of a bunch of isolated forum posts/this list's thread.




Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
***@statcan.gc.ca
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Rob Mensching [mailto:***@firegiant.com]
Sent: August-26-14 12:45 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Okay. That points to the fix having issues and not being isolated to Burn. Which, fortunately or unfortunately, means Microsoft probably needs to fix the fix.

_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:***@gmail.com]
Sent: Tuesday, August 26, 2014 9:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Custom Autorun/Setup.exe (elevating) that's been working fine for years, OR on the CMD line line msiexec /i path to msi (where it will prompt to elevate as well).
Post by Rob Mensching
How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-----Original Message-----
Sent: Tuesday, August 26, 2014 3:35 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Err!
or: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
Post by Rob Mensching
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig. However
removing the kb update has fixed it for at least one customer. I'm
hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918
6 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREP
A
IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp
7 596414p7596418.html Sent from the wix-users mailing list archive
at Nabble.com.
--------------------------------------------------------------------
-
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
-
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
John Cooper
2014-08-26 20:10:12 UTC
Permalink
We have a support contract, and I have forwarded this thread to my manager as it is of some concern, although we haven't seen this yet. If it hits us, we'll definitely be looking into it. Meanwhile, I'll politic for further investigation.

--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: ***@statcan.gc.ca [mailto:***@statcan.gc.ca]
Sent: Tuesday, August 26, 2014 2:52 PM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Has anyone with a support contract or the like with Microsoft asked about this? I've pre-emptively raised a concern with some of my colleagues but people don't know what to make of a bunch of isolated forum posts/this list's thread.




Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 ***@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Rob Mensching [mailto:***@firegiant.com]
Sent: August-26-14 12:45 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Okay. That points to the fix having issues and not being isolated to Burn. Which, fortunately or unfortunately, means Microsoft probably needs to fix the fix.

_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:***@gmail.com]
Sent: Tuesday, August 26, 2014 9:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Custom Autorun/Setup.exe (elevating) that's been working fine for years, OR on the CMD line line msiexec /i path to msi (where it will prompt to elevate as well).
Post by Rob Mensching
How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-----Original Message-----
Sent: Tuesday, August 26, 2014 3:35 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Err!
or: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
Post by Rob Mensching
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig. However
removing the kb update has fixed it for at least one customer. I'm
hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918
6 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREP
A
IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp
7 596414p7596418.html Sent from the wix-users mailing list archive
at Nabble.com.
--------------------------------------------------------------------
-
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
-
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
Rob Mensching
2014-08-26 20:33:34 UTC
Permalink
FWIW, we haven't seen this with any FireGiant customers yet. That's a large part of why I'm at a loss.

However, we have been hearing stories of other issues in the last couple batches of updates from Microsoft. Quality control may have slipped up there a bit recently.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: John Cooper [mailto:***@jackhenry.com]
Sent: Tuesday, August 26, 2014 1:10 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

We have a support contract, and I have forwarded this thread to my manager as it is of some concern, although we haven't seen this yet. If it hits us, we'll definitely be looking into it. Meanwhile, I'll politic for further investigation.

--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: ***@statcan.gc.ca [mailto:***@statcan.gc.ca]
Sent: Tuesday, August 26, 2014 2:52 PM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Has anyone with a support contract or the like with Microsoft asked about this? I've pre-emptively raised a concern with some of my colleagues but people don't know what to make of a bunch of isolated forum posts/this list's thread.




Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 ***@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Rob Mensching [mailto:***@firegiant.com]
Sent: August-26-14 12:45 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Okay. That points to the fix having issues and not being isolated to Burn. Which, fortunately or unfortunately, means Microsoft probably needs to fix the fix.

_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:***@gmail.com]
Sent: Tuesday, August 26, 2014 9:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Custom Autorun/Setup.exe (elevating) that's been working fine for years, OR on the CMD line line msiexec /i path to msi (where it will prompt to elevate as well).
Post by Rob Mensching
How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-----Original Message-----
Sent: Tuesday, August 26, 2014 3:35 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Err!
or: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
Post by Rob Mensching
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig. However
removing the kb update has fixed it for at least one customer. I'm
hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918
6 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREP
A
IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp
7 596414p7596418.html Sent from the wix-users mailing list archive
at Nabble.com.
--------------------------------------------------------------------
-
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
-
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
Matt O'Connell
2014-08-27 13:01:19 UTC
Permalink
For those without a support contract, where's the most visible place to
post? msdn forums (clickonce and setup & deployment projects, I've never
found an MSI one...) or microsoft.public.platformsdk.msi newsgroup? The
installer team blog would've been a good place but its not updated anymore..
Neil Sleightholm
2014-08-28 20:05:47 UTC
Permalink
I think it is somehow related to the user context it is running as, in our case we using PowerShell remoting to install the MSI (using msiexec). The bit I have never seen before are the SECREPAIR messages, these only get triggered for us when we do this remote deployment. Although it works with kb2918614 installed I have also seen SECREPAIR messages if I psexec to a server and then install an MSI using msiexec.

Neil

-----Original Message-----
From: Rob Mensching [mailto:***@firegiant.com]
Sent: 26 August 2014 21:34
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

FWIW, we haven't seen this with any FireGiant customers yet. That's a large part of why I'm at a loss.

However, we have been hearing stories of other issues in the last couple batches of updates from Microsoft. Quality control may have slipped up there a bit recently.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: John Cooper [mailto:***@jackhenry.com]
Sent: Tuesday, August 26, 2014 1:10 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

We have a support contract, and I have forwarded this thread to my manager as it is of some concern, although we haven't seen this yet. If it hits us, we'll definitely be looking into it. Meanwhile, I'll politic for further investigation.

--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: ***@statcan.gc.ca [mailto:***@statcan.gc.ca]
Sent: Tuesday, August 26, 2014 2:52 PM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Has anyone with a support contract or the like with Microsoft asked about this? I've pre-emptively raised a concern with some of my colleagues but people don't know what to make of a bunch of isolated forum posts/this list's thread.




Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 ***@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Rob Mensching [mailto:***@firegiant.com]
Sent: August-26-14 12:45 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Okay. That points to the fix having issues and not being isolated to Burn. Which, fortunately or unfortunately, means Microsoft probably needs to fix the fix.

_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:***@gmail.com]
Sent: Tuesday, August 26, 2014 9:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Custom Autorun/Setup.exe (elevating) that's been working fine for years, OR on the CMD line line msiexec /i path to msi (where it will prompt to elevate as well).
Post by Rob Mensching
How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-----Original Message-----
Sent: Tuesday, August 26, 2014 3:35 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Err!
or: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
Post by Rob Mensching
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig. However
removing the kb update has fixed it for at least one customer. I'm
hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918
6 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREP
A
IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp
7 596414p7596418.html Sent from the wix-users mailing list archive
at Nabble.com.
--------------------------------------------------------------------
-
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
-
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.


------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
K***@statcan.gc.ca
2014-09-05 20:15:07 UTC
Permalink
I've gotten hold of a Windows 7 x64 VM and tried installing, uninstalling, repairing a few dinky products we have built installers for over the last while. Even added a new one with a large (100 megabytes uncompressed) payload. Tried with and without UAC for all. No troubles at all with the trouble KB installed. User was a domain account, for what that is worth.

I'm still waiting to hear on our support-contract folks and am thinking about how to do more tests.

Does anyone have a MSI that provokes a problem that they wish me to try and can send to me somehow? I'd be willing to investigate it.



Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
***@statcan.gc.ca
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Douglas, Keith - CoSD/DSCo
Sent: August-26-14 3:52 PM
To: 'General discussion about the WiX toolset.'
Subject: RE: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Has anyone with a support contract or the like with Microsoft asked about this? I've pre-emptively raised a concern with some of my colleagues but people don't know what to make of a bunch of isolated forum posts/this list's thread.




Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 ***@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Rob Mensching [mailto:***@firegiant.com]
Sent: August-26-14 12:45 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Okay. That points to the fix having issues and not being isolated to Burn. Which, fortunately or unfortunately, means Microsoft probably needs to fix the fix.

_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/

-----Original Message-----
From: Matt O'Connell [mailto:***@gmail.com]
Sent: Tuesday, August 26, 2014 9:02 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Custom Autorun/Setup.exe (elevating) that's been working fine for years, OR on the CMD line line msiexec /i path to msi (where it will prompt to elevate as well).
Post by Rob Mensching
How are you installing the MSIs? Just double-click the .MSI directly, as part of a Bundle, some other mechanism?
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-----Original Message-----
Sent: Tuesday, August 26, 2014 3:35 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Err!
or: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
Post by Rob Mensching
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig. However
removing the kb update has fixed it for at least one customer. I'm
hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918
6 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREP
A
IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp
7 596414p7596418.html Sent from the wix-users mailing list archive
at Nabble.com.
--------------------------------------------------------------------
-
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
-
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Nicolás Alvarez
2014-09-06 17:27:09 UTC
Permalink
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing, uninstalling, repairing a few dinky products we have built installers for over the last while. Even added a new one with a large (100 megabytes uncompressed) payload. Tried with and without UAC for all. No troubles at all with the trouble KB installed. User was a domain account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
K***@statcan.gc.ca
2014-09-08 12:41:07 UTC
Permalink
Ah! There seems to be some confusion on this point. I will see.


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
***@statcan.gc.ca
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Nicolás Alvarez [mailto:***@gmail.com]
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing, uninstalling, repairing a few dinky products we have built installers for over the last while. Even added a new one with a large (100 megabytes uncompressed) payload. Tried with and without UAC for all. No troubles at all with the trouble KB installed. User was a domain account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?

--
Nicolás

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo
K***@statcan.gc.ca
2014-09-08 15:40:26 UTC
Permalink
I've now tried a "small update". I've never fully understood why you’d use these, but my co-workers wanted to use MSPs for some of our updating, so I built a front end for making those and hence small updates. That all to say that I may be doing something unusual or "wrong" with them. However, that disclaimer aside, I cannot reproduce any trouble with that either.


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
***@statcan.gc.ca
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


-----Original Message-----
From: ***@statcan.gc.ca [mailto:***@statcan.gc.ca]
Sent: September-08-14 8:41 AM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Ah! There seems to be some confusion on this point. I will see.


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 ***@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Nicolás Alvarez [mailto:***@gmail.com]
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing, uninstalling, repairing a few dinky products we have built installers for over the last while. Even added a new one with a large (100 megabytes uncompressed) payload. Tried with and without UAC for all. No troubles at all with the trouble KB installed. User was a domain account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/li
John Cooper
2014-09-08 16:44:03 UTC
Permalink
I haven't been able to reproduce this using signed or unsigned MSIs deploying in an "Open" or "Closed" Environment.

I would be very happy to take a look at some verbose logs of the failures.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: ***@statcan.gc.ca [mailto:***@statcan.gc.ca]
Sent: Monday, September 8, 2014 10:40 AM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I've now tried a "small update". I've never fully understood why you’d use these, but my co-workers wanted to use MSPs for some of our updating, so I built a front end for making those and hence small updates. That all to say that I may be doing something unusual or "wrong" with them. However, that disclaimer aside, I cannot reproduce any trouble with that either.


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 ***@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: ***@statcan.gc.ca [mailto:***@statcan.gc.ca]
Sent: September-08-14 8:41 AM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Ah! There seems to be some confusion on this point. I will see.


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 ***@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Nicolás Alvarez [mailto:***@gmail.com]
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing, uninstalling, repairing a few dinky products we have built installers for over the last while. Even added a new one with a large (100 megabytes uncompressed) payload. Tried with and without UAC for all. No troubles at all with the trouble KB installed. User was a domain account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all c
Sascha Sertel
2014-09-08 18:29:21 UTC
Permalink
The issue is very easily reproducible for me when doing an upgrade from one
bundle to another one. I emailed Keith links to two installers that have
100% repro for me when upgrading from the one to the other while having
KB2918614 installed. Repros on any machine.

I'm happy to share some logs but given that KB2918614 directly determines
whether the upgrade fails or works I don't know if there is anything that
can be done to fix this from our end, it seems to me like Microsoft needs
to reissue the hotfix or have another hotfix that fixes the broken one.

// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned MSIs
deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the failures.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
I've now tried a "small update". I've never fully understood why you’d use
these, but my co-workers wanted to use MSPs for some of our updating, so I
built a front end for making those and hence small updates. That all to say
that I may be doing something unusual or "wrong" with them. However, that
disclaimer aside, I cannot reproduce any trouble with that either.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built installers for
over the last while. Even added a new one with a large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No troubles at
all with the trouble KB installed. User was a domain account, for what that
is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
John Cooper
2014-09-08 18:40:39 UTC
Permalink
I am sure that Microsoft will ultimately have to make a fix, but I have a lot of installers out in the wild, and I feel very exposed when none of my testers can replicate. I'm much more interested in understanding the mechanism of failure--especially since I can't currently replicate.

Also, it is very hard to justify to management invoking our support agreement when the issue does not reproduce with any of our product installers. Much easier if I can replicate.

I'm basically trying to figure out what is different in our installers and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

The issue is very easily reproducible for me when doing an upgrade from one bundle to another one. I emailed Keith links to two installers that have 100% repro for me when upgrading from the one to the other while having
KB2918614 installed. Repros on any machine.

I'm happy to share some logs but given that KB2918614 directly determines whether the upgrade fails or works I don't know if there is anything that can be done to fix this from our end, it seems to me like Microsoft needs to reissue the hotfix or have another hotfix that fixes the broken one.

// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned MSIs
deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the failures.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why you’d
use these, but my co-workers wanted to use MSPs for some of our
updating, so I built a front end for making those and hence small
updates. That all to say that I may be doing something unusual or
"wrong" with them. However, that disclaimer aside, I cannot reproduce any trouble with that either.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built installers
for over the last while. Even added a new one with a large (100
megabytes
uncompressed) payload. Tried with and without UAC for all. No troubles
at all with the trouble KB installed. User was a domain account, for
what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the
K***@statcan.gc.ca
2014-09-08 18:48:18 UTC
Permalink
Let me echo John here, I am trying to help us and also help the community. We are worse off, too, than some, because the machines I deal with are mostly-disconnected remotes which receive the vast majority of their tech support via RDP if at all. It seems that most of the hypotheses around are wrong, unless we're just unlucky.

Sascha: I have yet to try your stuff out. I know already now that you are dealing with MSIs in a bundle (correct?), which we don't do - we use bundles to use Windows Update files (MSUs) only, at present. All the rest of our stuff is just MSI. (Or rarely - testing only, I think, MSP.) So there's a difference right off.

I wonder (list owners willing) if it is time to play "what do we know?"


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
***@statcan.gc.ca
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


-----Original Message-----
From: John Cooper [mailto:***@jackhenry.com]
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I am sure that Microsoft will ultimately have to make a fix, but I have a lot of installers out in the wild, and I feel very exposed when none of my testers can replicate. I'm much more interested in understanding the mechanism of failure--especially since I can't currently replicate.

Also, it is very hard to justify to management invoking our support agreement when the issue does not reproduce with any of our product installers. Much easier if I can replicate.

I'm basically trying to figure out what is different in our installers and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

The issue is very easily reproducible for me when doing an upgrade from one bundle to another one. I emailed Keith links to two installers that have 100% repro for me when upgrading from the one to the other while having
KB2918614 installed. Repros on any machine.

I'm happy to share some logs but given that KB2918614 directly determines whether the upgrade fails or works I don't know if there is anything that can be done to fix this from our end, it seems to me like Microsoft needs to reissue the hotfix or have another hotfix that fixes the broken one.

// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned MSIs
deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the failures.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why you’d
use these, but my co-workers wanted to use MSPs for some of our
updating, so I built a front end for making those and hence small
updates. That all to say that I may be doing something unusual or
"wrong" with them. However, that disclaimer aside, I cannot reproduce any trouble with that either.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built installers
for over the last while. Even added a new one with a large (100
megabytes
uncompressed) payload. Tried with and without UAC for all. No troubles
at all with the trouble KB installed. User was a domain account, for
what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wi
Sascha Sertel
2014-09-08 19:01:42 UTC
Permalink
Yes, my installer uses a bundle because I have .NET Framework 4.5.1 and
Visual C++ 12 runtime components as a prerequisite before running my actual
product MSI.

I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe it's
actually something about upgrading a bundle that causes the failure to
happen.

In terms of what do we know, I don't think we know anything, we have yet to
find anything common between the failing installers. It seems to fail for
both per-user and per-machine installs, domain as well as workgroup user
accounts, elevated and non-elevated privileges, none of that seems to
matter.

// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the community.
We are worse off, too, than some, because the machines I deal with are
mostly-disconnected remotes which receive the vast majority of their tech
support via RDP if at all. It seems that most of the hypotheses around are
wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that you are
dealing with MSIs in a bundle (correct?), which we don't do - we use
bundles to use Windows Update files (MSUs) only, at present. All the rest
of our stuff is just MSI. (Or rarely - testing only, I think, MSP.) So
there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
I am sure that Microsoft will ultimately have to make a fix, but I have a
lot of installers out in the wild, and I feel very exposed when none of my
testers can replicate. I'm much more interested in understanding the
mechanism of failure--especially since I can't currently replicate.
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our installers and
deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
The issue is very easily reproducible for me when doing an upgrade from
one bundle to another one. I emailed Keith links to two installers that
have 100% repro for me when upgrading from the one to the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly determines
whether the upgrade fails or works I don't know if there is anything that
can be done to fix this from our end, it seems to me like Microsoft needs
to reissue the hotfix or have another hotfix that fixes the broken one.
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned MSIs
deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why you’d
use these, but my co-workers wanted to use MSPs for some of our
updating, so I built a front end for making those and hence small
updates. That all to say that I may be doing something unusual or
"wrong" with them. However, that disclaimer aside, I cannot reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built installers
for over the last while. Even added a new one with a large (100
megabytes
uncompressed) payload. Tried with and without UAC for all. No troubles
at all with the trouble KB installed. User was a domain account, for
what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
John Cooper
2014-09-08 19:17:37 UTC
Permalink
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll all are completely unversioned (no version numbers at all). When an upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com


-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Yes, my installer uses a bundle because I have .NET Framework 4.5.1 and Visual C++ 12 runtime components as a prerequisite before running my actual product MSI.

I haven't actually tried if the upgrade failure also repros using the product MSI only instead of the bundle, I'll try that out today. Maybe it's actually something about upgrading a bundle that causes the failure to happen.

In terms of what do we know, I don't think we know anything, we have yet to find anything common between the failing installers. It seems to fail for both per-user and per-machine installs, domain as well as workgroup user accounts, elevated and non-elevated privileges, none of that seems to matter.

// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the community.
We are worse off, too, than some, because the machines I deal with are
mostly-disconnected remotes which receive the vast majority of their
tech support via RDP if at all. It seems that most of the hypotheses
around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that you
are dealing with MSIs in a bundle (correct?), which we don't do - we
use bundles to use Windows Update files (MSUs) only, at present. All
the rest of our stuff is just MSI. (Or rarely - testing only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed when
none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't currently replicate.
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our installers
and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one to
the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there is
anything that can be done to fix this from our end, it seems to me
like Microsoft needs to reissue the hotfix or have another hotfix that fixes the broken one.
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned MSIs
deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something unusual
or "wrong" with them. However, that disclaimer aside, I cannot
reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately ad
K***@statcan.gc.ca
2014-09-08 19:28:27 UTC
Permalink
For what it is worth, I tried one of my investigation packages with a "fake exe" (for the sake of ease of recognizing as a fake) which, needless to say, has no version at all. It seems to upgrade fine with no trouble.


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
***@statcan.gc.ca
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


-----Original Message-----
From: John Cooper [mailto:***@jackhenry.com]
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll all are completely unversioned (no version numbers at all). When an upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com


-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Yes, my installer uses a bundle because I have .NET Framework 4.5.1 and Visual C++ 12 runtime components as a prerequisite before running my actual product MSI.

I haven't actually tried if the upgrade failure also repros using the product MSI only instead of the bundle, I'll try that out today. Maybe it's actually something about upgrading a bundle that causes the failure to happen.

In terms of what do we know, I don't think we know anything, we have yet to find anything common between the failing installers. It seems to fail for both per-user and per-machine installs, domain as well as workgroup user accounts, elevated and non-elevated privileges, none of that seems to matter.

// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the community.
We are worse off, too, than some, because the machines I deal with are
mostly-disconnected remotes which receive the vast majority of their
tech support via RDP if at all. It seems that most of the hypotheses
around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that you
are dealing with MSIs in a bundle (correct?), which we don't do - we
use bundles to use Windows Update files (MSUs) only, at present. All
the rest of our stuff is just MSI. (Or rarely - testing only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed when
none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't currently replicate.
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our installers
and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one to
the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there is
anything that can be done to fix this from our end, it seems to me
like Microsoft needs to reissue the hotfix or have another hotfix that fixes the broken one.
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned MSIs
deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something unusual
or "wrong" with them. However, that disclaimer aside, I cannot
reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-
John Cooper
2014-09-08 19:53:46 UTC
Permalink
If a file is unversioned, the normal file versioning rules and process don’t apply to it.

In the case of these three assemblies, they end up being entries in the MsiFileHash table. However, file timestamps control whether the MsiFileHash table is even entered.

Repairs are also going to be strange. Likewise patching.

That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: ***@statcan.gc.ca [mailto:***@statcan.gc.ca]
Sent: Monday, September 8, 2014 2:28 PM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

For what it is worth, I tried one of my investigation packages with a "fake exe" (for the sake of ease of recognizing as a fake) which, needless to say, has no version at all. It seems to upgrade fine with no trouble.


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 ***@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: John Cooper [mailto:***@jackhenry.com]
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll all are completely unversioned (no version numbers at all). When an upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com


-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Yes, my installer uses a bundle because I have .NET Framework 4.5.1 and Visual C++ 12 runtime components as a prerequisite before running my actual product MSI.

I haven't actually tried if the upgrade failure also repros using the product MSI only instead of the bundle, I'll try that out today. Maybe it's actually something about upgrading a bundle that causes the failure to happen.

In terms of what do we know, I don't think we know anything, we have yet to find anything common between the failing installers. It seems to fail for both per-user and per-machine installs, domain as well as workgroup user accounts, elevated and non-elevated privileges, none of that seems to matter.

// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the community.
We are worse off, too, than some, because the machines I deal with are
mostly-disconnected remotes which receive the vast majority of their
tech support via RDP if at all. It seems that most of the hypotheses
around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that you
are dealing with MSIs in a bundle (correct?), which we don't do - we
use bundles to use Windows Update files (MSUs) only, at present. All
the rest of our stuff is just MSI. (Or rarely - testing only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed when
none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't currently replicate.
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our installers
and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one to
the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there is
anything that can be done to fix this from our end, it seems to me
like Microsoft needs to reissue the hotfix or have another hotfix that fixes the broken one.
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned MSIs
deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something unusual
or "wrong" with them. However, that disclaimer aside, I cannot
reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the send
John Cooper
2014-09-08 22:07:02 UTC
Permalink
It doesn't replicate for me in the NOT installed case for the 1709 version of the product. I'll get the earlier product tonight and test the upgrade case tomorrow.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Monday, September 8, 2014 2:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

If a file is unversioned, the normal file versioning rules and process don’t apply to it.

In the case of these three assemblies, they end up being entries in the MsiFileHash table. However, file timestamps control whether the MsiFileHash table is even entered.

Repairs are also going to be strange. Likewise patching.

That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: ***@statcan.gc.ca [mailto:***@statcan.gc.ca]
Sent: Monday, September 8, 2014 2:28 PM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

For what it is worth, I tried one of my investigation packages with a "fake exe" (for the sake of ease of recognizing as a fake) which, needless to say, has no version at all. It seems to upgrade fine with no trouble.


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 ***@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: John Cooper [mailto:***@jackhenry.com]
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll all are completely unversioned (no version numbers at all). When an upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com


-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Yes, my installer uses a bundle because I have .NET Framework 4.5.1 and Visual C++ 12 runtime components as a prerequisite before running my actual product MSI.

I haven't actually tried if the upgrade failure also repros using the product MSI only instead of the bundle, I'll try that out today. Maybe it's actually something about upgrading a bundle that causes the failure to happen.

In terms of what do we know, I don't think we know anything, we have yet to find anything common between the failing installers. It seems to fail for both per-user and per-machine installs, domain as well as workgroup user accounts, elevated and non-elevated privileges, none of that seems to matter.

// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the community.
We are worse off, too, than some, because the machines I deal with are
mostly-disconnected remotes which receive the vast majority of their
tech support via RDP if at all. It seems that most of the hypotheses
around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that you
are dealing with MSIs in a bundle (correct?), which we don't do - we
use bundles to use Windows Update files (MSUs) only, at present. All
the rest of our stuff is just MSI. (Or rarely - testing only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed when
none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't currently replicate.
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our installers
and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one to
the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there is
anything that can be done to fix this from our end, it seems to me
like Microsoft needs to reissue the hotfix or have another hotfix that fixes the broken one.
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned MSIs
deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something unusual
or "wrong" with them. However, that disclaimer aside, I cannot
reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and de
Sascha Sertel
2014-09-08 22:31:10 UTC
Permalink
Right, fresh install works fine for me, it's only the upgrade case that is
borked.

// Sascha
Post by John Cooper
It doesn't replicate for me in the NOT installed case for the 1709 version
of the product. I'll get the earlier product tonight and test the upgrade
case tomorrow.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |
-----Original Message-----
From: John Cooper
Sent: Monday, September 8, 2014 2:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
If a file is unversioned, the normal file versioning rules and process don’t apply to it.
In the case of these three assemblies, they end up being entries in the
MsiFileHash table. However, file timestamps control whether the
MsiFileHash table is even entered.
Repairs are also going to be strange. Likewise patching.
That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
-----Original Message-----
Sent: Monday, September 8, 2014 2:28 PM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
For what it is worth, I tried one of my investigation packages with a
"fake exe" (for the sake of ease of recognizing as a fake) which, needless
to say, has no version at all. It seems to upgrade fine with no trouble.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll all
are completely unversioned (no version numbers at all). When an upgrade
works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
-----Original Message-----
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
Yes, my installer uses a bundle because I have .NET Framework 4.5.1 and
Visual C++ 12 runtime components as a prerequisite before running my actual
product MSI.
I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe it's
actually something about upgrading a bundle that causes the failure to
happen.
In terms of what do we know, I don't think we know anything, we have yet
to find anything common between the failing installers. It seems to fail
for both per-user and per-machine installs, domain as well as workgroup
user accounts, elevated and non-elevated privileges, none of that seems to
matter.
// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the
community.
Post by K***@statcan.gc.ca
We are worse off, too, than some, because the machines I deal with are
mostly-disconnected remotes which receive the vast majority of their
tech support via RDP if at all. It seems that most of the hypotheses
around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that you
are dealing with MSIs in a bundle (correct?), which we don't do - we
use bundles to use Windows Update files (MSUs) only, at present. All
the rest of our stuff is just MSI. (Or rarely - testing only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed when
none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't
currently replicate.
Post by K***@statcan.gc.ca
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our installers
and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one to
the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there is
anything that can be done to fix this from our end, it seems to me
like Microsoft needs to reissue the hotfix or have another hotfix that
fixes the broken one.
Post by K***@statcan.gc.ca
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned MSIs
deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something unusual
or "wrong" with them. However, that disclaimer aside, I cannot
reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are
intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential and/or
privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message in
error, please immediately advise the sender by reply email and delete all
copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are
intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential and/or
privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message in
error, please immediately advise the sender by reply email and delete all
copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
John Cooper
2014-09-09 14:41:33 UTC
Permalink
Ok, did some install testing of the upgrade from the earlier version to 1709 this morning.

Windows Server 2008 R2 No repro
Windows Server 2012 No repro

Windows 8 Reproduces

I'm digging through the logs . . .
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 5:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Right, fresh install works fine for me, it's only the upgrade case that is borked.

// Sascha
Post by John Cooper
It doesn't replicate for me in the NOT installed case for the 1709
version of the product. I'll get the earlier product tonight and test
the upgrade case tomorrow.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
From: John Cooper
Sent: Monday, September 8, 2014 2:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
If a file is unversioned, the normal file versioning rules and process don’t apply to it.
In the case of these three assemblies, they end up being entries in
the MsiFileHash table. However, file timestamps control whether the
MsiFileHash table is even entered.
Repairs are also going to be strange. Likewise patching.
That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:28 PM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
For what it is worth, I tried one of my investigation packages with a
"fake exe" (for the sake of ease of recognizing as a fake) which,
needless to say, has no version at all. It seems to upgrade fine with no trouble.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll
all are completely unversioned (no version numbers at all). When an
upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Yes, my installer uses a bundle because I have .NET Framework 4.5.1
and Visual C++ 12 runtime components as a prerequisite before running
my actual product MSI.
I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe
it's actually something about upgrading a bundle that causes the
failure to happen.
In terms of what do we know, I don't think we know anything, we have
yet to find anything common between the failing installers. It seems
to fail for both per-user and per-machine installs, domain as well as
workgroup user accounts, elevated and non-elevated privileges, none of
that seems to matter.
// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the
community.
Post by K***@statcan.gc.ca
We are worse off, too, than some, because the machines I deal with
are mostly-disconnected remotes which receive the vast majority of
their tech support via RDP if at all. It seems that most of the
hypotheses around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that
you are dealing with MSIs in a bundle (correct?), which we don't do
- we use bundles to use Windows Update files (MSUs) only, at
present. All the rest of our stuff is just MSI. (Or rarely - testing
only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed
when none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't
currently replicate.
Post by K***@statcan.gc.ca
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our
installers and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one
to the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there
is anything that can be done to fix this from our end, it seems to
me like Microsoft needs to reissue the hotfix or have another hotfix
that
fixes the broken one.
Post by K***@statcan.gc.ca
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned
MSIs deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something
unusual or "wrong" with them. However, that disclaimer aside, I
cannot reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
------------------------------------------------------------------
--
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted
with it are intended exclusively for the individual or entity to
which it is addressed. The message, together with any attachment,
may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying,
disclosure or distribution is strictly prohibited. If you have
received this message in error, please immediately advise the
sender by reply email and delete all copies.
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply
John Cooper
2014-09-09 15:52:54 UTC
Permalink
Factor that may or may not mean anything:

Upgrade Scheduling appears to be InstallValidate
REINSTALLMODE: vomus
OS: Windows 8 with latest updates including KB2918614
Profile: Roaming (only able to reproduce on a laptop)
MajorUpgrade authoring is not being used (custom Upgrade Table entries)

Failure looks like this in the MSI log:

MSI (s) (A8:E8) [09:20:04:609]: Determining source type
MSI (s) (A8:E8) [09:20:04:609]: Source type from package 'Lyve Product.msi': 10
MSI (s) (A8:E8) [09:20:04:609]: SECREPAIR: Hash Database: C:\WINDOWS\Installer\SourceHash{C5E60292-2E11-4FAE-883F-E548ECF032F7}
MSI (s) (A8:E8) [09:20:04:625]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (A8:E8) [09:20:04:844]: SECREPAIR: filename: Lyve Product.msi Stored Hash Value:RUgGMOmbpYsraTZ8VjLP1M9KGepCCMUiBVmXkOMCD6w= Current Hash:TfXkukwiWlgqxX0jqHwgUEwjjKlSG2KJpuZX/cEM3Uw=
MSI (s) (A8:E8) [09:20:04:844]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (A8:E8) [09:20:04:844]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (A8:E8) [09:20:04:844]: MSI_LUA: Elevation prompt disabled for silent installs
MSI (s) (A8:E8) [09:20:04:844]: Note: 1: 3
MSI (s) (A8:E8) [09:20:04:844]: SECUREREPAIR: SecureRepair Failed. Error code: 364DF2640
MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (A8:E8) [09:20:04:859]: Machine policy value 'DisableRollback' is 0
MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
Action ended 9:20:04: RegisterProduct. Return value 2.

It looks like this in the bootstrapper log:

[1D64:1100][2014-09-09T09:20:01]i300: Apply begin
[1D64:1100][2014-09-09T09:20:02]i000: Caching bundle from: 'C:\Users\jocooper\AppData\Local\Temp\{a8554c44-e09c-479f-a8e5-685f5bf90487}\.be\Lyve Setup.exe' to: 'C:\Users\jocooper\AppData\Local\Package Cache\{a8554c44-e09c-479f-a8e5-685f5bf90487}\Lyve Setup.exe'
[1D64:1100][2014-09-09T09:20:02]i320: Registering bundle dependency provider: {a8554c44-e09c-479f-a8e5-685f5bf90487}, version: 1.0.1.1079
[1D64:1FFC][2014-09-09T09:20:02]i305: Verified acquired payload: Lyve at path: C:\Users\jocooper\AppData\Local\Package Cache\.unverified\Lyve, moving to: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi.
[1D64:1100][2014-09-09T09:20:02]i323: Registering package dependency provider: {C5E60292-2E11-4FAE-883F-E548ECF032F7}, version: 1.0.1.1079, package: Lyve
[1D64:1100][2014-09-09T09:20:02]i301: Applying execute package: Lyve, action: MinorUpgrade, path: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to perform minor upgrade of MSI package.
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to configure per-user MSI package.
[1D64:1100][2014-09-09T09:20:04]i319: Applied execute package: Lyve, result: 0x80070642, restart: None
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to execute MSI package.

An earlier upgrade with the same installers succeed when KB2918614 was missing. I then remove the product, applied the update, and rebooted. Initial install of the older product succeeded. Upgrade failed.

It appears that the digital signature requirements for repair/upgrade using msiexec 5.0 have been more strict. The stored hash and the computed hash are not matching after the update (they did before) and that is failing the upgrade.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com


-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 9:42 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Ok, did some install testing of the upgrade from the earlier version to 1709 this morning.

Windows Server 2008 R2 No repro
Windows Server 2012 No repro

Windows 8 Reproduces

I'm digging through the logs . . .
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 5:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Right, fresh install works fine for me, it's only the upgrade case that is borked.

// Sascha
Post by John Cooper
It doesn't replicate for me in the NOT installed case for the 1709
version of the product. I'll get the earlier product tonight and test
the upgrade case tomorrow.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
From: John Cooper
Sent: Monday, September 8, 2014 2:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
If a file is unversioned, the normal file versioning rules and process don’t apply to it.
In the case of these three assemblies, they end up being entries in
the MsiFileHash table. However, file timestamps control whether the
MsiFileHash table is even entered.
Repairs are also going to be strange. Likewise patching.
That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:28 PM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
For what it is worth, I tried one of my investigation packages with a
"fake exe" (for the sake of ease of recognizing as a fake) which,
needless to say, has no version at all. It seems to upgrade fine with no trouble.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll
all are completely unversioned (no version numbers at all). When an
upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Yes, my installer uses a bundle because I have .NET Framework 4.5.1
and Visual C++ 12 runtime components as a prerequisite before running
my actual product MSI.
I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe
it's actually something about upgrading a bundle that causes the
failure to happen.
In terms of what do we know, I don't think we know anything, we have
yet to find anything common between the failing installers. It seems
to fail for both per-user and per-machine installs, domain as well as
workgroup user accounts, elevated and non-elevated privileges, none of
that seems to matter.
// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the
community.
Post by K***@statcan.gc.ca
We are worse off, too, than some, because the machines I deal with
are mostly-disconnected remotes which receive the vast majority of
their tech support via RDP if at all. It seems that most of the
hypotheses around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that
you are dealing with MSIs in a bundle (correct?), which we don't do
- we use bundles to use Windows Update files (MSUs) only, at
present. All the rest of our stuff is just MSI. (Or rarely - testing
only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed
when none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't
currently replicate.
Post by K***@statcan.gc.ca
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our
installers and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one
to the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there
is anything that can be done to fix this from our end, it seems to
me like Microsoft needs to reissue the hotfix or have another hotfix
that
fixes the broken one.
Post by K***@statcan.gc.ca
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned
MSIs deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something
unusual or "wrong" with them. However, that disclaimer aside, I
cannot reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
------------------------------------------------------------------
--
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted
with it are intended exclusively for the individual or entity to
which it is addressed. The message, together with any attachment,
may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying,
disclosure or distribution is strictly prohibited. If you have
received this message in error, please immediately advise the
sender by reply email and delete all copies.
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and
Sascha Sertel
2014-09-09 16:25:24 UTC
Permalink
By the way this also only seems to affect MinorUpgrade.

I tried out changing the product code to execute a MajorUpgrade, and indeed
the upgrade worked fine. So this further narrows it down and explains why
many others aren't seeing this, I guess MinorUpgrades aren't as common as I
thought?

// Sascha
Post by John Cooper
Upgrade Scheduling appears to be InstallValidate
REINSTALLMODE: vomus
OS: Windows 8 with latest updates including KB2918614
Profile: Roaming (only able to reproduce on a laptop)
MajorUpgrade authoring is not being used (custom Upgrade Table entries)
MSI (s) (A8:E8) [09:20:04:609]: Determining source type
MSI (s) (A8:E8) [09:20:04:609]: Source type from package 'Lyve
Product.msi': 10
C:\WINDOWS\Installer\SourceHash{C5E60292-2E11-4FAE-883F-E548ECF032F7}
MSI (s) (A8:E8) [09:20:04:625]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (A8:E8) [09:20:04:844]: SECREPAIR: filename: Lyve Product.msi
Stored Hash Value:RUgGMOmbpYsraTZ8VjLP1M9KGepCCMUiBVmXkOMCD6w= Current
Hash:TfXkukwiWlgqxX0jqHwgUEwjjKlSG2KJpuZX/cEM3Uw=
MSI (s) (A8:E8) [09:20:04:844]: Machine policy value
'AlwaysInstallElevated' is 0
MSI (s) (A8:E8) [09:20:04:844]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (A8:E8) [09:20:04:844]: MSI_LUA: Elevation prompt disabled for silent installs
MSI (s) (A8:E8) [09:20:04:844]: Note: 1: 3
MSI (s) (A8:E8) [09:20:04:844]: SECUREREPAIR: SecureRepair Failed. Error code: 364DF2640
MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (A8:E8) [09:20:04:859]: Machine policy value 'DisableRollback' is 0
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts
3: 2
Action ended 9:20:04: RegisterProduct. Return value 2.
[1D64:1100][2014-09-09T09:20:01]i300: Apply begin
'C:\Users\jocooper\AppData\Local\Temp\{a8554c44-e09c-479f-a8e5-685f5bf90487}\.be\Lyve
Setup.exe' to: 'C:\Users\jocooper\AppData\Local\Package
Cache\{a8554c44-e09c-479f-a8e5-685f5bf90487}\Lyve Setup.exe'
[1D64:1100][2014-09-09T09:20:02]i320: Registering bundle dependency
provider: {a8554c44-e09c-479f-a8e5-685f5bf90487}, version: 1.0.1.1079
[1D64:1FFC][2014-09-09T09:20:02]i305: Verified acquired payload: Lyve at
path: C:\Users\jocooper\AppData\Local\Package Cache\.unverified\Lyve,
moving to: C:\Users\jocooper\AppData\Local\Package
Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi.
[1D64:1100][2014-09-09T09:20:02]i323: Registering package dependency
provider: {C5E60292-2E11-4FAE-883F-E548ECF032F7}, version: 1.0.1.1079,
package: Lyve
[1D64:1100][2014-09-09T09:20:02]i301: Applying execute package: Lyve,
action: MinorUpgrade, path: C:\Users\jocooper\AppData\Local\Package
Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi,
arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to perform
minor upgrade of MSI package.
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to
configure per-user MSI package.
[1D64:1100][2014-09-09T09:20:04]i319: Applied execute package: Lyve,
result: 0x80070642, restart: None
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to execute MSI package.
An earlier upgrade with the same installers succeed when KB2918614 was
missing. I then remove the product, applied the update, and rebooted.
Initial install of the older product succeeded. Upgrade failed.
It appears that the digital signature requirements for repair/upgrade
using msiexec 5.0 have been more strict. The stored hash and the computed
hash are not matching after the update (they did before) and that is
failing the upgrade.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |
-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 9:42 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
Ok, did some install testing of the upgrade from the earlier version to 1709 this morning.
Windows Server 2008 R2 No repro
Windows Server 2012 No repro
Windows 8 Reproduces
I'm digging through the logs . . .
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
-----Original Message-----
Sent: Monday, September 8, 2014 5:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
Right, fresh install works fine for me, it's only the upgrade case that is borked.
// Sascha
Post by John Cooper
It doesn't replicate for me in the NOT installed case for the 1709
version of the product. I'll get the earlier product tonight and test
the upgrade case tomorrow.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
From: John Cooper
Sent: Monday, September 8, 2014 2:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
If a file is unversioned, the normal file versioning rules and process
don’t apply to it.
In the case of these three assemblies, they end up being entries in
the MsiFileHash table. However, file timestamps control whether the
MsiFileHash table is even entered.
Repairs are also going to be strange. Likewise patching.
That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 2:28 PM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
For what it is worth, I tried one of my investigation packages with a
"fake exe" (for the sake of ease of recognizing as a fake) which,
needless to say, has no version at all. It seems to upgrade fine with no
trouble.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll
all are completely unversioned (no version numbers at all). When an
upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Yes, my installer uses a bundle because I have .NET Framework 4.5.1
and Visual C++ 12 runtime components as a prerequisite before running
my actual product MSI.
I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe
it's actually something about upgrading a bundle that causes the
failure to happen.
In terms of what do we know, I don't think we know anything, we have
yet to find anything common between the failing installers. It seems
to fail for both per-user and per-machine installs, domain as well as
workgroup user accounts, elevated and non-elevated privileges, none of
that seems to matter.
// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the
community.
Post by K***@statcan.gc.ca
We are worse off, too, than some, because the machines I deal with
are mostly-disconnected remotes which receive the vast majority of
their tech support via RDP if at all. It seems that most of the
hypotheses around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that
you are dealing with MSIs in a bundle (correct?), which we don't do
- we use bundles to use Windows Update files (MSUs) only, at
present. All the rest of our stuff is just MSI. (Or rarely - testing
only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed
when none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't
currently replicate.
Post by K***@statcan.gc.ca
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our
installers and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one
to the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there
is anything that can be done to fix this from our end, it seems to
me like Microsoft needs to reissue the hotfix or have another hotfix
that
fixes the broken one.
Post by K***@statcan.gc.ca
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned
MSIs deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something
unusual or "wrong" with them. However, that disclaimer aside, I
cannot reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
------------------------------------------------------------------
--
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
Post by John Cooper
Post by K***@statcan.gc.ca
Post by John Cooper
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
Post by John Cooper
Post by K***@statcan.gc.ca
Post by John Cooper
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted
with it are intended exclusively for the individual or entity to
which it is addressed. The message, together with any attachment,
may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying,
disclosure or distribution is strictly prohibited. If you have
received this message in error, please immediately advise the
sender by reply email and delete all copies.
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
Post by John Cooper
Post by K***@statcan.gc.ca
Post by John Cooper
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed.
Post by John Cooper
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed.
Post by John Cooper
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
John Cooper
2014-09-09 17:39:45 UTC
Permalink
I figure it was a minor upgrade with the ProductCodes.

There was some expression of interest in a registry dump on my reproducing machine for HKCR\Msi.Package. So, here it is:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Msi.Package]
@="Windows Installer Package"
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"
"EditFlags"=hex:00,00,10,00
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,\
00,2d,00,33,00,34,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\DefaultIcon]
@="C:\\Windows\\System32\\msiexec.exe,0"

[HKEY_CLASSES_ROOT\Msi.Package\shell]
@="Open,Repair,Uninstall"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit]
@="&Edit with Orca"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit\command]
@="\"C:\\Program Files (x86)\\Orca\\Orca.exe\" \"%1\""
"command"=hex(7):36,00,59,00,55,00,27,00,53,00,72,00,2d,00,54,00,35,00,40,00,\
45,00,40,00,35,00,4c,00,28,00,28,00,2e,00,6d,00,4a,00,55,00,4f,00,72,00,63,\
00,61,00,3e,00,6e,00,52,00,37,00,39,00,66,00,5e,00,26,00,71,00,66,00,28,00,\
76,00,3f,00,65,00,71,00,46,00,28,00,29,00,77,00,26,00,47,00,20,00,22,00,25,\
00,31,00,22,00,00,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open]
@="&Install"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,36,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair]
@="Re&pair"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,37,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,66,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser]
@="@shell32.dll,-50944"
"SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}"
"Extended"=""

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser\command]
"DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}"

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall]
@="&Uninstall"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,38,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,78,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shellex]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers]
@="Compatibility"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers\Compatibility]
@="{1d27f844-3a1f-4410-85ac-14651078412d}"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers\ShimLayer Property Page]
@="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 10:53 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Factor that may or may not mean anything:

Upgrade Scheduling appears to be InstallValidate
REINSTALLMODE: vomus
OS: Windows 8 with latest updates including KB2918614
Profile: Roaming (only able to reproduce on a laptop) MajorUpgrade authoring is not being used (custom Upgrade Table entries)

Failure looks like this in the MSI log:

MSI (s) (A8:E8) [09:20:04:609]: Determining source type MSI (s) (A8:E8) [09:20:04:609]: Source type from package 'Lyve Product.msi': 10 MSI (s) (A8:E8) [09:20:04:609]: SECREPAIR: Hash Database: C:\WINDOWS\Installer\SourceHash{C5E60292-2E11-4FAE-883F-E548ECF032F7}
MSI (s) (A8:E8) [09:20:04:625]: SECREPAIR: CryptAcquireContext succeeded MSI (s) (A8:E8) [09:20:04:844]: SECREPAIR: filename: Lyve Product.msi Stored Hash Value:RUgGMOmbpYsraTZ8VjLP1M9KGepCCMUiBVmXkOMCD6w= Current Hash:TfXkukwiWlgqxX0jqHwgUEwjjKlSG2KJpuZX/cEM3Uw=
MSI (s) (A8:E8) [09:20:04:844]: Machine policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: User policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: MSI_LUA: Elevation prompt disabled for silent installs MSI (s) (A8:E8) [09:20:04:844]: Note: 1: 3 MSI (s) (A8:E8) [09:20:04:844]: SECUREREPAIR: SecureRepair Failed. Error code: 364DF2640 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 2265 2: 3: -2147287035 MSI (s) (A8:E8) [09:20:04:859]: Machine policy value 'DisableRollback' is 0 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 9:20:04: RegisterProduct. Return value 2.

It looks like this in the bootstrapper log:

[1D64:1100][2014-09-09T09:20:01]i300: Apply begin
[1D64:1100][2014-09-09T09:20:02]i000: Caching bundle from: 'C:\Users\jocooper\AppData\Local\Temp\{a8554c44-e09c-479f-a8e5-685f5bf90487}\.be\Lyve Setup.exe' to: 'C:\Users\jocooper\AppData\Local\Package Cache\{a8554c44-e09c-479f-a8e5-685f5bf90487}\Lyve Setup.exe'
[1D64:1100][2014-09-09T09:20:02]i320: Registering bundle dependency provider: {a8554c44-e09c-479f-a8e5-685f5bf90487}, version: 1.0.1.1079
[1D64:1FFC][2014-09-09T09:20:02]i305: Verified acquired payload: Lyve at path: C:\Users\jocooper\AppData\Local\Package Cache\.unverified\Lyve, moving to: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi.
[1D64:1100][2014-09-09T09:20:02]i323: Registering package dependency provider: {C5E60292-2E11-4FAE-883F-E548ECF032F7}, version: 1.0.1.1079, package: Lyve
[1D64:1100][2014-09-09T09:20:02]i301: Applying execute package: Lyve, action: MinorUpgrade, path: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to perform minor upgrade of MSI package.
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to configure per-user MSI package.
[1D64:1100][2014-09-09T09:20:04]i319: Applied execute package: Lyve, result: 0x80070642, restart: None
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to execute MSI package.

An earlier upgrade with the same installers succeed when KB2918614 was missing. I then remove the product, applied the update, and rebooted. Initial install of the older product succeeded. Upgrade failed.

It appears that the digital signature requirements for repair/upgrade using msiexec 5.0 have been more strict. The stored hash and the computed hash are not matching after the update (they did before) and that is failing the upgrade.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com


-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 9:42 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Ok, did some install testing of the upgrade from the earlier version to 1709 this morning.

Windows Server 2008 R2 No repro
Windows Server 2012 No repro

Windows 8 Reproduces

I'm digging through the logs . . .
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 5:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Right, fresh install works fine for me, it's only the upgrade case that is borked.

// Sascha
Post by John Cooper
It doesn't replicate for me in the NOT installed case for the 1709
version of the product. I'll get the earlier product tonight and test
the upgrade case tomorrow.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
From: John Cooper
Sent: Monday, September 8, 2014 2:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
If a file is unversioned, the normal file versioning rules and process don’t apply to it.
In the case of these three assemblies, they end up being entries in
the MsiFileHash table. However, file timestamps control whether the
MsiFileHash table is even entered.
Repairs are also going to be strange. Likewise patching.
That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:28 PM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
For what it is worth, I tried one of my investigation packages with a
"fake exe" (for the sake of ease of recognizing as a fake) which,
needless to say, has no version at all. It seems to upgrade fine with no trouble.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll
all are completely unversioned (no version numbers at all). When an
upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Yes, my installer uses a bundle because I have .NET Framework 4.5.1
and Visual C++ 12 runtime components as a prerequisite before running
my actual product MSI.
I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe
it's actually something about upgrading a bundle that causes the
failure to happen.
In terms of what do we know, I don't think we know anything, we have
yet to find anything common between the failing installers. It seems
to fail for both per-user and per-machine installs, domain as well as
workgroup user accounts, elevated and non-elevated privileges, none of
that seems to matter.
// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the
community.
Post by K***@statcan.gc.ca
We are worse off, too, than some, because the machines I deal with
are mostly-disconnected remotes which receive the vast majority of
their tech support via RDP if at all. It seems that most of the
hypotheses around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that
you are dealing with MSIs in a bundle (correct?), which we don't do
- we use bundles to use Windows Update files (MSUs) only, at
present. All the rest of our stuff is just MSI. (Or rarely - testing
only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed
when none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't
currently replicate.
Post by K***@statcan.gc.ca
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our
installers and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one
to the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there
is anything that can be done to fix this from our end, it seems to
me like Microsoft needs to reissue the hotfix or have another hotfix
that
fixes the broken one.
Post by K***@statcan.gc.ca
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned
MSIs deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something
unusual or "wrong" with them. However, that disclaimer aside, I
cannot reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
------------------------------------------------------------------
--
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted
with it are intended exclusively for the individual or entity to
which it is addressed. The message, together with any attachment,
may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying,
disclosure or distribution is strictly prohibited. If you have
received this message in error, please immediately advise the
sender by reply email and delete all copies.
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advis
John Cooper
2014-09-09 20:13:41 UTC
Permalink
Just got this from Microsoft as a proposed fix:

http://www.vindamedia.com/windows/help/windows-installer-msi-hash-mismatch
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 12:40 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I figure it was a minor upgrade with the ProductCodes.

There was some expression of interest in a registry dump on my reproducing machine for HKCR\Msi.Package. So, here it is:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Msi.Package]
@="Windows Installer Package"
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"
"EditFlags"=hex:00,00,10,00
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,\
00,2d,00,33,00,34,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\DefaultIcon]
@="C:\\Windows\\System32\\msiexec.exe,0"

[HKEY_CLASSES_ROOT\Msi.Package\shell]
@="Open,Repair,Uninstall"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit]
@="&Edit with Orca"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit\command]
@="\"C:\\Program Files (x86)\\Orca\\Orca.exe\" \"%1\""
"command"=hex(7):36,00,59,00,55,00,27,00,53,00,72,00,2d,00,54,00,35,00,40,00,\
45,00,40,00,35,00,4c,00,28,00,28,00,2e,00,6d,00,4a,00,55,00,4f,00,72,00,63,\
00,61,00,3e,00,6e,00,52,00,37,00,39,00,66,00,5e,00,26,00,71,00,66,00,28,00,\
76,00,3f,00,65,00,71,00,46,00,28,00,29,00,77,00,26,00,47,00,20,00,22,00,25,\
00,31,00,22,00,00,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open]
@="&Install"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,36,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair]
@="Re&pair"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,37,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,66,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser]
@="@shell32.dll,-50944"
"SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}"
"Extended"=""

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser\command]
"DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}"

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall]
@="&Uninstall"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,38,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,78,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shellex]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers]
@="Compatibility"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers\Compatibility]
@="{1d27f844-3a1f-4410-85ac-14651078412d}"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers\ShimLayer Property Page] @="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 10:53 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Factor that may or may not mean anything:

Upgrade Scheduling appears to be InstallValidate
REINSTALLMODE: vomus
OS: Windows 8 with latest updates including KB2918614
Profile: Roaming (only able to reproduce on a laptop) MajorUpgrade authoring is not being used (custom Upgrade Table entries)

Failure looks like this in the MSI log:

MSI (s) (A8:E8) [09:20:04:609]: Determining source type MSI (s) (A8:E8) [09:20:04:609]: Source type from package 'Lyve Product.msi': 10 MSI (s) (A8:E8) [09:20:04:609]: SECREPAIR: Hash Database: C:\WINDOWS\Installer\SourceHash{C5E60292-2E11-4FAE-883F-E548ECF032F7}
MSI (s) (A8:E8) [09:20:04:625]: SECREPAIR: CryptAcquireContext succeeded MSI (s) (A8:E8) [09:20:04:844]: SECREPAIR: filename: Lyve Product.msi Stored Hash Value:RUgGMOmbpYsraTZ8VjLP1M9KGepCCMUiBVmXkOMCD6w= Current Hash:TfXkukwiWlgqxX0jqHwgUEwjjKlSG2KJpuZX/cEM3Uw=
MSI (s) (A8:E8) [09:20:04:844]: Machine policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: User policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: MSI_LUA: Elevation prompt disabled for silent installs MSI (s) (A8:E8) [09:20:04:844]: Note: 1: 3 MSI (s) (A8:E8) [09:20:04:844]: SECUREREPAIR: SecureRepair Failed. Error code: 364DF2640 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 2265 2: 3: -2147287035 MSI (s) (A8:E8) [09:20:04:859]: Machine policy value 'DisableRollback' is 0 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 9:20:04: RegisterProduct. Return value 2.

It looks like this in the bootstrapper log:

[1D64:1100][2014-09-09T09:20:01]i300: Apply begin
[1D64:1100][2014-09-09T09:20:02]i000: Caching bundle from: 'C:\Users\jocooper\AppData\Local\Temp\{a8554c44-e09c-479f-a8e5-685f5bf90487}\.be\Lyve Setup.exe' to: 'C:\Users\jocooper\AppData\Local\Package Cache\{a8554c44-e09c-479f-a8e5-685f5bf90487}\Lyve Setup.exe'
[1D64:1100][2014-09-09T09:20:02]i320: Registering bundle dependency provider: {a8554c44-e09c-479f-a8e5-685f5bf90487}, version: 1.0.1.1079
[1D64:1FFC][2014-09-09T09:20:02]i305: Verified acquired payload: Lyve at path: C:\Users\jocooper\AppData\Local\Package Cache\.unverified\Lyve, moving to: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi.
[1D64:1100][2014-09-09T09:20:02]i323: Registering package dependency provider: {C5E60292-2E11-4FAE-883F-E548ECF032F7}, version: 1.0.1.1079, package: Lyve
[1D64:1100][2014-09-09T09:20:02]i301: Applying execute package: Lyve, action: MinorUpgrade, path: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to perform minor upgrade of MSI package.
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to configure per-user MSI package.
[1D64:1100][2014-09-09T09:20:04]i319: Applied execute package: Lyve, result: 0x80070642, restart: None
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to execute MSI package.

An earlier upgrade with the same installers succeed when KB2918614 was missing. I then remove the product, applied the update, and rebooted. Initial install of the older product succeeded. Upgrade failed.

It appears that the digital signature requirements for repair/upgrade using msiexec 5.0 have been more strict. The stored hash and the computed hash are not matching after the update (they did before) and that is failing the upgrade.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com


-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 9:42 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Ok, did some install testing of the upgrade from the earlier version to 1709 this morning.

Windows Server 2008 R2 No repro
Windows Server 2012 No repro

Windows 8 Reproduces

I'm digging through the logs . . .
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 5:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Right, fresh install works fine for me, it's only the upgrade case that is borked.

// Sascha
Post by John Cooper
It doesn't replicate for me in the NOT installed case for the 1709
version of the product. I'll get the earlier product tonight and test
the upgrade case tomorrow.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
From: John Cooper
Sent: Monday, September 8, 2014 2:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
If a file is unversioned, the normal file versioning rules and process don’t apply to it.
In the case of these three assemblies, they end up being entries in
the MsiFileHash table. However, file timestamps control whether the
MsiFileHash table is even entered.
Repairs are also going to be strange. Likewise patching.
That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:28 PM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
For what it is worth, I tried one of my investigation packages with a
"fake exe" (for the sake of ease of recognizing as a fake) which,
needless to say, has no version at all. It seems to upgrade fine with no trouble.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll
all are completely unversioned (no version numbers at all). When an
upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Yes, my installer uses a bundle because I have .NET Framework 4.5.1
and Visual C++ 12 runtime components as a prerequisite before running
my actual product MSI.
I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe
it's actually something about upgrading a bundle that causes the
failure to happen.
In terms of what do we know, I don't think we know anything, we have
yet to find anything common between the failing installers. It seems
to fail for both per-user and per-machine installs, domain as well as
workgroup user accounts, elevated and non-elevated privileges, none of
that seems to matter.
// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the
community.
Post by K***@statcan.gc.ca
We are worse off, too, than some, because the machines I deal with
are mostly-disconnected remotes which receive the vast majority of
their tech support via RDP if at all. It seems that most of the
hypotheses around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that
you are dealing with MSIs in a bundle (correct?), which we don't do
- we use bundles to use Windows Update files (MSUs) only, at
present. All the rest of our stuff is just MSI. (Or rarely - testing
only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed
when none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't
currently replicate.
Post by K***@statcan.gc.ca
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our
installers and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one
to the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there
is anything that can be done to fix this from our end, it seems to
me like Microsoft needs to reissue the hotfix or have another hotfix
that
fixes the broken one.
Post by K***@statcan.gc.ca
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned
MSIs deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something
unusual or "wrong" with them. However, that disclaimer aside, I
cannot reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
------------------------------------------------------------------
--
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted
with it are intended exclusively for the individual or entity to
which it is addressed. The message, together with any attachment,
may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying,
disclosure or distribution is strictly prohibited. If you have
received this message in error, please immediately advise the
sender by reply email and delete all copies.
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise
John Cooper
2014-09-09 20:16:22 UTC
Permalink
Microsoft forum, I should say.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 3:14 PM
To: 'General discussion about the WiX toolset.'
Subject: RE: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Just got this from Microsoft as a proposed fix:

http://www.vindamedia.com/windows/help/windows-installer-msi-hash-mismatch
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 12:40 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I figure it was a minor upgrade with the ProductCodes.

There was some expression of interest in a registry dump on my reproducing machine for HKCR\Msi.Package. So, here it is:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Msi.Package]
@="Windows Installer Package"
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"
"EditFlags"=hex:00,00,10,00
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,\
00,2d,00,33,00,34,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\DefaultIcon]
@="C:\\Windows\\System32\\msiexec.exe,0"

[HKEY_CLASSES_ROOT\Msi.Package\shell]
@="Open,Repair,Uninstall"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit]
@="&Edit with Orca"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit\command]
@="\"C:\\Program Files (x86)\\Orca\\Orca.exe\" \"%1\""
"command"=hex(7):36,00,59,00,55,00,27,00,53,00,72,00,2d,00,54,00,35,00,40,00,\
45,00,40,00,35,00,4c,00,28,00,28,00,2e,00,6d,00,4a,00,55,00,4f,00,72,00,63,\
00,61,00,3e,00,6e,00,52,00,37,00,39,00,66,00,5e,00,26,00,71,00,66,00,28,00,\
76,00,3f,00,65,00,71,00,46,00,28,00,29,00,77,00,26,00,47,00,20,00,22,00,25,\
00,31,00,22,00,00,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open]
@="&Install"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,36,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair]
@="Re&pair"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,37,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,66,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser]
@="@shell32.dll,-50944"
"SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}"
"Extended"=""

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser\command]
"DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}"

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall]
@="&Uninstall"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,38,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,78,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shellex]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers]
@="Compatibility"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers\Compatibility]
@="{1d27f844-3a1f-4410-85ac-14651078412d}"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers\ShimLayer Property Page] @="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 10:53 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Factor that may or may not mean anything:

Upgrade Scheduling appears to be InstallValidate
REINSTALLMODE: vomus
OS: Windows 8 with latest updates including KB2918614
Profile: Roaming (only able to reproduce on a laptop) MajorUpgrade authoring is not being used (custom Upgrade Table entries)

Failure looks like this in the MSI log:

MSI (s) (A8:E8) [09:20:04:609]: Determining source type MSI (s) (A8:E8) [09:20:04:609]: Source type from package 'Lyve Product.msi': 10 MSI (s) (A8:E8) [09:20:04:609]: SECREPAIR: Hash Database: C:\WINDOWS\Installer\SourceHash{C5E60292-2E11-4FAE-883F-E548ECF032F7}
MSI (s) (A8:E8) [09:20:04:625]: SECREPAIR: CryptAcquireContext succeeded MSI (s) (A8:E8) [09:20:04:844]: SECREPAIR: filename: Lyve Product.msi Stored Hash Value:RUgGMOmbpYsraTZ8VjLP1M9KGepCCMUiBVmXkOMCD6w= Current Hash:TfXkukwiWlgqxX0jqHwgUEwjjKlSG2KJpuZX/cEM3Uw=
MSI (s) (A8:E8) [09:20:04:844]: Machine policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: User policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: MSI_LUA: Elevation prompt disabled for silent installs MSI (s) (A8:E8) [09:20:04:844]: Note: 1: 3 MSI (s) (A8:E8) [09:20:04:844]: SECUREREPAIR: SecureRepair Failed. Error code: 364DF2640 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 2265 2: 3: -2147287035 MSI (s) (A8:E8) [09:20:04:859]: Machine policy value 'DisableRollback' is 0 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 9:20:04: RegisterProduct. Return value 2.

It looks like this in the bootstrapper log:

[1D64:1100][2014-09-09T09:20:01]i300: Apply begin
[1D64:1100][2014-09-09T09:20:02]i000: Caching bundle from: 'C:\Users\jocooper\AppData\Local\Temp\{a8554c44-e09c-479f-a8e5-685f5bf90487}\.be\Lyve Setup.exe' to: 'C:\Users\jocooper\AppData\Local\Package Cache\{a8554c44-e09c-479f-a8e5-685f5bf90487}\Lyve Setup.exe'
[1D64:1100][2014-09-09T09:20:02]i320: Registering bundle dependency provider: {a8554c44-e09c-479f-a8e5-685f5bf90487}, version: 1.0.1.1079
[1D64:1FFC][2014-09-09T09:20:02]i305: Verified acquired payload: Lyve at path: C:\Users\jocooper\AppData\Local\Package Cache\.unverified\Lyve, moving to: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi.
[1D64:1100][2014-09-09T09:20:02]i323: Registering package dependency provider: {C5E60292-2E11-4FAE-883F-E548ECF032F7}, version: 1.0.1.1079, package: Lyve
[1D64:1100][2014-09-09T09:20:02]i301: Applying execute package: Lyve, action: MinorUpgrade, path: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to perform minor upgrade of MSI package.
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to configure per-user MSI package.
[1D64:1100][2014-09-09T09:20:04]i319: Applied execute package: Lyve, result: 0x80070642, restart: None
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to execute MSI package.

An earlier upgrade with the same installers succeed when KB2918614 was missing. I then remove the product, applied the update, and rebooted. Initial install of the older product succeeded. Upgrade failed.

It appears that the digital signature requirements for repair/upgrade using msiexec 5.0 have been more strict. The stored hash and the computed hash are not matching after the update (they did before) and that is failing the upgrade.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com


-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 9:42 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Ok, did some install testing of the upgrade from the earlier version to 1709 this morning.

Windows Server 2008 R2 No repro
Windows Server 2012 No repro

Windows 8 Reproduces

I'm digging through the logs . . .
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 5:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Right, fresh install works fine for me, it's only the upgrade case that is borked.

// Sascha
Post by John Cooper
It doesn't replicate for me in the NOT installed case for the 1709
version of the product. I'll get the earlier product tonight and test
the upgrade case tomorrow.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
From: John Cooper
Sent: Monday, September 8, 2014 2:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
If a file is unversioned, the normal file versioning rules and process don’t apply to it.
In the case of these three assemblies, they end up being entries in
the MsiFileHash table. However, file timestamps control whether the
MsiFileHash table is even entered.
Repairs are also going to be strange. Likewise patching.
That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:28 PM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
For what it is worth, I tried one of my investigation packages with a
"fake exe" (for the sake of ease of recognizing as a fake) which,
needless to say, has no version at all. It seems to upgrade fine with no trouble.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll
all are completely unversioned (no version numbers at all). When an
upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Yes, my installer uses a bundle because I have .NET Framework 4.5.1
and Visual C++ 12 runtime components as a prerequisite before running
my actual product MSI.
I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe
it's actually something about upgrading a bundle that causes the
failure to happen.
In terms of what do we know, I don't think we know anything, we have
yet to find anything common between the failing installers. It seems
to fail for both per-user and per-machine installs, domain as well as
workgroup user accounts, elevated and non-elevated privileges, none of
that seems to matter.
// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the
community.
Post by K***@statcan.gc.ca
We are worse off, too, than some, because the machines I deal with
are mostly-disconnected remotes which receive the vast majority of
their tech support via RDP if at all. It seems that most of the
hypotheses around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that
you are dealing with MSIs in a bundle (correct?), which we don't do
- we use bundles to use Windows Update files (MSUs) only, at
present. All the rest of our stuff is just MSI. (Or rarely - testing
only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed
when none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't
currently replicate.
Post by K***@statcan.gc.ca
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our
installers and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one
to the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there
is anything that can be done to fix this from our end, it seems to
me like Microsoft needs to reissue the hotfix or have another hotfix
that
fixes the broken one.
Post by K***@statcan.gc.ca
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned
MSIs deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something
unusual or "wrong" with them. However, that disclaimer aside, I
cannot reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
------------------------------------------------------------------
--
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted
with it are intended exclusively for the individual or entity to
which it is addressed. The message, together with any attachment,
may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying,
disclosure or distribution is strictly prohibited. If you have
received this message in error, please immediately advise the
sender by reply email and delete all copies.
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email
John Cooper
2014-09-09 20:23:07 UTC
Permalink
Looking at the link, it would address the case where something was wrong with HKCR/Msi or HKCR/Msi.Package, but the repro I had on Window 8 appears to have the correct entries here.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 3:16 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Microsoft forum, I should say.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 3:14 PM
To: 'General discussion about the WiX toolset.'
Subject: RE: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Just got this from Microsoft as a proposed fix:

http://www.vindamedia.com/windows/help/windows-installer-msi-hash-mismatch
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 12:40 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I figure it was a minor upgrade with the ProductCodes.

There was some expression of interest in a registry dump on my reproducing machine for HKCR\Msi.Package. So, here it is:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Msi.Package]
@="Windows Installer Package"
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"
"EditFlags"=hex:00,00,10,00
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,\
00,2d,00,33,00,34,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\DefaultIcon]
@="C:\\Windows\\System32\\msiexec.exe,0"

[HKEY_CLASSES_ROOT\Msi.Package\shell]
@="Open,Repair,Uninstall"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit]
@="&Edit with Orca"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit\command]
@="\"C:\\Program Files (x86)\\Orca\\Orca.exe\" \"%1\""
"command"=hex(7):36,00,59,00,55,00,27,00,53,00,72,00,2d,00,54,00,35,00,40,00,\
45,00,40,00,35,00,4c,00,28,00,28,00,2e,00,6d,00,4a,00,55,00,4f,00,72,00,63,\
00,61,00,3e,00,6e,00,52,00,37,00,39,00,66,00,5e,00,26,00,71,00,66,00,28,00,\
76,00,3f,00,65,00,71,00,46,00,28,00,29,00,77,00,26,00,47,00,20,00,22,00,25,\
00,31,00,22,00,00,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open]
@="&Install"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,36,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair]
@="Re&pair"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,37,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,66,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser]
@="@shell32.dll,-50944"
"SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}"
"Extended"=""

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser\command]
"DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}"

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall]
@="&Uninstall"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,38,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,78,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shellex]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers]
@="Compatibility"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers\Compatibility]
@="{1d27f844-3a1f-4410-85ac-14651078412d}"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers\ShimLayer Property Page] @="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 10:53 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Factor that may or may not mean anything:

Upgrade Scheduling appears to be InstallValidate
REINSTALLMODE: vomus
OS: Windows 8 with latest updates including KB2918614
Profile: Roaming (only able to reproduce on a laptop) MajorUpgrade authoring is not being used (custom Upgrade Table entries)

Failure looks like this in the MSI log:

MSI (s) (A8:E8) [09:20:04:609]: Determining source type MSI (s) (A8:E8) [09:20:04:609]: Source type from package 'Lyve Product.msi': 10 MSI (s) (A8:E8) [09:20:04:609]: SECREPAIR: Hash Database: C:\WINDOWS\Installer\SourceHash{C5E60292-2E11-4FAE-883F-E548ECF032F7}
MSI (s) (A8:E8) [09:20:04:625]: SECREPAIR: CryptAcquireContext succeeded MSI (s) (A8:E8) [09:20:04:844]: SECREPAIR: filename: Lyve Product.msi Stored Hash Value:RUgGMOmbpYsraTZ8VjLP1M9KGepCCMUiBVmXkOMCD6w= Current Hash:TfXkukwiWlgqxX0jqHwgUEwjjKlSG2KJpuZX/cEM3Uw=
MSI (s) (A8:E8) [09:20:04:844]: Machine policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: User policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: MSI_LUA: Elevation prompt disabled for silent installs MSI (s) (A8:E8) [09:20:04:844]: Note: 1: 3 MSI (s) (A8:E8) [09:20:04:844]: SECUREREPAIR: SecureRepair Failed. Error code: 364DF2640 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 2265 2: 3: -2147287035 MSI (s) (A8:E8) [09:20:04:859]: Machine policy value 'DisableRollback' is 0 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 9:20:04: RegisterProduct. Return value 2.

It looks like this in the bootstrapper log:

[1D64:1100][2014-09-09T09:20:01]i300: Apply begin
[1D64:1100][2014-09-09T09:20:02]i000: Caching bundle from: 'C:\Users\jocooper\AppData\Local\Temp\{a8554c44-e09c-479f-a8e5-685f5bf90487}\.be\Lyve Setup.exe' to: 'C:\Users\jocooper\AppData\Local\Package Cache\{a8554c44-e09c-479f-a8e5-685f5bf90487}\Lyve Setup.exe'
[1D64:1100][2014-09-09T09:20:02]i320: Registering bundle dependency provider: {a8554c44-e09c-479f-a8e5-685f5bf90487}, version: 1.0.1.1079
[1D64:1FFC][2014-09-09T09:20:02]i305: Verified acquired payload: Lyve at path: C:\Users\jocooper\AppData\Local\Package Cache\.unverified\Lyve, moving to: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi.
[1D64:1100][2014-09-09T09:20:02]i323: Registering package dependency provider: {C5E60292-2E11-4FAE-883F-E548ECF032F7}, version: 1.0.1.1079, package: Lyve
[1D64:1100][2014-09-09T09:20:02]i301: Applying execute package: Lyve, action: MinorUpgrade, path: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to perform minor upgrade of MSI package.
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to configure per-user MSI package.
[1D64:1100][2014-09-09T09:20:04]i319: Applied execute package: Lyve, result: 0x80070642, restart: None
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to execute MSI package.

An earlier upgrade with the same installers succeed when KB2918614 was missing. I then remove the product, applied the update, and rebooted. Initial install of the older product succeeded. Upgrade failed.

It appears that the digital signature requirements for repair/upgrade using msiexec 5.0 have been more strict. The stored hash and the computed hash are not matching after the update (they did before) and that is failing the upgrade.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com


-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 9:42 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Ok, did some install testing of the upgrade from the earlier version to 1709 this morning.

Windows Server 2008 R2 No repro
Windows Server 2012 No repro

Windows 8 Reproduces

I'm digging through the logs . . .
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 5:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Right, fresh install works fine for me, it's only the upgrade case that is borked.

// Sascha
Post by John Cooper
It doesn't replicate for me in the NOT installed case for the 1709
version of the product. I'll get the earlier product tonight and test
the upgrade case tomorrow.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
From: John Cooper
Sent: Monday, September 8, 2014 2:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
If a file is unversioned, the normal file versioning rules and process don’t apply to it.
In the case of these three assemblies, they end up being entries in
the MsiFileHash table. However, file timestamps control whether the
MsiFileHash table is even entered.
Repairs are also going to be strange. Likewise patching.
That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:28 PM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
For what it is worth, I tried one of my investigation packages with a
"fake exe" (for the sake of ease of recognizing as a fake) which,
needless to say, has no version at all. It seems to upgrade fine with no trouble.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll
all are completely unversioned (no version numbers at all). When an
upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Yes, my installer uses a bundle because I have .NET Framework 4.5.1
and Visual C++ 12 runtime components as a prerequisite before running
my actual product MSI.
I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe
it's actually something about upgrading a bundle that causes the
failure to happen.
In terms of what do we know, I don't think we know anything, we have
yet to find anything common between the failing installers. It seems
to fail for both per-user and per-machine installs, domain as well as
workgroup user accounts, elevated and non-elevated privileges, none of
that seems to matter.
// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the
community.
Post by K***@statcan.gc.ca
We are worse off, too, than some, because the machines I deal with
are mostly-disconnected remotes which receive the vast majority of
their tech support via RDP if at all. It seems that most of the
hypotheses around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that
you are dealing with MSIs in a bundle (correct?), which we don't do
- we use bundles to use Windows Update files (MSUs) only, at
present. All the rest of our stuff is just MSI. (Or rarely - testing
only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed
when none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't
currently replicate.
Post by K***@statcan.gc.ca
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our
installers and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one
to the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there
is anything that can be done to fix this from our end, it seems to
me like Microsoft needs to reissue the hotfix or have another hotfix
that
fixes the broken one.
Post by K***@statcan.gc.ca
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned
MSIs deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something
unusual or "wrong" with them. However, that disclaimer aside, I
cannot reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
------------------------------------------------------------------
--
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted
with it are intended exclusively for the individual or entity to
which it is addressed. The message, together with any attachment,
may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying,
disclosure or distribution is strictly prohibited. If you have
received this message in error, please immediately advise the
sender by reply email and delete all copies.
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and
K***@statcan.gc.ca
2014-09-09 20:42:00 UTC
Permalink
I noticed that your reproduction was only slightly similar to one of the ones from earlier in the thread. The one earlier was an overlapped I/O, yours is a hash being different.

Also, didn't some report problems with Windows 7, and your testing is on 8?



Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
***@statcan.gc.ca
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


-----Original Message-----
From: John Cooper [mailto:***@jackhenry.com]
Sent: September-09-14 4:23 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Looking at the link, it would address the case where something was wrong with HKCR/Msi or HKCR/Msi.Package, but the repro I had on Window 8 appears to have the correct entries here.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 3:16 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Microsoft forum, I should say.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 3:14 PM
To: 'General discussion about the WiX toolset.'
Subject: RE: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Just got this from Microsoft as a proposed fix:

http://www.vindamedia.com/windows/help/windows-installer-msi-hash-mismatch
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 12:40 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I figure it was a minor upgrade with the ProductCodes.

There was some expression of interest in a registry dump on my reproducing machine for HKCR\Msi.Package. So, here it is:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Msi.Package]
@="Windows Installer Package"
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"
"EditFlags"=hex:00,00,10,00
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,\
00,2d,00,33,00,34,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\DefaultIcon]
@="C:\\Windows\\System32\\msiexec.exe,0"

[HKEY_CLASSES_ROOT\Msi.Package\shell]
@="Open,Repair,Uninstall"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit]
@="&Edit with Orca"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit\command]
@="\"C:\\Program Files (x86)\\Orca\\Orca.exe\" \"%1\""
"command"=hex(7):36,00,59,00,55,00,27,00,53,00,72,00,2d,00,54,00,35,00,40,00,\
45,00,40,00,35,00,4c,00,28,00,28,00,2e,00,6d,00,4a,00,55,00,4f,00,72,00,63,\
00,61,00,3e,00,6e,00,52,00,37,00,39,00,66,00,5e,00,26,00,71,00,66,00,28,00,\
76,00,3f,00,65,00,71,00,46,00,28,00,29,00,77,00,26,00,47,00,20,00,22,00,25,\
00,31,00,22,00,00,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open]
@="&Install"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,36,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair]
@="Re&pair"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,37,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,66,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser]
@="@shell32.dll,-50944"
"SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}"
"Extended"=""

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser\command]
"DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}"

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall]
@="&Uninstall"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,38,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,78,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shellex]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers]
@="Compatibility"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers\Compatibility]
@="{1d27f844-3a1f-4410-85ac-14651078412d}"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers\ShimLayer Property Page] @="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 10:53 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Factor that may or may not mean anything:

Upgrade Scheduling appears to be InstallValidate
REINSTALLMODE: vomus
OS: Windows 8 with latest updates including KB2918614
Profile: Roaming (only able to reproduce on a laptop) MajorUpgrade authoring is not being used (custom Upgrade Table entries)

Failure looks like this in the MSI log:

MSI (s) (A8:E8) [09:20:04:609]: Determining source type MSI (s) (A8:E8) [09:20:04:609]: Source type from package 'Lyve Product.msi': 10 MSI (s) (A8:E8) [09:20:04:609]: SECREPAIR: Hash Database: C:\WINDOWS\Installer\SourceHash{C5E60292-2E11-4FAE-883F-E548ECF032F7}
MSI (s) (A8:E8) [09:20:04:625]: SECREPAIR: CryptAcquireContext succeeded MSI (s) (A8:E8) [09:20:04:844]: SECREPAIR: filename: Lyve Product.msi Stored Hash Value:RUgGMOmbpYsraTZ8VjLP1M9KGepCCMUiBVmXkOMCD6w= Current Hash:TfXkukwiWlgqxX0jqHwgUEwjjKlSG2KJpuZX/cEM3Uw=
MSI (s) (A8:E8) [09:20:04:844]: Machine policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: User policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: MSI_LUA: Elevation prompt disabled for silent installs MSI (s) (A8:E8) [09:20:04:844]: Note: 1: 3 MSI (s) (A8:E8) [09:20:04:844]: SECUREREPAIR: SecureRepair Failed. Error code: 364DF2640 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 2265 2: 3: -2147287035 MSI (s) (A8:E8) [09:20:04:859]: Machine policy value 'DisableRollback' is 0 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 9:20:04: RegisterProduct. Return value 2.

It looks like this in the bootstrapper log:

[1D64:1100][2014-09-09T09:20:01]i300: Apply begin
[1D64:1100][2014-09-09T09:20:02]i000: Caching bundle from: 'C:\Users\jocooper\AppData\Local\Temp\{a8554c44-e09c-479f-a8e5-685f5bf90487}\.be\Lyve Setup.exe' to: 'C:\Users\jocooper\AppData\Local\Package Cache\{a8554c44-e09c-479f-a8e5-685f5bf90487}\Lyve Setup.exe'
[1D64:1100][2014-09-09T09:20:02]i320: Registering bundle dependency provider: {a8554c44-e09c-479f-a8e5-685f5bf90487}, version: 1.0.1.1079
[1D64:1FFC][2014-09-09T09:20:02]i305: Verified acquired payload: Lyve at path: C:\Users\jocooper\AppData\Local\Package Cache\.unverified\Lyve, moving to: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi.
[1D64:1100][2014-09-09T09:20:02]i323: Registering package dependency provider: {C5E60292-2E11-4FAE-883F-E548ECF032F7}, version: 1.0.1.1079, package: Lyve
[1D64:1100][2014-09-09T09:20:02]i301: Applying execute package: Lyve, action: MinorUpgrade, path: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to perform minor upgrade of MSI package.
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to configure per-user MSI package.
[1D64:1100][2014-09-09T09:20:04]i319: Applied execute package: Lyve, result: 0x80070642, restart: None
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to execute MSI package.

An earlier upgrade with the same installers succeed when KB2918614 was missing. I then remove the product, applied the update, and rebooted. Initial install of the older product succeeded. Upgrade failed.

It appears that the digital signature requirements for repair/upgrade using msiexec 5.0 have been more strict. The stored hash and the computed hash are not matching after the update (they did before) and that is failing the upgrade.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com


-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 9:42 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Ok, did some install testing of the upgrade from the earlier version to 1709 this morning.

Windows Server 2008 R2 No repro
Windows Server 2012 No repro

Windows 8 Reproduces

I'm digging through the logs . . .
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 5:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Right, fresh install works fine for me, it's only the upgrade case that is borked.

// Sascha
Post by John Cooper
It doesn't replicate for me in the NOT installed case for the 1709
version of the product. I'll get the earlier product tonight and test
the upgrade case tomorrow.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
From: John Cooper
Sent: Monday, September 8, 2014 2:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
If a file is unversioned, the normal file versioning rules and process don’t apply to it.
In the case of these three assemblies, they end up being entries in
the MsiFileHash table. However, file timestamps control whether the
MsiFileHash table is even entered.
Repairs are also going to be strange. Likewise patching.
That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:28 PM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
For what it is worth, I tried one of my investigation packages with a
"fake exe" (for the sake of ease of recognizing as a fake) which,
needless to say, has no version at all. It seems to upgrade fine with no trouble.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll
all are completely unversioned (no version numbers at all). When an
upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Yes, my installer uses a bundle because I have .NET Framework 4.5.1
and Visual C++ 12 runtime components as a prerequisite before running
my actual product MSI.
I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe
it's actually something about upgrading a bundle that causes the
failure to happen.
In terms of what do we know, I don't think we know anything, we have
yet to find anything common between the failing installers. It seems
to fail for both per-user and per-machine installs, domain as well as
workgroup user accounts, elevated and non-elevated privileges, none of
that seems to matter.
// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the
community.
Post by K***@statcan.gc.ca
We are worse off, too, than some, because the machines I deal with
are mostly-disconnected remotes which receive the vast majority of
their tech support via RDP if at all. It seems that most of the
hypotheses around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that
you are dealing with MSIs in a bundle (correct?), which we don't do
- we use bundles to use Windows Update files (MSUs) only, at
present. All the rest of our stuff is just MSI. (Or rarely - testing
only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed
when none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't
currently replicate.
Post by K***@statcan.gc.ca
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our
installers and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one
to the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there
is anything that can be done to fix this from our end, it seems to
me like Microsoft needs to reissue the hotfix or have another hotfix
that
fixes the broken one.
Post by K***@statcan.gc.ca
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned
MSIs deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something
unusual or "wrong" with them. However, that disclaimer aside, I
cannot reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
------------------------------------------------------------------
--
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted
with it are intended exclusively for the individual or entity to
which it is addressed. The message, together with any attachment,
may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying,
disclosure or distribution is strictly prohibited. If you have
received this message in error, please immediately advise the
sender by reply email and delete all copies.
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
John Cooper
2014-09-09 21:00:50 UTC
Permalink
That is true. Haven't gotten it to reproduce on any of our 7 Enterprise machines. Did get the Windows 8 to reproduce. No luck on Server 2008 R2 or Server 2012.

The Lyve installer was doing a minor upgrade with a non-standard REINSTALLMODE, but that shouldn't have created the problem I repo'ed. Mine was specific to the hash as you've said.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: ***@statcan.gc.ca [mailto:***@statcan.gc.ca]
Sent: Tuesday, September 9, 2014 3:42 PM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I noticed that your reproduction was only slightly similar to one of the ones from earlier in the thread. The one earlier was an overlapped I/O, yours is a hash being different.

Also, didn't some report problems with Windows 7, and your testing is on 8?



Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 ***@statcan.gc.ca Telephone | Téléphone 613-854-5589 Facsimile | Télécopieur 613-951-4674 Government of Canada | Gouvernement du Canada


-----Original Message-----
From: John Cooper [mailto:***@jackhenry.com]
Sent: September-09-14 4:23 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Looking at the link, it would address the case where something was wrong with HKCR/Msi or HKCR/Msi.Package, but the repro I had on Window 8 appears to have the correct entries here.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 3:16 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Microsoft forum, I should say.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 3:14 PM
To: 'General discussion about the WiX toolset.'
Subject: RE: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Just got this from Microsoft as a proposed fix:

http://www.vindamedia.com/windows/help/windows-installer-msi-hash-mismatch
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 12:40 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I figure it was a minor upgrade with the ProductCodes.

There was some expression of interest in a registry dump on my reproducing machine for HKCR\Msi.Package. So, here it is:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Msi.Package]
@="Windows Installer Package"
"InfoTip"="prop:System.ItemType;System.Author;System.Title;System.Subject;System.Comment;System.DateModified;System.Size"
"EditFlags"=hex:00,00,10,00
"FullDetails"="prop:System.PropGroup.Description;System.Title;System.Subject;System.Category;System.Keywords;System.Comment;System.PropGroup.Origin;System.Author;System.Document.RevisionNumber;System.Document.DateCreated;System.ApplicationName;System.PropGroup.FileSystem;System.ItemNameDisplay;System.ItemType;System.ItemFolderPathDisplay;System.DateCreated;System.DateModified;System.Size;System.FileAttributes;System.OfflineAvailability;System.OfflineStatus;System.SharedWith;System.FileOwner;System.ComputerName"
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,\
00,2d,00,33,00,34,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\DefaultIcon]
@="C:\\Windows\\System32\\msiexec.exe,0"

[HKEY_CLASSES_ROOT\Msi.Package\shell]
@="Open,Repair,Uninstall"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit]
@="&Edit with Orca"

[HKEY_CLASSES_ROOT\Msi.Package\shell\edit\command]
@="\"C:\\Program Files (x86)\\Orca\\Orca.exe\" \"%1\""
"command"=hex(7):36,00,59,00,55,00,27,00,53,00,72,00,2d,00,54,00,35,00,40,00,\
45,00,40,00,35,00,4c,00,28,00,28,00,2e,00,6d,00,4a,00,55,00,4f,00,72,00,63,\
00,61,00,3e,00,6e,00,52,00,37,00,39,00,66,00,5e,00,26,00,71,00,66,00,28,00,\
76,00,3f,00,65,00,71,00,46,00,28,00,29,00,77,00,26,00,47,00,20,00,22,00,25,\
00,31,00,22,00,00,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open]
@="&Install"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,36,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Open\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,69,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair]
@="Re&pair"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,37,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Repair\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,66,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser]
@="@shell32.dll,-50944"
"SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}"
"Extended"=""

[HKEY_CLASSES_ROOT\Msi.Package\shell\runasuser\command]
"DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}"

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall]
@="&Uninstall"
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
00,6d,00,73,00,69,00,6d,00,73,00,67,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,\
33,00,38,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shell\Uninstall\command]
@=hex(2):22,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,\
73,00,69,00,65,00,78,00,65,00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,2f,\
00,78,00,20,00,22,00,25,00,31,00,22,00,20,00,25,00,2a,00,00,00

[HKEY_CLASSES_ROOT\Msi.Package\shellex]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers]
@="Compatibility"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\ContextMenuHandlers\Compatibility]
@="{1d27f844-3a1f-4410-85ac-14651078412d}"

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers]

[HKEY_CLASSES_ROOT\Msi.Package\shellex\PropertySheetHandlers\ShimLayer Property Page] @="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 10:53 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Factor that may or may not mean anything:

Upgrade Scheduling appears to be InstallValidate
REINSTALLMODE: vomus
OS: Windows 8 with latest updates including KB2918614
Profile: Roaming (only able to reproduce on a laptop) MajorUpgrade authoring is not being used (custom Upgrade Table entries)

Failure looks like this in the MSI log:

MSI (s) (A8:E8) [09:20:04:609]: Determining source type MSI (s) (A8:E8) [09:20:04:609]: Source type from package 'Lyve Product.msi': 10 MSI (s) (A8:E8) [09:20:04:609]: SECREPAIR: Hash Database: C:\WINDOWS\Installer\SourceHash{C5E60292-2E11-4FAE-883F-E548ECF032F7}
MSI (s) (A8:E8) [09:20:04:625]: SECREPAIR: CryptAcquireContext succeeded MSI (s) (A8:E8) [09:20:04:844]: SECREPAIR: filename: Lyve Product.msi Stored Hash Value:RUgGMOmbpYsraTZ8VjLP1M9KGepCCMUiBVmXkOMCD6w= Current Hash:TfXkukwiWlgqxX0jqHwgUEwjjKlSG2KJpuZX/cEM3Uw=
MSI (s) (A8:E8) [09:20:04:844]: Machine policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: User policy value 'AlwaysInstallElevated' is 0 MSI (s) (A8:E8) [09:20:04:844]: MSI_LUA: Elevation prompt disabled for silent installs MSI (s) (A8:E8) [09:20:04:844]: Note: 1: 3 MSI (s) (A8:E8) [09:20:04:844]: SECUREREPAIR: SecureRepair Failed. Error code: 364DF2640 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 2265 2: 3: -2147287035 MSI (s) (A8:E8) [09:20:04:859]: Machine policy value 'DisableRollback' is 0 MSI (s) (A8:E8) [09:20:04:859]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 9:20:04: RegisterProduct. Return value 2.

It looks like this in the bootstrapper log:

[1D64:1100][2014-09-09T09:20:01]i300: Apply begin
[1D64:1100][2014-09-09T09:20:02]i000: Caching bundle from: 'C:\Users\jocooper\AppData\Local\Temp\{a8554c44-e09c-479f-a8e5-685f5bf90487}\.be\Lyve Setup.exe' to: 'C:\Users\jocooper\AppData\Local\Package Cache\{a8554c44-e09c-479f-a8e5-685f5bf90487}\Lyve Setup.exe'
[1D64:1100][2014-09-09T09:20:02]i320: Registering bundle dependency provider: {a8554c44-e09c-479f-a8e5-685f5bf90487}, version: 1.0.1.1079
[1D64:1FFC][2014-09-09T09:20:02]i305: Verified acquired payload: Lyve at path: C:\Users\jocooper\AppData\Local\Package Cache\.unverified\Lyve, moving to: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi.
[1D64:1100][2014-09-09T09:20:02]i323: Registering package dependency provider: {C5E60292-2E11-4FAE-883F-E548ECF032F7}, version: 1.0.1.1079, package: Lyve
[1D64:1100][2014-09-09T09:20:02]i301: Applying execute package: Lyve, action: MinorUpgrade, path: C:\Users\jocooper\AppData\Local\Package Cache\{C5E60292-2E11-4FAE-883F-E548ECF032F7}v1.0.1.1079\Lyve Product.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to perform minor upgrade of MSI package.
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to configure per-user MSI package.
[1D64:1100][2014-09-09T09:20:04]i319: Applied execute package: Lyve, result: 0x80070642, restart: None
[1D64:1100][2014-09-09T09:20:04]e000: Error 0x80070642: Failed to execute MSI package.

An earlier upgrade with the same installers succeed when KB2918614 was missing. I then remove the product, applied the update, and rebooted. Initial install of the older product succeeded. Upgrade failed.

It appears that the digital signature requirements for repair/upgrade using msiexec 5.0 have been more strict. The stored hash and the computed hash are not matching after the update (they did before) and that is failing the upgrade.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com


-----Original Message-----
From: John Cooper
Sent: Tuesday, September 9, 2014 9:42 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Ok, did some install testing of the upgrade from the earlier version to 1709 this morning.

Windows Server 2008 R2 No repro
Windows Server 2012 No repro

Windows 8 Reproduces

I'm digging through the logs . . .
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |***@jackhenry.com



-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: Monday, September 8, 2014 5:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Right, fresh install works fine for me, it's only the upgrade case that is borked.

// Sascha
Post by John Cooper
It doesn't replicate for me in the NOT installed case for the 1709
version of the product. I'll get the earlier product tonight and test
the upgrade case tomorrow.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
From: John Cooper
Sent: Monday, September 8, 2014 2:54 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
If a file is unversioned, the normal file versioning rules and process don’t apply to it.
In the case of these three assemblies, they end up being entries in
the MsiFileHash table. However, file timestamps control whether the
MsiFileHash table is even entered.
Repairs are also going to be strange. Likewise patching.
That being said, it is a concern, but unlikely to be the source of your problem.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:28 PM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
For what it is worth, I tried one of my investigation packages with a
"fake exe" (for the sake of ease of recognizing as a fake) which,
needless to say, has no version at all. It seems to upgrade fine with no trouble.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 3:18 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll
all are completely unversioned (no version numbers at all). When an
upgrade works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
-----Original Message-----
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Yes, my installer uses a bundle because I have .NET Framework 4.5.1
and Visual C++ 12 runtime components as a prerequisite before running
my actual product MSI.
I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe
it's actually something about upgrading a bundle that causes the
failure to happen.
In terms of what do we know, I don't think we know anything, we have
yet to find anything common between the failing installers. It seems
to fail for both per-user and per-machine installs, domain as well as
workgroup user accounts, elevated and non-elevated privileges, none of
that seems to matter.
// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the
community.
Post by K***@statcan.gc.ca
We are worse off, too, than some, because the machines I deal with
are mostly-disconnected remotes which receive the vast majority of
their tech support via RDP if at all. It seems that most of the
hypotheses around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that
you are dealing with MSIs in a bundle (correct?), which we don't do
- we use bundles to use Windows Update files (MSUs) only, at
present. All the rest of our stuff is just MSI. (Or rarely - testing
only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed
when none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't
currently replicate.
Post by K***@statcan.gc.ca
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our
installers and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one
to the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there
is anything that can be done to fix this from our end, it seems to
me like Microsoft needs to reissue the hotfix or have another hotfix
that
fixes the broken one.
Post by K***@statcan.gc.ca
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned
MSIs deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something
unusual or "wrong" with them. However, that disclaimer aside, I
cannot reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A
0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa
ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
------------------------------------------------------------------
--
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted
with it are intended exclusively for the individual or entity to
which it is addressed. The message, together with any attachment,
may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying,
disclosure or distribution is strictly prohibited. If you have
received this message in error, please immediately advise the
sender by reply email and delete all copies.
------------------------------------------------------------------
--
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is addressed.
The message, together with any attachment, may contain confidential
and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email an
Sascha Sertel
2014-09-08 19:46:40 UTC
Permalink
In a successful upgrade AgentLib.Interop.dll gets replaced if there was a
newer version (which is the case going from 396 to 1079), looks like MSI
doesn't pay much attention to the version but looks at file properties like
size and hash code instead. I should fix the version on this, I remember
having seen this in the past but forgot to fix it since it wasn't causing
any issues then.

The two CefSharp dlls don't get replaced because they didn't change. Those
come from a third party NuGet package, so I don't control the versioning of
those files and will have to live without a version number on them.

// Sascha
Post by John Cooper
I notice that Agent.Interop.dll, CefSharp.dll, and CefSharpt.Wpf.dll all
are completely unversioned (no version numbers at all). When an upgrade
works, what to does the log look like for these three files?
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing Development
Jack Henry & Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |
-----Original Message-----
Sent: Monday, September 8, 2014 2:02 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
Yes, my installer uses a bundle because I have .NET Framework 4.5.1 and
Visual C++ 12 runtime components as a prerequisite before running my actual
product MSI.
I haven't actually tried if the upgrade failure also repros using the
product MSI only instead of the bundle, I'll try that out today. Maybe it's
actually something about upgrading a bundle that causes the failure to
happen.
In terms of what do we know, I don't think we know anything, we have yet
to find anything common between the failing installers. It seems to fail
for both per-user and per-machine installs, domain as well as workgroup
user accounts, elevated and non-elevated privileges, none of that seems to
matter.
// Sascha
Post by K***@statcan.gc.ca
Let me echo John here, I am trying to help us and also help the
community.
Post by K***@statcan.gc.ca
We are worse off, too, than some, because the machines I deal with are
mostly-disconnected remotes which receive the vast majority of their
tech support via RDP if at all. It seems that most of the hypotheses
around are wrong, unless we're just unlucky.
Sascha: I have yet to try your stuff out. I know already now that you
are dealing with MSIs in a bundle (correct?), which we don't do - we
use bundles to use Windows Update files (MSUs) only, at present. All
the rest of our stuff is just MSI. (Or rarely - testing only, I think,
MSP.) So there's a difference right off.
I wonder (list owners willing) if it is time to play "what do we know?"
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile | Télécopieur 613-951-4674 Government of Canada |
Gouvernement du Canada
-----Original Message-----
Sent: September-08-14 2:41 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I am sure that Microsoft will ultimately have to make a fix, but I
have a lot of installers out in the wild, and I feel very exposed when
none of my testers can replicate. I'm much more interested in
understanding the mechanism of failure--especially since I can't
currently replicate.
Post by K***@statcan.gc.ca
Also, it is very hard to justify to management invoking our support
agreement when the issue does not reproduce with any of our product
installers. Much easier if I can replicate.
I'm basically trying to figure out what is different in our installers
and deployment scenarios such that we don't see this issue.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 1:29 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
The issue is very easily reproducible for me when doing an upgrade
from one bundle to another one. I emailed Keith links to two
installers that have 100% repro for me when upgrading from the one to
the other while having
KB2918614 installed. Repros on any machine.
I'm happy to share some logs but given that KB2918614 directly
determines whether the upgrade fails or works I don't know if there is
anything that can be done to fix this from our end, it seems to me
like Microsoft needs to reissue the hotfix or have another hotfix that
fixes the broken one.
Post by K***@statcan.gc.ca
// Sascha
Post by John Cooper
I haven't been able to reproduce this using signed or unsigned MSIs
deploying in an "Open" or "Closed" Environment.
I would be very happy to take a look at some verbose logs of the
failures.
Post by John Cooper
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications |
Continuing Development Jack Henry & Associates, Inc.® | Lenexa, KS
-----Original Message-----
Sent: Monday, September 8, 2014 10:40 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
I've now tried a "small update". I've never fully understood why
you’d use these, but my co-workers wanted to use MSPs for some of
our updating, so I built a front end for making those and hence
small updates. That all to say that I may be doing something unusual
or "wrong" with them. However, that disclaimer aside, I cannot
reproduce
any trouble with that either.
Post by John Cooper
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-08-14 8:41 AM
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Ah! There seems to be some confusion on this point. I will see.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A
Facsimile
| Télécopieur 613-951-4674 Government of Canada | Gouvernement du
| Canada
-----Original Message-----
Sent: September-06-14 1:27 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Post by K***@statcan.gc.ca
I've gotten hold of a Windows 7 x64 VM and tried installing,
uninstalling, repairing a few dinky products we have built
installers for over the last while. Even added a new one with a
large (100 megabytes
uncompressed) payload. Tried with and without UAC for all. No
troubles at all with the trouble KB installed. User was a domain
account, for what that is worth.
Well, previous messages indicate the problem is with minor updates.
Did you try updates, or only install/uninstall/repair?
--
Nicolás
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with
it are intended exclusively for the individual or entity to which it
is addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure
or distribution is strictly prohibited. If you have received this
message in error, please immediately advise the sender by reply
email and delete all copies.
--------------------------------------------------------------------
--
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message
in error, please immediately advise the sender by reply email and
delete all copies.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control.
Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Neil Sleightholm
2014-08-28 20:00:41 UTC
Permalink
I have seen that reported but I think it is slightly different. Does removing kb2918614 fix it?

-----Original Message-----
From: Matt O'Connell [mailto:***@gmail.com]
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

We get a slightly different error out of CryptAcquireContext, ours follow this pattern:
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: Hash Database:
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt Provider not initialized. Error:997 MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: Failed to CreateContentHash of the file: xxxx\xxxxx\xxxx.JPG: for computing its hash. Error: 997 MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Failed to create hash for the install source files MSI (s) (28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8

Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig. However
removing the kb update has fixed it for at least one customer. I'm
hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb29186
14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPA
IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7
596414p7596418.html Sent from the wix-users mailing list archive at
Nabble.com.
---------------------------------------------------------------------
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------------------------------------------
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Sascha Sertel
2014-08-28 20:31:03 UTC
Permalink
@Neil: Yes, for us removing KB2918614 fixed the error and got us back to
working state. No other workaround known at this time.

I've been trying to figure out why this only seems to affect certain MSIs.
Here some parameters that might be relevant:
- WiX 3.8
- per-User install, no elevated privileges
- Custom managed bootstrapper on .NET 4.0
- Custom managed action

Since this is reproducible directly with the MSI already I don't think it
has anything to do with the bundle or any of the bundle parameters.

The KB2918614 information website shows that Msi.dll and other related
binaries are being replaced, I wish there was some more information on what
they actually changed in Windows Installer, that would probably help locate
where these issues are coming from and what scenarios trigger them.

// Sascha
Post by Neil Sleightholm
I have seen that reported but I think it is slightly different. Does
removing kb2918614 fix it?
-----Original Message-----
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file
already exists. Deleting it.
MSI (s) (28:BC) [10:47:26:839]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash Database creation
complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s)
(28:BC) [10:47:26:860]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s)
(28:BC) [10:47:26:862]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt
SECREPAIR: Failed to create hash for the install source files MSI (s)
(28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig. However
removing the kb update has fixed it for at least one customer. I'm
hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb29186
14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPA
IR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7
596414p7596418.html Sent from the wix-users mailing list archive at
Nabble.com.
---------------------------------------------------------------------
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------------------------------------------
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Neil Sleightholm
2014-08-28 21:09:46 UTC
Permalink
Our install isn't any of those :-)
WiX 3.7, Per Machine, No bootstrapper, No managed CA

I can reproduce the issue with a very minimal MSI, no UI, only installs 1 file.

Neil

-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: 28 August 2014 21:31
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

@Neil: Yes, for us removing KB2918614 fixed the error and got us back to working state. No other workaround known at this time.

I've been trying to figure out why this only seems to affect certain MSIs.
Here some parameters that might be relevant:
- WiX 3.8
- per-User install, no elevated privileges
- Custom managed bootstrapper on .NET 4.0
- Custom managed action

Since this is reproducible directly with the MSI already I don't think it has anything to do with the bundle or any of the bundle parameters.

The KB2918614 information website shows that Msi.dll and other related binaries are being replaced, I wish there was some more information on what they actually changed in Windows Installer, that would probably help locate where these issues are coming from and what scenarios trigger them.

// Sascha
Post by Neil Sleightholm
I have seen that reported but I think it is slightly different. Does
removing kb2918614 fix it?
-----Original Message-----
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file
already exists. Deleting it.
-2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash
Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s)
(28:BC) [10:47:26:860]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s)
(28:BC) [10:47:26:862]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt
SECREPAIR: Failed to create hash for the install source files MSI (s)
(28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig.
However removing the kb update has fixed it for at least one
customer. I'm hoping to find a recipe to replicate it but we're not there yet.
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb291
86 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECRE
PA
IR-CryptAcquireContext-Could-not-create-the-default-key-container-t
p7 596414p7596418.html Sent from the wix-users mailing list archive
at Nabble.com.
-------------------------------------------------------------------
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Sascha Sertel
2014-08-28 21:27:49 UTC
Permalink
@Neil: That's good to know, and great to have an easy repro, I'm sure
Microsoft will need that to come up with a fix. But this still only affects
the upgrade case, or does it happen on first install for you as well? In my
case it's only on (minor) upgrade, fresh install works fine.

This makes me wonder even more why others aren't affected by this, maybe
most people simply don't update their Windows machines with the latest
updates that often? I update my test machine regularly exactly for this
scenario where a new KB update breaks something.

// Sascha
Post by Neil Sleightholm
Our install isn't any of those :-)
WiX 3.7, Per Machine, No bootstrapper, No managed CA
I can reproduce the issue with a very minimal MSI, no UI, only installs 1 file.
Neil
-----Original Message-----
Sent: 28 August 2014 21:31
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
@Neil: Yes, for us removing KB2918614 fixed the error and got us back to
working state. No other workaround known at this time.
I've been trying to figure out why this only seems to affect certain MSIs.
- WiX 3.8
- per-User install, no elevated privileges
- Custom managed bootstrapper on .NET 4.0
- Custom managed action
Since this is reproducible directly with the MSI already I don't think it
has anything to do with the bundle or any of the bundle parameters.
The KB2918614 information website shows that Msi.dll and other related
binaries are being replaced, I wish there was some more information on what
they actually changed in Windows Installer, that would probably help locate
where these issues are coming from and what scenarios trigger them.
// Sascha
Post by Neil Sleightholm
I have seen that reported but I think it is slightly different. Does
removing kb2918614 fix it?
-----Original Message-----
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file
already exists. Deleting it.
-2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash
Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s)
(28:BC) [10:47:26:860]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0 MSI (s)
(28:BC) [10:47:26:862]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt
SECREPAIR: Failed to create hash for the install source files MSI (s)
(28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig.
However removing the kb update has fixed it for at least one
customer. I'm hoping to find a recipe to replicate it but we're not
there yet.
Post by Neil Sleightholm
Post by Matt O'Connell
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb291
86 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECRE
PA
IR-CryptAcquireContext-Could-not-create-the-default-key-container-t
p7 596414p7596418.html Sent from the wix-users mailing list archive
at Nabble.com.
-------------------------------------------------------------------
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Neil Sleightholm
2014-08-29 05:14:45 UTC
Permalink
It also happens with a clean install in my scenario.

-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: 28 August 2014 22:28
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

@Neil: That's good to know, and great to have an easy repro, I'm sure Microsoft will need that to come up with a fix. But this still only affects the upgrade case, or does it happen on first install for you as well? In my case it's only on (minor) upgrade, fresh install works fine.

This makes me wonder even more why others aren't affected by this, maybe most people simply don't update their Windows machines with the latest updates that often? I update my test machine regularly exactly for this scenario where a new KB update breaks something.

// Sascha
Post by Neil Sleightholm
Our install isn't any of those :-)
WiX 3.7, Per Machine, No bootstrapper, No managed CA
I can reproduce the issue with a very minimal MSI, no UI, only
installs 1 file.
Neil
-----Original Message-----
Sent: 28 August 2014 21:31
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
@Neil: Yes, for us removing KB2918614 fixed the error and got us back
to working state. No other workaround known at this time.
I've been trying to figure out why this only seems to affect certain MSIs.
- WiX 3.8
- per-User install, no elevated privileges
- Custom managed bootstrapper on .NET 4.0
- Custom managed action
Since this is reproducible directly with the MSI already I don't think
it has anything to do with the bundle or any of the bundle parameters.
The KB2918614 information website shows that Msi.dll and other related
binaries are being replaced, I wish there was some more information on
what they actually changed in Windows Installer, that would probably
help locate where these issues are coming from and what scenarios trigger them.
// Sascha
Post by Neil Sleightholm
I have seen that reported but I think it is slightly different. Does
removing kb2918614 fix it?
-----Original Message-----
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file
already exists. Deleting it.
-2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash
Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI
(s)
(28:BC) [10:47:26:860]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI
(s)
(28:BC) [10:47:26:862]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt
SECREPAIR: Failed to create hash for the install source files MSI (s)
(28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig.
However removing the kb update has fixed it for at least one
customer. I'm hoping to find a recipe to replicate it but we're not
there yet.
Post by Neil Sleightholm
Post by Matt O'Connell
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could
not create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2
91
86 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SEC
RE
PA
IR-CryptAcquireContext-Could-not-create-the-default-key-container
-t
p7 596414p7596418.html Sent from the wix-users mailing list
archive at Nabble.com.
-----------------------------------------------------------------
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-----------------------------------------------------------------
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Phil Wilson
2014-08-29 18:23:41 UTC
Permalink
Is this happening primarily in domains or networks? This may or may
not be connected, but I'm wondering if that's a common theme, and
other occurrences of this tend to suggest that trusting the computer
or the user to allow delegation might be a fix.
---------------
Phil Wilson
Post by Neil Sleightholm
It also happens with a clean install in my scenario.
-----Original Message-----
Sent: 28 August 2014 22:28
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container
@Neil: That's good to know, and great to have an easy repro, I'm sure Microsoft will need that to come up with a fix. But this still only affects the upgrade case, or does it happen on first install for you as well? In my case it's only on (minor) upgrade, fresh install works fine.
This makes me wonder even more why others aren't affected by this, maybe most people simply don't update their Windows machines with the latest updates that often? I update my test machine regularly exactly for this scenario where a new KB update breaks something.
// Sascha
Post by Neil Sleightholm
Our install isn't any of those :-)
WiX 3.7, Per Machine, No bootstrapper, No managed CA
I can reproduce the issue with a very minimal MSI, no UI, only installs 1 file.
Neil
-----Original Message-----
Sent: 28 August 2014 21:31
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
@Neil: Yes, for us removing KB2918614 fixed the error and got us back
to working state. No other workaround known at this time.
I've been trying to figure out why this only seems to affect certain MSIs.
- WiX 3.8
- per-User install, no elevated privileges
- Custom managed bootstrapper on .NET 4.0
- Custom managed action
Since this is reproducible directly with the MSI already I don't think
it has anything to do with the bundle or any of the bundle parameters.
The KB2918614 information website shows that Msi.dll and other related
binaries are being replaced, I wish there was some more information on
what they actually changed in Windows Installer, that would probably
help locate where these issues are coming from and what scenarios trigger them.
// Sascha
Post by Neil Sleightholm
I have seen that reported but I think it is slightly different. Does
removing kb2918614 fix it?
-----Original Message-----
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
We get a slightly different error out of CryptAcquireContext, ours
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database file
already exists. Deleting it.
-2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash
Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: Crypt
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI
(s)
(28:BC) [10:47:26:860]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:860]: SECREPAIR: Crypt
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI
(s)
(28:BC) [10:47:26:862]: SECREPAIR: A general error running
CryptAcquireContext MSI (s) (28:BC) [10:47:26:862]: SECREPAIR: Crypt
SECREPAIR: Failed to create hash for the install source files MSI (s)
(28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that but
we've had no success with disabling Anti-virus with msconfig.
However removing the kb update has fixed it for at least one
customer. I'm hoping to find a recipe to replicate it but we're not
there yet.
Post by Neil Sleightholm
Post by Matt O'Connell
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both look
similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could
not create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2
91
86 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SEC
RE
PA
IR-CryptAcquireContext-Could-not-create-the-default-key-container
-t
p7 596414p7596418.html Sent from the wix-users mailing list
archive at Nabble.com.
-----------------------------------------------------------------
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-----------------------------------------------------------------
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
K***@statcan.gc.ca
2014-08-29 18:33:53 UTC
Permalink
Some of the posts I saw about the topic in other places (e.g. the OpenOffice.org one) seemed to suggest to me that it was local installs as well, but am I not sure I understood the remarks correctly.

Incidentally: my chain of command has raised it with the folks that maintain / have access to our support at Microsoft. I have also requested some VMs be set up so I can do some investigation on my own, but before a long weekend ...



Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
***@statcan.gc.ca
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


-----Original Message-----
From: Phil Wilson [mailto:***@gmail.com]
Sent: August-29-14 2:24 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Is this happening primarily in domains or networks? This may or may not be connected, but I'm wondering if that's a common theme, and other occurrences of this tend to suggest that trusting the computer or the user to allow delegation might be a fix.
---------------
Phil Wilson
Post by Neil Sleightholm
It also happens with a clean install in my scenario.
-----Original Message-----
Sent: 28 August 2014 22:28
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
@Neil: That's good to know, and great to have an easy repro, I'm sure Microsoft will need that to come up with a fix. But this still only affects the upgrade case, or does it happen on first install for you as well? In my case it's only on (minor) upgrade, fresh install works fine.
This makes me wonder even more why others aren't affected by this, maybe most people simply don't update their Windows machines with the latest updates that often? I update my test machine regularly exactly for this scenario where a new KB update breaks something.
// Sascha
Post by Neil Sleightholm
Our install isn't any of those :-)
WiX 3.7, Per Machine, No bootstrapper, No managed CA
I can reproduce the issue with a very minimal MSI, no UI, only installs 1 file.
Neil
-----Original Message-----
Sent: 28 August 2014 21:31
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
@Neil: Yes, for us removing KB2918614 fixed the error and got us back
to working state. No other workaround known at this time.
I've been trying to figure out why this only seems to affect certain MSIs.
- WiX 3.8
- per-User install, no elevated privileges
- Custom managed bootstrapper on .NET 4.0
- Custom managed action
Since this is reproducible directly with the MSI already I don't
think it has anything to do with the bundle or any of the bundle parameters.
The KB2918614 information website shows that Msi.dll and other
related binaries are being replaced, I wish there was some more
information on what they actually changed in Windows Installer, that
would probably help locate where these issues are coming from and what scenarios trigger them.
// Sascha
On Thu, Aug 28, 2014 at 1:00 PM, Neil Sleightholm
Post by Neil Sleightholm
I have seen that reported but I think it is slightly different.
Does removing kb2918614 fix it?
-----Original Message-----
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
We get a slightly different error out of CryptAcquireContext, ours
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
} MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database
file already exists. Deleting it.
-2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash
Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI
(s)
(28:BC) [10:47:26:860]: SECREPAIR: A general error running
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI
(s)
(28:BC) [10:47:26:862]: SECREPAIR: A general error running
SECREPAIR: Failed to create hash for the install source files MSI (s)
(28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that
but we've had no success with disabling Anti-virus with msconfig.
However removing the kb update has fixed it for at least one
customer. I'm hoping to find a recipe to replicate it but we're not
there yet.
Post by Neil Sleightholm
Post by Matt O'Connell
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both
look similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could
not create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb
2
91
86 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SE
C
RE
PA
IR-CryptAcquireContext-Could-not-create-the-default-key-containe
r
-t
p7 596414p7596418.html Sent from the wix-users mailing list
archive at Nabble.com.
----------------------------------------------------------------
-
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------
-
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------
-
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------
-
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------------------------------------------
-
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------------------------------------------
-
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Neil Sleightholm
2014-08-29 21:11:30 UTC
Permalink
I am seeing this on a domain.

We have raised this through our access to Microsoft support and have been told it has been reported to them by a few customers.

Neil

-----Original Message-----
From: Phil Wilson [mailto:***@gmail.com]
Sent: 29 August 2014 19:24
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Is this happening primarily in domains or networks? This may or may not be connected, but I'm wondering if that's a common theme, and other occurrences of this tend to suggest that trusting the computer or the user to allow delegation might be a fix.
---------------
Phil Wilson
Post by Neil Sleightholm
It also happens with a clean install in my scenario.
-----Original Message-----
Sent: 28 August 2014 22:28
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
@Neil: That's good to know, and great to have an easy repro, I'm sure Microsoft will need that to come up with a fix. But this still only affects the upgrade case, or does it happen on first install for you as well? In my case it's only on (minor) upgrade, fresh install works fine.
This makes me wonder even more why others aren't affected by this, maybe most people simply don't update their Windows machines with the latest updates that often? I update my test machine regularly exactly for this scenario where a new KB update breaks something.
// Sascha
Post by Neil Sleightholm
Our install isn't any of those :-)
WiX 3.7, Per Machine, No bootstrapper, No managed CA
I can reproduce the issue with a very minimal MSI, no UI, only installs 1 file.
Neil
-----Original Message-----
Sent: 28 August 2014 21:31
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
@Neil: Yes, for us removing KB2918614 fixed the error and got us back
to working state. No other workaround known at this time.
I've been trying to figure out why this only seems to affect certain MSIs.
- WiX 3.8
- per-User install, no elevated privileges
- Custom managed bootstrapper on .NET 4.0
- Custom managed action
Since this is reproducible directly with the MSI already I don't
think it has anything to do with the bundle or any of the bundle parameters.
The KB2918614 information website shows that Msi.dll and other
related binaries are being replaced, I wish there was some more
information on what they actually changed in Windows Installer, that
would probably help locate where these issues are coming from and what scenarios trigger them.
// Sascha
On Thu, Aug 28, 2014 at 1:00 PM, Neil Sleightholm
Post by Neil Sleightholm
I have seen that reported but I think it is slightly different.
Does removing kb2918614 fix it?
-----Original Message-----
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
We get a slightly different error out of CryptAcquireContext, ours
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
} MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database
file already exists. Deleting it.
-2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash
Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI
(s)
(28:BC) [10:47:26:860]: SECREPAIR: A general error running
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI
(s)
(28:BC) [10:47:26:862]: SECREPAIR: A general error running
SECREPAIR: Failed to create hash for the install source files MSI (s)
(28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate it.
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that
but we've had no success with disabling Anti-virus with msconfig.
However removing the kb update has fixed it for at least one
customer. I'm hoping to find a recipe to replicate it but we're not
there yet.
Post by Neil Sleightholm
Post by Matt O'Connell
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both
look similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could
not create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb
2
91
86 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SE
C
RE
PA
IR-CryptAcquireContext-Could-not-create-the-default-key-containe
r
-t
p7 596414p7596418.html Sent from the wix-users mailing list
archive at Nabble.com.
----------------------------------------------------------------
-
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------
-
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------
-
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------
-
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------------------------------------------
-
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------------------------------------------
-
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Sascha Sertel
2014-08-29 21:28:32 UTC
Permalink
I am seeing this both on domain and workgroup configurations, and both with
users with and without administrator privileges.

I've been trying out all kinds of things but nothing I can think of seems
to make a difference so far.

@Neil: Is your package signed or unsigned? All our packages are signed with
an official code signing certificate, haven't actually disabling the
signing yet to see if that makes any difference.

// Sascha
Post by Neil Sleightholm
I am seeing this on a domain.
We have raised this through our access to Microsoft support and have been
told it has been reported to them by a few customers.
Neil
-----Original Message-----
Sent: 29 August 2014 19:24
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container
Is this happening primarily in domains or networks? This may or may not
be connected, but I'm wondering if that's a common theme, and other
occurrences of this tend to suggest that trusting the computer or the user
to allow delegation might be a fix.
---------------
Phil Wilson
Post by Neil Sleightholm
It also happens with a clean install in my scenario.
-----Original Message-----
Sent: 28 August 2014 22:28
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
@Neil: That's good to know, and great to have an easy repro, I'm sure
Microsoft will need that to come up with a fix. But this still only affects
the upgrade case, or does it happen on first install for you as well? In my
case it's only on (minor) upgrade, fresh install works fine.
Post by Neil Sleightholm
This makes me wonder even more why others aren't affected by this, maybe
most people simply don't update their Windows machines with the latest
updates that often? I update my test machine regularly exactly for this
scenario where a new KB update breaks something.
Post by Neil Sleightholm
// Sascha
Post by Neil Sleightholm
Our install isn't any of those :-)
WiX 3.7, Per Machine, No bootstrapper, No managed CA
I can reproduce the issue with a very minimal MSI, no UI, only installs 1 file.
Neil
-----Original Message-----
Sent: 28 August 2014 21:31
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
@Neil: Yes, for us removing KB2918614 fixed the error and got us back
to working state. No other workaround known at this time.
I've been trying to figure out why this only seems to affect certain
MSIs.
Post by Neil Sleightholm
Post by Neil Sleightholm
- WiX 3.8
- per-User install, no elevated privileges
- Custom managed bootstrapper on .NET 4.0
- Custom managed action
Since this is reproducible directly with the MSI already I don't
think it has anything to do with the bundle or any of the bundle
parameters.
Post by Neil Sleightholm
Post by Neil Sleightholm
The KB2918614 information website shows that Msi.dll and other
related binaries are being replaced, I wish there was some more
information on what they actually changed in Windows Installer, that
would probably help locate where these issues are coming from and what
scenarios trigger them.
Post by Neil Sleightholm
Post by Neil Sleightholm
// Sascha
On Thu, Aug 28, 2014 at 1:00 PM, Neil Sleightholm
Post by Neil Sleightholm
I have seen that reported but I think it is slightly different.
Does removing kb2918614 fix it?
-----Original Message-----
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
We get a slightly different error out of CryptAcquireContext, ours
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
} MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash database
file already exists. Deleting it.
-2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash
Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error running
Crypt Provider not initialized. Error:0 MSI (s) (28:BC)
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:859]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI
(s)
(28:BC) [10:47:26:860]: SECREPAIR: A general error running
Crypt Provider not initialized. Error:0 MSI (s) (28:BC)
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:861]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI
(s)
(28:BC) [10:47:26:862]: SECREPAIR: A general error running
Crypt Provider not initialized. Error:997 MSI (s) (28:BC)
SECREPAIR: Failed to create hash for the install source files MSI (s)
(28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate
it.
Post by Neil Sleightholm
Post by Neil Sleightholm
Post by Neil Sleightholm
Post by Matt O'Connell
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that
but we've had no success with disabling Anti-virus with msconfig.
However removing the kb update has fixed it for at least one
customer. I'm hoping to find a recipe to replicate it but we're not
there yet.
Post by Neil Sleightholm
Post by Matt O'Connell
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both
look similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could
not create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb
2
91
86 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SE
C
RE
PA
IR-CryptAcquireContext-Could-not-create-the-default-key-containe
r
-t
p7 596414p7596418.html Sent from the wix-users mailing list
archive at Nabble.com.
----------------------------------------------------------------
-
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------
-
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------
-
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------
-
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------------------------------------------
-
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------------------------------------------
-
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Neil Sleightholm
2014-08-29 21:31:13 UTC
Permalink
So far only seen with unsigned.

-----Original Message-----
From: Sascha Sertel [mailto:***@gmail.com]
Sent: 29 August 2014 22:29
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I am seeing this both on domain and workgroup configurations, and both with users with and without administrator privileges.

I've been trying out all kinds of things but nothing I can think of seems to make a difference so far.

@Neil: Is your package signed or unsigned? All our packages are signed with an official code signing certificate, haven't actually disabling the signing yet to see if that makes any difference.

// Sascha
Post by Neil Sleightholm
I am seeing this on a domain.
We have raised this through our access to Microsoft support and have
been told it has been reported to them by a few customers.
Neil
-----Original Message-----
Sent: 29 August 2014 19:24
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
Is this happening primarily in domains or networks? This may or may
not be connected, but I'm wondering if that's a common theme, and
other occurrences of this tend to suggest that trusting the computer
or the user to allow delegation might be a fix.
---------------
Phil Wilson
On Thu, Aug 28, 2014 at 10:14 PM, Neil Sleightholm
Post by Neil Sleightholm
It also happens with a clean install in my scenario.
-----Original Message-----
Sent: 28 August 2014 22:28
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
@Neil: That's good to know, and great to have an easy repro, I'm sure
Microsoft will need that to come up with a fix. But this still only
affects the upgrade case, or does it happen on first install for you
as well? In my case it's only on (minor) upgrade, fresh install works fine.
Post by Neil Sleightholm
This makes me wonder even more why others aren't affected by this, maybe
most people simply don't update their Windows machines with the latest
updates that often? I update my test machine regularly exactly for
this scenario where a new KB update breaks something.
Post by Neil Sleightholm
// Sascha
On Thu, Aug 28, 2014 at 2:09 PM, Neil Sleightholm
Post by Neil Sleightholm
Our install isn't any of those :-)
WiX 3.7, Per Machine, No bootstrapper, No managed CA
I can reproduce the issue with a very minimal MSI, no UI, only installs 1 file.
Neil
-----Original Message-----
Sent: 28 August 2014 21:31
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not
create the default key container
@Neil: Yes, for us removing KB2918614 fixed the error and got us
back to working state. No other workaround known at this time.
I've been trying to figure out why this only seems to affect certain
MSIs.
Post by Neil Sleightholm
Post by Neil Sleightholm
- WiX 3.8
- per-User install, no elevated privileges
- Custom managed bootstrapper on .NET 4.0
- Custom managed action
Since this is reproducible directly with the MSI already I don't
think it has anything to do with the bundle or any of the bundle
parameters.
Post by Neil Sleightholm
Post by Neil Sleightholm
The KB2918614 information website shows that Msi.dll and other
related binaries are being replaced, I wish there was some more
information on what they actually changed in Windows Installer,
that would probably help locate where these issues are coming from
and what
scenarios trigger them.
Post by Neil Sleightholm
Post by Neil Sleightholm
// Sascha
On Thu, Aug 28, 2014 at 1:00 PM, Neil Sleightholm
Post by Neil Sleightholm
I have seen that reported but I think it is slightly different.
Does removing kb2918614 fix it?
-----Original Message-----
Sent: 26 August 2014 11:35
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could
not create the default key container
We get a slightly different error out of CryptAcquireContext,
C:\Windows\Installer\SourceHash{xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
xx } MSI (s) (28:BC) [10:47:26:837]: SECREPAIR: SourceHash
database file already exists. Deleting it.
-2147287038 MSI (s) (28:BC) [10:47:26:852]: SECREPAIR: New Hash
Database creation complete.
MSI (s) (28:BC) [10:47:26:854]: SECREPAIR: A general error
Crypt Provider not initialized. Error:0 MSI (s) (28:BC)
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:859]: SECREPAIR: Crypt Provider not initialized.
Error:0 MSI
(s)
(28:BC) [10:47:26:860]: SECREPAIR: A general error running
Crypt Provider not initialized. Error:0 MSI (s) (28:BC)
SECREPAIR: A general error running CryptAcquireContext MSI (s) (28:BC)
[10:47:26:861]: SECREPAIR: Crypt Provider not initialized.
Error:0 MSI
(s)
(28:BC) [10:47:26:862]: SECREPAIR: A general error running
Crypt Provider not initialized. Error:997 MSI (s) (28:BC)
SECREPAIR: Failed to create hash for the install source files MSI (s)
(28:BC) [10:47:26:862]: SECUREREPAIR: SecureRepair Failed. Error
code: 3e5F6C634B8
Error 997 being the Windows error 'Overlapped I/O operation is in progress.'
Post by Matt O'Connell
We've started seeing this a lot recently.
Installed the kb on to Win 7 and Win 8 VMs but it didn't replicate
it.
Post by Neil Sleightholm
Post by Neil Sleightholm
Post by Neil Sleightholm
Post by Matt O'Connell
Our customers with the issue are usually running some sort of
antivirus and we presumed it's some kind of conflict with that
but we've had no success with disabling Anti-virus with msconfig.
However removing the kb update has fixed it for at least one
customer. I'm hoping to find a recipe to replicate it but we're not
there yet.
Post by Neil Sleightholm
Post by Matt O'Connell
I'm hoping MS find a fix an re-issue the update.:-)
Post by Neil Sleightholm
Thanks, seen that one and this one
https://community.logos.com/forums/p/87997/617278.aspx. Both
look similar.
Neil
-----Original Message-----
Sent: 18 August 2014 20:13
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could
not create the default key container
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-
kb
2
91
86 14-causing-overlapped-i-o-operation-progress-errors.html
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/
SE
C
RE
PA
IR-CryptAcquireContext-Could-not-create-the-default-key-contai
ne
r
-t
p7 596414p7596418.html Sent from the wix-users mailing list
archive at Nabble.com.
--------------------------------------------------------------
--
-
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------
--
-
--
--
---------
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-----------------------------------------------------------------
--
-
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-----------------------------------------------------------------
--
-
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------
--
-
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------
--
-
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
--------------------------------------------------------------------
--
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------
--------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
InstallDev
2014-09-01 16:10:22 UTC
Permalink
Sascha,

You are not alone, we have seen the exact same thing you are experiencing
and we couldn't find yet a way around it except by removing the KB2918614
Windows update.

http://forum.installsite.net/index.php?showtopic=21681

Note that we don't see the issue when we install for the first time but only
when we do the upgrade.
We are still hoping to find or hear from Microsoft a solution to avoid such
issue.





--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596627.html
Sent from the wix-users mailing list archive at Nabble.com.
roberthyang
2014-08-28 19:53:08 UTC
Permalink
We just started seeing a possibly-related error recently. We have a burn
bootstrapper in Wix 3.8 and among the bundle MSI's is SQL Server Compact SP2
x64 (SSCERuntime-ENU-x64.msi). When the bootstrapper attempts to repair the
application, the repair of SQL Server Compact SP2 x64 fails with "Error
1316.The specified account already exists."

An excerpt from the log is as follows :

Action start 12:09:35: PublishFeatures.
MSI (s) (D4:54) [12:09:35:006]: Doing action: PublishProduct
Action ended 12:09:35: PublishFeatures. Return value 1.
Action start 12:09:35: PublishProduct.
MSI (s) (D4:54) [12:09:35:008]: Resolving source.
MSI (s) (D4:54) [12:09:35:008]: Resolving source to launched-from source.
MSI (s) (D4:54) [12:09:35:008]: Setting launched-from source as last-used.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourceDir property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SOURCEDIR property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourcedirProduct
property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR ==> C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\
MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR product ==>
{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (D4:54) [12:09:35:008]: Determining source type
MSI (s) (D4:54) [12:09:35:008]: Note: 1: 2203 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\SSCERuntime_x64-enu.msi 3: -2147287038
MSI (s) (D4:54) [12:09:35:008]: Note: 1: 1316 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\SSCERuntime_x64-enu.msi
MSI (s) (D4:54) [12:09:35:008]: SECREPAIR: Error determining package source
type
MSI (s) (D4:54) [12:09:35:008]: SECUREREPAIR: SecureRepair Failed. Error
code: 524F5C634B8
MSI (s) (D4:54) [12:09:38:487]: Product: Microsoft SQL Server Compact 3.5
SP2 x64 ENU -- Error 1316.The specified account already exists.

Repair of SQL Server Compact SP2 x64 works fine from the Control Panel and
from Explorer. I know this used to work, as I tested it earlier this year.
Here is our Wix code to include the MSI :

<MsiPackage
Id="SSCERuntime_x64"
Cache="no"
Compressed="no"
Permanent="yes"
Visible="yes"
Vital="yes"
Name="SQL Server Compact Edition\SSCERuntime-ENU-x64.msi"
SourceFile="$(var.MSSDKBootstrapperPath)Packages\SQL Server Compact
Edition\EN\SSCERuntime-ENU-x64.msi"
DownloadUrl="http://go.microsoft.com/fwlink/?LinkID=166086"/>

I'm guessing it has to do with this :

https://technet.microsoft.com/library/security/MS14-049

I'm hoping there is a workaround. Thanks for any advice !
-Rob




--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596608.html
Sent from the wix-users mailing list archive at Nabble.com.
roberthyang
2014-08-28 21:52:39 UTC
Permalink
I just tried it with KB2918614 removed, and got a different error, "Error
1316.A network error occurred while attempting to read from the file" :

Action start 14:45:54: PublishFeatures.
MSI (s) (7C:8C) [14:45:54:217]: Doing action: PublishProduct
Action ended 14:45:54: PublishFeatures. Return value 1.
Action start 14:45:54: PublishProduct.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source to launched-from source.
MSI (s) (7C:8C) [14:45:54:217]: Setting launched-from source as last-used.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourceDir property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SOURCEDIR property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourcedirProduct
property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR ==> C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\
MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR product ==>
{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (7C:8C) [14:45:54:217]: Determining source type
MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 2203 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\SSCERuntime_x64-enu.msi 3: -2147287038
MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 1316 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\SSCERuntime_x64-enu.msi
MSI (s) (7C:8C) [14:45:58:507]: Product: Microsoft SQL Server Compact 3.5
SP2 x64 ENU -- Error 1316.A network error occurred while attempting to read
from the file C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\SSCERuntime_x64-enu.msi

Error 1316.A network error occurred while attempting to read from the file
C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\SSCERuntime_x64-enu.msi

Any thoughts ?
Post by roberthyang
We just started seeing a possibly-related error recently. We have a burn
bootstrapper in Wix 3.8 and among the bundle MSI's is SQL Server Compact
SP2 x64 (SSCERuntime-ENU-x64.msi). When the bootstrapper attempts to
repair the application, the repair of SQL Server Compact SP2 x64 fails
with "Error 1316.The specified account already exists."
Action start 12:09:35: PublishFeatures.
MSI (s) (D4:54) [12:09:35:006]: Doing action: PublishProduct
Action ended 12:09:35: PublishFeatures. Return value 1.
Action start 12:09:35: PublishProduct.
MSI (s) (D4:54) [12:09:35:008]: Resolving source.
MSI (s) (D4:54) [12:09:35:008]: Resolving source to launched-from source.
MSI (s) (D4:54) [12:09:35:008]: Setting launched-from source as last-used.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourceDir
property. Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SOURCEDIR
property. Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourcedirProduct
property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR ==> C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\
MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR product ==>
{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (D4:54) [12:09:35:008]: Determining source type
MSI (s) (D4:54) [12:09:35:008]: Note: 1: 2203 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\SSCERuntime_x64-enu.msi 3: -2147287038
MSI (s) (D4:54) [12:09:35:008]: Note: 1: 1316 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact
Edition\SSCERuntime_x64-enu.msi
MSI (s) (D4:54) [12:09:35:008]: SECREPAIR: Error determining package
source type
MSI (s) (D4:54) [12:09:35:008]: SECUREREPAIR: SecureRepair Failed. Error
code: 524F5C634B8
MSI (s) (D4:54) [12:09:38:487]: Product: Microsoft SQL Server Compact 3.5
SP2 x64 ENU -- Error 1316.The specified account already exists.
Repair of SQL Server Compact SP2 x64 works fine from the Control Panel and
from Explorer. I know this used to work, as I tested it earlier this
<MsiPackage
Id="SSCERuntime_x64"
Cache="no"
Compressed="no"
Permanent="yes"
Visible="yes"
Vital="yes"
Name="SQL Server Compact Edition\SSCERuntime-ENU-x64.msi"
SourceFile="$(var.MSSDKBootstrapperPath)Packages\SQL Server
Compact Edition\EN\SSCERuntime-ENU-x64.msi"
DownloadUrl="http://go.microsoft.com/fwlink/?LinkID=166086"/>
https://technet.microsoft.com/library/security/MS14-049
I'm hoping there is a workaround. Thanks for any advice !
-Rob
--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596614.html
Sent from the wix-users mailing list archive at Nabble.com.
K***@statcan.gc.ca
2014-08-28 21:58:36 UTC
Permalink
I got that once when some McAfee product or other was trying to install itself at the same time (we run its AV and a few other things on my target machines), and a few months ago - well before this update.

Somehow also when that happens one gets the McAfee product details in the install log created for *my* application.

I thought nothing of it at the time, since we know that WI is effectively not re-entrant. But ...


Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
***@statcan.gc.ca
Telephone | Téléphone 613-854-5589
Facsimile | Télécopieur 613-951-4674
Government of Canada | Gouvernement du Canada


-----Original Message-----
From: roberthyang [mailto:***@agilent.com]
Sent: August-28-14 5:53 PM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I just tried it with KB2918614 removed, and got a different error, "Error 1316.A network error occurred while attempting to read from the file" :

Action start 14:45:54: PublishFeatures.
MSI (s) (7C:8C) [14:45:54:217]: Doing action: PublishProduct Action ended 14:45:54: PublishFeatures. Return value 1.
Action start 14:45:54: PublishProduct.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source to launched-from source.
MSI (s) (7C:8C) [14:45:54:217]: Setting launched-from source as last-used.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourceDir property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SOURCEDIR property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR ==> C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\ MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR product ==> {D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (7C:8C) [14:45:54:217]: Determining source type MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 2203 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038 MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 1316 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi MSI (s) (7C:8C) [14:45:58:507]: Product: Microsoft SQL Server Compact 3.5
SP2 x64 ENU -- Error 1316.A network error occurred while attempting to read from the file C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi

Error 1316.A network error occurred while attempting to read from the file C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi

Any thoughts ?
Post by roberthyang
We just started seeing a possibly-related error recently. We have a
burn bootstrapper in Wix 3.8 and among the bundle MSI's is SQL Server
Compact
SP2 x64 (SSCERuntime-ENU-x64.msi). When the bootstrapper attempts to
repair the application, the repair of SQL Server Compact SP2 x64 fails
with "Error 1316.The specified account already exists."
Action start 12:09:35: PublishFeatures.
MSI (s) (D4:54) [12:09:35:006]: Doing action: PublishProduct Action
ended 12:09:35: PublishFeatures. Return value 1.
Action start 12:09:35: PublishProduct.
MSI (s) (D4:54) [12:09:35:008]: Resolving source.
MSI (s) (D4:54) [12:09:35:008]: Resolving source to launched-from source.
MSI (s) (D4:54) [12:09:35:008]: Setting launched-from source as last-used.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourceDir
property. Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SOURCEDIR
property. Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding
SourcedirProduct property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR ==> C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\ MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR product ==>
{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (D4:54) [12:09:35:008]: Determining source type MSI (s)
(D4:54) [12:09:35:008]: Note: 1: 2203 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038 MSI (s) (D4:54)
[12:09:35:008]: Note: 1: 1316 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\SSCERuntime_x64-enu.msi MSI (s) (D4:54)
[12:09:35:008]: SECREPAIR: Error determining package source type MSI
(s) (D4:54) [12:09:35:008]: SECUREREPAIR: SecureRepair Failed. Error
code: 524F5C634B8
MSI (s) (D4:54) [12:09:38:487]: Product: Microsoft SQL Server Compact 3.5
SP2 x64 ENU -- Error 1316.The specified account already exists.
Repair of SQL Server Compact SP2 x64 works fine from the Control Panel
and from Explorer. I know this used to work, as I tested it earlier
<MsiPackage
Id="SSCERuntime_x64"
Cache="no"
Compressed="no"
Permanent="yes"
Visible="yes"
Vital="yes"
Name="SQL Server Compact Edition\SSCERuntime-ENU-x64.msi"
SourceFile="$(var.MSSDKBootstrapperPath)Packages\SQL Server
Compact Edition\EN\SSCERuntime-ENU-x64.msi"
DownloadUrl="http://go.microsoft.com/fwlink/?LinkID=166086"/>
https://technet.microsoft.com/library/security/MS14-049
I'm hoping there is a workaround. Thanks for any advice !
-Rob
--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596614.html
Sent from the wix-users mailing list archive at Nabble.com.
Yannick Morin-Rivest
2014-09-04 01:04:52 UTC
Permalink
One of my user is getting the same error message after uninstalling the windows update. Did you find any way to make it work Robert ?



-----Original Message-----
From: roberthyang [mailto:***@agilent.com]
Sent: Friday, 29 August 2014 5:53 AM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I just tried it with KB2918614 removed, and got a different error, "Error 1316.A network error occurred while attempting to read from the file" :

Action start 14:45:54: PublishFeatures.
MSI (s) (7C:8C) [14:45:54:217]: Doing action: PublishProduct Action ended 14:45:54: PublishFeatures. Return value 1.
Action start 14:45:54: PublishProduct.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source to launched-from source.
MSI (s) (7C:8C) [14:45:54:217]: Setting launched-from source as last-used.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourceDir property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SOURCEDIR property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR ==> C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\ MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR product ==> {D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (7C:8C) [14:45:54:217]: Determining source type MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 2203 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038 MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 1316 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi MSI (s) (7C:8C) [14:45:58:507]: Product: Microsoft SQL Server Compact 3.5
SP2 x64 ENU -- Error 1316.A network error occurred while attempting to read from the file C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi

Error 1316.A network error occurred while attempting to read from the file C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi

Any thoughts ?
Post by roberthyang
We just started seeing a possibly-related error recently. We have a
burn bootstrapper in Wix 3.8 and among the bundle MSI's is SQL Server
Compact
SP2 x64 (SSCERuntime-ENU-x64.msi). When the bootstrapper attempts to
repair the application, the repair of SQL Server Compact SP2 x64 fails
with "Error 1316.The specified account already exists."
Action start 12:09:35: PublishFeatures.
MSI (s) (D4:54) [12:09:35:006]: Doing action: PublishProduct Action
ended 12:09:35: PublishFeatures. Return value 1.
Action start 12:09:35: PublishProduct.
MSI (s) (D4:54) [12:09:35:008]: Resolving source.
MSI (s) (D4:54) [12:09:35:008]: Resolving source to launched-from source.
MSI (s) (D4:54) [12:09:35:008]: Setting launched-from source as last-used.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourceDir
property. Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SOURCEDIR
property. Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding
SourcedirProduct property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR ==> C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\ MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR product ==>
{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (D4:54) [12:09:35:008]: Determining source type MSI (s)
(D4:54) [12:09:35:008]: Note: 1: 2203 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038 MSI (s) (D4:54)
[12:09:35:008]: Note: 1: 1316 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\SSCERuntime_x64-enu.msi MSI (s) (D4:54)
[12:09:35:008]: SECREPAIR: Error determining package source type MSI
(s) (D4:54) [12:09:35:008]: SECUREREPAIR: SecureRepair Failed. Error
code: 524F5C634B8
MSI (s) (D4:54) [12:09:38:487]: Product: Microsoft SQL Server Compact 3.5
SP2 x64 ENU -- Error 1316.The specified account already exists.
Repair of SQL Server Compact SP2 x64 works fine from the Control Panel
and from Explorer. I know this used to work, as I tested it earlier
<MsiPackage
Id="SSCERuntime_x64"
Cache="no"
Compressed="no"
Permanent="yes"
Visible="yes"
Vital="yes"
Name="SQL Server Compact Edition\SSCERuntime-ENU-x64.msi"
SourceFile="$(var.MSSDKBootstrapperPath)Packages\SQL Server
Compact Edition\EN\SSCERuntime-ENU-x64.msi"
DownloadUrl="http://go.microsoft.com/fwlink/?LinkID=166086"/>
https://technet.microsoft.com/library/security/MS14-049
I'm hoping there is a workaround. Thanks for any advice !
-Rob
--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596614.html
Sent from the wix-users mailing list archive at Nabble.com.
Yannick Morin-Rivest
2014-09-04 01:41:32 UTC
Permalink
I manage to fix my problem, here is what happen:

1- try to do a minor upgrade of the installer
2- didn't work with error : Error 1316.The specified account already exists.
3- Removed KB2918614 update
4- Try to run the installer and got : Error 1316 "A network error occurred while attempting to read from the file"
5- ** Head scratching **
6- tried http://support.microsoft.com/mats/program_install_and_uninstall in desperation
7- The utility fixed my installer and after everything worked find.

Hopefully this can be helpful to someone else.



-----Original Message-----
From: Yannick Morin-Rivest [mailto:***@micromine.com]
Sent: Thursday, 4 September 2014 9:05 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

One of my user is getting the same error message after uninstalling the windows update. Did you find any way to make it work Robert ?



-----Original Message-----
From: roberthyang [mailto:***@agilent.com]
Sent: Friday, 29 August 2014 5:53 AM
To: wix-***@lists.sourceforge.net
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

I just tried it with KB2918614 removed, and got a different error, "Error 1316.A network error occurred while attempting to read from the file" :

Action start 14:45:54: PublishFeatures.
MSI (s) (7C:8C) [14:45:54:217]: Doing action: PublishProduct Action ended 14:45:54: PublishFeatures. Return value 1.
Action start 14:45:54: PublishProduct.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source.
MSI (s) (7C:8C) [14:45:54:217]: Resolving source to launched-from source.
MSI (s) (7C:8C) [14:45:54:217]: Setting launched-from source as last-used.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourceDir property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SOURCEDIR property.
Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (7C:8C) [14:45:54:217]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR ==> C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\ MSI (s) (7C:8C) [14:45:54:217]: SOURCEDIR product ==> {D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (7C:8C) [14:45:54:217]: Determining source type MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 2203 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038 MSI (s) (7C:8C) [14:45:54:217]: Note: 1: 1316 2: C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi MSI (s) (7C:8C) [14:45:58:507]: Product: Microsoft SQL Server Compact 3.5
SP2 x64 ENU -- Error 1316.A network error occurred while attempting to read from the file C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi

Error 1316.A network error occurred while attempting to read from the file C:\ProgramData\Package Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\SSCERuntime_x64-enu.msi

Any thoughts ?
Post by roberthyang
We just started seeing a possibly-related error recently. We have a
burn bootstrapper in Wix 3.8 and among the bundle MSI's is SQL Server
Compact
SP2 x64 (SSCERuntime-ENU-x64.msi). When the bootstrapper attempts to
repair the application, the repair of SQL Server Compact SP2 x64 fails
with "Error 1316.The specified account already exists."
Action start 12:09:35: PublishFeatures.
MSI (s) (D4:54) [12:09:35:006]: Doing action: PublishProduct Action
ended 12:09:35: PublishFeatures. Return value 1.
Action start 12:09:35: PublishProduct.
MSI (s) (D4:54) [12:09:35:008]: Resolving source.
MSI (s) (D4:54) [12:09:35:008]: Resolving source to launched-from source.
MSI (s) (D4:54) [12:09:35:008]: Setting launched-from source as last-used.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SourceDir
property. Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding SOURCEDIR
property. Its value is 'C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server Compact Edition\'.
MSI (s) (D4:54) [12:09:35:008]: PROPERTY CHANGE: Adding
SourcedirProduct property. Its value is '{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}'.
MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR ==> C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\ MSI (s) (D4:54) [12:09:35:008]: SOURCEDIR product ==>
{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}
MSI (s) (D4:54) [12:09:35:008]: Determining source type MSI (s)
(D4:54) [12:09:35:008]: Note: 1: 2203 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\SSCERuntime_x64-enu.msi 3: -2147287038 MSI (s) (D4:54)
[12:09:35:008]: Note: 1: 1316 2: C:\ProgramData\Package
Cache\{D4AD39AD-091E-4D33-BB2B-59F6FCB8ADC3}v3.5.8080.0\SQL Server
Compact Edition\SSCERuntime_x64-enu.msi MSI (s) (D4:54)
[12:09:35:008]: SECREPAIR: Error determining package source type MSI
(s) (D4:54) [12:09:35:008]: SECUREREPAIR: SecureRepair Failed. Error
code: 524F5C634B8
MSI (s) (D4:54) [12:09:38:487]: Product: Microsoft SQL Server Compact 3.5
SP2 x64 ENU -- Error 1316.The specified account already exists.
Repair of SQL Server Compact SP2 x64 works fine from the Control Panel
and from Explorer. I know this used to work, as I tested it earlier
<MsiPackage
Id="SSCERuntime_x64"
Cache="no"
Compressed="no"
Permanent="yes"
Visible="yes"
Vital="yes"
Name="SQL Server Compact Edition\SSCERuntime-ENU-x64.msi"
SourceFile="$(var.MSSDKBootstrapperPath)Packages\SQL Server
Compact Edition\EN\SSCERuntime-ENU-x64.msi"
DownloadUrl="http://go.microsoft.com/fwlink/?LinkID=166086"/>
https://technet.microsoft.com/library/security/MS14-049
I'm hoping there is a workaround. Thanks for any advice !
-Rob
--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596614.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
roberthyang
2014-09-04 20:43:35 UTC
Permalink
I think we have a workaround: before doing the repair, first uninstall SQL
Server CE 3.5 SP2 x64. That way repairing the bundle will simply reinstall
the missing MSI.

I would like to be able to disable repair of that MSI, since it is marked
"visible" and "permanent" ... maybe that will be possible in Wix 4.0.


One of my user is getting the same error message after uninstalling the
windows update. Did you find any way to make it work Robert ?



-----Original Message-----
From: roberthyang [mailto:robert_yang@]
Sent: Friday, 29 August 2014 5:53 AM
To: wix-***@.sourceforge
Subject: Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create
the default key container

I just tried it with KB2918614 removed, and got a different error, "Error
1316.A network error occurred while attempting to read from the file" :
[...]



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596663.html
Sent from the wix-users mailing list archive at Nabble.com.
nick2893
2014-08-29 00:27:29 UTC
Permalink
I got a very similar issue on one of my client's machines; the fix was to
un-install the KB update. We had antivirus disabled. We could not install
anything on that machine until we un-installed the KB update. The error we
got from the installer was something like "error: object not found", and
unfortunately I didn't save the msi LOG. But, it looked very similar to the
OP - I found this thread by searching the net for some excerpt from my msi
LOG.



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7596616.html
Sent from the wix-users mailing list archive at Nabble.com.
bgavin
2014-10-16 21:34:20 UTC
Permalink
Neil,

I have the identical problem on Server 2012.
The offending patch is KB2984005 which installs a companion KB2977174.

My MSI error log is exactly the same as yours.

My workaround is:
Skip installation of KB2984005 and KB2918614.

If removal is required:
Uninstall KB2984005 and KB2918614, and the companion KB2977174



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-tp7596414p7597345.html
Sent from the wix-users mailing list archive at Nabble.com.
Neil Sleightholm
2014-10-17 12:49:29 UTC
Permalink
Installing KB3000988 should fix this now.
Post by bgavin
Neil,
I have the identical problem on Server 2012.
The offending patch is KB2984005 which installs a companion KB2977174.
My MSI error log is exactly the same as yours.
Skip installation of KB2984005 and KB2918614.
Uninstall KB2984005 and KB2918614, and the companion KB2977174
--
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-Cr
yptAcquireContext-Could-not-create-the-default-key-container-tp7596414p759
7345.html
Sent from the wix-users mailing list archive at Nabble.com.
--------------------------------------------------------------------------
----
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
WiX-users mailing list
https://lists.sourceforge.net/lists/listinfo/wix-users
Loading...