r/sysadmin • • 11d ago

General Discussion Patch Tuesday Megathread - (November 10, 2026)

Hello r/sysadmin, I'm u/AutoModerator, and welcome to this month's Patch Megathread!

This is the (mostly) safe location to talk about the latest patches, updates, and releases. We put this thread into place to help gather all the information about this month's updates: What is fixed, what broke, what got released and should have been caught in QA, etc. We do this both to keep clutter out of the subreddit, and provide you, the dear reader, a singular resource to read.

For those of you who wish to review prior Megathreads, you can do so here.

While this thread is timed to coincide with Microsoft's Patch Tuesday, feel free to discuss any patches, updates, and releases, regardless of the company or product. NOTE: This thread is usually posted before the release of Microsoft's updates, which are scheduled to come out at 5:00PM UTC.

Remember the rules of safe patching:

  • Deploy to a test/dev environment before prod.

  • Deploy to a pilot/test group before the whole org.

  • Have a plan to roll back if something doesn't work.

  • Test, test, and test!

129 Upvotes

360 comments sorted by

View all comments

12

u/manvscar 10d ago

We applied to a Hyper-V host and now CSV's are broken between our 2-host cluster. The hosts can't agree on who has ownership of anything. Very sus, will keep you updated. Server 2019

8

u/manvscar 10d ago

Update: we removed KB5131085 and the issue remains. However, we did have KB5120238 installed at the same time (just fixed WSUS) and that is NOT uninstalling for us. So this may be a false alarm on the November CU and a residual issue with that previous CU.

Edit: If you do find yourself in this situation, you can simply shut one node down and run everything from one host. That works fine because it's the cluster comm that's broken. We are doing this until we have some sleep and more time to troubleshoot.

9

u/Yilvazir 10d ago

I've read about this issue in the october megathread. It seems to affect iSCSI CSVs in some environments.

https://www.reddit.com/r/sysadmin/s/bZJFWBk6cT

4

u/manvscar 10d ago

This is exceptionally helpful! Somehow I missed this on the October mega thread.

4

u/Yilvazir 9d ago

Reddit has seemingly started to limit the amount of posts that you see in a thread (for some reason). I only found this post, because I always also sort this thread by "New" to find issues that popped up a bit later.

0

u/[deleted] 10d ago

[deleted]

4

u/manvscar 10d ago

Me too! We're uninstalling now so I'll post back if that fixes the issue.

2

u/damoesp IT Manager 10d ago

Following this as this is also my biggest nightmare when it comes to patching our 2 host Hyper-V Cluster

1

u/LoveTechHateTech Sr. Sysadmin 10d ago

Mine too. I held off on the October updates for my two hosts (Server 2025) when I saw the reports on iSCSI/CSV connectivity issues, but can only do that for so long.

3

u/MediumFIRE 10d ago

FWIW - Server 2025 2-node cluster updated with November CU and had no issues.

3

u/Jimmyv81 9d ago

Have updated a 4 node and 6 node 2025 Hyper V cluster utilising Fiber Channel and have not seen any issues.

2

u/schuhmam 10d ago

I wish I would not read this. Last month, I have read those reports regarding CSV as well.

2

u/nachodude 10d ago

ISCSI or FC?

2

u/nachodude 10d ago

Rolling out on a test hyperv2022 cluster with two nodes and FC backed CSVs in a couple of hours. Let's see...

5

u/nachodude 10d ago

FWIW, Successfully installed on all nodes and everything looks healthy.

1

u/manvscar 10d ago

We're on iSCSI