Scanning and repairing drive on every start-up

Page 1 of 5 123 ... LastLast

  1. Posts : 53
    Windows 10 Pro
       #1

    Scanning and repairing drive on every start-up


    I recently had an issue with my PC that wouldn't let it start up. Re-plugging my hard drives fixed it, but now it gives me a scanning and repairing drive message on every start-up, taking up a lot more time to start up Windows. What can I do to get rid of this?

    Another side issue is an occasional tick sound I'm hearing from within my PC while it's on. I had this on a previous computer some years ago as well, and no idea what's causing it. This started happening after the issue.
      My Computer


  2. Posts : 11,396
    Windows 10 Home x64 Version 21H2 Build 19044.1706
       #2

    When I once had the same continual scanning-repairing at reboot, I resolved it using this procedure in an Admin cmd window -
    1 fsutil dirty query C: I knew it would be reported as dirty but I wanted to see it so I could be sure that it had changed at step 3
    2 chkdsk c: /F /V /R /X This is the most severe set of switches available in ChkDsk [see Chkdsk - MSDocs or chkdsk - SS64]
    3 fsutil dirty query C: This was now reported as not dirty so I knew that the chkdsk command had fixed things and there were no further scans at reboot.

    If you have dual-booting then you will probably need to run these commands in both OSs.

    HOWEVER

    Your subsequent comment about ticking concerns me. I have no direct experience of this but I think others have posted that it indicates a hardware fault in an HDD. Perhaps you could search for ticking to see if you can get some authoritative advice.
    Advanced Search - TenForums

    Denis
      My Computer


  3. Posts : 53
    Windows 10 Pro
    Thread Starter
       #3

    Try3 said:
    When I once had the same continual scanning-repairing at reboot, I resolved it using this procedure in an Admin cmd window -
    1 fsutil dirty query C: I knew it would be reported as dirty but I wanted to see it so I could be sure that it had changed at step 3
    2 chkdsk c: /F /V /R /X This is the most severe set of switches available in ChkDsk [see Chkdsk - MSDocs or chkdsk - SS64]
    3 fsutil dirty query C: This was now reported as not dirty so I knew that the chkdsk command had fixed things and there were no further scans at reboot.
    Thanks. I did step 1, and it said C wasn't dirty.
    I did step 2, but after it finished the whole repair, it continues to give me the same scanning and repairing message on start-up.

    I got a picture of the message, if that helps.
    Attached Thumbnails Attached Thumbnails Scanning and repairing drive on every start-up-thumbnail_20200702_183212.jpg  
      My Computer


  4. Posts : 11,396
    Windows 10 Home x64 Version 21H2 Build 19044.1706
       #4

    If C:\ is not dirty then that scan is not of drive C:\.

    I think it is scanning a volume that has no drive letter. Does that volume identification show up if you run
    Code:
    Diskpart
    then
    Code:
    List Volume
    ?

    Have you recently changed any partitions?

    ADDN - I have a note of other Diskpart commands that can reveal volume IDs. Give me a few minutes and I'll post again [my notes on this subject are about an old configuration and it is difficult decyphering my notes].

    Denis
    Last edited by Try3; 02 Jul 2020 at 12:37.
      My Computer


  5. Posts : 11,396
    Windows 10 Home x64 Version 21H2 Build 19044.1706
       #5

    To get partition data I went through
    Diskpart
    List disk
    Select disk 1 {or whichever disk is the one Windows is on but you might have to repeat the procedure for each one}
    list part
    Select part 1 {starting with the one I suspected then working though each one in turn}
    Detail disk
    Detail part

    The various IDs showed up in response to the Detail ... commands.

    I am straying well beyond my competency in trying to go any further so I'd suggest you study
    DiskPart commands - Microsoft Docs
    DiskPart - SS64
    to see how you might progress by referring to volumes instead of disk & partitions.

    Alternatively, start a new thread just for that topic How to identify a volume using DiskPart
    - include that initial photo in it.
    - Explain that you are trying to find out what it is that is being scanned so you can then consider what might be wrong with it and fix it.

    The only time I have seen anything similar was a decade ago when I had partitioned a disk and saw that my routine defrag C:\ task had now been converted [by Windows] into defrag Volume{****** - just like your photo}.

    Best of luck,
    Denis
      My Computer


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

    How to identify a volume using DiskPart


    Recently, I had a start-up error with the "Reboot and select proper Boot device" message. I fixed it by unplugging and then plugging back in my drives, but since then it has been slow with starting up Windows, attempting to scan and repair an unknown drive before the login screen.

    I need help to figure out which disk it is referring to and how to get rid of the scan and repair thing on start-up.

    Windows Version Number: 1903 (OS Build 18362.900)

    (Link to the previous thread: Scanning and repairing drive on every start-up
    Tried the things listed there, but couldn't get much further. Was suggested to start this new thread...)
    Attached Thumbnails Attached Thumbnails Scanning and repairing drive on every start-up-thumbnail_20200702_183212.jpg  
      My Computer


  7. Posts : 1,867
    Windows 10 Pro 2004 20H1
       #7

    "I need help to figure out which disk it is referring to and how to get rid of the scan and repair thing on start-up"

    Open a Command prompt.

    Enter mountvol

    Once you get the drive letter, run the following in an elevated Command prompt to see if the "dirty bit" has been set on that drive.

    In the format -

    fsutil dirty query DriveLetter:

    Example -

    fsutil dirty query c:

    - - - Updated - - -

    I noticed that you have an existing thread on the same subject matter.

    Scanning and repairing drive on every start-up

    Please keep things in one thread.
      My Computer


  8. Posts : 1,867
    Windows 10 Pro 2004 20H1
       #8

    Same subject matter cross-posted in another TenForums thread here -

    https://www.tenforums.com/drivers-ha...ml#post1956176
      My Computer


  9. Posts : 11,396
    Windows 10 Home x64 Version 21H2 Build 19044.1706
       #9

    OldNavyGuy said:
    Once you get the drive letter ...
    That is the OP's problem. He does not know the drive letter.

    I told the OP to open this new thread and I believe that it is the approach that is most likely to yield a successful conclusion.

    Denis
      My Computer


  10. Posts : 11,396
    Windows 10 Home x64 Version 21H2 Build 19044.1706
       #10

    OldNavyGuy said:
    Same subject matter cross-posted in another TenForums thread here -

    https://www.tenforums.com/drivers-ha...ml#post1956176
    Yes, I told the OP to open a new thread and I believe that it is the approach that is most likely to yield a successful conclusion.

    Denis
      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 14:39.
Find Us




Windows 10 Forums