Replies

Rob Kay wrote:

maybe it meant that the last RE update was done by vs 2004?

I believe this to be the case. The latest RE available to me in the latest/last version of Macrium Reflect free is from 2004, a Feature update I skipped entirely. See attached screenshot. I rely on bootable USB media for any Windows RE needs I may have.

1 user thanked author for this post.

Rob Kay

Windows 10 Pro 22H2. BitLocker has never been enabled and I have no plans to change that. I also have Windows RE disabled as I rely on USB rescue media for that courtesy of Macrium Reflect.

That way, I am not only able to access the RE should I encounter issues, but I can also fall back on restoring a full disk image if the issue cannot be rectified with the RE.

Windows 10 Pro 22H2. Made a full image backup (the first of 2024) then installed KB5033372 before January’s updates arrive this coming Tuesday. No issues whatsoever.

In Windows Update the Get the latest updates as soon as they’re available switch was already disabled and greyed out due to pre-existing Group Policy settings.

I also used GP to pre-emptively disable Copilot – this policy wasn’t present prior to installing KB5033372. So, that’s everything taken care of in advance of the upcoming January patches.

1 user thanked author for this post.

Kathy Stevens

+1 for Open-Shell – I’ve used it for almost 4 years and it’s great. I even use a custom Start button to make it look more like Windows 7’s.

The registry key pre-emptively disables Copilot, which will be in the December updates, presumably the CU. Hiding/ignoring it likely means it will still be running in the background whether you require its services or not.

As you’re on Home edition, the registry key is your only way to disable it. Whether you do it now or once Copilot is actually on your system, makes little difference in my opinion. Doing it now or any time before installing the December updates, means once Copilot is installed it will already be disabled. So, pre-emptive like I said.

I’m on Windows 10 22H2 Pro and I’m just going to wait and disable Copilot in Group Policy when it’s installed with the December updates.

3 users thanked author for this post.

R, NaNoNyMouse, Peobody

Why did you hide it? It does contain security fixes as well as non-security ones. Just curious

Yeah, I checked the MS Update Catalog earlier and saw it was still available there – all 1.3GB of it. Kind of surprised at the size to be honest, but yeah I’ll download the .msu from there if it’s not back in the WU queue when I come to install the November updates.

Does anyone know what happened to 2023-11 .NET 6.0.25 Security Update for x64 Client (KB5032883) for Windows 10 22H2? I had it in my Windows Update queue up until around 23rd November, after which time it has since disappeared and has not returned, and nor can be found in wushowhide. Was it pulled like before? I expected it to reappear within a few days, but almost a week now and it’s yet to return.

It’s not installed on my system either; the latest .NET security update I have installed is 6.0.24 which I installed with the October updates.

Hi Kenneth,

in Task Manager, have you tried sorting by CPU usage in the Processes tab? If not, try checking to see if Antimalware Service Executable (linked to the Microsoft Defender Antivirus Service) is the culprit.

I have a similar issue with this, and while it doesn’t impair my system to any serious degree, it does spike my CPU usage for about the first 10 minutes and I’m not sure why. I use Defender as my active AV, whereas I previously used third-party.

1 user thanked author for this post.

Kenneth Stephens

Made a full disk image in Macrium Reflect, then installed this month’s updates. I had the same experiences as seen reported in this thread, insofar as the 2023-06 .NET Framework CU (KB5027538) prompted a restart before the June CU (KB5027215) had finished installing. Then, once both had completed the ‘Cleaning up’ phase took a few minutes to complete – again, as I’ve seen reported in this thread. However, I then signed in as normal and have faced no apparent issues since.

Running sfc /verifyonly did find some integrity violations which were easily rectified with the /scannow switch and a reboot immediately afterwards. In the clear, it would seem.

2 users thanked author for this post.

geekdom, jburk07

I’m still on 21H2, but will be going over to 22H2 after installing the May patches.

While I usually wait for the MS-DEFCON status to reach 3 or 4, yesterday I had just done a full disk image backup and so threw caution to the wind and installed the following updates on Windows 10 Pro 21H2, bringing the build version up to the latest 19044.2846.

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

2023-04 .NET 6.0.16 Security Update for x64 Client (KB5025915)

2023-04 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5025221)

No (apparent) issues whatsoever.

1 user thanked author for this post.

geekdom

Installed MSRT KB890830 v5.110, .NET 6.0.14 update KB5023288, .NET Framework 3.5, 4.85, 4.8.1 KB5022728 & CU KB5022834 – all no problem on 21H2 Windows 10 Pro.

2 users thanked author for this post.

jburk07, MrToad28

I hid it with wushowhide and it’s not re-appeared in the WU queue.

I experienced exactly that just a couple of minutes ago when I was replying to you in the MS-DEFCON 4 thread regarding KB4023057 going from 2022-04 version to 2023-01.

1 user thanked author for this post.

geekdom