KB4036479 will not install
Question
All replies
-
Hi wjkessler,
Is the Hyper V host 2012R2?
I tested in my lab to install KB4036479 on VM server 2012R2(Host 2016), I installed the KB successfully and after restart, I checked again for windows update, the KB4036479 didn't show up again. Everything seems OK after installing the KB:
Welcome to feedback if you have any additional information, I will report this issue to more professional team and involve them to look into it.
Best Regards,
Anne
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
- Edited by Anne HeMicrosoft contingent staff Thursday, September 21, 2017 6:42 AM
-
Hi All!
In my case, this update causes double reboot with rollback on the 2012 r2 Hyper-V node, but was installed successfully on clean test 2012 r2 guest.
I've get direct link for this update, then extracted it. It contains updated (6.3.9600.18792) Guest Integration Services for 2012 r2. It seems, all ok with the guest OS after installation.
I hoped, that it also resolved cosmetic issue with incompatibility of time sync protocols between 2016 Hyper-V host and 2012 r2 guest, but got the same check results.
(Pictures in attach)
- Edited by Nikita Semenov Thursday, September 21, 2017 8:53 AM
-
Thanks, Anne. Yes it is a 2012R2 host, as is the guest.
-
I'm experiencing the same problem on 2012R2 guests and host with not only KB4036479 but also KB4038774 (https://support.microsoft.com/en-us/help/4038774/windows-81-update-kb4038774), both being advertised through WSUS since the morning of 20 SEP 2017.
They both install successfully, ask for a reboot, then they reboot twice, and still show as available in Windows Update despite the history showing them as successfully installed.
Event log shows them requiring reboot, then being changed to "Installed" after the reboot, than back to "Staged" upon the next check for updates.
I've had to decline the updates in WSUS while MS works on fixing these patches.
- Edited by IamGimli Thursday, September 21, 2017 4:54 PM
-
Update for Windows Server 2012 R2 (KB4036479) is offered after it has already been successfully installed. You can install it over and over, and it is still offered.
This occurs on VMs running on both 2012R2 and 2016 Hyper-V clusters.
This causes Cluster Aware Updating to get stuck in an endless loop:
The update history shows the update installed successfully several times:
We are using WSUS, so I am simply declining the update for now. I would like a fix though.
-Tony
-
Just to echo what other people are saying, I've had exactly the same problem. I have several host servers (all running Windows Server 2012 R2) and each virtual server (also Windows Server 2012 R2) prompts for this update. If I install it, it claims to have succeeded, but then it prompts for the same update again after the reboot. If I install other updates at the same time, it prompts for all of them again too; the only exception is the Malicious Software Removal Tool, probably because that doesn't require a reboot.
I installed the other September patches on the guest OS, so that KB4036479 was the only one left. I ran "sfc /scannow" on the host and guest OS, but it didn't find any problems on either of them.
I then tried installing the September patches on the host OS. (This didn't prompt for KB4036479.) They installed successfully, but then I still had the same problem on the guest OS.
Looking in Hyper-V Manager, it said that the integration services needed an update on the guest OS. I did that, but I still had the same problem afterwards.
Looking in the System log, there's an extra event which pops up mid-reboot when I try to install this patch:
Source: User32
Event ID: 1074
Description:
The process C:\Windows\servicing\TrustedInstaller.exe (PEANUT) has initiated the restart of computer PEANUT on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Upgrade (Planned)Reason Code: 0x80020003
Shutdown Type: restart
Comment:(I've replaced my actual server name with "PEANUT".)
That event doesn't appear when I install other patches.
NB It comes after event ID 6009, i.e. this happens during boot-up rather than shutdown. It also causes a few knock-on errors for the Windows Time service, since that's trying to start up while the rest of the system is shutting down.I've had a look at WindowsUpdate.log, but I can't see anything relevant in there. According to the Windows Update history (and the WSUS server), there weren't any errors. However, if I watch the guest OS via Hyper-V Manager, it displays a message just before it gets to the logon screen:
