Click here to read this mailing online.

Your email updates, powered by FeedBlitz


Here is a sample subscription for you. Click here to start your FREE subscription


  1. 20 days and counting
  2. 21 days and counting
  3. 2919355 and WSUS
  4. Enterprises (those of us behind WSUS/Intune) have more time
  5. Tuesday! SMBKitchen ASP Chat
  6. More Recent Articles
  8. Prior Mailing Archive

20 days and counting

(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: <>

and here:

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.




21 days and counting

21 days before unmanaged 8.1 systems are locked out of getting security updates.  And I'm still seeing issues with folks trying to get the update installed.

I worked with Robert (the PowerShell genius) to build a PowerShell tool that let's you run some of the commands in the post in the answers forum as well as checking on the free space in the C drive and in the reserved partition.

This however is very disturbing.  I can confirm that after installing KB2919355 and running that dism command you get a failure


Seeing what I can find about it now.


2919355 and WSUS

For those running default SBS 2003 R2/2008 and 2011 with WSUS - it auto approves security updates to servers and workstations.  If you have an 8.1 or R2 deployed in that network, KB2919355 will be automatically approved and probably automatically installed tonight.

Just be aware and watch your patch settings.

2919355 is deemed a critical security update and thus will automatically be installed if you have not changed the settings.


Enterprises (those of us behind WSUS/Intune) have more time

For those of you behind WSUS, Intune or System center the less than 30 days before KB2919355 has to be installed has been extended.

Folks who patch with WSUS/Intune or System center have until August to roll out KB2919355

The issue with WSUS has now been fixed.  You'll see on your manually or WU updates boxes that already have KB2919355 ANOTHER KB2919355 this time a much smaller update that fixes just the issue with the WSUS deployment



Tuesday! SMBKitchen ASP Chat

Tuesday! SMBKitchen ASP Chat | Third Tier:

Join us today at the SMBKitchen chat.  Remember that you can sign up and get a sneak peak of the documents we've released before April 30.

I'll be sending out a revision to the Heartbleed client facing communication to reflect some latest developments.  Hope to see you there this afternoon!


More Recent Articles

Click here to safely unsubscribe from "THE OFFICIAL BLOG OF THE SBS DIVA." Click here to view mailing archives, here to change your preferences, or here to subscribePrivacy