Problems with Hyper-V on Server 2019 (1809) after August 2020 patches

Cannon, Chris 121

We've been having problems after installing August 2020 Patches on our 2019 HyperV hosts. We have multiple hyper-v clusters across Dell VRTX and UCS blades w/ ISCSI backend SANS. Both environments have seen backup times double. Additionally loading a VMs settings in HyperV or Failover cluster manager is taking a very long time. We are not using a 3rd party AV but defender managed by SCCM. Usually when i see issues like this it feels like a storage performance issue but i'm seeing the issue across the board with iscsi as well as direct attached.

Patches applied
KB4566424
KB4565349
KB4569776

our change log indicates no other changes. Our hyperv hosts have no other roles.

I'm going to try roll back the august patching and do a quick A/B test to see if that remediates the issue, but thought i'd post to see if anyone else has seen this issue.

Chris

Daniel Zhou (Shanghai Wicresoft Co,.Ltd.) 256 Reputation points

2020-09-04T07:23:51.51+00:00

Hi，

Yes, you can roll back to the previous version to see if the question still exists. And you can update your result here.

And if anyone has the same issue, welcome to post your question here.

Best Regards,
Daniel
Cannon, Chris 121 Reputation points

2020-09-04T14:58:07.043+00:00

I removed only KB4565349 from a 5 node cluster (150 vms) on UCS blade chasssis and from a smaller 2 node cluster (dell vrtx) with around a dozen VMs. With the larger cluster, i was previously waiting on the window to open for a VM settings from FCM was taking between 20-40 seconds. I'm loading them now between 3 - 5. I do not yet have statistics on backups; I had to pause backups on the larger cluster b/c the job was running past the maintenance window. I'm re-enabling that back up now. With the smaller cluster, i made the change after backups had completed so i don't have a comparison.

With it being a longer holiday weekend i'll likely let things sit as they are over the weekend. If backups seem back to normal, i'm open to do some more testing with a couple other clusters (brand new UCS blades). To my knowledge, we're not seeing any VM performance issues at this point.

Thanks Chris
Daniel Zhou (Shanghai Wicresoft Co,.Ltd.) 256 Reputation points

2020-09-07T01:52:19.217+00:00

Sounds good.

Please let me know if you have any other questions.
Paul Webb 26 Reputation points

2020-11-12T06:30:17.36+00:00

We are also seeing delays on our 2019 Cluster. This manifests in slow "Get-VM" commands on the nodes and slowness opening settings for any of the VMs. It also seems to be causing delayed stats coming into Veeam One - sometimes these can be 15 minutes behind.

I don't like the idea of uninstalling updates to fix the issue - essentially if Microsoft is aware of the issue, they need to fix it! It could also affect anyone that has ISO compliance requiring fixes to be applied within a particular time window.

Does anyone have a link or reference to the Hotfix (Hotfix ID?) which solves the issue? I don't mind opening a case with Microsoft, if I need to go down that route to receive the fix, but it will be quicker if I can point them in the right direction.
Alessio P 66 Reputation points

2020-11-12T06:35:09.667+00:00

I don't think there is a public hotfix yet, only a private hotfix created ad hoc. You'll have to wait for a general release.
Alex
Cannon, Chris 121 Reputation points

2020-11-12T11:55:23.927+00:00

I'm not sure i feel comfortable sharing the hotfix MS provided me as i'm not sure it was anywhere close to a finished product. I should add that I am not comfortable putting this on any of our production 2019 Hyper V servers.; I'm waiting on the general release.
Paul Webb 26 Reputation points

2020-11-13T10:09:23.627+00:00

Hi Chris
I just looked at all the hotfixes and updates. Do you know which one you uninstalled on your test environment to get things back to speed?

Source Description HotFixID InstalledBy InstalledOn

NODE Update KB4580422 24/10/2020 00:00:00
NODE Security Update KB4470788 12/03/2019 00:00:00
NODE Update KB4494174 11/05/2020 00:00:00
NODE Security Update KB4549947 NT AUTHORITY\SYSTEM 11/05/2020 00:00:00
NODE Security Update KB4570332 NT AUTHORITY\SYSTEM 24/10/2020 00:00:00
NODE Security Update KB4577667 NT AUTHORITY\SYSTEM 24/10/2020 00:00:00
NODE Security Update KB4577668 NT AUTHORITY\SYSTEM 24/10/2020 00:00:00

Cheers
Paul Webb 26 Reputation points

2020-11-13T10:27:03.567+00:00

Notice there is a new CU released ....
2020-11 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB4586793) released Nov 11.
Tayschrenn 6 Reputation points

2020-11-23T15:11:51.463+00:00

This is certainly happening on clusters we run. We have not yet rolled back (more complicated than removing a single update) and inherently puts our environment in risk by running on an old rollup if we do.

