From: Joachim Henze Date: Sun, 9 Jan 2022 04:22:09 +0000 (+0100) Subject: [0.4.10][AUTOCHK] Don't check any volume on boot CORE-14638 X-Git-Url: https://git.reactos.org/?p=reactos.git;a=commitdiff_plain;h=d12c8e5ef3c8e5f58b1fd35ec7c123308db1c921 [0.4.10][AUTOCHK] Don't check any volume on boot CORE-14638 This will avoid triggering a FAT repair on unclean FAT volumes. If dosfstools.fsck works fine in Linux, its usage on ReactOS triggers worse corruption than unclean shutdown. 'autochk during OS startup' has been added during 0.4.9-dev-xxxx. Given I've no time for debugging this, I kill it off. This is just a workaround of course. For now the best chances to repair a FAT FS corruption after non-clean-shutdown is to mount that FS within 2k3sp2 and give the MS chkdsk an attempt to repair it. Success is not guaranteed, but it works surprisingly often. The earlier you do that after non-clean-shutdown, the better your chances for success will be. The workaround was picked from 0.4.13-dev-169-g ab69736a1d9c76260c500b11491328244d027893 --- diff --git a/boot/bootdata/hivesys.inf b/boot/bootdata/hivesys.inf index 4af1b1b5a42..202e10c783c 100644 --- a/boot/bootdata/hivesys.inf +++ b/boot/bootdata/hivesys.inf @@ -1418,7 +1418,7 @@ HKLM,"SYSTEM\CurrentControlSet\Control\GroupOrderList","SCSI Miniport", 0x000000 ; Session Manager stuff HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager","BootExecute", 0x00010000, \ - "autocheck autochk *" + "autocheck autochk" HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager","GlobalFlag", 0x00010003, 0x00000000 HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager","ObjectDirectories",0x00010000, \ "\Windows", \