none
Suspected problem with KB4088883 RRS feed

  • Question

  • Had a Server 2012 Standard server display the following this morning;

    Your PC needs to restart.

    Please hold down the power button.

    Error Code: 0x000000C4

    Parameters:

    0x0000000000000091
    0x0000000000000002
    0xFFFFF802DC5898C0
    0x0000000000000000

    We think it's to do with March 22, 2018—KB4088883 (Preview of Monthly Rollup) that installed early this morning.  Dropped to a recovery console and uninstalled the package 'Package_for_RollupFix~31bf3856ad364e35~amd64~~9200.22394.1.2' and all is well again.

    Have since declined KB4088883 in WSUS.  This was on a Dell PowerEdge R320 and we tried upgrading the BIOS to latest beforehand but that didn't help.

    Did come across a hotfix related to the error message, KB2816159, but upon requesting it there is no download for Server 2012 (despite it being listed as affected).

    Just an FYI for anyone else.

    EDIT - Had this occur with another R320 and removing that package also fixed it.  Weirdly, a third R320 installed KB4088883 absolutely fine.



    Sunday, March 25, 2018 12:11 PM

Answers

  • Same problem here on all 2012 VM's. 

    Ran dism.exe /image:C:\ /cleanup-image /revertpendingactions

     
    • Marked as answer by Ross Aveling Wednesday, March 28, 2018 3:20 PM
    Monday, March 26, 2018 8:02 AM