Very frustrating to not have Microsoft already patched this, so we'll likely burn a support case to get a hotfix.

Can you provide any estimate on resolution or acknowledgment that Microsoft has even identified this?
Cannon, Chris 121 Reputation points

2020-11-23T15:41:20.103+00:00

Its been a month since i've heard from them. I pinged them a moment ago to see if there is a schedule for it to be included in the normal rollup. Believe me... I share your frustration. It took several calls/screen shares with multiple teams to get anyone to really acknowledge the issue. I'm still waiting on it to be rolled into the monthly cumulative. I'll respond if i hear back.

Chris
Cannon, Chris 121 Reputation points

2020-11-23T15:43:59.977+00:00

I just heard back. The update is scheduled for inclusion in January.
Tayschrenn 6 Reputation points

2020-11-23T16:19:23.44+00:00

I appreciate you taking the time to update the thread - hopefully it helps others as well.
Daniel Walker 1 Reputation point

2020-11-24T21:08:22.617+00:00

Any chance you can share the hotfix ID (even if you aren't sharing the hotfix) so we can request it via our cases?
Cannon, Chris 121 Reputation points

2020-11-24T21:25:35.513+00:00

The exe has KB900644.
Brendon Holt 16 Reputation points

2020-11-30T10:51:24.997+00:00

Add us to the mix, this weekend (Thanksgiving) we decided to update the Hardware Platform. Installation of Server 2019 went fine and updates were applied, up until November.

We experienced VERY SLOW Hyper-V Manager to Create or to Manage Settings on the Two New Super Powerful Computers just installed. Testing showed that during Hyper-V Manager could slow Guests down so much login to RDS servers was slow/failed. Was just taking forever to work in settings. Sunday we re-installed 2019 Server on one Machine and it was fine until updates were applied.

We decided to apply updates and deal with this issue because we provide this platform to end users, and the Legal/Financial Liability from Zero Net Logon outweighs the speed of IT Management. NOTE WE CANNOT WORK IN HYPER-V MANAGER IN PRODUCTION HOURS, 11PM to 2AM.

This BUG NEEDS TO BE FIXED and it is a SEVERE LIMITATION. I understand we all work in a complex and dangerous world, but hopefully we get a Fix SOON for this issue.
Jens Klarskov Jensen 1 Reputation point

2021-01-14T11:20:42.117+00:00
On a 6 Nodes Win2019 SCVMM managed FailOverCluster, that we use for Automated Testing , which heavily relies on CheckPoints we have these findings:

Win2019/SCVMM2019 has double duration, when operations are performed on Non SCV owner, whereas Win2016/SCVMM2016 has no measureable difference.

Win2019+KB4586793 doubles Hyper-V Restore on Non owner. SCVMM Restore is four times slowere, mostly affected by prolonged Refresh durations

Win2019+KB4598230 adds 30% to Hyper-V Restore. Doubles SCVMM Restore duration,

Eventually MigrateVm AWAY from SCV Owner ends up lasting 6 – 14 minutes

Measurements when Restoring a complex CheckPoint (Numbers are seconds):

So January Update was even worse!
Jens Klarskov Jensen 1 Reputation point

2021-01-14T11:28:34.283+00:00

BTW: Due to lots of SCVMM Error ID 2606 From the superslow Refresh(*), we have added 'Retry' SCVMM Command' for ERRORID:2606 to our Test Automation Execution , but are still severely down on Test Thrioughput.. We are still on KB4586793!

Unable to acquire a 'Delete' lock on object '52112b4e-3c4c-42b0-a2d9-0e708231d1c5' of type 'VirtualHardDisk' because it is locked by task 'ec55c407-f8dc-4900-9f3a-ce570d4a5d02' 'Refresh host cluster' with a 'Write' lock. (Error ID: 2606)
Jens Klarskov Jensen 1 Reputation point

2021-01-14T14:37:52.13+00:00

For completeness, we changed VmDatStore.dll back to the latest available in WinSxS before August 2020, an got these numbers - so no relief compared to August, but sime relief compared to the Jan 2021 results (We have only tried this on a Staging environment!)

.
Mikkel Lund Knudsen 106 Reputation points

2021-01-15T09:49:37.533+00:00

Hello Jens.
Have you been in talk with Microsoft regarding this issue? :)
DaxtechIT 6 Reputation points

2021-01-17T19:59:04.62+00:00

We opened a ticket with MS and referenced this post and the case# CannonChris-5226 provided. We were provided a private hotfix that is time limited which they stated they have had for a few months. It was time stamped in October 2020. Installing this hotfix requires using bcdedit to put and leave the server in test mode until the patch is removed and replaced with the public version. They also make accept a bunch of warnings that the hotfix is provided as-in and may cause other issues.

