20 days and counting

On April 24, 2014, in news, by

(broken record here just making it clear) Unmanaged systems – those not behind WSUS/Intune/System center still have a May 13th deadline of getting 2919355 installed.

Spotted a post in the forum with some interesting debugging:

Windows 8.1 update fails to install – KB2919355 – Microsoft Community:

Success at last. I have been researching and working on this for over a week and have attempted every single “fix” or “repair” proposed here and via MS troubleshooting pages with absolutely no success.

sfc /scannow reported no errors. I used Dism which indicated the store was repairable however RestoreHealth always provided the following message:

The restore operation failed. Either the repair source was not found or the component store cannot be repaired.
Error: 0x800f081f
DISM failed. No operation was performed.

I reviewed the CBS.log file and found a report of missing files (mshtml.tlb, mshtml.dll and F12.dll) which I tracked down via the log file to update KB2909921. I downloaded the KB2909921.msu and used 7-Zip to extract the files contained in the msu to a folder on a USB drive. I then expanded the cabinet archive to the same folder. After locating the above files I restored them to the appropriate containers using the information found here:

http://technet.microsoft.com/en-us/library/ee619779(v=ws.10).aspx <http://technet.microsoft.com/en-us/library/ee619779%28v=ws.10%29.aspx>

and here: http://superuser.com/questions/718805/how-to-repair-corrupt-system-files-from-a-installation-disc

After making the repairs dism /restorehealth continued to indicate the restore operation failed with the same message, *HOWEVER now the CBS.log file reported everything appeared to be ok* other than a reference to a problem with meta data.

Operation: Detect and Repair
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:0
CBS Manifest Corruption:0
CBS Metadata Corruption:0
CSI Manifest Corruption:0
CSI Metadata Corruption:0
*CSI Payload Corruption:**0*
Total Repaired Corruption:0
CBS Manifest Repaired:0
CSI Manifest Repaired:0
CSI Payload Repaired:0
CSI Store Metadata refreshed:True

Previously it was reporting “CSI Payload Corruption: 3” which was apparently related to the missing files referred to above and which previously indicated was not repaired, presumably because the files could not be found.

I had previously been unable to install KB2939087 and KB2919355 and always received error 80073712 after trying every fix mentioned in the forum. I ran Windows Update Diagnostic again and received the same messages I had always received, but because the CBS log showed things were ok, I decided to try to download and install again using Desktop Windows Update.

I first attempted to install KB2939087 which installed, asked for a restart and was successful. I then attempted to install KB2919355 which likewise installed, asked for a restart and was successful.




One Response to 20 days and counting

  1. Hello, Susan,

    did you read the blog post Posted on: Apr 16, 2014 by Brandon LeBlanc?

    He stated: “[….] we’ve decided to extend the timeframe for enterprise customers to deploy these new product updates from 30 to 120 days. In order to receive future updates, all customers managing updates using WSUS, Windows Intune, or System Center Configuration Manager have until August 12th to apply the new updates. For those that decide to defer installation, separate security updates will be published during the 120-day window.” (source URL: http://blogs.windows.com/windows/b/springboard/archive/2014/04/16/windows-8-1-update-and-wsus-availability-and-adjusted-timeline.aspx)

    I think, this is a good decision and will mitigate some of the painpoints, like yours.

    So, we have more than 20 days left for us and our business clients, as long as we´re managing them :=)

    On the other hand, I totally agree with you, that such a rapide release cycle outside the lifecycle policy is a great pain not only in business infrastructures, but also for those who have to develope these releases and for the corp itself, cause we have a lower quality, as in the past (e.g. SharePoint 2013 SP1 and the bunch of revoked Security Bulletins and SystemCenter Updates in the last half year).

    The shorter the product lifecycle, the higher is the probability for human errors, somewhere.