DefCon 2 – August updates include Print spooler fixes

Topic

New Reply

And they are out….. August updates include fixes for the Print spooler bug that wasn’t quite fixed last month so if you disabled the print spooler a
[See the full post at: DefCon 2 – August updates include Print spooler fixes]

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

vp2006, abbodi86

Reply | Quote

Replies

AKB 2000003 has been updated for Group B Win7 (ESU) and Win8.1 on August 10, 2021.

There is a Security-only Update for those with Win7 ESU subscriptions.
There is an August IE11 CU KB5005036 for Win7. Download 32-bit or 64-bit.

August Rollup KB5005088 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 2021 Servicing Stack KB5004378 – 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.

There are .NET updates listed for Win7. See #2382937.

2 users thanked author for this post.

jburk07, abbodi86

Reply | Quote

KB5005033 Cumulative Update for Windows 10 Version 21H1 for x64-based Systems

Malicious Software Removal Tool

No hiccups, printer is OK.  On the other hand, the printer has been OK; I have had no issues with it.

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 with 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.

CAS, jburk07, Geo, Fred

Reply | Quote

bbearren wrote:

KB5005033 Cumulative Update for Windows 10 Version 21H1 for x64-based Systems Malicious Software Removal Tool

My NAS got the push last night.  No hiccups.

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 with our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

Reply | Quote

SSU-19041.1161 (KB5005260) still has the compatibilty issue which prevent offline servcing on Host OS below 19041

Reply | Quote

One of three Win8.1 Pro x64 systems patched up with SMQR kb5005076, no problems with printer, Event viewer logs, performance or system integrity. Reliability of Win8.1 is too good to be forgotten 🙂

No problem can be solved from the same level of consciousness that created IT- AE

5 users thanked author for this post.

Intrepid, JD, KWGuy, abbodi86, DrBonzo

Reply | Quote

Same here, though it took a long time churning after the install before the CPU activity settled down.

1 user thanked author for this post.

DrBonzo

Reply | Quote

I just left the device to update whilst doing other things, came back to it after installation to manually invoke restart and left it again. so can’t verify your observation.
I don’t use windows update on Win8.1, patch downloaded from the catalog and distributed to the three devices. WU is a royal pain at times, so I don’t use it 🙂

No problem can be solved from the same level of consciousness that created IT- AE

1 user thanked author for this post.

DrBonzo

Reply | Quote

I have a PC hooked up to my television for DVR and streaming use and I let it update every month as its only function is to go out to the Internet (if the Internet breaks there are far bigger problems than a Windows update).  It seemed as though yesterday’s update took longer than usual as per PKCano’s observation and I have an NVME drive which is very fast.  Once everything updated, the PC went back onto the Internet to stream from Amazon Prime and all was good.

Our two workstations are set to defer updates until the end of August.

Reply | Quote

Installed on Test machine:

Data files for Get-WinVer.ps1 program updated & tested. 😎

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

2 users thanked author for this post.

CAS, jburk07

Reply | Quote

What about the update making backup software inoperable?  I  would appreciate some comments on this.  Should I be apprehensive?

 

Reply | Quote

I’m not tracking any issues making any specific backup software inoperable.  If you backup BEFORE the update is installed, you can always roll back to that image before the update.

Susan Bradley Patch Lady/Prudent patcher

3 users thanked author for this post.

GoneToPlaid, jburk07, bbearren

Reply | Quote

Thank you for replying. Sorry, my mistake. Although the update was for Windows 8.1 and Windows Server 2012, the warning was for Windows Server 2008 R2.

Microsoft documentation is confusing.

“After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote).”

They suggest that you contact the backup software publisher for an update.

I guess I am safe with Windows 8.1.

Reply | Quote

I think that Windows Updates making third party backup software inoperable would be an extremely rare occurrence. I suppose it “could” happen, yet I don’t recall any instances of this actually occurring. Look at it this way: Windows updates which could brick third party backup software would also likely brick the Windows backup software via bricking all VSS services. Such a snafu by Microsoft would be legendary were it to occur.

Yet like Susan mentioned, if you perform a backup prior to installing Windows Updates, then you should be able to readily restore the backup if the newly installed Windows Updates have issues. It would be better to first try uninstalling the latest updates.

Reply | Quote

