Master Patch List for 10-10-2023

Topic

New Reply

I’ve updated the Master Patch list for the October updates.  Remember to always review the known issues we are tracking on the Master Patch List page.
[See the full post at: Master Patch List for 10-10-2023]

Susan Bradley Patch Lady/Prudent patcher

4 users thanked author for this post.

abbodi86, deuce120, Alex5723, lmacri

Reply | Quote

Replies

To block this use Download reg file to block Windows Copilot 

‘Disable Windows Copilot’ may be a clearer message.

Group A (but Telemetry disabled Tasks and Registry)
1) Dell Inspiron with Win 11 64 Home permanently in dock due to "sorry spares no longer made".
2) Dell Inspiron with Win 11 64 Home (substantial discount with Pro version available only at full price)

Reply | Quote

Fixed.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I have done the .reg file solution and also the Group Policy solution. Neither work. I am still stucj with Copilot (Preview). I have a Dell Precision 3660 workstation with Windows 22H2 Pro. As usual, Microsoft stinks!

 

Can anything be done about this? Also, I can’t get rid of (uninstall) Edge or widgets and some other Windows junk.

 

Reply | Quote

You can’t remove copilot, only disable it. See the latest newsletter.

You could try Edge Blocker. https://www.sordum.org/9312/edge-blocker-v1-9/

cheers, Paul

Reply | Quote

Win 11 22H2 just installed a week ago up from win10 22H2.
I put on KB5031354 cumulative and KB5031323 .net updates with no probs yet.

I get a message that explorer update 22621.2361.58.4 is available to put on and rt click taskbat, but no idea how to put it on. Using WuMgr.
Tnx.

Reply | Quote

I AM seeing KB5011048 .NET 4.8.1 being pushed to machines.

I got KB5011048 and KB5030180

Windows 10/11 may see multiple reboots this month.

No multiple reboots with WUmgr.

Reply | Quote

Test Group of 50 computers on Windows 10 22H2 – Monthly Channel

4 users reported they were unable to use their search bar, unable to click open the start menu (right click ok), Outlook profile was not loading, Unable to log in to Teams on one.

Rolling back updates, SFC /ScanNow, Dism, System Restore point, all did not work

We had found that there were some applocker files within C:\Windows\System32\AppLocker and we do not use applocker or have any GPs that would have utlized applocker enabled.

Removed the files and Windows returned to normal.

Reply | Quote

The October 2023 security update might fail to install

Status Confirmed

Affected platforms Client Versions Message ID Originating KB Resolved KB Windows 10, version 22H2 WI681180 KB5031356 – Windows 10, version 21H2 WI681181 KB5031356 –

Microsoft has received reports of an issue where Windows updates released October 10, 2023 (the Originating KBs listed above) fail to install. Devices might initially display progress, but then fail to complete installation. Based on our reports, some of the most common errors being encountered is Error 8007000D (ERROR_INVALID_DATA). This error can be found from the Windows Update view under System settings, by selecting Update History. If you are experiencing this issue, please report it via Feeback Hub. For details, see Send feedback to Microsoft with the Feedback Hub app. For additional guidance on quality update install errors see Troubleshoot problems updating Windows. Workaround: We are presently investigating and will provide an update when more information is available.

Susan Bradley Patch Lady/Prudent patcher

4 users thanked author for this post.

Douglas, windbg, curious leo, Lars220

Reply | Quote

Microsoft continues to prove the point that for most of us it’s best not to update until they have had plenty of time to patch their mistakes.

1 user thanked author for this post.

Douglas

Reply | Quote

Microsoft is using KIR to recall KB5031356 update.

https://www.askwoody.com/forums/topic/october-updates-here-comes-copilot/#post-2594085

2 users thanked author for this post.

curious leo, windbg

Reply | Quote

Yes, reported here:

https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22H2#2989msgdesc

Reply | Quote

FYI

