@EDK-Rise I just opened the start menu and copy-pasted your post to it while playing a game. It works. .685 too.
I have this problem for a fair while on my VirtualBox Windows 10 VMs, previously only on the Insider builds (I routinely create a snapshot before doing anything Chkdsk-related, and often have to go back). Please note that it specifically occurs after chkdsk runs at Windows boot, but not always. I suspect that a special prior corruption or constellation is made worse by the chkdsk run. VMs will crash at bootup with a BSOD/GSOD (Error caused by ntfs.sys). The VMs have regular hard disks configured, and the underlying media is also mechanical HDDs. The problem seems to have been backported and carried over from them to the 20H2 builds, now.
That reply you quoted was aimed at a very specific person because of accumulated very specific posts. This "waste of space" is on a VM which runs on a SSD and it ran at windows boot (afaik, it rebooted and ran the scheduled chkdsk): https://forums.mydigitallife.net/th...20h1-2-vb_release.80763/page-293#post-1636583 And i am not saying that there won't be errors as mentioned in the article, but the article first claims it happens after an upgrade to 20H2 and update it, next they claim it was because of the 19042.685 update. And later on they play it down.
The behavior started at one time on the DEV branch/channel. Due to backporting, it now appears to be in 20H2, too. Older branches will hardly get anything backported now and are thus mostly unaffected. The quoting was a bit off, granted.
So, the problem only occurs when you upgrade from a 1809/1903/9 build with a LCU released September 16, 2020 or later and upgrade using a source that doesn't have an LCU released October 13, 2020 or later integrated. My latest real hardware test was with a 18363.1256 build to a 19042.685 build, no problems occurred when running chkdsk c: /f right after the upgrade was finished. edit, wrong issue
@Enthousiast the issue is listed down further Code: A small number of devices that have installed this update have reported that when running chkdsk /f, their file system might get damaged and the device might not boot. their msi fix: Code: reg add HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2372249226 /t REG_DWORD /d 0
@Enthousiast the registry/GPO prevent the issue from occuring (restart might required) those who already won't boot, will need the Recovery Console fix
I don't understand - I had this on since june - and i have been updating - no issues. until yesterday i received office updates - i accepted it and after a while i saw the activate windows. same for my office products.