Master Patch list updated as of January 10, 2023 @ AskWoody (2024)

January 17, 2023 at 1:29 pm #2524289

Drcard:)) wrote:

The new Chromium Edge checks for updates regularly on its own and will automatically update. There is no setting to stop these automatic Edge updates

Edge never updates automatically on my Windows 10. I always update manually (I run SUMo app once a week which flags new software updates).

Reply | Quote

January 17, 2023 at 4:30 pm #2524345

Alex5723 wrote:

Edge never updates automatically on my Windows 10. I always update manually

On my Windows 10 Home 22H2 it updated automatically. Edge by default updates when opened, but I never open it. The WebNots article at the following link states:

How to Stop Automatic Microsoft Edge Update?

The Chromium based Edge works exactly like Google Chrome browser which is also based on the Chromium backend code. It will automatically run the update process, download the latest version, and updates your browser version. It all happens in the background, and you will not even notice the version is updated.

Although written for Windows 11, it works for Windows 10 too.

Reply | Quote

January 18, 2023 at 12:14 pm #2524656

Here’s how to prevent Edge from “automatically” updating itself.

Open Task Scheduler and disable the following 2 tasks:

MicrosoftEdgeUpdateTaskMachineCore

MicrosoftEdgeUpdateTaskMachineUA

Note: Windows update will recreate these tasks if you “delete” them but will leave them “as is” (i.e. disabled) if they already exist.

Disable the “Microsoft Edge Update Service (edgeupdate)” by entering SC config edgeupdate start=disabled at an elevated command prompt.

Doing this prevents Edge from “automatically” updating itself but you can still “manually” update it from within Edge itself by selecting:

⋯ > Help and Feedback > About Microsoft Edge.

Reply | Quote

January 19, 2023 at 11:22 pm #2525172

Just to be clear, Fred’s Edge web view is NOT Microsoft Edge and is a result of Microsoft 365 needing some components.

I wouldn’t stop any browser from auto updating.

Reply | Quote

January 19, 2023 at 11:43 pm #2525174

Susan Bradley wrote:

I wouldn’t stop any browser from auto updating

So very true

* _ being 20 in the 70's was fun _ *

Reply | Quote

January 20, 2023 at 10:05 am #2525278

No one replied to Sheldon when he asked about the file mismatch for hidsense.sys mentioned in the Masterpatch list for 10Jan2023. Could someone let use know about this oversight.

KB5022282 on you Master Patch List you have “Possible blue screen of death if hidsense.sys file has mismatch” which appears to be incorrect, since you indicated “the issue with thehidparse.sys file located in c:\windows\System32 folder has been resolved”

Reply | Quote

January 21, 2023 at 3:30 pm #2525635

is there any chance of this new edge update taking up disk space??

today suddenly my ssd disk space lost around 10gb, no app update except edge and discord. and i only use it to play online game which is on different ssd(no extra edge shortcut)

my brother laptop also experiencing the same thing but he also got the extra shortcut from edge update. i dont know where the missing disk space used

Reply | Quote

January 21, 2023 at 5:08 pm #2525644

I’ve been working this weekend on cleaning up some patching and found the following event in the workstations I checked around the time of their latest patch run:

Windows System Log Event ID 30

The event logging service encountered an error (5) while enabling publisher {a70ff94f-570b-4979-ba5c-e59c9feab61b} to channel Microsoft-Windows-WinINet/Operational. This does not affect channel operation, but does affect the ability of the publisher to raise events to the channel. One common reason for this error is that the Provider is using ETW Provider Security and has not granted enable permissions to the Event Log service identity.

On the servers I found the following:

Windows System Event Log ID 30

The event logging service encountered an error (5) while enabling publisher {0BF2FB94-7B60-4B4D-9766-E82F658DF540} to channel Microsoft-Windows-Kernel-ShimEngine/Operational. This does not affect channel operation, but does affect the ability of the publisher to raise events to the channel. One common reason for this error is that the Provider is using ETW Provider Security and has not granted enable permissions to the Event Log service identity.

In the case of the server event, this particular example came after I applied the January 2023 updates during the reboot. It doesn’t repeat on subsequent reboots. The workstation example is from an earlier patch cycle from the October or November update.

I’m not finding anything on the web that indicates this is a problem with this updates and I’ve seen it on enough servers that initially I thought it might be a patch problem. I was wondering if anyone else is seeing this (and also should I be freaked out about it).

Reply | Quote