Neowin – Microsoft releases Group Policy fix for Windows 10 KB5031356 Patch Tuesday “8007000D” fails :

“Today, Microsoft has again updated its Windows health dashboard website to add an additional way to carry out the KIR that involves Group Policy (GPO) changes. Microsoft has released this especially for enterprised-managed devices such that system admins and IT admins can deploy the known issue rollback easily and conveniently on such managed devices.

The tech giant has explained how to deploy the new group policy and has also provided the necessary download:

For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> . For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.

Group Policy downloads with Group Policy name:
Download for Windows 10, version 22H2 and Windows 10, version 21H2 – Windows 10 20H2, 21H1, 21H2 and 22H2 KB5026879 230627_173533 Known Issue Rollback.msi

You may find additional details on the Microsoft health dashboard website which documents the topic.”

HTH.

Reply | Quote

curious leo wrote:

Microsoft continues to prove the point that for most of us it’s best not to update until they have had plenty of time to patch their mistakes.

Most of us don’t encounter problems with monthly updates.
Some do. I recon that most of those that do are using 3rd party tweaking apps.

Reply | Quote

Did anyone successfully uninstall KB5031354?  I tried, using DISM, but Microsoft gave the wrong commands, and I wasn’t able to understand the right procedures that I found elsewhere.  Yes, I have blocked CoPilot, but I would like to eliminate it completely in case Microsoft brings it back.

I don’t care what anyone says, KB5031354 is a feature update, and InControl missed it.  InControl will be removed from my system.

Mark

 

 

 

Reply | Quote

Mark wrote:

Did anyone successfully uninstall KB5031354?  I tried, using DISM, but Microsoft gave the wrong commands, and I wasn’t able to understand the right procedures that I found elsewhere.  Yes, I have blocked CoPilot, but I would like to eliminate it completely in case Microsoft brings it back.

I don’t care what anyone says, KB5031354 is a feature update, and InControl missed it.  InControl will be removed from my system.

Mark

 

 

 

You mention 354 and copilot – are you feeling they are one and the same. I read 354 before I took it and there didn’t seem to be anything I didn’t want. Or did I blow it?

https://support.microsoft.com/en-us/topic/october-10-2023-kb5031354-os-build-22621-2428-ecc07685-218f-4ba9-b3c8-fe2e35059aec

Nothing in my search or settings for copilot.
No probs with 354 for me.

copilot: I would assume that anything that came out in the past year probably had copilot in mind, even if not de-facto yet.

I would duck back to Mint but a simple thing like ading an extenal monitor caused it cuniptions (sp?) so I came back here. I will watch @SB ‘s advice and others’ here on how to keep it as tame as possible, yet learn about it.

Always learning!

(I had no “fails to install” or “multiple boots” with this month’s 2 that I took (see my post above) very boring. ).

Just checked WuMgr and nothing in the wings for me.

Reply | Quote

Mark wrote:

I don’t care what anyone says, KB5031354 is a feature update, and InControl missed it.  InControl will be removed from my system.

You may not care but you are wrong.
The update to 23H2 will be a feature update.

Reply | Quote

Alex5723:

When is a feature update not a feature update?  When it is not called a feature update.  That is how it sneaked past InControl.

Mark

 

Reply | Quote

Cumulative Update KB5031354 did not “sneak past” InControl.
InControl is not designed to interact with monthly Cumulative Updates.
You are misinformed.

Reply | Quote

My OS:

Edition Windows 11 Pro
Version 22H2
Installed on ‎Fri ‎9/‎29
OS build 22621.2428
Experience Windows Feature Experience Pack 1000.22674.1000.0

From Susan’s Master Patch List:

To use local group policy to block Windows Copilot:

Search for gpedit and click the top result to open the Group Policy Editor.
Open the following path: User Configuration then Administrative Templates then Windows Components then Windows Copilot.
Double-click the “Turn off Windows Copilot” policy.
Select the Enabled option.

