Disk Check at Startup

Laptop with Win XP Pro up to date.
A new Win XP Pro install.
No other problems, all works, CD, USB mouse, USB ports etc.

Every time I boot up, windows insists on doing a disk check on the 32G
SD and finds no problems.

32G SD in slot all the time.
Formatted exFAT.
Formatted in this laptop.

read / write with small or large files with no problems.
files compare byte for byte with source on C:

1G used out of 32G.

What is going on ?
How do I avoid this disk check at startup ?

In message , Manly
writes:

Laptop with Win XP Pro up to date.
A new Win XP Pro install.
No other problems, all works, CD, USB mouse, USB ports etc.

Every time I boot up, windows insists on doing a disk check on the 32G
SD and finds no problems.

32G SD in slot all the time.
Formatted exFAT.
Formatted in this laptop.

read / write with small or large files with no problems.
files compare byte for byte with source on C:

Is this a laptop with two disc slots? If not, is "C:" the SD or not?

1G used out of 32G.

What is going on ?
How do I avoid this disk check at startup ?

--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

The fifth bestselling detail of all time: the Ford Transit. (RT/C4 2015-5-24.)

On 10/12/2017 2:04 PM, Manly wrote:

Laptop with Win XP Pro up to date.
A new Win XP Pro install.
No other problems, all works, CD, USB mouse, USB ports etc.

Every time I boot up, windows insists on doing a disk check on the 32G
SD and finds no problems.

32G SD in slot all the time.
Formatted exFAT.
Formatted in this laptop.

read / write with small or large files with no problems.
files compare byte for byte with source on C:

1G used out of 32G.

What is going on ?
How do I avoid this disk check at startup ?


Is it Windows doing the check, or is it your anti-virus application?

--
David E. Ross
http://www.rossde.com/

By allowing employers to eliminate coverage for birth control
from their insurance plans, President Trump has guaranteed there
will be an increase in the demand for abortions.

Manly wrote:
Laptop with Win XP Pro up to date.
A new Win XP Pro install.
No other problems, all works, CD, USB mouse, USB ports etc.

Every time I boot up, windows insists on doing a disk check on the 32G
SD and finds no problems.

32G SD in slot all the time.
Formatted exFAT.
Formatted in this laptop.

read / write with small or large files with no problems.
files compare byte for byte with source on C:

1G used out of 32G.

What is going on ?
How do I avoid this disk check at startup ?

I am wondering if this is one of those chkdsk flag problems, where checkdisk
runs at bootup unless you clear the flag? An article on this used to be on
the MS website, but I can't find it. The article title was "Chkdsk runs
each time you start your computer". As I recall, it required a certain
flag for either chkdsk or fsutil, but maybe someone else remembers.

Bill in Co wrote:
Manly wrote:
Laptop with Win XP Pro up to date.
A new Win XP Pro install.
No other problems, all works, CD, USB mouse, USB ports etc.

Every time I boot up, windows insists on doing a disk check on the 32G
SD and finds no problems.

32G SD in slot all the time.
Formatted exFAT.
Formatted in this laptop.

read / write with small or large files with no problems.
files compare byte for byte with source on C:

1G used out of 32G.

What is going on ?
How do I avoid this disk check at startup ?

I am wondering if this is one of those chkdsk flag problems, where checkdisk
runs at bootup unless you clear the flag? An article on this used to be on
the MS website, but I can't find it. The article title was "Chkdsk runs
each time you start your computer". As I recall, it required a certain
flag for either chkdsk or fsutil, but maybe someone else remembers.

A chkdsk can be scheduled before shutdown, by inserting a call for
checking in the BootExecute key. That's one way to trigger a check.
If you use File Explorer, select C: and attempt to do a check, it
will "schedule" a check for the next boot time, when the partition
is not busy and the check can be carried out. And that's done with
BootExecute.

In addition, there is a "dirty bit". It can be set by the
user, and the dirty bit is checked at startup too, by the
default command loaded in BootExecute.

*******

