Scanning and repairing drive D at every boot

Page 1 of 2 12 LastLast

  1. Posts : 64
    Windows 10 Pro
       #1

    Scanning and repairing drive D at every boot


    Hi,

    Recently I started to see the following message at Windows boot: 'Scanning and repairing drive (D:): 100% complete'.
    Every time I boot my computer the message pops up for few seconds and then Windows finishes booting normally.
    It didn't happen previously.
    I didn't make any hardware nor major software change on this machine.

    What is your advice?

    Thank you in advance guys,

    Windows version: 21H2 (OS Build 19044.1526)
      My Computer


  2. Posts : 41,547
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    Please perform the following steps in sequence:

    1) Run HD Tune: (free or trial version)
    HD Tune website
    Post images or share links for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan


    2) Sea Tools for Windows:
    SeaTools (Windows) |
    Seagate

    SeaTools | Seagate Support US
    How to use SeaTools for Windows | Seagate Support US
    long generic test


    3) Open administrative command prompt and type or copy and paste:

    chkdsk /b /v C:

    C:\WINDOWS\system32>chkdsk /b /v C:
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y

    This may take many hours so plan to run overnight.


    4) These tests can be performed overnight:
    a) HD Tune full error scan
    b) Sea Tools for Windows long generic test
    c) Chkdsk /b /v


    5) After completing the above drive tests please run these scripts and post share links into this thread using one drive, drop box, or google drive

    https://www.tenforums.com/attachment...p_plus_log.bat

    https://www.tenforums.com/attachment...iskparinfo.bat

    https://www.tenforums.com/attachment...2021-09-14.bat


    Last edited by zbook; 01 Mar 2022 at 02:56.
      My Computer


  3. Posts : 2,555
    Windows 10 Pro 64bit
       #3

    Open powershell with admin & enter:
    fsutil dirty query D:
    If there’s no problem then this should clear the message.
      My Computer


  4. Posts : 64
    Windows 10 Pro
    Thread Starter
       #4

    Hi,

    Thank you both for your answer.

    @zbook:

    1) I ran HD Tune free:
    _ the Health tab is blank, there'a nothing to view there, probably because it's a NVMe drive
    _ the benchmark ran without any particular issue:

    Scanning and repairing drive D at every boot-hdtune_02.jpg

    _ Full error scan ran without any particular issue as well:

    Scanning and repairing drive D at every boot-hdtune_01.jpg

    2) Seatools Seagate detected only one NVMe disk (I have 2, same model, same size). I don't have any way to know if the detected drive was D: or another, so I ran the long test, but I can't guarantee this is the correct drive unfortunatley:

    Scanning and repairing drive D at every boot-seagate_01.jpg

    3) I ran a chkdsk /b /v C: on D:, and here are the results:

    Microsoft Windows [Version 10.0.19044.1526]
    (c) Microsoft Corporation. All rights reserved.

    C:\Windows\system32>chkdsk/b /v D:
    The type of the file system is NTFS.

    Chkdsk cannot run because the volume is in use by another
    process. Chkdsk may run if this volume is dismounted first.
    ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
    Would you like to force a dismount on this volume? (Y/N) y
    Volume dismounted. All opened handles to this volume are now invalid.
    Volume label is ASSETS.

    Stage 1: Examining basic file system structure ...
    293120 file records processed.
    File verification completed.
    Phase duration (File record verification): 1.72 seconds.
    14 large file records processed.
    Phase duration (Orphan file record recovery): 0.00 milliseconds.
    0 bad file records processed.
    Phase duration (Bad file record checking): 0.31 milliseconds.

    Stage 2: Examining file name linkage ...
    44 reparse records processed.
    326480 index entries processed.
    Index verification completed.
    Phase duration (Index verification): 3.51 seconds.
    0 unindexed files scanned.
    Phase duration (Orphan reconnection): 45.99 milliseconds.
    0 unindexed files recovered to lost and found.
    Phase duration (Orphan recovery to lost and found): 0.70 milliseconds.
    44 reparse records processed.
    Phase duration (Reparse point and Object ID verification): 1.71 milliseconds.

    Stage 3: Examining security descriptors ...
    Cleaning up 13 unused index entries from index $SII of file 9.
    Cleaning up 13 unused index entries from index $SDH of file 9.
    Cleaning up 13 unused security descriptors.
    Security descriptor verification completed.
    Phase duration (Security descriptor verification): 0.80 milliseconds.
    16680 data files processed.
    Phase duration (Data attribute verification): 0.30 milliseconds.

    Stage 4: Looking for bad clusters in user file data ...
    293104 files processed.
    File data verification completed.
    Phase duration (User file recovery): 30.05 minutes.

    Stage 5: Looking for bad, free clusters ...
    87460328 free clusters processed.
    Free space verification is complete.
    Phase duration (Free space recovery): 0.00 milliseconds.

    Windows has scanned the file system and found no problems.
    No further action is required.

    1953498111 KB total disk space.
    1603154360 KB in 276243 files.
    83712 KB in 16682 indexes.
    0 KB in bad sectors.
    418723 KB in use by the system.
    65536 KB occupied by the log file.
    349841316 KB available on disk.

    4096 bytes in each allocation unit.
    488374527 total allocation units on disk.
    87460329 allocation units available on disk.
    Total duration: 30.14 minutes (1808457 ms).

    C:\Windows\system32>

    At that stage I restarted my computer to see if the 'Scanning and repairing drive (D:): 100% complete' message was still there: it was.

    5) I didn't run these scripts yet.
    Excuse my suspicion but I like to know what's going on in my machine everytime, even when scripts come from a reputable source like this forum: so I opened the scripts in notepad to see what they are doing, and honestly I don't understand anything.

    Can you tell please confirm what do these scripts do on my hdd?
    I just want to be sure it's 100% safe and there's nothing I can't undo if I run them.
    Thank you for your comprehension.

    Also note the second link is invalid. I have the following error:
    'Invalid Attachment specified. If you followed a valid link, please notify the administrator'.

    - - - Updated - - -

    Bastet said:
    Open powershell with admin & enter:
    fsutil dirty query D:
    If there’s no problem then this should clear the message.
    Thanks @Bastet,

    Here is the result:

    PS C:\Windows\system32> fsutil dirty query D:
    Volume - D: is NOT Dirty
    PS C:\Windows\system32>
      My Computer


  5. Posts : 41,547
    windows 10 professional version 1607 build 14393.969 64 bit
       #5

    These are the descriptions of the scripts.

    These are old versions.

    Please run the links in the earlier post.

    Batch files for use in BSOD debugging

    tuneup plus runs scannow, restorehealth, chkdsk, etc. these check the operating system, component store, and drive file system (most superficial scan and very quick check)

    diskpar info displays information about the disks, partitions, and volumes

    event viewer predominantly system and application reports but also most common errors


    All of the scripts can run in the background.
    Post share links using one drive, drop box, or google drive.



    Run:
    HD Sentinel (free or trial version)
    Hard Disk Sentinel - HDD health and temperature monitoring

    Results are instantaneous.
    Post results for all drives displaying results on these tabs:
    a) Overview
    b) Temperature
    c) SMART


    latest scripts:

    https://www.tenforums.com/attachment...p_plus_log.bat

    https://www.tenforums.com/attachment...2021-09-14.bat

    https://www.tenforums.com/attachment...iskparinfo.bat
      My Computer


  6. Posts : 64
    Windows 10 Pro
    Thread Starter
       #6

    When I run the first script it ends with an error saying it didn't succeed in creating the log (.zip) file.
      My Computer


  7. Posts : 17,015
    Windows 10 Home x64 Version 22H2 Build 19045.4170
       #7

    You're not on a dual-boot computer, by any chance?

    Denis
      My Computer


  8. Posts : 7,606
    Windows 10 Home 20H2
       #8

    Jambon28 said:
    When I run the first script it ends with an error saying it didn't succeed in creating the log (.zip) file.
    Please specify which script.
      My Computer


  9. Posts : 679
    Windows 10
       #9

    Ive had this problem before. Hopefully it will be as easy as what i went through to fix it.

    I had to take ownership of the drive and all its sub folders with my current Admin login. Take ownership of the 'Recycle BIN'. Full control for all files. Also show all hidden folders and files. Removed the tick out of the box that hides protected operating system files.

    Then, when i went into the root of drive, i found 15 folders that had appeared which id never seen before, with alot of my old software inside each folder. God knows how they ended up in there. Its like they were all corrupt from one of my other drives.
    I instantly deleted all of these wierd folders that had appeared, cleaned all crap out, did a format. Rebooted.

    This stopped the 'Repairing Drive' scan prior to login and my drive was accessible again.

    Good luck
      My Computer


  10. Posts : 2,555
    Windows 10 Pro 64bit
       #10

    Thanks @Jambon28, it means there’s no disk corruption. Hopefully that’ll mark the drive as clean & it’ll not run a scan at startup again.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:22.
Find Us




Windows 10 Forums