Error installing Windows 8.1 Update for x64-based Systems (KB2919355) - error 80070005

Posted on Saturday, April 26, 2014 by Nicki de Wet

My computer is not able to install this latest update from Microsoft. It has already been upgraded to 8.1 without any issues.

I ran ProcessMonitor and found this:

Date & Time: 2014-04-26 05:30:50 PM
Event Class: File System
Operation: SetLinkInformationFile
Path: C:\Windows\WinSxS\amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_6.3.9600.16384_en-gb_680d99c9c1bb411e\bootmgr.efi.mui
TID: 3056
Duration: 0.0000421
ReplaceIfExists: True
FileName: \SystemRoot\WinSxS\amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_6.3.9600.17031_en-gb_68408c0dc1958b90\bootmgr.efi.mui

The process details:
Description: Windows Modules Installer Worker
Company: Microsoft Corporation
Name: TiWorker.exe
Version: 6.3.9600.17031 (winblue_gdr.140221-1952)
Path: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17031_none_fa50b3979b1bcb4a\TiWorker.exe
Command Line: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17031_none_fa50b3979b1bcb4a\TiWorker.exe -Embedding
PID: 3316
Parent PID: 672
Session ID: 0
Auth ID: 00000000:000003e7
Architecture: 64-bit
Virtualized: False
Integrity: System
Started: 2014-04-26 05:21:13 PM
Ended: (Running)

 Having a look at the permissions on the bootmgr.efi.mui files in both referenced locations shows that SYSTEM can only read and execute these files, which is most likely why the update fails.

My machine originally had a local account, and when I installed the 8.1 upgrade it changed my local account to a live account against my wishes. This should not have anything to do with it, as Windows Update does not run as me, right?

Is it safe to change the permissions so that SYSTEM has write access as well?

EDIT: After all this, the solution found here is quite simple: just reboot and only open Windows Update and install the update. It seems some files might have been held by other processes.

SSL connection issues when using client certificate authentication

Posted on Friday, April 4, 2014 by Nicki de Wet

The SSL subsystem in Windows has a limitation as to the maximum size of the Trusted Issuers list the server sends to the client during the client certificate authentication process. This causes the list to be truncated, and if the issuer of your client certificate is not listed, causes the authentication to fail with the following message

HTTP/1.1 403 Forbidden
Content-Length: 0
Server: Microsoft-HTTPAPI/2.0
Date: Fri, 04 Apr 2014 10:00:13 GMT
This will be accompanied by an entry with Event ID 36885 in the Windows System Eventlog
When asking for client authentication, this server sends a list of trusted certificate authorities to the client. The client uses this list to choose a client certificate that is trusted by the server. Currently, this server trusts so many certificate authorities that the list has grown too long. This list has thus been truncated. The administrator of this machine should review the certificate authorities trusted for client authentication and remove those that do not really need to be trusted.

There are two approaches to fix this:

  • remove certificates from the list of Trusted Issuers (not always easy or safe, you might delete certificates required by the operating system or other installed software), or
  • create a registry setting that will cause the SSL subsystem to no longer send the list of Trusted Issuers to the client
I personally prefer the 2nd option, as there is less chance of disaster IMHO.

HTTP client, SSL and CRL check

Posted on Tuesday, November 26, 2013 by Nicki de Wet

We recently experienced a severe spike in latency of our one applications that uses HttpWebRequest to connect to a remote service over SSL under high load. After looking at it from a lot of angles, the thought of the certificate verification being blocked seemed like a possible cause, especially since the application is hosted in a locked-down DMZ and only the necessary minimum access granted to access the service URL. Once we granted access to be able to perform the OCSP and/or CRL checks, transactions started flowing immediately. I found this article at the time explaining the whole process. I also think a contributing factor was that only two active HTTP requests are allowed to a destination at once by default according to RFC 2616, my guess is that the CryptoAPI would adhere to this same limit, so all OCSP/CRL requests queued until the active ones timed out.

HTTP concurrent connections

Posted on by Nicki de Wet

