Windows 10: secure launch

I have an asus b5 b5404 with intel core ultra 7 155h. I want to enable sytem guard/secure launch. In systeminfo it says it is configured but not runnig. in event viewer i see this two logs: System Guard enabled but not supported. Reason: TXT is disabled by the BIOS in MSR_FEATURE_CONTROL and Failed to update the SBAT value in FW. what can i do?

:)

 

Corporate Security Solution

That made me so facepalm. Some people have absolutely no clue. I hope they don't take you for granted with all this you're doing for them.

SonicWall is a good security product, so Mindweaver's suggestion sounds like a good one and should make for a rather bigger baby step. Let's hope they take it.

 

Windows Security won't launch

Sup people,

For some reason I don't seem to be able to launch Windows Security. The Windows Security icon on the taskbar is constantly showing a warning sign. If I try to launch Windows Security, a new app window would open but it'd just indefinitely show the Windows Security icon. I tried the steps suggested in this post (except for the complete OS reset) and nothing seems to work. For some reason I can't add any screenshots here so I'm hoping what I mean is clear enough.

Running Windows 11 23H2

P.S.: I recently sent in my laptop for repair and when I got it back a new "User" Windows account had already been set up. Thought this might also be relevant somehow.

Thank you

 

Microsoft Edge TLS Security

After trying everything (not a lot of steps) listed in the Microsoft Edge support site, I did a wider search and found this very simple youtube video that fixed it immediately:

For those who prefer not to click links the steps are simple:

1. Click in the Cortana search bar next to the Win 10 Start button

2. Type internet options

3. Select internet options (control panel) from the list

4. Click on the advanced tab

5. Scroll down to the security section

6. Make sure the following are all clicked:
Use SSL 3.0
Use TLS 1.0
Use TLS 1.1
Use TLS 1.2

7. Click apply

8. Refresh the page that was giving the error and it should now connect.

Hope this helps, it was a 30 second fix after hours of pounding my head against the error with the Support site suggestions.