July Windows security updates are out

Topic

New Reply

Here we go again where we sit on the sidelines and watch the carnage…. excuse me review for side effects. In the meantime check out some of the Amaz
[See the full post at: July Windows security updates are out]

Susan Bradley Patch Lady

4 users thanked author for this post.

geekdom, Pim, abbodi86, Alex5723

Reply | Quote

Replies

AKB 2000003 has been updated for Group B Win7 (ESU) and Win8.1 on July 12, 2022.

There is a Security-only Update for those with Win7 ESU subscriptions.
There is July. IE11 CU  for Win7 ESU subscriptions.

July Rollup KB5015861 Download 32-bit or 64-bit for those with Win7 ESU subscriptions.

You must have at least the August 2020 Servicing Stack KB4570673 previously installed to receive these updates).

There is a July 2022 Servicing Stack KB5016057– Download 32-bit or 64-bit for those with Win7 ESU subscriptions.

There is a revised Licensing Preparation Package KB4575903 dated 7/29/2020 for Win7 ESU subscriptions, if you need it. You will need a year-3 ESU license.

There are no .NET Framework updates listed for Win7. See #2459969

3 users thanked author for this post.

Microfix, SueW, abbodi86

Reply | Quote

FYI: Win8.1 has an SSU issued this month kb5016264 along with the usual offerings. – remember to check WU again once SMQR is installed (whenever updating)

Keeping IT Lean, Clean and Mean!

1 user thanked author for this post.

EricW

Reply | Quote

Monthly Rollup KB5015874 (and SO KB5015877) contain ESU licenses and keys support, including Client ESU as well
they might extend Windows 8.1 for ESU eventually, or it’s just generic licenses for completion

1 user thanked author for this post.

7ProSP1

Reply | Quote

Could also be a generic for Server 2012 R2?
I’d presume 2012 R2 only, read template.

Keeping IT Lean, Clean and Mean!

Reply | Quote

Server 2012 R2 will officially get ESU, the licenses are also shared with Server 2012 R1

Windows 7 also got licenses for additional 3 years of ESU, it’s not clear if they will use them or they add them for confusion

5 users thanked author for this post.

Steve, Pim, Microfix, 7ProSP1, PKCano

Reply | Quote

Coincidentaly Office 2019 for Mac got a brace of updates today, I thought Office updates came out on the 1st Tuesday of the Month?  Its a sporadic arrival at best for MacOS last batch was May I think.

Anyway up to now no apparent faults comparing the 2 machines here. (See inset for Version numbers etc)

Reply | Quote

Non security Office comes out on the first Tuesday, security updates for Office come out on the second Tuesday.  Typically Mac releases are often delayed another week so for once they are timely.

Susan Bradley Patch Lady

Reply | Quote

https://www.ghacks.net/2022/07/12/microsoft-windows-security-updates-july-2022-overview/

1 user thanked author for this post.

DrBonzo

Reply | Quote

Win8.1 (as expected) Fullscreen end of support nag incorporated into this months CU. Options available: Remind me at end of support or Remind me later.

Keeping IT Lean, Clean and Mean!

1 user thanked author for this post.

DrBonzo

Reply | Quote

As I understand it – it will come back every 35 days and also will nag on Enterprise versions (can’t personally confirm that last part as I don’t have Enterprise)

Susan Bradley Patch Lady

1 user thanked author for this post.

DrBonzo

Reply | Quote

It can be suppressed similar to Win7 one

reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\EOSNotify /f /v DiscontinueEOS /t REG_DWORD /d 1
reg add HKCU\Software\Microsoft\Windows\CurrentVersion\EOSNotify /f /v DiscontinueEOS /t REG_DWORD /d 1
reg add HKCU\Software\Microsoft\Windows\CurrentVersion\EOSNotify /f /v RemindMeAfterEndOfSupport /t REG_DWORD /d 1

3 users thanked author for this post.

Microfix, 7ProSP1, PKCano

Reply | Quote

Mind if I make registry keys out of this?

Susan Bradley Patch Lady

1 user thanked author for this post.

Fred

Reply | Quote

At your disposal

one would probably also disable these tasks:

schtasks /Change /DISABLE /TN "Microsoft\Windows\Setup\EOSNotify"
schtasks /Change /DISABLE /TN "Microsoft\Windows\Setup\EOSNotify2"

3 users thanked author for this post.

Microfix, 7ProSP1, PKCano

Reply | Quote

nice additions to the post patch telemetry script. Thanks abbodi86

Keeping IT Lean, Clean and Mean!

Reply | Quote

Windows 11 x64 Beta Test (Guinea Pig)

• 2022-07 .NET 6.0.7 Update for x64 Client (KB5016405)
• Windows Malicious Software Removal Tool x64 – v5.103 (KB890830)
• 2022-07 Cumulative Update for Windows 11 for x64-based Systems (KB5015814)

Installed via WUMgr without error.
Rebooted without error.

Carpe Diem {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1778 x64 i5-9400 RAM16GB HDD Firefox114.0b8 MicrosoftDefender

Reply | Quote

FYI, I just went to install the July updates on Windows 11 x64 and was stuck in a reboot loop until the changes were eventually rolled back.  I don’t really have time to investigate further at this point and I have them paused for now, but I figured I’d post here to let you know it seems like there’s an issue.

3 users thanked author for this post.

OldTechGuy, TechTango, geekdom

Reply | Quote

I had the exact same problem on Win 11 updates – –  being stuck in loop of trying to install then rolling back and then repeating 4 more times.  I stopped the updates after that.

1 user thanked author for this post.

geekdom

Reply | Quote

ibell63 wrote:

FYI, I just went to install the July updates on Windows 11 x64 and was stuck in a reboot loop until the changes were eventually rolled back…

Hi ibell63:

Any chance you have Malwarebytes Premium installed on your computer? I noticed there are a few recent topics in the Malwarebytes for Windows forum about issues installing KB5015814 on Win 11 computers, but the general consensus (at least from the Malwarebytes employees) is that something other than Malwarebytes is causing the problem.  See:

• Windows 11 KB5015814 Failed to install 0x8007007e
• Malwarebytes 4.5.10 stopped installing MS Update KB5015814 on 5 Win11 PCs

———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v21H2 build 19044.1766 * Firefox v102.0.1 * Microsoft Defender v4.18.2205.7-1.1.19300.2 * Malwarebytes Premium v4.5.11.202-1.0.1716 * Macrium Reflect Free v8.0.6867

Reply | Quote

Both the Monthly Rollup (KB5015874) and Security-only (KB5015877) state the following:

“Starting with this release, we are displaying a dialog box to remind users about the End of Support (EOS) for Windows 8.1 in January 2023. If you click Remind me later, the dialog box will appear once every 35 days. If you click Remind me after the end of support date, the dialog box will not appear again until after the EOS date. This reminder does not appear on the following:

Managed Pro and Enterprise devices.
Windows Embedded 8.1 Industry Enterprise and Windows Embedded 8.1 Industry Pro devices.”
“Managed” for Pro and Enterprise most likely refer to computers that are part of/joined to a domain and managed by an IT Dept.

It will be interesting to find out if this notification can be permanently disabled via the registry or deleting scheduled tasks as was the case with Windows 7. Or even if possible, subsequent updates may re-enable it? I have not had a chance yet to install any updates on either of my two Windows 8.1 Pro systems to test this out. But hopefully I will have a chance in the next few days and will report back what I find.

Reply | Quote

Yesterday I had no problems updating the B side of my dual boot daily driver.

KB5015814 2022-07 Cumulative Update for Windows 11 for x64-based Systems
KB890830 Windows Malicious Software Removal Tool x64 – v5.103

installed with no hiccups.  The A side was a very different story.  Updates would download and begin installation, then “Restart required” and I clicked the  button.  Updates would not complete, then try to revert, then get into an endless reboot cycle.

I restored my drive image, Restorehealth and Scannow turned up nothing, and I tried again.  Same result.  I restored a previous drive image, Restorehealth and Scannow turned up nothing, and I tried again.  Same result.  So I went back all the way to the Windows 10 image before I had upgraded to Windows 11.  Scannow found and repaired corrupted system files.  I checked for updates and installed

KB5015807 2022-07 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems

No hiccups.  Then I went through the Windows 11 Upgrade again.  That completed successfully, so I ran Restorehealth and Scannow (found nothing), checked for updates and installed

KB5013889 2022-06 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 11 for x64
KB4023057 2022-04 Update for Windows 11 for x64-based Systems
KB890830 Windows Malicious Software Removal Tool x64 – v5.103

No hiccups this time.  Windows Update says I’m up to date.  Both sides are working normally.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do to our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

4 users thanked author for this post.

Coldheart9020, CAS, geekdom, Lars220

Reply | Quote

bbearren wrote:

Then I went through the Windows 11 Upgrade again.

To clarify, the first time I upgraded from Windows 10 to Windows 11 through Windows Update, I was logged in as a local account Standard user.

When I was going through all this on July 13th, I logged off my local account Standard user and back on with a local account that is a member of the Administrators group.

I almost always run as a Standard user, and hardly ever use an Admin account.  To me, that was the underlying cause of the issue I had July 13th.  My Windows 11 upgrade from Windows 10 as a Standard user was somehow incomplete.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do to our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

1 user thanked author for this post.

geekdom

Reply | Quote

Windows 11 Pro – now at 22000.795 after

2022-07 .NET 6.0.7 Update for x64 Client (KB5016405)

2022-07 .NET Core 3.1.27 Update for x64 Client (KB5016404)

2022-07 Cumulative Update for Windows 11 for x64-based Systems (KB5015814)

Windows Malicious Software Removal Tool x64 – v5.103 (KB890830)

All installed without issue.

--Joe

1 user thanked author for this post.

geekdom

Reply | Quote

No issues to report on two Windows 8.1 Pro systems.

After taking a Macrium image of the system, installed the Servicing Stack Update first (KB5016264) downloaded from the Microsoft Catalog. Then via Windows Update installed the Monthly Rollup (KB5015874) and Security and Quality Rollup for .NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 for x64 (KB5016568).

Last step was to disable the End of Support (EOS) notification via instructions here (A big thank you to abbodi86 and Susan!):

https://www.askwoody.com/forums/topic/2000017-registry-keys-and-command-line-info-to-block-the-windows-8-1-end-of-life/

3 users thanked author for this post.

EricW, Microfix, DrBonzo

Reply | Quote

Getting reboot loops on my Azure Virtual Desktop VMs (Win 10 21H2 multi-session + O365 apps installed from gallery) when this CU is installed.

Have to mount the OS disk in a Rescue VM and use “DISM /Image:<path_to_offline_image> /Cleanup-Image /RevertPendingActions” to fix.

How this isn’t already a troubleshooting process in Azure or part of Startup Repair in Windows Recovery is beyond me.

1 user thanked author for this post.

geekdom

Reply | Quote

Over here I got some bad systempages, where the  windows-update page is hidden or gone,  plus failures in parts of .Net updates.

Anoying, grrr . Also need a repair image

 

* _ the metaverse is poisonous _ *

1 user thanked author for this post.

geekdom

Reply | Quote

Office 364 v2206 build 15330.20246
Office 2013 kb5002121 and Office 2016 kb5002112
are apparently exhibiting app and access runtime errors..

more info from Borncity

Keeping IT Lean, Clean and Mean!

1 user thanked author for this post.

geekdom

Reply | Quote

Problems here as well with July updates on both Windows 10 and Windows 11 on three computers so far. On one of them (Windows 10) I could not get into Settings and had to unistall from Control Panel. Have not investigated more, just uninstall the update and postpone updates for 14 days.

1 user thanked author for this post.

geekdom

Reply | Quote

When update reporting, please provide:

• Operating system, version, and build
• 64-bit or 32-bit machine
• Updates attempted (KB is useful)
• Error and error numbers
• Remedies attempted

Carpe Diem {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1778 x64 i5-9400 RAM16GB HDD Firefox114.0b8 MicrosoftDefender

Reply | Quote

Anyone else noticed that with this update it broke automatic maintenance, it will now never complete…

Normally, maintenance completes before power management suspends your PC; if maintenance completes when scheduled, it will not automatically run again until the next scheduled run. If it is interrupted, however, it will restart the next time your PC is idle.

With this update, now no matter how long you leave the system idle, automatic maintenance never completes, it’s always says in progress…

https://i.imgur.com/MVIE9B6.png

I’m on Windows 10 Pro for what’s its worth.

Also I did notice this part in the Event Viewer when trying to find any clues as to why this stall was happening, in tasks, I noticed this;

Maintenance Task “NT TASK\Microsoft\Windows.NET Framework.NET Framework NGEN v4.0.30319 64 Critical” requests computer wakeup during next regular maintenance run.

Might have something to do with what’s blocking things from finishing? Still don’t have a solution though.

Reply | Quote

E wrote:

this update

Which update for which version?

Windows 11 Pro version 22H2 build 22621.1778 + Microsoft 365 + Edge

Reply | Quote

July 12, 2022 – KB5015807

Currently I’m at;
OS Name : Windows 10 Pro (64-bit)
OS Version : 21H2
OS Build : 19044.1826

1 user thanked author for this post.

b

Reply | Quote

One if my Windows 10 Home computers seems to be trapped in a startup loop after the updates. Trying to uninstall didn’t work, and backing up to an old system restore point didn’t work. No time to debug at this time.

Wherever you go ... there you are!

1 user thanked author for this post.

geekdom

Reply | Quote

For severe problems I think the fastest fix if you aren’t comfortable restoring full image backups is the “repair install” aka “in-place upgrade, keep data” aka “over the top reinstall”.  https://www.tomshardware.com/how-to/fix-windows-10-repair-install

Reply | Quote

https://www.askwoody.com/forums/topic/smart-card-authentication-might-cause-print-and-scan-failures/

Mod edit: Deleted “deleted”

Reply | Quote

Windows 10 Pro 21H2

Updated : KB890830, KB5015807.
winver : 19044.1826

All well.

2 users thanked author for this post.

ECWS, geekdom

Reply | Quote

Microsoft Forum July update information:

https://answers.microsoft.com/en-us/windows/forum/all/cumulative-updates-for-windows-10-and-windows-11/dca0ff6c-b5e4-4241-9c91-0936ff8f625d

Carpe Diem {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1778 x64 i5-9400 RAM16GB HDD Firefox114.0b8 MicrosoftDefender

1 user thanked author for this post.

DrBonzo

Reply | Quote

The following July 2022 Patch Tuesday updates were installed successfully on my Win 10 Pro v21H2 laptop by Windows Update. The install phase seemed to get stuck at 21% for a long time but eventually ran to completion and requested a system restart.

• KB5015807: 2022-07 Cumulative Update for Win 10 v21H2 (OS Build 19044.1826)
• KB890830 : Windows Malicious Software Removal Tool x64 – v5.103

To date I haven’t noticed any negative side-effects, and the Windows automated maintenance task mentioned by E in post # 2460595 seems to be running correctly on my machine.

—————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1826 * Firefox v102.0.1 * Microsoft Defender v4.18.2205.7-1.1.19400.3 * Malwarebytes Premium v4.5.11.202-1.0.1716 * Macrium Reflect Free v8.0.6867

1 user thanked author for this post.

geekdom

Reply | Quote

Hello, on a Asus FlipBook TP412 Win10 21H2 unit a user proceeded to install KB5015807 Monday and it killed the wireless network (realize this is what I signed up for, but what fun talking over the phone with a non-technical and mainly Apple user on initial troubleshooting and uninstalling the KB on company assigned system with no local admin access to the user).

After uninstalling KB5015807 / rebooting wireless came back with no issues.

Have my IT colleague issuing a support call to Asus, along with checking Reddit and seeing what comes of it.

Quickly scan the above and didn’t see a similar issue, though if I missed it, my apologies.

Take care,

IT Manager Geek

1 user thanked author for this post.

geekdom

Reply | Quote

I would like to do an in-place repair install for Windows 10 21H1.

The MS download seems to be only available for 21H2!

As Susan Bradley advises us home users not to go for 21H2 yet, what can I do?

Reply | Quote

Au contraire; Susan has recommended 21H2 for the last eight months:

Follow the prompts to install Windows 10 21H2. I’m comfortable with that version at this time and recommend it.

Windows 11 Pro version 22H2 build 22621.1778 + Microsoft 365 + Edge

Reply | Quote

Sorry, I made a mistake!  I have 21H2!

Thanks for that.

1 user thanked author for this post.

b

Reply | Quote