In my policy: (no idea when it was placed there): (I put on KB5031354 cumulative and KB5031323 .net updates a few days ago w no probs.)

I have not shut it off. No idea if I “should”. I think I am waiting for instructions/advice on how to control/limit it – which may not happen until 23H2.

Reply | Quote

It’s an on or off at this time.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

a

Reply | Quote

I believe the DWORD should be “TurnOffWindowsCopilot” (observe Caps and no spaces)

Reply | Quote

Mark wrote:

Did anyone successfully uninstall KB5031354?

Probably not. Always best to image your whole SSD or whatever (I have used terabyte for a while now) before doing any updates so if you need to “back things out” you can simply restore that image. Would be far better than any set of instructions to supposedly uninstall something, which invariably leaves trash around, or screws up your system.

My feeling now is that 354 did add some copilot stuff (to policy editor, etc)(Susan told us this would happen!!!!!!), but I cannot be sure and I am FAR too lazy to restore my backup image to find out!

I do not believe the sky is falling. If you wish to be wary, simply delay updating to 23H2. Or shut it off now. I will probably put 23H2 on a test bed fairly quickly and play and learn. Any system can be turned into a test bed if you image before update! 🙂

Info: I just used Agent Ransack and found 6 files with the embedded name copilot, all about 1 or 2KB, and 2 in Policy Definitions and the rest in SXS. So my guess is that it installed a few names and switches and little else. But just a guess. Nite!

1 user thanked author for this post.

Mark

Reply | Quote

I thought about backing out, but that has problems too, so for the moment I am leaving things as is in that regard.  I would like to remove KB5031354 using DISM, but I do not understand how to do this.  The reason that it is difficult is that the update has a SSU attached, which cannot be uninstalled.

Mark

Reply | Quote

Paul T wrote:

You can’t remove copilot, only disable it. See the latest newsletter.

You could try Edge Blocker. https://www.sordum.org/9312/edge-blocker-v1-9/

cheers, Paul

CoPilot has been disabled, and Edge neutralized some time ago.

But I would like to completely remove as much as possible KB5031354.

Mark

 

Reply | Quote

Mark wrote:

But I would like to completely remove as much as possible KB5031354.

Mark

Then simply restore the image you took before update.

Reply | Quote

PKCano wrote:

I believe the DWORD should be “TurnOffWindowsCopilot” (observe Caps and no spaces)

yes, the registry fix which Susan gave us is

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\WindowsCopilot]
“TurnOffWindowsCopilot”=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsCopilot]
“TurnOffWindowsCopilot”=dword:00000001

Reply | Quote

Check your screenshot – it’s not correct.

Reply | Quote

PKCano wrote:

Check your screenshot – it’s not correct.

that screenshot of policy editor simply shows the policy editor label for that option – I did not click on it. I did below…

At the moment, unless Susan advises me otherwise, I was NOT planning on using (either Policy editor or registry fix) to shut it off…

If I click on it I get:

I don’t think Policy Editor is accustomed to showing us ACTUAL registry labels.

Reply | Quote

OK, My mistake. I thought that was a shot of the Registry.
I have applied both the Group Policy and the Registry blocks (Reg entry in HKLM done manually). But I have also removed Edge, which hamstrings Copilot as well.

1 user thanked author for this post.

a

Reply | Quote

Ah! I could be asking for trouble by leaving it on but I have a good image so I think I’m safe.

Reply | Quote

That’s got me thinking more…:

How many of you are disabling it?

Do you need to do both Policy edit AND registry zap?

Thanks.

Reply | Quote

GP only covers the Current User (HKCU in the Reg). The script that adds the block, has an HKLM entry (as well as an HKCU entry), which covers the Local Machine.

1 user thanked author for this post.

a

Reply | Quote

Thanks. Still torn as to which way to go. Want to be able to easily turn it back on and use part if that is decided as being a preferred safe way to go.

Reply | Quote