Hi!
Yes, I think your problem is somehow related to this issue of mine, i.e.
1. Regular start-up behaviour until the light blue screen for Disk Check
2. On the screen appearing in some two-three-four seconds the following
text rows
The file system of the drive C: will be checked
File system type NTFS
The drive cannot be opened into use directly
Windows has checked the hard drive
....... (yes, some dots appearing one by one)
3. When system is got on upon checking the statuses
- the DirtyBit is seen still on
- BootExecute key is seen still remaining "ready" for a check of the
drive C:
You may have the point 2. with slightly different texts ...
So, this "no Disk Check for C:" symptom may be caused somehow like this
a) for some obvious pertinent reason the disk/file system of the disk C: is
seen having some slight problem and thus the DirtyBit of that disk is set on
b) due to the DirtyBit set on, on the next start-up the Disk Check
chkdsk.exe /f is started automatically for the disk C: by the autochk.exe
c) now, a good guess for the reason is -> due to a fact that the disk C:
has during the start-up just for a few seconds before already been taken in
use i.e. locked by some unknown program the chkdsk.exe is failing to begin
it's process and thus the Disk Check for the disk C: is not done even
requested to be done
d) and, all this will be valid and repeated constantly on all subsequent
start-up's due to the DirtyBit remaining on all the time until set off by the
fulfillment of the chkdsk.exe ...
So, the solution for this could be to locate which program is the mysterious
unknown one locking the disk just before the chkdsk.exe ...
I may come back if finding something new for this.
Best regards,
Pete V.
