r/sysadmin • • Oct 13 '26

General Discussion Patch Tuesday Megathread - (October 13, 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!

116 Upvotes

491 comments sorted by

View all comments

6

u/netadmin_404 Oct 15 '26

We deployed to our test Hyper-V cluster and were in a world of pain with cluster shared volumes. Volumes would come up and down, and not come up on certain nodes. We also had crashes of the cluster service. It seems to maybe be related to iSCSI issues.

Cluster passed validation pre-upgrade.

Rolling back the updates stabilized the issue. Anyone have any similar issues?

2

u/rismoney Oct 15 '26

I am seeing iscsi issues with the timing of volumes being mounted happening after mssql service started rather than before. It is an HPE SAN. AI thinks that favorites/ip address and nic are being renumbered or something after CU. Not totally sure whats going on.

3

u/netadmin_404 Oct 15 '26

Gotcha.

We’re seeing this on a Dell Powerstore with all CSVs on specific hosts with the October update. When an affected host would try to take ownership of the CSV, it would fail, hang, and then take down the cluster service. Other nodes would also disconnect that volume as it was not being managed by any node. Prior to this the cluster had been stable for 6+ months.

We checked MPIO, validated connectivity between hosts on the SAN. Still didn’t work right. Had to downgrade the hosts. I know this upgrade addressed a vulnerability in the Windows iSCSI service.

1

u/the_lazy_sysadmin Sr. Sysadmin Oct 16 '26

Were any of the CSV's on the SAN cloned? I've ran into issues before with a cloned volume on a SAN just NOT wanting to reside on the same node as the volume it was cloned from, causing those resources to fail. This would really only apply if you have multiple CSV's setup (one for each VM), which is something that I don't think is often done, but we started doing in a CMMC environment after a data spill forced us to wipe the entirety of the singular CSV we had set up.

1

u/Somali-Pirate-MN5569 28d ago

Any others with iSCSI service problems ?

1

u/That_Difference_3583 27d ago

yup, spent a while yesterday trying to figure out why the iscsi connection would establish but drives weren't showing up. I rolled back the October update today and drives came back.

1

u/Somali-Pirate-MN5569 26d ago edited 26d ago

Has anyone opened up a Case yet with Microsoft ? Hopefully someone has a test Hyper-V Cluster.

1

u/Mayimbe007 Oct 16 '26

After installing this our Fibre Channel drives couldn't start. I had to roll back the Cumulative Update for the iSCSI service to start working normally again. After uninstalling I was able to start the Disks up and bring them online.

1

u/netadmin_404 Oct 16 '26

My iSCSI service also locked up. The UI couldn’t discover disks or add volumes.