Windows 10: Error 7023 Service Control Manager....System Guard Runtime Monitor Broker.exe terminated

Hello all. I am on Win10 Home Version 22H2 OS Build 19045.5371 on a HP Omen Desktop and a HP Envy Laptop. I noticed today upon checking my Event Viewer after installing patch Tuesday updates Cumulative Update for Windows 10 Version 22H2 for x64-based Systems KB5049981 and KB5050188 and also KB890830 I started seeing the below Error 7023 Service Control Manager....SgrmBroker.exe System Guard Runtime Monitor Broker] after restarting my computer. The error is %%3489660935

:)

 

system guard runtime monitor broker using a lot of memory

Recently I have noticed that system guard runtime monitor broker has been using a lot of memory. Restarting my computer temporally fixes a problem but after a few hours it's back to using a lot of memory. I know it should use about 1.2 mb of memory where
mine is using over a 100 mb. Is there a way to fix this?

Thanks in advance

 

runtime broker ex

Controlled folder access blocks runtime broker ex from making changes to the folder userprofile\pictures. This happens about every 15 minutes 24/7. Should I allow access? Could this be some type of virus?

 

System Guard Runtime Monitor Using Absurd Amounts of RAM

System Guard Runtime Monitor Is using absolutely insane amounts of ram.

I have 16 Gigabytes of RAM along with 25 Gigabytes of vRAM, this single program manages to sometime use 20% of that. I can't click end task on it, it says "access denied", if I restart it stays at a few MB for about 5 minutes then shoots back up to hundreds
of MB or even a few thousand. I can't even change its priority in the details menu of the task manager because I again get an "access denied" message.

I have seen this problem in many other forum posts, all of which have incorrect answers that "fix" the wrong problem or don't work at all. Often people have been saying to close the Runtime Broker even though this is a different program and I have not had
any problems with it. They also say to close it, which again, doesn't work, as you can close Runtime Broker but not System Guard Runtime Monitor. Even an answer saying to close the task and restart the person's computer when in their question they stated that
they couldn't close the task and restarting didn't fix it.

Microsoft, I (and probably many others) would like an actual method of fixing this from an actual person for this problem.