Due to Chromium - see Chromium bug tracker #711159. New Edge would be affected, and baked into this release now. Appears to trigger on opening local html files.
Edge bundled with 20H2 Enablment package is v84 or did they updated it in sysprep stage before capturing install.wim?
The bugs (another closed/duplicate example: 997951), are dating back to at least v76 so it wouldn't surprise me. It seems more people have been reporting it as of v85, but it's been around for a while? Chromium developers have flagged the recently reported ones this week as duplicates of the older one from years ago. I haven't installed 20H2 to see what version of Edge is in there though.
Fresh isos finally! I am now downloading them from tb.rg-adguard.net. I hope they are version 19042.572 and their sums will match.
so 508 is the official public release and it still needs the latest CU and SSU integrated to it ?? right ?
Hey, nope, I need the usual consumer editions. WZT has posted them though, so thanks for your help anyway
excited wow a whole bunch of new versions of applications and even a new NVidia driver 456.71 came out today must be the 20/H2 release LOL
I think that this is ms's fault. It has stopped providing the sums since 1909 at least. Do you mean in the new 20h2 iso? How can I check that? ---edit The setup.exe on the iso is on version 19041.1. Why?
Nvidia GRD v456.71 [27.21.14.5671] was released on 7th Oct 2020, not today. The Studio driver version 456.71 released yesterday if you're referring to that for this matter.
official Win10_20H2_English_x64.iso dated 09/27/2020 can't believe MS hold on to it for over a month File: Win10_20H2_English_x64.iso CRC-32: 23717768 MD4: 8b24d035ee4f00887df020ddbee24fbf MD5: e80f6ce987b2bba288469e7379129e12 SHA-1: 30dd6a48dfea77c37e51573bcb75be4edd6febff
I am at 19041.572 right now, Can anybody tell me how can I update to the latest 19042.508 version without reinstalling windows
just install the EP KB4562830 (see in the 1st page of this OP, everything listed there), you'll be on 20H2 (19042.572) after a reboot.
nope you can't check what build it is before setup only after you complete windows installation and run winver.exe then you can know