All replies

  • Same here as well.

    Ran the following and rebooted.  Everything was fine after that.

    dism /image:C:\ /remove-package/packname:Package_for_RollupFix~31bf3856ad364e35~amd64~~9200.22394.1.2

    • Proposed as answer by jcombel Monday, March 26, 2018 6:37 PM
    • Unproposed as answer by jcombel Monday, March 26, 2018 6:37 PM
    • Proposed as answer by i.chamin Tuesday, March 27, 2018 11:14 AM
    Sunday, March 25, 2018 12:25 PM
  • Hi,

    I just wanted to second that I had the same thing occur on quite a few VM's. All of them were running Windows 2012 (not R2). I did not realize that this was the issue immediately - performed a Veeam restore, all good. Installed Update - Crash after reboot , just as described.

    Thanks for posting this!

    Jason

    Monday, March 26, 2018 12:33 AM
  • Same problem here on all 2012 VM's. 

    Ran dism.exe /image:C:\ /cleanup-image /revertpendingactions

     
    • Marked as answer by Ross Aveling Wednesday, March 28, 2018 3:20 PM
    Monday, March 26, 2018 8:02 AM
  • Just a heads up, same here. T110 II using 2012 (not R2). Noted the KB was the only update installed, searched, found this thread. Also used DISM to remove the package and am temporarily blacklisting update.

    Haven't had a chance to check other servers (R2 or not) to see if they've installed the update.

    edit:

    Several other servers have restarted without issue. We only had one other 2012 non-R2 (6.2.9200), and it had installed this update, but no restarts yet.

    Not willing to risk it, so I removed it with dism /online and will look for updates on this patch before re-issuing.

    • Edited by jcombel Monday, March 26, 2018 6:39 PM
    Monday, March 26, 2018 5:16 PM
  • Same problem here on all 2012 VM's. 

    Ran dism.exe /image:C:\ /cleanup-image /revertpendingactions

     

    thank you, that fixed our 2012 servers as well.

    Monday, March 26, 2018 7:35 PM
  • Had the same problem. Windows Server 2012. Installed KB4088883 on the 24'th. Rebooted this morning and ended up with "Error Code: 0x000000C4"

    Removed the update using dism and the OS booted ok.

    Monday, March 26, 2018 10:37 PM
  • Hi,
    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Frank

    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Wednesday, March 28, 2018 9:06 AM
    Moderator
  • We have the same issue - except we're not able to pass any keyboard or mouse input to the VM - so cannpt get to command prompt. Please advise ASAP.

    Thanks

    Wednesday, March 28, 2018 2:26 PM
  • Good to know I wasn't the only one.  I liked ggjcc's approach actually, saves mucking around trying to find out the package name.
    Wednesday, March 28, 2018 3:23 PM
  • The discussion provided has been helpful.  Would be nice for Microsoft to offer some decent contribution however like an admittance that there is a problem with the update or indeed why KB2816159 seems to be a possible fix but has no download for Server 2012?
    Wednesday, March 28, 2018 3:25 PM
  • What hypervisor are you using JohnVlahos?
    Wednesday, March 28, 2018 3:27 PM
  • Hyper-V 2012 R2
    Wednesday, March 28, 2018 3:31 PM
  • With 2012 (non-R2) guests?  Maybe boot an affected VM from a 2012 ISO and drop to a recovery command prompt from there? 
    Wednesday, March 28, 2018 3:33 PM
  • With 2012 (non-R2) guests?  Maybe boot an affected VM from a 2012 ISO and drop to a recovery command prompt from there? 
    Very interesting idea - thanks Ross - we'll give that a try. Also waiting for a call back from Microsoft support.
    Wednesday, March 28, 2018 3:39 PM
  • Same issue here on a Dell R720xd with Server 2012. 

    dism.exe /image:C:\ /cleanup-image /revertpendingactions got the server to boot once again and I'm in the process of blocking KB4088883.

    The only other updates that tried to install last night were KB4074806, KB4088877, and KB4074593. But I'm pretty confident KB4088883 is the culprit.



    Wednesday, March 28, 2018 3:49 PM
  • Thanks much - this worked for us - all VMs are back.
    Wednesday, March 28, 2018 4:36 PM
  • Hi,
    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

    Best Regards,

    Frank

    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Frank, is Microsoft able to proactively join this discussion at all and tell us anything about this problem?  Thanks.

    Thursday, March 29, 2018 11:46 AM
  • This happened to a customer server last weekend, and running the same cleanup command from the command line worked for us.  Reapplied the same KB and was able to recreate the issue, as well as the fix.

    The server is a physical server, not VM, running on an IBM ThinkServer T130, with Server 2012 Foundation as the OS, otherwise completely patched up.

    Would be good to hear an acknowledgement of the issue, as well as that it will be addressed in the next monthly release or preview.

    Friday, March 30, 2018 12:51 PM
  • Error Code: 0x000000C4

    Parameters:

    0x0000000000000091
    0x0000000000000002
    0xFFFFF802DC5898C0
    0x0000000000000000

    the same issue, DELL T110, Windows Server 2012 Foundation. :(

    Saturday, March 31, 2018 10:39 PM
  • I had the same problem with this: March 22, 2018—KB4088883 (Preview of Monthly Rollup) for one server.

    Ran dism.exe /image:C:\ /cleanup-image /revertpendingactions

    Thank you for posting this!!!


    • Edited by Adrian CSS Sunday, April 1, 2018 7:08 PM
    Sunday, April 1, 2018 7:05 PM
  • I am unfamiliar with using DISM. Do I run this command on the HYPER-V host or in the "broken" VM while booted to a recovery command prompt or something else? 

    I've got a Windows 2016 Hyperv-V host with 8 VMs. The two VMs running Windows 2012 Server (not R2) are both not booting after MS Updates were installed last night. Searching the error message brings me to many people describing using DISM to fix the virtual servers but I don't know how enough to use the DISM tool as recommended here and elsewhere.

    Thanks,

    Stephen Hammond

    Sunday, April 1, 2018 8:21 PM
  • I figured this out. For anyone else with the same question, the answer is that you boot to a recovery mode command prompt in the broken VM to run the command. I was using a Windows 2012 Server ISO and found that because my broken VMs are Gen 2, the keyboard didn't work. I ended up booting to a Windows 2016 Server ISO, went to recovery command prompt, and then my keyboard worked.

    Using the DISM command listed several times above got my VMs back up and running!

    Sunday, April 1, 2018 9:28 PM
  • Thanks so very much. Your instructions worked perfectly. So glad I ran across this thread.
    Tuesday, April 3, 2018 5:12 PM
  • Hi,

    Thanks for the solution. Any idea it only works for VM or will work on the physical server as well.

    Regards

    Wednesday, April 4, 2018 1:51 AM
  • Nice Catch! Thanks
    Wednesday, April 4, 2018 1:31 PM
  • Frank?  Have you informed the product group that it strongly appears this KB4088883 is the problem and this code will make it into the April cumulative update unless Microsoft takes action. 
    Wednesday, April 4, 2018 1:45 PM
  • Hi Susan.

    I think there are other issues with this Windows Update as well.

    I installed it on my Server 2012 Essentials last week (not VM; H/W based) and over the weekend my server froze and booted 14 times. Started immediately after applying the update.

    As the server is headless, RDP was not much use so I attached a monitor. What I could see was that every 90-120 minutes the screen would completely freeze and then after a couple of minutes blue screen with a DPC_WATCHDOG_VIOLATION ERROR. Nothing in the error logs apart from the expected "the server shut down unexpectedly".

    This usually happened when the server was busy doing something, such as performing a client backup, performing a disk clean-up or even running a DISM (got to 40% then crashed).

    Removing the update stopped the problem (server happy for a week). Reinstalling the update caused continuous reboots again. So I have had to block the update and future updates until I am sure the problem is fixed.

    Regards

    Robert

    Wednesday, April 4, 2018 2:10 PM
  • Same problem here with KB4088883.  Took out our Windows 2012 Standard PDC server running on a Dell PowerEdge R720 (not VM).  Found this article after I already had performed a bare metal restore from a cloud backup.

    btw:  The title of this thread is missing an 8.

    • Edited by rdagger Sunday, April 8, 2018 3:45 PM
    Sunday, April 8, 2018 3:42 PM
  • Thanks !!!
    Monday, April 9, 2018 6:41 AM
  • Hi, Aprils's cumulative update (released on April 10th) looks to solve the problem. We tried to successfully update our system yesterday (ufff :). 3 KBs (this time 'important') have been pending, the unlucky KB408883 from March 22th was disappeared.

    DELL T-110, Win Server 2012.

    Wednesday, April 11, 2018 7:25 PM
  • Yep, KB4093123 has installed fine on all our physical and virtual 2012 machines.

    Since this problem first arose I've scheduled a bit of PowerShell to decline any "Preview of..." updates coming through WSUS.


    Monday, April 16, 2018 4:00 PM