![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi !
I have windows 8.1 32 pro edition in C partition, Windows 7 32 bit pro in drive D and E has only data. I have installed windows 7 recently (in past 15 days). I am getting error "we found some error on this drive" Restart this drive to repair the drive". Status is important. Further it is also written there "Restart your drive to prevent the lose of data". This happened first time yesterday 3 time. First time it got update and was installing this. I hope the issue would get resolve after this...
Later on yesterday it asked me again and I restarted my PC. Now it has asked me again. I need your help to solve this issue. One thing I want to ask in the process of updating if someone closed the lid by mistake then does it matter on process of installing update? Actually I had restored the default plan for battery last night and forgot to change "choose what closing the lid does".) I closed the lid but after when I open the lid it started installing update.
Don't hesitate for further info...
your help will be appreciated...
Thanks in Advance...
I doubt interrupting an update caused any real problems if you say that it began the installation of the same update later on. My post was really just to let people know that uninstalling Lavasoft Ada-aware fixed my problems as well as several other peoples' issue.
That being said, if you tried clicking on the icon to restart to repair drives and nothing was fixed, and you don't have an issue with Ad-aware, some other things can be contributing to this problem. You should check under event viewer to see what kinds (if any) errors you have had, and click on any recent ones. There was definitely nothing physically wrong with my drives, just as another poster said, but there was an issue with shadow copy having a corrupt file system which caused some of the problems. If you find that your errors say something to the effect that the file structure is corrupt, but that it cannot locate the drive, and it gives you an address that looks like a couple of question marks followed by a massive hexadecimal address enclosed in parentheses (in other words a couple question marks and a bunch of numbers and letters separated by dashes and enclosed in these things - > { } ).
If the shadow copy is coming up as what is not repaired, do a google search for "corrupt shadow copy file structure". You might have to play around with the words for a bit, but there should be a tutorial somewhere. That's how I ended up fixing that part of the problem. You can also find the shadowcopy service by right clicking the windows 8.1 start icon in the lower left, selecting Computer Management> Services and Applications> Services and then finding the service called "Volume Shadow Copy" in the right hand column. That will probably be part of any tutorial you find on how to fix the problem.
Finally, I also had errors showing that the maximum filesize of Readyboot (Readyboot, NOT Readyboost) had been exceeded and that it could cause logging for other programs to fail. Again, a google search of "readyboot has reached maximum filesize" should lead to a tutorial on how to increase it in size, but if this is happening to you, a more important additional step is to look up readyboot and from there change the setting for the service to overwrite the file when it exceeds its limit. You should still increase the filesize. To do this, once again you must right click the start/window icon in the lower left and then select Computer Management> Performance> Data Collector Sets> Startup Event Trace Sessions and then doubleclick the program ReadyBoot. There are quite a few tabs, but you should be concerned with 2. The first is simply "File" and make sure the option "Circular" is checked/selected. This will allow the file to overwrite itself instead of just crashing when the maximum filesize is reached. The other tab to click on is "Stop Condition". After selecting it, near the bottom you will see the maximum filesize which is probably set to something like 20 MB. If you were having the maximum filesize error, that is too low. The tutorial I found suggested changing it to 120 MB, which is what I suggest you do, and then click "apply" obviously. But remember to also select the "Circular" logging from the "File" tab, or the log will just continue to grow and the problem will just re-appear, and waste memory or disk space.
Well that certainly went way off topic from my original suggestion of simply uninstalling adaware if you were running it to see if it fixed the problem. If you are having the other problems I mentioned, try following the steps I suggested. Unfortunately, I am not a tech or a hacker, so there isn't much more I can suggest.
The real problem here is that this error has been occurring since at least Windows 7 (in other words for years) and Microsoft has still not bothered to fix it after all this time (unless they are oblivious to a bug affecting thousands of users). That shows how poor Microsoft products are, and why computer manufacturers need to get behind a new operating system, even if they have to band together and code it themselves. They would save in the long run by owning the rights to their own operating system, being able to provide full install system discs (all of 50 cents if not less) and providing competition for Microsoft (No offense to Linux or Apple users, but they just aren't a real threat to Microsoft). That's just my opinion.
Anyway, I hope something I told you helps you out.