Another day...
I ran chkdsk c: /F /V on 3 three systems which were updated to 2004.
Upon reboot or booting from a cold start, the routine completes without completion of the boot - the little dotted circle keeps spinning.
Difficulty in powering off by holding in the button.
Once restarted, it says "100%" complete and boots fully.
2 desktops and 1 laptop are involved.
Bug? Can anyone replicate?
TIA
Trying it on my laptop now, 500GB SSD.
Worked ok for me. Finished chkdsk, rebooted as expected and I'm back to my Desktop.
HP DV7 19041.331 2004 Samsung SSD 860 EVO 500GB.
Why are you running Chkdsk only for the FAT/FAT32 (/V) and not the full disk(chkdsk C: /r) Compumind?
Hello @Cliff S,
I did look at that myself when he first posted . . .
Chkdsk /? Checks a disk and displays a status report.
CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B]
volume Specifies the drive letter (followed by a colon), mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for fragmentation.
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of every file on the disk.
/V On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information (implies /F).
/L:size NTFS only: Changes the log file size to the specified number
of kilobytes. If size is not specified, displays current size.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be invalid (implies /F).
/I NTFS only: Performs a less vigorous check of index entries.
/C NTFS only: Skips checking of cycles within the folder structure.
/B NTFS only: Re-evaluates bad clusters on the volume (implies /R)
The /I or /C switch reduces the amount of time required to run Chkdsk by skipping certain checks of the volume.
Hi Cliff -
Same issue with those switches, as well. Even NTFS - forgot to mention.
However, I found this and it might just be the common thread among my 3 systems:
Problems with Norton Security and Windows 10 2004 chkdsk /f | Norton Community
Yes, all bar the 'Difficulty in powering off by holding in the button' - I had no such problem.
19041.329 x64 Pro, disk is an HDD, no Norton or any other 3rd-party AV installed.
Chkdsk appears to have completed successfully, it's just the restart that fails to take place. On a chkdsk at boot the log is recorded in C:\System Volume Information as usual. Here's what mine says:
Code:.... Windows has scanned the file system and found no problems. No further action is required. 243997695 KB total disk space. 45256652 KB in 128093 files. 85788 KB in 32570 indexes. 0 KB in bad sectors. 476303 KB in use by the system. 65536 KB occupied by the log file. 198178952 KB available on disk. 4096 bytes in each allocation unit. 60999423 total allocation units on disk. 49544738 allocation units available on disk. Total duration: 50.80 seconds (50809 ms). Internal Info: 00 76 05 00 a2 73 02 00 89 e1 04 00 00 00 00 00 .v...s.......... de 00 00 00 51 00 00 00 00 00 00 00 00 00 00 00 ....Q........... Windows has finished checking your disk. Please wait while your computer restarts.
...but it never restarts.
My log is similar in content to yours.
Some users may not be able to gain access to this log since it is hidden and protected.
Try first. If no go, here is a fix for that... proceed at your own risk...
How to fix: C:System Volume Information is not accessible - Access Denied. - wintips.org - Windows Tips & How-tos
Now I can rule out Norton, thanks.
Last edited by Compumind; 20 Jun 2020 at 08:10.
Isn't the log in Event viewer?
I always get it at Windows logs/application then use "Find" chkdsk, and then it shows me the last chkdsk.
Yes, there too. But for a chkdsk at boot up the event log isn't running yet, so the log is initially written to System Volume Information which is where the Event log picked it up from. Unlike the event log which gets cleared at each feature update, the logs in System Volume Information persist until you reformat the drive.
Quote
