Replies

I suppose one with 8th, 9th or 10th gen CPU can run Microsoft Health Check

This seems to answer the question

“Microsoft has officially dropped the support for several generations of Intel processors on Windows 11’s latest version, 24H2. This is regarding only OEMs and not users, which means newer OEM machines after Microsoft’s mandate with any of these processors won’t receive a Windows 11 24H2 update, which may make things difficult for OEMs. However, users who already own these chips can still get the latest Windows 11 updates.”

https://wccftech.com/microsoft-drops-support-for-intels-10th-gen-processors-on-windows-11-24h2/

6 users thanked author for this post.

satrow, RetiredGeek, opti1, Cybertooth, PL1, Alex5723

“Changes to the processors listed do not indicate or impact a customer’s existing Windows support and are intended for OEMs to determine processors which may be used in new Windows devices.

<a class=”relative pointer-events-auto a cursor-pointer

underline
” href=”https://learn.microsoft.com/en-us/windows-hardware/design/minimum/windows-processor-requirements&#8221; target=”_blank” rel=”noopener nofollow ugc”>https://learn.microsoft.com/en-us/windows-hardware/design/minimum/windows-processor-requirements

misleading article. this page is for OEMs to determine which processors may be used in new windows devices.”

https://www.reddit.com/r/hardware/comments/1iq909m/microsoft_removes_windows_11_24h2_official/

1 user thanked author for this post.

PL1

My point is the WIN 10 cumulative update is mislabeled in Master Patch Listing

 

1 user thanked author for this post.

Robert

WIN 10 cumulative update, KB5051974 listed as:
“May need to install second time Windows Recovery Environment update”

Sure the request was from Microsoft? Maybe you PC has virus/malware?

none

Microsoft informed some customers:

Event Viewer displays an error for System Guard Runtime Monitor Broker service

Status: Mitigated

Affected platforms:

OS Versions
Message ID
Originating KB
Resolved KB

Windows 10, version 22H2
WI982633
KB5049981

Windows Server 2022
WI982632
KB5049983

The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices which have installed Windows updates released January 14, 2025 (the Originating KBs listed above) or later.

This error can be found under Windows Logs > System as Event 7023, with text similar to ‘The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935‘.

This error is only observable if the Windows Event Viewer is monitored closely. It is otherwise silent and does not appear as a dialog box or notification.

SgrmBroker.exe refers to the System Guard Runtime Monitor Broker Service.
This service was originally created for Microsoft Defender, but it has not been a part of its operation for a very long time.
Although Windows updates released January 14, 2025 conflict with the initialization of this service, no impact to performance or functionality should be observed.
There is no change to the security level of a device resulting from this issue.
This service has already been disabled in other supported versions of Windows, and SgrmBroker.exe presently serves no purpose.

Note: There is no need to manually start this service or configure it in any way (doing so might trigger errors unnecessarily).
Future Windows updates will adjust the components used by this service and SgrmBroker.exe.
For this reason, please do not attempt to manually uninstall or remove this service or its components.

Workaround:

No specific action is required, however, the service can be safely disabled in order to prevent the error from appearing in Event Viewer.
To do so, you can follow these steps:

1) Open a Command Prompt window. This can be accomplished by opening the Start menu and typing ‘cmd’.
The results will include “Command Prompt” as a System application. Select the arrow to the right of “Command Prompt” and select “Run as administrator”.

2) Once the window is open, carefully enter the following text:

sc.exe config sgrmagent start=disabled

3) A message may appear afterwards. Next, enter the following text:

reg add HKLM\System\CurrentControlSet\Services\SgrmBroker /v Start /d 4 /t REG_DWORD

4) Close the Command Prompt window. This will prevent the related error from appearing in the Event Viewer on subsequent device start up.

Note that some of these steps might be restricted by group policy set by your organization.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

 

Will Microsoft blink in the next 10 months?  We shall see.  Pass the popcorn please.

“Apple released its new devices this fall. But if you are like me, most of my Apple devices still work and are still fully supported. Whether you upgrade to iOS 18.1.1 or stay on 17.7.2 is entirely up to you.”

The patch list still says defer “Unless you want hearing aid feature”.

Why do you still says” defer”? Is there some issue you are concerned with?

 

hearing aid function for Apple air pods = no

Susan,

Apple 18.x – any thoughts when you may recommend the upgrade?

about 70% of the windows PCs are WIN10.   Unless it changes a lot in the next 12 moths, Microsoft will have a big problem.

1 user thanked author for this post.

TaskForce141

link to PDF in “Master Patch List” no good

I have win10 Pro 22H2 installed. After August update, still don’t have onedrive installed.

You are fine.