Server2012R2 - Issues - July Rollup 2021-07 KB5004298

[timbo343]

We have 2 HyperVisor Hosts running 2012R2 and we are trying to install KB5004298 which is the July Rollup 2021-07.

 

It's sat there in the Windows Updates and we've downloaded the standalone MSU file from Microsoft and still the offline installer does not install completely.

 

Once the installer does seem like it's installed the server restarts but when booting back into windows it says that the Windows Module Installer is shutting down and then restarts. After it restarts again it says windows could not install the update.

 

We have seen people have said that creating the "Macromed" or "macromed\flash" folders in system32 and syswow64 have rsolved the issues but this doesnt work with our servers.

 

We are literally at our witts end with these servers as they have never been happy since day one!

 

Is anyone able to offer and other suggestions on how to get these servers to update?

 

Just thinking whilst typing this out, i'll make sure there is no Group Policy objects applying to the server - i'm sure there isnt!

[Steve21]

You say about your server but it's deffo not a problem on your side, as we have 8 old 2012r2's still running and 7 worked fine, 1 was a complete nightmare

 

In the end, it seemed to be a combination of a few programs for us:

 

a) The folders you mentioned

b) The files "within" those folders, yes we had to repopulate them with the original flash files (Flash.ocx etc)

c) Finally, we found it error'ing deep in the Windows Update logs because of a missing folder in ProgramData -

 

2021-08-02 19:07:17, Error CSI 00000447 (F) STATUS_OBJECT_NAME_NOT_FOUND #5829301# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0, name= ("null")}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0xbdab48dfd8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[77]"\??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools"

 

Seemingly if you don't have the admin tools folder it blows up too. Made that blank folder and it installed the patch fine, then just manually removed it all again after!

 

Yet all the other servers were fine without any of this, so very odd patch logic!

 

Steve

[timbo343]

You say about your server but it's deffo not a problem on your side, as we have 8 old 2012r2's still running and 7 worked fine, 1 was a complete nightmare

 

In the end, it seemed to be a combination of a few programs for us:

 

a) The folders you mentioned

b) The files "within" those folders, yes we had to repopulate them with the original flash files (Flash.ocx etc)

c) Finally, we found it error'ing deep in the Windows Update logs because of a missing folder in ProgramData -

 

 

 

Seemingly if you don't have the admin tools folder it blows up too. Made that blank folder and it installed the patch fine, then just manually removed it all again after!

 

Yet all the other servers were fine without any of this, so very odd patch logic!

 

Steve

 

Thanks. I do have 2x 2012r2 virtual machines which were not a problem.

 

I found the following in C:\Windows\Windowsupdate.log file:

 

2021-08-02 19:15:59:531 2040 222c Report REPORT EVENT: {EC6E97EE-452F-4899-8BBE-FB979D7BF8FF} 2021-08-02 19:15:54:453+0100 1 183 [AGENT_INSTALLING_SUCCEEDED] 101 {D86A94E5-9E25-4146-AE69-FBC0ADBF6AD4} 501 0 wusa Success Content Install Installation Successful: Windows successfully installed the following update: Security Update for Windows (KB5004298)

2021-08-02 19:15:59:531 2040 222c Report WARNING: Failed to get service object: 80248014

2021-08-02 19:15:59:531 2040 222c Report WARNING: Failed to get service object: 80248014

2021-08-02 19:15:59:531 2040 222c Report CWERReporter finished handling 2 events. (00000000)

2021-08-02 19:16:11:656 2040 2154 AU Currently AUX is enabled - so not show any WU Upgrade notifications.

2021-08-02 19:16:11:656 2040 2154 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037

2021-08-02 19:16:11:671 2040 2154 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037

2021-08-02 19:16:14:515 2040 2154 AU ReAttemptDownloadsAsUserIfNecessary, No calls in download progress.

2021-08-02 19:16:14:515 2040 2154 AU Currently AUX is enabled - so not show any WU Upgrade notifications.

2021-08-02 19:16:14:515 2040 2154 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037

2021-08-02 19:16:14:531 2040 2154 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037

2021-08-02 19:16:23:939 2040 1ab0 IdleTmr Incremented idle timer priority operation counter to 1

2021-08-02 19:22:37:943 2040 2234 Handler FATAL: UH: 0x800f0823: EvaluateApplicability failed in CCbs::EvaluateApplicability

