25 total posts
We can run CHKDSK off a Windows DVD as well.
This way, there is nothing stopping CHKDSK other than hardware issues.
But your first step is to confirm the backups of what you can't lose are done.
Before I get into running CHKDSK from DVD or USB I'll share I use the CHKDSK off a W10 USB install stick and think we should read your Web Speccy report from https://www.piriform.com/docs/speccy/using-speccy/publishing-a-speccy-profile-to-the-web which will give me your HDD health report and maybe more.
https://neosmart.net/wiki/chkdsk/ covers how to run CHKDSK from almost any of the Windows boot CD/DVD and USB. ALWAYS use the same if not higher version of Windows for the boot disc/USB.
Doesn't answer my question
Thanks for your response, however, it doesn't really answer my question. I'm sorry I didn't make that clear. What can I do to make chkdsk work properly on my machine?
Re: run properly from your machine
By running it from the Windows install DVD or the hirens boot cd. That's easy, isn't it?
My advice is to avoid a wipe out.
Since I don't know everything about the state of your OS (drivers, damage, apps and more) my advice is to use the other ways to run chkdsk and see if that gets a good chkdsk result. Then it may be possible that chkdsk will work as I've seen cases where the chkdsk on the HDD can't resolve the issue and then running it from DVD/USB/CD fixes it and then it works.
If all this is unacceptable then we have to wipe the drive clean, install the OS, apps, drivers and see if that fixed it.
Since you can now get into safe mode does chkdsk work from there?
chkdsk does not work in safe mode
Thanks Bob__B for your suggestion, but no, it does not work in safe mode. I get the same error thing as before. Based on my theory that EaseUs made changes to my registry that weren't cleared up upon the uninstall, could I possibly go into the registry and delete all references to EaseUs Todo Backup Free?
Yes, this is my error.
OK, let me begin this post by saying, I'm sorry I have you guys going in so many directions. I appreciate all of you so much, but as you can tell by now, this is my first time at this posting to a forum business. Please bear with me. Also, I don't have a lot of time to dedicate to this.
I tried to run chkdsk on C: from my Windows 7 install disc, but it said I couldn't do that because that drive was protected. After reviewing everything so far, I think I would like to do the Speccy report thing, so please give me some time to do that. It may take me a couple days before I can get back to it. Thanks.
Please supply the exact "protected" error message.
Is there any disk encryption going on here or maybe a root kit? Some root kits can cause all the above I've read.
OK, I'm back.
In order to supply you with the exact "protection" error, I had to try running chkdsk from the Windows 7 install disc again. This time I was able to get chkdsk to work enough for it to ask me if I wanted to make it run on the next boot. I selected that, but when it rebooted, chkdsk failed to interrupt the boot sequence. It went straight to the usual boot. It may be because the Windows 7 disc is a preinstallation disc for Microsoft Refurbishers.
I have included the Speccy report here: http://speccy.piriform.com/results/zrBmhxStGPF6jfH8z2t48uA
I don't know if I did it right because it didn't turn red like yours did. Anyway, I hope you can view it.
I will be having surgery tomorrow, so I don't know when I will be able to get back to this. Thanks again for your patience.
Many possible issues in that report.
1. 465GB Maxone USB 3.0 USB Device (USB)
7GB Kingston DataTraveler 2.0 USB Device (USB)
These should be unplugged for boot time chkdsk checks.
2. The CHKDSK from the Windows 7 DVD is suspect. I've been using my W10 USB install stick to run CHKDSK on machines from XP to 10. But that's a long story.
3. I see Norton and Everyday Backup. These could interfere with boot time CHKDSK. Norton is notorious about it's boot time protection so that much be removed.
Bin that disk.
Get a new one quick and hope you can clone old > new before old decides to croak.
Notice all the errors smart is showing?
The drive indeed looks to have errors.
I see other issues as well.
If the disk decides to fail then the op is looking at a bare metal install.
Most folks are not prepared for that.
If the clone functions and the chkdsk problem follows to the new disk then it's time to chase that.
OK, I'm back with... you guessed it, new problems.
It sounds like you guys are talking to each other in geek talk, or something. I understand part of it but, Bob__B, when you talk about "smart" errors, you are talking about the C: drive, right? It has actually been suspect for a while, ever since I tried to make an image with the Windows tool and it wouldn't do it because of some bad clusters. That's why I went to using the EaseUS Todo program and the Maxone to house the image. Maybe all I need now is to get a new hard drive and load that image onto it. What do you think?
In trying to get the chkdsk to work, it said, "Cannot lock current drive. 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? <yes/no>"
I didn't know if I should say yes or no, so I went with no and it just booted normal. Would it have been alright to say yes?
I also was able to run a sfc scannow. The result said, "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log windir\Logs\CBS\CBS.log." However, when I went to that log file, I could not open it because I didn't have the right permissions.
Next, I tried disconnecting the two USB drives while running chkdsk, but to no avail. And because I have Norton set to automatically upgrade to the latest version, that latest version does not allow me to temporarily bypass it's boot time protection like I used to do.
When a drive is failing, you might not be able to
Clone it. Let's hope after all this your files are safe on backups and you are ready for this drive to fail.
Let's not mince words here. The drive is failing. Cloning, CHKDSK and more should fail. There are some that want a fix for a failing drive and they keep asking how to fix the drive. Answer? Put in a new good drive. Can be cheap.
As to the Yes/No question.
Unless you answer Yes, chkdsk won't run. And it still might not run for the many reasons above.
That's settled; I'm getting a new drive.
Thanks for your patience and good advice. You guys are the best!
I think I'm supposed to do something to close this thread, but I don't see any way to do it here. I hope this is enough.
Chkdsk problems DID follow.
I bought a new hdd and got the clone transferred to the new one. Everything seems to be working fine except now chkdsk still does not work. It shows the same error. I have included a new Speccy report here: http://speccy.piriform.com/results/1ZVD84PJ3GtWjBRVu8CiexQ
There are some errors that CHKDSK never did fix.
I had two drives, both NTFS and chkdsk never could fix the file system errors. One had to go back to production so we wiped the drive and started fresh. Cured.
The second was a second work machine that I used so I left it as-is so I could try things. 2 years and many tools yet never could get a clean file system. We tried booting a Windows DVD and running chkdsk from the dvd so we were sure the HDD was open to change and no issues with possible corrupted Windows. Linux fsck of many versions was tried and something from piriform.
After 5 years we replaced that machine so the consensus is there are some file system errors that today's tools will not repair.
I see I asked for the protected message and can't find the answer. I wonder if it's the old "Write Protected" message. If so, try the method at https://www.easeus.com/resource/windows-cannot-run-disk-checking-on-this-volume-because-it-is-write-protected.html
We've tried to avoid a wipe out but I'm missing the answer to my question above.
That out of the way, did you try clearing the dirty bit? How, why and other musings at:
chkdsk worked... I think.
In order to replicate the "Write Protected" message that I got a while ago, I booted to the Windows 7 install disk again. After asking to run chkdsk /f on my new drive c:, I got the thing asking me, "Would you like to force a dismount on this volume? <yes/no>". This time I chose "yes" and what happened next was very strange to me. Chkdsk suddenly went through three different checks in less than two seconds, and then gave me this answer: "Windows has checked the file system and found no problems."
When I was looking over your link to EaseUS.com, the wording of the "Write Protected" problem there looked exactly as I remember mine was. However, some of the solutions offered there (and in the other link you sent) seemed too dangerous for me to try. Anyway, I'm satisfied for now. Thanks again for all your help!
Now try it this way
Start>computer>right click your C drive>properties>tools>error checking.
That should schedule a chkdsk at the next boot.
You will have to use the event viewer to see the results.
As they say. "Any road that gets you there."
I've see folk get all so close then answer no and the chkdsk doesn't get done.
-> In parting all the moderators say "we only lose what we don't backup." So now is the time to secure your backups.