Guess that was just down to an NVIDIA issue then, as I had no issues whatsoever when I got the CU, and good you got it sorted. Though I must admit I haven't gone as far as checking out the .gov links in edge. I didn't seem to have any issues with 113 other than the WD Offline scan not working, and still not working in 116. Can't say I noticed the edge issue if that was in 113 and I know I did go onto some .gov sites using edge.
Here are some to test. It appears to mainly affect local government sites.
Some GOV.UK Sites Unreachable Due to HSTS Changes in Windows UpdatesSome of the known GOV.UK sites that are affected include Doncaster Council, www.reading.gov.uk, and www.southglos.gov.uk
For example, in .113 Edge gives....
Thanks @Bree , will take a look and see what happens. Interesting how it was seemingly selective though.Here are some to test. It appears to mainly affect local government sites....
Some GOV.UK Sites Unreachable Due to HSTS Changes in Windows Updates
For example, in .113 Edge gives....
From the Bleeping Computer article I linked to, it appears the problem was that the Patch Tuesday update (for all versions) added "gov.uk" to the HTTP Strict Transport Security Top Level Domains (HSTS TLD) for Internet Explorer and Microsoft Edge. See for example...
Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14This update includes quality improvements. Key changes include:
.... Adds "uk.gov" into the HTTP Strict Transport Security Top Level Domains (HSTS TLD) for Internet Explorer and Microsoft Edge.
Unfortunately, not every GOV.UK site supports HTTPS and thus those sites that don't became unreachable in Microsoft Edge and Internet Explorer. Local government sites seem the main culprits. For example, the Doncaster example in my screenshot ishttp://www.doncaster.gov.uk/ (not https: as it would be for a secure site).
Tried some out, including my local one and all seem fine now. I can see how http vs https might be a problem but hadn't realised that any gov.uk sites were different as I thought they all came under the same umbrella as far as standards are concerned. I also hadn't realised the implication of HSTS TLD for IE & Edge. We live and learn
It's an appalling state of affairs that our local government websites are not using https.
But in view of the elections in three days time MS could have been accused of interfering with local politics if they hadn't fixed this ASAP. Under the circumstances it's no wonder they felt compelled to rush out a fix late on Sunday
Couldn't agree more. you would think in this day and age they would be more tech safety savvy, as far as the net is concerned, but I guess we can just dream on as they don't practice what they preach.It's an appalling state of affairs that our local government websites are not using https.
But in view of the elections in three days time MS could have been accused of interfering with local politics if they hadn't fixed this ASAP. Under the circumstances it's no wonder they felt compelled to rush out a fix late on Sunday
As you say the implication on the forthcoming elections could well have been seen by those into conspiracies as an attempt to pervert the EU elections, as if we haven't had enough alreadySo it's hats off to MS for nipping that one in the bud
Quote