No issues after Win 10 21H1 update for August 2021 .

1 Desktop Win 11
1 Laptop Win 10
Both tweaked to look, behave and feel like Windows 95
(except for the marine blue desktop, rgb(0, 3, 98)

2 users thanked author for this post.

CAS, jburk07

Reply | Quote

Hope the printer issue really is fixed. It broke Follow You printing for us with 20H2, so we’ve had to hold off on patching for a couple of months (doing all the other mitigations manually).

No matter where you go, there you are.

Reply | Quote

Nope.  Read the Bleeping Computer article.  There’s an update stating it still hasn’t fully resolved the issue.

Reply | Quote

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-36958

Nope, not fixed.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

A note if you use “Point and Print” (and “Package Point and Print”) to add printers (as non-admin users): This month’s updates change to require admin permissions if adding a printer when the driver doesn’t already exist in the computer’s driver store, even if the driver is “package-aware”. KB5005652 has details, though it was not clear to me if this affected packaged point and print until I tested it on an updated computer. The previous updates regarding printnightmare only affected non-package-aware drivers. Print queues using Type 4 drivers (“Enhanced Point and Print”) do not seem to be affected by this change (since they use an “Enhanced Point and Print” driver built-in to Windows or download the driver from Windows Update).

If you’re a home user, you probably get print drivers from Windows update or from manually installing them, not point and print (so this should not affect you). Point and print is used when connecting to printer shares on Windows print servers.

If you have a print server and this change affects you, try to find (and test) type 4 drivers for your print queues or pre-install the type 3 drivers on the computers before they connect to the printer share (I believe pnputil could be used for this).

Reply | Quote

may be unrelated but I saw this recently from MS yesterday:

Simplified deployment of Windows servicing stack updates: what’s new

“We are thrilled to announce that combined cumulative update deployment capabilities are coming to Windows 10, version 1809, Windows Server 2019, and Windows 10, version 1909.”

Reply | Quote

That’s why they had to separately release SSU-19041.1161 (KB5005260) to compensate those who skipped some problematic CUs in order to be able to install latest CUs
yeah, great strategy

Reply | Quote

“We are thrilled…”

Translate that to “We screwed up and didn’t test so we need to now release a fix…”

Susan Bradley Patch Lady/Prudent patcher

3 users thanked author for this post.

GoneToPlaid, jburk07, wavy

Reply | Quote

So does this mean it is OK to run all of the updates from August’s Patch Tuesday? I am confused, I thought you waited to see what issues or hiccups there were going to be before advising anyone to update. I have Windows 10 Home 64 bit OS, version 20H2. I also have had the printer spooler disabled when I do not need to print anything and I still have it off. I have paused my updates per one of your posts which suggested we do so until 8/24.

Thanks. I am simply trying to find my way along here….this is new to me.

Vicki

Reply | Quote

DefCon-2 means a HOLD on patching.
Have you checked the status for the August updates on the Master Patch List? July patches were approved. August – not yet there.

1 user thanked author for this post.

vp2006

Reply | Quote

I’ll be posting the spreadsheet tonight, still working on it.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

There are a group of folks that like to test updates and report here.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

bbearren

Reply | Quote

I am Win10/Pro, 21H1.

Did I read somewhere in AskWoody that if we haven’t updated .NET CUs beyond February’s .NET KB4601050 since no security patches have been released since then, we should probably go ahead and install the July .NET CU KB5003537, just to be up-to-date on non-security fixes? I can’t find the reference now, but I recall reading something like this.

P.S. There is an August .NET CU KB5004331 out (no security fixes in it), but I presume it’s still under DefCon-2.

Reply | Quote

Yes, .NET 4.x did not get any security-level CUs since February

versions 1809 and later got the same July .NET CU Preview in August, while version 1607 and Windows 8.1/7 got newer ones
all non security

1 user thanked author for this post.

jburk07

Reply | Quote

abbodi86 wrote:

Yes, .NET 4.x did not get any security-level CUs since February

I am Win10/Pro, 21H1.

“Yes” means ‘go ahead and install the July .NET CU KB5003537, even though there are no security fixes’?

or
“Yes” means ‘you are right, no security fixes since February so no need to install July .NET CU KB5003537’?

Reply | Quote

It’s your choice
latest .NET updates provide useful reliability fixes

1 user thanked author for this post.

WCHS

Reply | Quote

Just checking in after trying to update to KB5005033. This time I did it different than in July when KB5004237 failed on my system after chkdsk stuck in “Attempting Repairs” mode for about 20 minutes or so then windows removed the KB5004237 update itself due to a problem.

In today’s attempt, I manually downloaded KB5005033 and the install process went fine. after about 20 minutes or so it asked to restart…finished installing and after entering password to get to the desktop, it took a few minutes to finally get there which I always know when that happens something likely went wrong. So I was at the desktop…it seemed “fine” so I decided before doing ANY maintenance cleanup as I have always done after a CU, I just chose to restart…

It said “Restarting” and the monitor went into sleep mode and never woke back up. Had to hold the start button down for a few seconds for a hard shutdown. Rebooted, same problem, monitor would not come out of sleep mode. Said “No signal”.

Another hard shutdown, let it sit while, rebooted, this time monitor came on normally, and I immediately used the F8 key (I changed the bootmenupolicy and set it to Legacy a few months ago to have the F8 function back), booted into recovery, and restored a drive image back to August 9 that I had made.

Everything is running fine now…I have no idea what happened, but since the July update, this system will not function properly after an update, and I was not going to try and reboot again and watch Windows attempt repairs and then remove another update.

So, for me, perhaps my system cannot handle the latest CU’s…I never had problems with them until the July KB5004237…and now with August KB5005033. This system runs great normally…I am going to shut down Windows Update and keep pausing it as long as I can. No more wasting time trying to get these latest CU’s to work properly. I’ll keep pausing disconnecting from the internet, then trying to  update, then reconnect and it will let me pause again for up to 35 days I think. I really have no other idea what happened starting in the July CU.

Just letting you guys and gals know, this is another skip for me. My last CU is June. System has been stable, I’ll stay here for awhile. I am looking at a new desktop but what a shame to have to upgrade a well running system, though older, because of a CU that does not like it. This gets tiring…maybe it is a hardware issue…but it is running Windows 10 20h2 just fine after the June CU…after that all have caused boot issues or odd operation as today.

 

Reply | Quote

Your problem with chkdsk suggests to me you may have a problem with the health of your HDD/SSD. It is not wise to interrupt chkdsk repairs out of impatience.
I would suggest you use some disk utilities to examine the health of your disk.
You can run chkdsk /f on either HDD or SSD.
You may have a built-in utility for SMART, or you can use third-party utilities like Speccy.
There are other utilities recommended on this site.
If you find problems of this kind, it may be time to replace the drive.

After you solve the drive issues and verify its integrity, I would suggest a “Repair over the top” for the Windows OS, in case some of the files were damaged.

1 user thanked author for this post.

unstablecomic

Reply | Quote

Sorry, I posted my reply without being logged in…and is showing as “anonymous”, just wanted to let you know the reply did come from me. Thanks again…

Reply | Quote

I never interrupted chkdsk. Me mentioning the steps I took back in July with KB5004237, where my usual maintenance after installing a CU is to run chkdsk. That was when after running, it then stated “Attempting Repairs”, the windows removed KB5004237 because it found problems with it. I wrote about this in July.

The latest, August KB5005033 installed fine, as mentioned, then the oddities started after a restart…so when I finally came back to the desktop, I restarted a second time, this is when I knew there were problems, PC would not boot properly. I ran no regular maintenance that I usually do with this update KB5005033 such as chkdsk scheduling, or running “disk clean”. I knew something was amiss before doing any maintenance.

Again, as in July, I restored the system from a backup, system is running great. My HDD is regularly checked, no issues, and I check the SMART outputs on a regular basis. This is an older system, and I never had issues with CU updates until July. Strange behavior and I have read a few others reporting some oddities, perhaps their systems are older also.

Thank you for your help and thoughts, I appreciate them. It is a head scratcher for me…I have been a Computer tech since 1997, some things make little sense lately to me. Nothing stands out, other than restoring the drive takes care of the issues after the last 2 CU’s. Before this, CU’s were flawless for me until July.

Reply | Quote

So you run chkdsk after every installation?  I honestly would do no such cleaning routines for at least a day after.

In particular I would check the video card driver and make sure you are on the latest.

 

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

GoneToPlaid, unstablecomic

Reply | Quote

I usually do a maintenance routine after each update. First, I clean out this folder, “C:\Windows\SoftwareDistribution\Download”.

I then check windows log files for any error reports. I then run Ccleaner to clear the logs, temp files, etc. that accumulate after a CU.

Then I run the Windows tool “Disk Cleanup” (root exe cleanmgr.exe). After that finishes the routines such as Windows update cleanup, etc., I will boot into the Winpe environment, using the hold down shift key and choose restart. Then the usual steps to get to choosing “command prompt”, and the system reboots into winpe. I then run from the command prompt “chkdsk c: /f” That reports “no problems found”. I reboot and if all is running properly, I will defrag and then do a drive image backup. I don’t overdue maintenance, these steps I do usually after a CU to keep a clean system.

Done this for years, all my systems and my wife’s Dell tower, no issues after CU’s. For July the only thing I did different was to use the command prompt to schedule a “check disk” rather than running chkdsk within winpe. That was when it ended up trying to “attempt repairs” ultimately windows uninstalling the July KB5004237.

Last night I did no such maintenance, I knew already something was wrong after installing KB5005033…it installed fine after manual install, asked to restart, finally booted back to login window, and when I logged in, it took quite awhile for it to show desktop…I knew then something went wrong. I restarted, and this is where the monitor went into sleep, “no signal”, turned off system. it finally came back, I didn’t bother to let it boot into windows, I entered winpe and restored an image from August 9, and everything was back up and is running excellent.

I have no idea what is going on, but July out right failed, windows removing the update with “something went wrong”, now August had its own oddities as mentioned. As long as I stay on the June KB5003637 or earlier, everything is great.

I hope that helps explain things and thanks Susan for your input, appreciate it.

Reply | Quote

As I said this isn’t the end of PrintNightmare bug.

Windows Print Spooler Remote Code Execution Vulnerability
CVE-2021-36958

A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

The workaround for this vulnerability is stopping and disabling the Print Spooler service.

BleepingComputer : Microsoft confirms another Windows print spooler zero-day bug

2 users thanked author for this post.

jburk07, Microfix

Reply | Quote

SNAFU then, mitigations still in place here.

Scaremongering, Microsoft has classified this as a remote code execution vulnerability, even though the attack needs to be performed locally on a computer.

So in essence homeusers, beware of email attachments, browser extensions and dodgy site links (as always)

No problem can be solved from the same level of consciousness that created IT- AE

1 user thanked author for this post.

jburk07

Reply | Quote

yup – PrintNightmare problem NOT over

Windows PrintNightmare, next round with CVE-2021-36958

Reply | Quote

One of my test users got  this message: do you trust this printer?

He was able to print to the printserver yesterday w/o issues > after the patch he got this… Anyone else?

I am unable to replicate the issue in my test machines

Reply | Quote

Folks are having issues with the new behavior “Are we the only ones which cant get the group policies (mentioned under Partial mitigations for environments that cannot use the default behavior) to work?

KB5005652—Manage new Point and Print default driver installation behavior (CVE-2021-34481) (microsoft.com)

if we don’t set the RestrictDriverInstallationToAdministrators-value users are prompted for admininistrator priviliges when trying connect to a network printer (which triggers a driver instalation).

if we set RestrictDriverInstallationToAdministrators to 0, and tries to restrict the installation to specific serveres through Point and Click Restrictions GPO users are still able to install printers from other (not specified) servers.”

Bottom line, it’s not just you.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Just a quick follow up to installing KB5005033:

Reinstalled manually for a second try today…from the file downloaded from MS Update Catalog. Went ok…but restart caused no monitor signal again…I just left it running to do its thing and finish, waited until the HDD stopped churning. Then hard shutdown. Turned system back on and off a few times…finally monitor was normal, getting signal, and so far KB5005033 is doing fine. Restarted a few times, no issues so far. Strange behavior in any case. I think you are right Susan, video display adapter is old, probably either slowly dying or a hiccup from Windows every now and then. Card itself checks out fine, Windows just doesn’t like it sometimes…apparently.

Performed the disk maintenance, ran chkdsk from within WinPe, no issues found. Rebooted, running good so far. Going to do an image of the drive while it is running good.

Appreciate all your thoughts and help, I am thinking it is a random video adapter issue not getting signal to the monitor. Not sure though, but for now, doing ok. The driver is up to date for the adapter, well, it is still old, from 2016, so definitely old video card, the latest driver from MS Update Catalog for Windows 10. Nvidia Geforce 9800 GT.

I just updated my old Dell Laptop, Inspiron E1705…flawless as always LOL It is 14 years old and although lags a bit, runs windows 10 x64 20h2 like a champ. Go figure…

Have a good evening all!

Reply | Quote

Win 10 21h1 64 bit.  August CU and .NET updates downloaded/installed via WuMgr OK, stable for 2 days.    MS update package routine now includes a final “Cleaning up” message and activity phase.

Reply | Quote

FYI,

“Resumed update” via Windows Update for 2 Windows 10 Home v21H1 systems (one x64 laptop and another x86 netbook) and successfully installed the following:

– 2021-08 Cumulative Update for Windows 10 Version 21H1 for x64 (x86)-based Systems (KB5005033)
– 2021-08 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H1 for x64 (x86)-based Systems (KB5004331)
– Windows Malicious Software Removal Tool for x64 (x86)-based Systems v5.92 (KB890830)
– 2021-07 Update for Windows 10 Version 21H1 for x64 (x86)-based Systems (KB4023057)

2021-07 KB4023057 installed the Microsoft Update Health Tools version 2.82.0.0 and are listed as both a program under Control Panel > All Control Panel Items > Programs And Features and as an app under Settings > Apps & features.

Paused Windows Update for both systems to furthest date available.

New OS Build : 19043.1165. Both systems are running stable for 2 days now.

Scanning and printing via USB cable to local printer are working (no WIFI network or LAN printing here). Macrium Reflect system backups for before and after patching are working as usual. Belarc Advisor (Security Definition Update : 2021.8.12.3) reports Security Updates for both systems are up-to-date.

Hope this helps.

Reply | Quote

ylm wrote:

Belarc Advisor (Security Definition Update : 2021.8.12.3) reports Security Updates for both systems are up-to-date.

Belarc Advisor report up-to-date for me too and I haven’t installed AUG. updates and Belarc Advisor doesn’t show them as missing.

1 user thanked author for this post.

Fred

Reply | Quote

That’s odd. No idea why though. I got the fresh Belarc Advisor installer downloaded just a couple of hours ago. It has the latest Security Definition Update : 2021.8.12.3 as reported by their website.

The Belarc Advisor Report – Missing Updates Section has the following:

All required security updates have been installed (using Advisor definitions version 2021.8.12.3) according to the 08/10/2021 Microsoft Security Bulletin Summary and bulletins from other vendors.

After the successful 2021-08 patching process, Windows Update did report as up-to-date when running the check-for-updates again.

1 user thanked author for this post.

Fred

Reply | Quote

Freezing, crashing, games performance hit… after KB5005033

Reply | Quote

Hi all,

I patched our qual group (30 Dell PCs) Wednesday morning.

No issues reported until now.

Will update in a few days.

Reply | Quote

I got the newest version of KB4023057 Update for Windows 10 Version 21H1 for x64-based Systems today when I visited Settings > Windows Update, it was pending installation, which I did.

My NAS got it pushed yesterday.

No hiccups.

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 with our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

Reply | Quote

The KB4023057 update has deprecated on the AskWoody list.

Reply | Quote

I never can keep up with when that dang thing comes out.  I’ll update the list.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Susan Bradley wrote:

I never can keep up with when that dang thing comes out. I’ll update the list.

Is KB4023057  there now?  I don’t see it.

Reply | Quote

Susan Bradley wrote:

I never can keep up with when that dang thing comes out. I’ll update the list.

I see it today on the 08/16/2021 Patch List. How does one review the general health of one’s computer?

Reply | Quote

Make sure that you have enough space on the C drive.  Review that updating has been working and not throwing off any errors.  In general, is the computer working “okay” for you?

Reply | Quote

I have 262GB free, surely enough for any CUs or FUs, and updating has not thrown any errors. So, I would say the laptop is working OK. The Reliability Monitor also reports no problems. But I asked because I thought there might be some other places to check.

I have been hiding KB4023057 every time it appears and I keep it that way.

Welcome aboard!!

Reply | Quote

Why are there separate SSU’s for 20H2/21H1?

Weren’t the CU’s for 20H2/21H1 have SSU’s built in?

Reply | Quote

See @abbodi86 ‘s post #2383107.

Reply | Quote

bbearren wrote:

I got the newest version of KB4023057 Update for Windows 10 Version 21H1 for x64-based Systems today when I visited Settings > Windows Update, it was pending installation, which I did.

My NAS got it pushed yesterday.

No hiccups.

Got it today for 21H1. Installed. No issues.

Reply | Quote

I’ve just discovered two different versions of the patches update 8/10/2021 — strangely the pdf is dated  2021-7-31 (see attachment) but the sheet’s actually headed 8/10/2021 — the earliest, ref. 20H2, says ‘install’ for 5004237, the new (current) one doesn’t list 5004237 and defers both listed patches. Luckily, I avoided 5004237, though my wife found herself forced to install it on her laptop.

I’m completely flummoxed. What’s up?

Reply | Quote

The date at the top is the date the sheet was updated.

The July excel sheet list July patches, August sheet lists August ones.

 

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I got Microsoft security update (KB5005419) .NET 5.0 Update to 5.0.9

Will hide for now as HandBrake won’t run with .NET higher than 5.0

Reply | Quote

Correction :

According to this post any .NET 5 including 5.0.9 is fine.
I’ll have to test.

https://forum.handbrake.fr/viewtopic.php?f=11&t=41511

Just a quick note to say that HandBrake 1.4 uses “Microsoft .NET 5 Desktop Runtime”

When downloading, please make sure to download the correct version. See the highlighted download link in the image below!

https://dotnet.microsoft.com/download/dotnet/5.0/runtime
If you download the Console Runtime, the application will fail to launch and prompt you to download the desktop runtime.

Please also note that any 5.0.x version is fine. The current version at the time of posting is 5.0.9 but all future versions of Runtime 5 will be ok.

Thanks

Reply | Quote

W10 Pro 21H1 -64: Installed KB5005033 CU and MSRT okay .. so far.

But, I got the Settings Banner (sign-in, reset default browser, etc.), which I don’t want or care for.  Removal with ViveTool now requires two commands:

.\vivetool.exe addconfig 18299130 1

.\vivetool.exe addconfig 31950543 1

Background: https://geekermag.com/how-to-enable-header-in-windows-10-settings-app/

The relevant registry entries can be found here: https://www.deskmodder.de/blog/2021/08/03/windows-10-header-in-den-einstellungen-laesst-sich-nun-wieder-deaktivieren/

NOTE: don’t do this unless you know what you are doing and do an image backup before!

 

Reply | Quote

When I first try to open the August 10 patch file at Master Patch List, I get this dialog box. When I try to open it a 2nd time, it opens OK. What could be the problem?

This hasn’t happened before when I’ve opened Excel patch files from previous dates.

P.S. The Excel file always opens in Protected View.

Reply | Quote

It will always open in protected view because it’s coming from the web.  I have to update it tonight anyway, try it tomorrow and let me know if it’s still happening?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Yes, I know it’s supposed to be opening in Protected View and it has always opened that way, but not with that dialog box. I was meaning to say that opening in Protected View is not the problem; something else is going on with this file.

I will try opening it tomorrow to see if I get the dialog box again. Thanks.

Reply | Quote

It opened first time for me.

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

Reply | Quote

Master Patch List @ AskWoody

Can you try it now?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Susan Bradley wrote:

Can you try it now?

No problem today, 08/17/2021 Thanks.

Reply | Quote

Installed KB5005033 on 21H1 Pro.
No problems so far.

Reply | Quote

Per the Master Patch List:

“Consumers – Don’t install updates until 8/24/2021.”

Any new August CU installation Feedback?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

KB5005033 was installed with Aug patch, it presented itself again today and I installed it along with the latest Defender update.
It took 30 minutes to complete, did not require restart and it did NOT change the install dates in either View Update History or Installed Updates. It also did NOT change the OS Build from 19043.1165. Windows 10 Pro x64.
PC is a Dell XPS all-in-one. The update has NOT appeared today on my Surface Pro 3 at same OS build.
Not seing any issues yet so this is just FYI.

Reply | Quote