In Windows 10 /64, CHKDSK C: returns (among other normal output) the error "The Volume Bitmap is incorrect."
Changing the command to CHKDSK C: /SCAN results in
"Windows has scanned the file system and found no problems. No further action is required."
Why is there a difference? What is the volume bitmap, and why would CHKDSK only find a problem when not using the /SCAN option?
I run chkdsk in my script before imagew64.exe to be sure the drive doesn't have errors. This is causing the script to error out before the image.
I can just change the command to CHKDSK C: /SCAN, but I'd like to understand more about what's going on.
Windows 10 - CHKDSK volume bitmap inconsistency
-
- Posts: 3644
- Joined: Thu May 05, 2011 10:37 pm
Re: Windows 10 - CHKDSK volume bitmap inconsistency
at some point (one of the windows upgrades - might have been vista/7) their
non /f checking (on unlocked drives) can find problems since things are
changing and inconsistent.
"timg11" wrote in message news:12756@public.image...
In Windows 10 /64, CHKDSK C: returns (among other normal output) the error
"The Volume Bitmap is incorrect."
Changing the command to CHKDSK C: /SCAN results in
"Windows has scanned the file system and found no problems. No further
action is required."
Why is there a difference? What is the volume bitmap, and why would CHKDSK
only find a problem when not using the /SCAN option?
I run chkdsk in my script before imagew64.exe to be sure the drive doesn't
have errors. This is causing the script to error out before the image.
I can just change the command to CHKDSK C: /SCAN, but I'd like to understand
more about what's going on.
non /f checking (on unlocked drives) can find problems since things are
changing and inconsistent.
"timg11" wrote in message news:12756@public.image...
In Windows 10 /64, CHKDSK C: returns (among other normal output) the error
"The Volume Bitmap is incorrect."
Changing the command to CHKDSK C: /SCAN results in
"Windows has scanned the file system and found no problems. No further
action is required."
Why is there a difference? What is the volume bitmap, and why would CHKDSK
only find a problem when not using the /SCAN option?
I run chkdsk in my script before imagew64.exe to be sure the drive doesn't
have errors. This is causing the script to error out before the image.
I can just change the command to CHKDSK C: /SCAN, but I'd like to understand
more about what's going on.
Re: Windows 10 - CHKDSK volume bitmap inconsistency
So you're thinking the volume bitmap error is a false positive, and I'm doing the right thing by changing my script to use "CHKDSK C: /SCAN"
-
- Posts: 3644
- Joined: Thu May 05, 2011 10:37 pm
Re: Windows 10 - CHKDSK volume bitmap inconsistency
right, maybe add /x ?
"timg11" wrote in message news:12758@public.image...
So you're thinking the volume bitmap error is a false positive, and I'm
doing the right thing by changing my script to use "CHKDSK C: /SCAN"
"timg11" wrote in message news:12758@public.image...
So you're thinking the volume bitmap error is a false positive, and I'm
doing the right thing by changing my script to use "CHKDSK C: /SCAN"