Windows 10: Windows 10 Error Message using Microsoft Edge

Hi all,


Desktop PC is using the latest version of Windows 10. The last few nights I've noticed that I've been getting an error message when I've been on the internet using Microsoft Edge. It comes with a beeping noise and it keeps telling me that files are corrupt and to update server.


I immediately close down edge window and ensure that the windows update has gone through successfully.


Unfortunately I haven't been able to obtain a screenshot of this error message, does anyone have any advice on what to do?


Norton is running in the background, can't recall if Windows Defender is bringing this up on the error screen.


When these messages come up the webpage is on the msn home page


Thanks in advance for any thoughts


Lesley

:)

 

Microsoft Edge

Hello,

There could be a few possible reasons why you are experiencing this issue. We have here some troubleshooting questions that may help to look further into this:

• What is the build and version of your Windows 10?
• Are you encountering an error message? If so, kindly provide the full error message.
• Were there any updates installed or changes made prior to experiencing the issue?

For the mean time, we suggest that you perform the methods provided by Tiero Chi
in this thread for the steps on:
How to recover Microsoft Edge if it fails to launch.

We are eager on getting this resolved for you; we will wait for your feedback.

 

Microsoft is developing a built-in ad blocker for its Edge browser

"One of the first browser add-ons many people install to improve their online experience is Adblock Plus or something similar. Until recently, Microsoft Edge's lack of support for add-ons put off a lot of would-be users, but reports from Build 2016 suggest that native ad blocking is on its way to the Internet Explorer successor.

Adblock Plus is coming to Edge, but built-in ad blocking would negate the need for such an add-on. A slide shown off and snapped at a Build presentation shows that the next version of Edge, in response to user feedback, will feature ad blocking capabilities. There's no word on delivery timescale, but the upcoming Windows 10 Anniversary Update would seem a likely candidate.

ZDNet's Ed Bott photographed the slide which shows Microsoft's development roadmap built around feedback from testers. Right at the top of the list is reference to plans to create a plugin and extension store for Edge, but it's entry number four that's more intriguing.

"Build ad blocking features into the browser" is listed as a Feature Request from users. But the good news is that it is not only listed as being "Deliverable 4682811", but as "Targeted for the next version".

This will no doubt come as good news for those who have fallen in love with Edge, but it's not something that will be welcomed by the likes of Adblock Plus. It does seem that, particularly in the mobile arena, there is a move to baking ad blocking into the browser so it makes sense that Microsoft is following the trend. But it is the fact that Edge straddles Windows 10 on the desktop and Windows 10 Mobile that makes this a particularly interesting move.

Keep an eye out for Insider builds in the coming weeks as the feature may be just around the corner."

Forget extensions, built-in ad blocking is coming to Microsoft Edge - [UPDATE... no it's not!]

 

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.