Windows 10: No Internet, secured - Can't fix

So frustrating. My laptop suddenly won't connect to the internet.My router is working absolutely fine. Other devices are connected fine. I have reset my router, reset my network settings, my VPN says it's connected. I have run the trouble shooter and unsurprisingly for Windows, it says it cannot detect any issues.All this, yet I simply cannot connect to my network.Any genuine ideas and ways to fix this?Thanks.

:)

 

Internet Security

IMO lots depends on the habits and the knowledge of the computer user...

Suggestion to read:

• Choosing an Anti-Virus Program
• Safe Steps for Replacing your Anti-virus - Why should you use Antivirus
  software?
• Supplementing your Anti-Virus Program with Anti-Malware Tools
• Best Practices for Safe Computing - Prevention of Malware Infection
  

Suggestion to watch:

 

Internet provider security for windows 10

I'm not familiar with 'wow internet provider' and don't know what kind of 'internet security' you're paying for...

But, IMO, that shouldn't be necessary.

Suggestion to read:
Answers to common security questions - Best Practices - Anti-Virus, Anti-Malware, and Privacy Software

especially:

• Choosing an Anti-Virus Program
• Safe Steps for Replacing your Anti-virus - Why should you use Antivirus
  software?
• Supplementing your Anti-Virus Program with Anti-Malware Tools

 

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.