Windows 10: Microsoft Security Blank Screen

I have a Windows 10 Pro,Version 1909 OS,Build:18363.997


My Windows Security has a Blank Screen


I tried to reset the PC but Windows Security is still Blank


Please help me


p.s I don't have a third-party antivirus,when I bought the laptop, Windows Security has a blank screen. I already have the latest update of windows but Windows Security is still blank.





:)

 

Blank Screen

Hi Virginia,

Conflicts with third-party software and outdated graphic drivers are common contributors to the black screen issue that you're having. To isolate the said issue, we'd like to ask a few questions:

• Are you getting any error messages before getting a blank screen?
• Are you experiencing this when using a particular app?
• Were there any changes made on your computer settings prior to this issue?

Meanwhile, we suggest that you refer to this
article which talks about the steps you can take to resolve blank screen errors.

We'll wait for your response and assist you accordingly.

 

Microsoft Security Bulletin for September 2007

Microsoft released yesterday the September Security Bulletin for Windows operating system, as part of its monthly security cycle. This bulletin summary lists one critical and three important updates. For more information, see Microsoft Security Bulletin Summary for September 2007.

Source: Microsoft

 

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.