fsutil utility, can query or set the dirty bit. But not clear it.
Microsoft really wants CHKDSK to clear the bit.

Examples of fsutil are shown here.

https://www.raymond.cc/blog/manually...ithout-chkdsk/

fsutil dirty query G:

That article also shows where the dirty bit is located,
for those brave (or foolish) enough to play with it :-)
I didn't know until this minute, that it was possible
to find that.

When you dual boot, sometimes one OS will corrupt the file
system on a volume, as far as the second OS is concerned. And
they cannot agree on what a "fixed" file system looks like.
In that case, you would see "complaints" when alternating
between the two OSes. But stability, if you stayed within
the one OS for a number of sessions.

Paul

C: is a HDD

F: is the 32G SSD formatted exFAT

I always let the disk check run to completion and it reports no problems.
It reports the SSD size correctly.

Only Win XP pro, no dual boot.

This started happening after I plugged in the 32G SSD and left it in and
subsequently booted over the last few weeks.

I have NO virus scanner running other than what comes on the recent
install of Win XP Pro.

I write to the SDD all the time and read back to verify contents.

C: & D: are partitions of a single HDD
C: os
D: data
E: DVD virtual
F: SD32
G: memory stick empty slot
H: RAM DISK
I: DVD

E: and H: are not present until the OS is up.

In message , Manly
writes:
C: is a HDD

