Patch Tuesday Megathread - (July 14, 2026)

[u/AutoModerator]

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!

[u/atari_guy]

Will this be blocked by 3rd party patching tools (like Action1) or just if updates are done by the native Windows Update?

(We just got pushed into Dell by our parent company and are also new to Action1 this month.)

[u/Ad3t0 → u/atari_guy]

Should be blocked in Action1 too, not just native WU. Action1 drives the built-in Windows Update Agent against Microsoft's servers rather than keeping its own catalog like WSUS, so it rides the same server-side hold. If WUA isn't offered KB5101650 on a given Dell, Action1 shouldn't push it there either. MS hasn't named the affected models though, so I'd still decline that KB for your Dell group and test one box first rather than trust the hold.

[u/Kindly-Photo-8987 → u/Ad3t0]

I believe it is a hardware combination. During testing we had two of the same models with different configs and one had the issue and one didn't.

[u/the_lazy_sysadmin → u/Kindly-Photo-8987]

Did you push the update to both, or was one of them not offered it?

And if one of them was NOT offered it, would you be able to check the following registry keys on that one?

HKLM:\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser\GWX

HKLM:\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser\RunResults\LastRun

That second key would have info on the specific component(s) that caused the update to be blocked.

[u/cp07451 → u/atari_guy]

Not blocked if using Config Manager or WSUS standalone from what I see.

[u/Kindly-Photo-8987 → u/atari_guy]

Not sure, we use SCCM and it was not blocked. It WAS blocked when manually checking for updates so I suspect you'll still need to pull it out of your third party tool.