Our application exposes a webservice interface to clients, and connects to other providers for performing transactions. Whilst doing loadtesting, I noticed that the client connecting to an upstream provider using HttpWebRequest was not opening more than 2 concurrent connections at any time, causing latency to go through the roof and tps not scaling once the number of simultaneous requests to the webservices goes over 5. Googling a bit yielded this link:

Googling a little bit more I found details about the connectionManagement config section. After adding a section to the application's config file it now scales as expected, with more simultaneous connections increasing the tps as expected.

Creating an eventlog source from the command line

Posted on Wednesday, October 30, 2013 by Nicki de Wet

We've all at some stage had to create an eventlog source for an ASP.Net application, as by default it does not have the privileges to create it on the fly. I found this nifty PowerShell command that does this without having to write a console app.

New-EventLog -LogName Application -Source MyApp

Find out which services are hosted by a running instance of svchost.exe

Posted on Wednesday, October 9, 2013 by Nicki de Wet

For some reason a svchost.exe process on one of our servers started using 23% of CPU. The process name just said svchost.exe, so what exactly was it hosting?

I found this neat command to give you the info:

tasklist /svc /fi "imagename eq svchost.exe"


TargetProcess exceptions in System Log because of MSMQ errors

Posted on Friday, August 16, 2013 by Nicki de Wet

I recently started seeing some errors in the TargetProcess System log. Below is one example.

at Tp.Web.Global.ConfigureBusAndStructureMap() in c:\.jenkins\workspace\BuildPackage\Code\Main\Tp.App_Code\Global.asax.cs:line 209at NServiceBus.Unicast.UnicastBus.NServiceBus.IStartableBus.Start() in c:\Projects\TargetProcess\trunk\Code\Libs\NServiceBus\src\src\unicast\NServiceBus.Unicast\UnicastBus.cs:line 738at NServiceBus.Unicast.UnicastBus.NServiceBus.IStartableBus.Start(Action startupAction) in c:\Projects\TargetProcess\trunk\Code\Libs\NServiceBus\src\src\unicast\NServiceBus.Unicast\UnicastBus.cs:line 791at NServiceBus.Unicast.UnicastBus.InitializeSelf() in c:\Projects\TargetProcess\trunk\Code\Libs\NServiceBus\src\src\unicast\NServiceBus.Unicast\UnicastBus.cs:line 810at Tp.Integration.Messages.ServiceBus.Transport.UiPriority.MsmqUiPriorityTransport.ReceiveMessageLater(TransportMessage m) in c:\.jenkins\workspace\BuildPackage\Code\Main\Tp.Integration.Messages\ServiceBus\Transport\UiPriority\MsmqUiPriorityTransport.cs:line 310at Tp.Integration.Messages.ServiceBus.Transport.UiPriority.MsmqUiPriorityTransport.Send(TransportMessage m, String destination) in c:\.jenkins\workspace\BuildPackage\Code\Main\Tp.Integration.Messages\ServiceBus\Transport\UiPriority\MsmqUiPriorityTransport.cs:line 384at System.Messaging.MessageQueue.Send(Object obj, MessageQueueTransactionType transactionType)at System.Messaging.MessageQueue.SendInternal(Object obj, MessageQueueTransaction internalTransaction, MessageQueueTransactionType transactionType)System.Messaging.MessageQueueException (0x80004005): Insufficient resources to perform operation.GET http://localhost/targetprocess2/2013-08-14 11:14:48,103 [3] ERROR Tp.Web.Global - Failed to configure TP to work with MSMQ because of the reason.

After investigating the cause I found that there were a lot of messages in some TargetProcess queues. To see the queues open Computer Management, expand Services and Applications, expand Message Queueing and click on Private Queues. You'll see a lot of queue names starting with "tp.". In my case queues for bugzilla integration and subversion integration had lots of messages in them and they reached their quota. To purge the queue(s), expand Private Queues, expand the queue you want to purge, right-click on Queue Messages, hover over All Tasks and click Purge. Click Yes if you want to purge the queues.
After purging all the queues with lots of messages I had to recycle the worker process that hosts Target Process, and the error was not logged in the System Log anymore.