F: is the 32G SSD formatted exFAT
[]
This started happening after I plugged in the 32G SSD and left it in
[]
You said this is a laptop - so, this _is_ a laptop with two disc slots?
(Into one of which you've plugged the C&D drive, and the other the SSD?)

Or, is the SSD in an external (USB?) housing?
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Capital flows toward lower costs like a river to lowest ground.
"MJ", 2015-12-05

"J. P. Gilliver (John)" wrote in message
...
In message , Manly
writes:
C: is a HDD

F: is the 32G SSD formatted exFAT
[]
This started happening after I plugged in the 32G SSD and left it in
[]
You said this is a laptop - so, this _is_ a laptop with two disc slots?
(Into one of which you've plugged the C&D drive, and the other the SSD?)

Or, is the SSD in an external (USB?) housing?

Now I'm REALly confused (not too unusual). First it was a 32G SD, which I
assumed was a Secure Digital card, and now it's an SSD, which, like you, I
assume is a hard disk. I'll be interested to see the OP's answer :-)
--

SC Tom

In article ,
says...

C: is a HDD

F: is the 32G SSD formatted exFAT

I always let the disk check run to completion and it reports no problems.
It reports the SSD size correctly.

Only Win XP pro, no dual boot.

This started happening after I plugged in the 32G SSD and left it in and
subsequently booted over the last few weeks.

I have NO virus scanner running other than what comes on the recent
install of Win XP Pro.

I write to the SDD all the time and read back to verify contents.

C: & D: are partitions of a single HDD
C: os
D: data
E: DVD virtual
F: SD32
G: memory stick empty slot
H: RAM DISK
I: DVD

E: and H: are not present until the OS is up.

Why do I have the feeling what he meant to say was a 32Gb SD card in the
card slot?

pjp wrote:
In article ,
says...
C: is a HDD

F: is the 32G SSD formatted exFAT

I always let the disk check run to completion and it reports no problems.
It reports the SSD size correctly.

Only Win XP pro, no dual boot.

This started happening after I plugged in the 32G SSD and left it in and
subsequently booted over the last few weeks.

I have NO virus scanner running other than what comes on the recent
install of Win XP Pro.

I write to the SDD all the time and read back to verify contents.

C: & D: are partitions of a single HDD
C: os
D: data
E: DVD virtual
F: SD32
G: memory stick empty slot
H: RAM DISK
I: DVD

E: and H: are not present until the OS is up.

Why do I have the feeling what he meant to say was a 32Gb SD card in the
card slot?

One thing that occurs to me, is if F: and G: are
part of a USB card reader, they should be using
four drive letters (typical for things like 52-in-1
card readers). And discretionary mounts should
be moved well away from them. The DVD virtual
could be moved up high (T , the RAM Disk could
go up high (U, then check to see whether the physical
DVD avoids the four letters a USB card reader
normally uses.

Paul

In article , lid says...

pjp wrote:
In article ,
says...
C: is a HDD

F: is the 32G SSD formatted exFAT

I always let the disk check run to completion and it reports no problems.
It reports the SSD size correctly.

Only Win XP pro, no dual boot.

This started happening after I plugged in the 32G SSD and left it in and
subsequently booted over the last few weeks.

I have NO virus scanner running other than what comes on the recent
install of Win XP Pro.

I write to the SDD all the time and read back to verify contents.

C: & D: are partitions of a single HDD
C: os
D: data
E: DVD virtual
F: SD32
G: memory stick empty slot
H: RAM DISK
I: DVD

E: and H: are not present until the OS is up.

Why do I have the feeling what he meant to say was a 32Gb SD card in the
card slot?

One thing that occurs to me, is if F: and G: are
part of a USB card reader, they should be using
four drive letters (typical for things like 52-in-1
card readers). And discretionary mounts should
be moved well away from them. The DVD virtual
could be moved up high (T , the RAM Disk could
go up high (U, then check to see whether the physical
DVD avoids the four letters a USB card reader
normally uses.

Paul

I always assign such card readers the drives W thru Z using Disk Manager
tools. Mind you I specifically assign pretty much everything leaving a
"hole" for random thumbdrives. All external/portable hard disks get
their own unique drive letter assigned.

On Thu, 12 Oct 2017 20:08:13 -0400, Paul
wrote:

Bill in Co wrote:
Manly wrote:
Laptop with Win XP Pro up to date.
A new Win XP Pro install.
No other problems, all works, CD, USB mouse, USB ports etc.

Every time I boot up, windows insists on doing a disk check on the 32G
SD and finds no problems.

32G SD in slot all the time.
Formatted exFAT.
Formatted in this laptop.

read / write with small or large files with no problems.
files compare byte for byte with source on C:

1G used out of 32G.

What is going on ?
How do I avoid this disk check at startup ?

I am wondering if this is one of those chkdsk flag problems, where checkdisk
runs at bootup unless you clear the flag? An article on this used to be on
the MS website, but I can't find it. The article title was "Chkdsk runs
each time you start your computer". As I recall, it required a certain
flag for either chkdsk or fsutil, but maybe someone else remembers.

A chkdsk can be scheduled before shutdown, by inserting a call for
checking in the BootExecute key. That's one way to trigger a check.
If you use File Explorer, select C: and attempt to do a check, it
will "schedule" a check for the next boot time, when the partition
is not busy and the check can be carried out. And that's done with
BootExecute.

In addition, there is a "dirty bit". It can be set by the
user, and the dirty bit is checked at startup too, by the
default command loaded in BootExecute.

*******

fsutil utility, can query or set the dirty bit. But not clear it.
Microsoft really wants CHKDSK to clear the bit.

Examples of fsutil are shown here.

https://www.raymond.cc/blog/manually...ithout-chkdsk/

fsutil dirty query G:

That article also shows where the dirty bit is located,
for those brave (or foolish) enough to play with it :-)
I didn't know until this minute, that it was possible
to find that.

I'm brave and foolish enough. My Drive-D partition had a dirty
bit set. System logs showed it was a Firefox problem (I keep my
profile there). I cleared it a few times, and the problem "went away".
DMDE.
Wondering if the OP's drive was formatted under XP or under
another OS. The "dirty bit" is in a different location, depending on
the OS. Maybe XP can't "see" it.
[]'s

When you dual boot, sometimes one OS will corrupt the file
system on a volume, as far as the second OS is concerned. And
they cannot agree on what a "fixed" file system looks like.
In that case, you would see "complaints" when alternating
between the two OSes. But stability, if you stayed within
the one OS for a number of sessions.

Paul
--
Don't be evil - Google 2004
We have a new policy - Google 2012