It was discussed with the 1909 EP, with all 19042.xxx releases and self updated ISOs. DISM doesn't show 19042 because it's registry only.
Anyone else getting SFC errors with the official 20H2 ISO? I tried the Win10_20H2_English_x64.iso from TechBench downloads (verified SHA256) and downloaded the ISO using the Microsoft Media Creation tool. Tried on both VMware Workstation and VirtualBox but SFC found corrupt files with both ISO's.
i didnt get it. i just downloaded the 2009 iso from adguard. so is it a fake iso? omg, what to do now?
What are the exact sfc errors? you can filter them by running this cmd in an elevated cmd: Code: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" It will create a file called sfcdetails.txt on your desktop.
anyone else get a weird debug.log on there desktop says [1020/181914.415:ERROR:settings.cc(430)] Settings version is not 5 , this is on a fresh install 19042.572 x64 English
btw two new lang iso came out mu_windows_10_version_2004_9b_local_experience_packs_lxps_released_oct_2020_x86_arm64_x64_dvd_3b3a4ca8.iso mu_windows_10_version_2004_9c_local_experience_packs_lxps_released_oct_2020_x86_arm64_x64_dvd_12868a71.iso the 9b version is old version 19041.10.24.0 the 9c version is new version 19041.11.27.0 so, not need to download 9b.
Yes, now I remember. Thanks for reminding me. My excuse is that I'm old and having a "senior moment." 'Seems like there's a lot of drama in the thread today. M$ officially releases a new version of Windows 10, and all hell seems to break loose. I just walked into the Windows 10 bar, and suddenly a brawl starts Would somebody please pour me a drink?? Thanks for all your work Enthousiast!
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?