2021-08-02 19:22:37:943 2040 2234 Agent WARNING: Failed to evaluate Installed rule, updateId = {{98B3C15B-9979-45B9-8BB1-8276A6AF9314}.201}, hr = 800F0823

2021-08-02 19:22:37:959 2040 2234 Handler FATAL: UH: 0x800f0823: EvaluateApplicability failed in CCbs::EvaluateApplicability

2021-08-02 19:22:37:959 2040 2234 Agent WARNING: Failed to evaluate Installable rule, updateId = {{98B3C15B-9979-45B9-8BB1-8276A6AF9314}.201}, hr = 800F0823

2021-08-02 19:22:37:959 2040 2234 Handler FATAL: UH: 0x800f0823: EvaluateApplicability failed in CCbs::EvaluateApplicability

2021-08-02 19:25:51:315 2040 2234 Agent Update {FF434E78-8B6A-4860-BD0F-4AC472E29063}.101 is pruned out due to potential supersedence

2021-08-02 19:25:51:315 2040 2234 Agent Update {566B95D4-66F6-47BA-8953-02CAEA29022C}.101 is pruned out due to potential supersedence

2021-08-02 19:25:51:315 2040 2234 Agent Update {B932D155-4C7F-4CBC-8527-D5DF17B0A220}.101 is pruned out due to potential supersedence

 

I think it's the FATAL and WARNING messages which could be causing the problem on one of the Server 2012R2 machines - yet to find the issue on the other one

[Steve21]

0x800f0823 is normally a service stack error.

 

Do you have the latest SSU applied? Think it's KB5001403 for 2012R2

 

Steve

[timbo343]

0x800f0823 is normally a service stack error.

 

Do you have the latest SSU applied? Think it's KB5001403 for 2012R2

 

Steve

 

So looks like i've got the update to install on the server that was giving the FATAL and WARNING messages and you were right, the SSU from April 2021 was installed after KB5004298 was installed.

 

 

Now to work on the more troublesome server - will be checking the logs on this one after i've moved all the VMs over.

 

UPDATE: I might have spoken too soon - it appears i have 4, now going on 5 listings in "view installed updates" for KB5004298. Something doesnt sound right for this server.

Edited August 2, 2021 by timbo343

[timbo343]

So, how many times is enough for installing an update on a server?

 

Is 10 times enough? I daren't click Check for updates just in case it appears again!

 

 

UPDATE:

 

It still wants to install the update. I'm not installing it for an 11th time!

 

Edited August 3, 2021 by timbo343

[timbo343]

So, how many times is enough for installing an update on a server?

 

Is 10 times enough? I daren't click Check for updates just in case it appears again!

 

[ATTACH=CONFIG]62753[/ATTACH]

 

UPDATE:

 

It still wants to install the update. I'm not installing it for an 11th time!

 

[ATTACH=CONFIG]62754[/ATTACH]

 

School boy error on the server i was having trouble with - i didnt create the Macromed\Flash folders - i thought i had but that was on the other server.

 

As soon as i created those folders things seem a lot stable now and i think the update has been installed - well, it's not saying t needs the update anyway - for now anyway.

[timbo343]

I give up with this update!

 

I spent the whole day yesterday and just clicked "check for updates" on both servers which have the macromed folders in system32 and syswow64 - both are reporting it needs the update yet again!

 

Just how many times does one need to install an update before thinking enough is enough!

 

Edited August 4, 2021 by timbo343

[pete]

Rebuild them on 2019, assuming you have software assurance? That's my strategy for 2012R2 of late if it becomes troublesome - otherwise I spend more time faffing with 2012R2 than it would take me to rebuild on 2019.

[timbo343]

Rebuild them on 2019, assuming you have software assurance? That's my strategy for 2012R2 of late if it becomes troublesome - otherwise I spend more time faffing with 2012R2 than it would take me to rebuild on 2019.

 

I would do but they were the HyperV Hosts - something i dont really want to touch to be honest as we got a company to build them years ago - honestly i think the installer did a crap job!

[3s-gtech]

Hyper-V is one of the most resilient roles when upgrading - as it doesn’t touch the VMs. You can even move them during the process if necessary.

 

I have seen an issue when going from 2012 R2 to 2016 where the VMs wouldn’t start, but it pays to remember that as long as the virtual disks are intact, you’ll get the VMs back up. Even if you have to re-create the virtual machine configs.