Given the impact on our environment and that there were no issues encountered in our test environment we have put this into production and it immediately resolved the IO performance issue. It did not solve the issue with VM settings taking a long time to load or the right click menu in cluster manager disappearing when you try to select something.
Jens Klarskov Jensen 1 Reputation point

2021-01-19T16:30:09.727+00:00

Yes we have a ticket and our 24/7 Team received HF KB900264 to test, but it is too old.

Here are Results with Nodes rolled back from Jan 2021 CU/Nov 2020 CU and with July 2020 CU:

To Compare with:
Jens Klarskov Jensen 1 Reputation point

2021-01-19T16:35:22.277+00:00

BTW, Numbers are in Seconds and average of three on an almost idle Two node Staging/Test Cluster with Lenovo SR650 + SSD SAN with duplicated Fibers.
Cannon, Chris 121 Reputation points

2021-02-26T21:18:42.927+00:00

Quick Followup. I'm hearing this fix is set to be released in March 2021. Why the delay?.. The fix was expanded to include additional issues and got pushed until the adjacent issues got looped in. I'm hopeful again

Chris
Smith, Trevor 1 Reputation point

2021-03-30T17:28:47.787+00:00

Does anyone know if the March 2021 updates resolved the slowness issue?
Smith, Trevor 1 Reputation point

2021-03-30T17:29:03.037+00:00

Does anyone know if the March 2021 updates resolved the slowness issue?
Brendon Holt 16 Reputation points

2021-05-26T02:56:22.203+00:00

I have read this and we decided to make the update to 2021-05 Cumulative Update. Our VEEAM backups are now completed without issue at normal speeds and after a lag the first time going into settings on Hyper-V we can now open all settings quickly. 40 Seconds to 1 Minute First Time, then 1 Second after that.

I believe they have fixed this issue, at least for my environment.

Thanks to all for your persistence on this issue.

33 answers

Cannon, Chris 121 Reputation points

2021-01-14T15:27:00.353+00:00

I've reached back out to the tech that worked my incident. (it was closed btw) I also pinged my sales rep. Not sure when I'll hear back.

If you haven't opened a ticket about this problem, i'd suggest doing that. More most attention to the problem may expedite the solution.

Chris
Please sign in to rate this answer.
DaxtechIT 6 Reputation points

2021-01-14T23:25:51.483+00:00

Chris, would you mind sharing your MS case number? We have been waiting for the patch since you first mentioned the promised January release. Now with this being pushed back I want to open another MS ticket on the issue. Referencing your ticket would help cut through the nonsense that is MS support bring direct attention to this issue.

Cannon, Chris 121 Reputation points

2021-01-15T11:56:02.033+00:00

120091424007097
Sign in to comment
Cannon, Chris 121 Reputation points

2021-01-14T20:33:59.727+00:00

I was told that the release was delayed and is now set for March 2021...FYi
Please sign in to rate this answer.
Josh Hargense 1 Reputation point

2021-01-15T02:04:20.277+00:00

Good grief, March!!! I don't think we can wait that long. Similar to DaxtechIT-4864, if you could provide the MS case number we will raise our own hotfix request.
Sign in to comment
Cannon, Chris 121 Reputation points

2021-01-14T20:34:02.757+00:00

I was told that the release was delayed and is now set for March 2021...FYi
Please sign in to rate this answer.
Menk Wolfgang 1 Reputation point

2021-02-17T11:41:44.01+00:00

Just got confirmation from MS that the hotfix is indeed not included in the 2021.02C update. The "new" scheduled release date is 2021.03C - as Chris told all along... Anyway, it's truely a shame.
Sign in to comment
Stewart Myles 1 Reputation point

2021-01-19T21:08:14.507+00:00

We are experiencing the same issues on a 4 node cluster but have a 6 node DR cluster and that appears to be OK, same software revision and similar hardware. I have received a hotfix KB900246-x64 from Microsoft and this appears to have resolved the issue, I need to deploy the patch to the rest of the nodes but its looking very hopeful.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Joseph W. Smith 1 Reputation point

2021-01-27T21:24:27.013+00:00

I am having the same issue here. Can anyone tell me where I can download the hotfix KB900246-x64 or version 10.1.17763.348 VmDataStore.dll?
Please sign in to rate this answer.
Cole T 1 Reputation point

2021-01-31T01:52:30.553+00:00

I'm also having the same issue on multiple Windows Server 2019 clusters and standalone servers. Same issue regardless of server or storage hardware.

I thought waiting over 2 years to migrate to 2019 for production would have been long enough.

Can't even get through to Microsoft partner support. Voicemail says, "Dear Valued Partner were currently experiencing delays and responding to support requests. Thank you for the patience and understand good bye." It has been like that for 10 hours.

Can someone please provide the hotfix? It would be much appreciated.

Thanks.
Sign in to comment