Windows 10: Microsoft error, not connected to the internet even tho i am.

I'm trying to play minecraft for like months, because i even paid for it, but in the xbox app, microsoft store app, like everywhere that is needed a microsoft account, i can't access. Maybe its because my account got hacked like 9 months ago, but i got it back and people are still trying to get in it, but idk why. I tried everything, removing microsoft store and getting it back, tried everything with the xbox app, did everything that youtube video said, but still nothing. PLEASE HELP!

:)

 

Microsoft Store opening- Internet connection problem error code 0x80072efd

Hi Syed,

Thank you for posting in Microsoft Community, we appreciate your interest in Windows 10.

I understand the inconvenience caused to you with accessing Microsoft Edge and Windows Store with error: 0x80072efd, we will help you with this issue.

• Do let us know if you are using wired/ wireless internet connection on your device?

I suggest you to try the below and check if it helps.

Step 1: Use
Internet Connection Troubleshooter.

Internet Connection Troubleshooter find and fix the problems with connecting to the internet or to websites.

• Click on Start; in the start search type
  Troubleshooter and hit Enter.
• In the left pane, click onView all.
• Click on Internet Connection Troubleshooter.
• Select Advance and click on
  Run as Administrator.
• Click Next and follow the on-screen instructions to complete the troubleshooting process.

Step 2: I suggest you to clear cache and cookies from the Microsoft Edge browser.

Steps:

• Open Microsoft Edge, click on
  More Action at the right top corner.
• Click on Settings, click on
  Choose what to clear under Clear browsing data.
• Select the Browsing history, caches and cookies and hit
  Clear.
• Close the browser and try to open it again.

Step 3: Run WSReset.exe .

• Press Windows+R key to open Run box
• Enter wsreset.exe in the Run command and then tap or click
  OK.
• Restart your computer and check.

Hope it helps. Reply to the post with an updated status of this issue, we will be happy to help you further.

 

W10 can connect to wider internet but cannot access web pages

I have an odd issue with my W10 laptop linked to Sky broadband in the UK via wifi using a Sky router. The effect is that while I can actually access the internet (I can send and receive emails using Outlook and can connect to other machines using TeamViewer) I cannot access any web site (Google, BBC etc). There is no specific error message, merely that the access request timed out and a suggestion that it may be to do with proxy. I have tried the following:

1. Other systems (W10 and ios) can access web sites using the same Sky router (therefore probably not a router problem)
2. I have sent and received emails using Outlook, so the broadband connection is working (probably not a Sky problem)
3. I have tried two different browsers (Firefox and Edge), no connection (not a browser problem)
4. I am using Windows Defender and have:
   1. Made sure that Firefox is in the list of allowed systems in its Firewall, no connection after a reboot
   2. Turned off the Firewall and tried again - no connection

My next step will be to re-install Windows, but has anyone got any other suggestions? Could it be some sort of virus (I have carried out a complete virus check using Defender) So - any suggestions?

 

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.