Windows 10: How to Remove Dirty Bit from Drive with Windows Installed on It

About a week and a half ago, my PC started scanning and repairing the C drive (which has windows installed on it) every time I would boot the computer. It never shows a percentage. It just shows "Scanning and repairing drive C..." and then after a few seconds it boots up without issue. When I ran FSUTIL DIRTY QUERY c: it said that the drive is dirty. When I run CHKDSK /C /F it tells me that it can't fix the drive because it's currently in use (obviously, because I'm using Windows and Windows is installed on it). It also says that it will run the fix when I reboot. Then it does the same thing again on boot.

It seems like it's not actually checking the drive because it never shows a percentage and nothing ever gets fixed. Another way I know there's a problem is when I right click on the drive and go to properties and click on Tools and then Scan it, it tells me there's a problem and to restart to scan the disc. Same thing on boot again.

Am I doing something wrong? Can anyone offer some insight on how to fix this issue of constantly scanning and repairing a drive that has Windows 10 installed on it. I'll be glad to list any pertinent specs you need me to.

Edit: If this is the wrong place to ask this question, I would appreciate a point in the right direction. Thanks!

submitted by /u/ImGuss
[link] [comments]

:)

 

windows xp installation and dual core am

could someone please list the steps they follow to install windows with a dual core processor and windows xp service pack to. I'm reletively new to amd dual core and i feel i'm missing a step. All help will be appreciated. thanx

 

Hard drive/ OS issue

a guy suggested :

• shutdown
• unhooked HDD
• restarted
• yay !!
• reconnected HDD
• restarted
• yay !!

also , try method 3
How do I unlock the drive where Windows 10 is installed?

 

Dirty Bit not same state on the two possible Command Prompts

Using Windows 10. When I enter Command Prompt with holding down shift key when restarting and using fsutil dirty query c: , the Dirty Bit state is 0 or off. When I enter Command Prompt (Admin) from running the Windows program and using fsutil
dirty query c: , the Dirty Bit is 1 or on. I think the latter condition is why I always get the Disk Check running notification when booting up. I've tried everything to clear the latter mentioned Dirty Bit state but nothing works. I saw one suggestion
to use a hex editor and actually go into the Bios? to put the Dirty Bit state back to 0, but don't feel comfortable with that. The disk check using
dskchk c: /f /r in the first mentioned Command Prompt shows the disk has no problems. Why are the Dirty Bit settings different? Could this be why Macruim does not want to clone the disk?

Thanks for any help and comments.