@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 On Thu, Aug 28, 2014 at 2:09 PM, Neil Sleightholm <n...@x2systems.com> wrote: > 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:sascha.ser...@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 > > > > On Thu, Aug 28, 2014 at 1:00 PM, Neil Sleightholm <n...@x2systems.com> > wrote: > > > I have seen that reported but I think it is slightly different. Does > > removing kb2918614 fix it? > > > > -----Original Message----- > > From: Matt O'Connell [mailto:techsupport...@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.' > > > > On 26/08/2014 11:05, Matt O'Connell wrote: > > > 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.:-) > > > > > > On 18/08/2014 22:54, Neil Sleightholm wrote: > > >> 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:phogl...@rimage.com] > > >> Sent: 18 August 2014 20:13 > > >> To: wix-users@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-kb291 > > >> 86 14-causing-overlapped-i-o-operation-progress-errors.html > > >> > > >> > > >> > > >> > > >> > > >> -- > > >> View this message in context: > > >> 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 > > >> WiX-users@lists.sourceforge.net > > >> https://lists.sourceforge.net/lists/listinfo/wix-users > > >> > > >> ------------------------------------------------------------------- > > >> -- > > >> --------- > > >> > > >> _______________________________________________ > > >> WiX-users mailing list > > >> WiX-users@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-users@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-users@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-users@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-users@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-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
