Main Forum > General Computer Support
(SOLVED) 0x80070005 error after running Windows Repair All In One
Shane:
Well the chkdsk is the first step. So there is a way to do it from the recovery console.
Here is one way to do it
http://surrealparadigm.com/?p=185
Since you can get a command window there you can run chkdsk from there, which will be ran from the recovery files and not the ones on the system.
Once you get to the command window there you are going to want to make sure what drive letter it mapped the windows drive to
so in the cmd window type in
cd C:\
and hit enter, the prompt should change to the C:\ drive. If it did then do
dir
and hit enter, this will list the folders and files. Look at those to confirm that is the correct windows drive letter.
If so do the command
chkdsk c: /f /r
and let it does it thing.
Shane
recognizer:
Get this - I turned off UAC and it let me look at the permissions for all the problematic folders in question. Somehow all the permissions for every account had been removed. Bizarre! It's like Windows just lost all the permissions data for every file except the basic system files.
I added my own account back in with full control and now I can see the contents of the folders... at this point it seems like I shouldn't have too much trouble backing up my files and then fixing my Windows installation without worrying about my data. Thanks for your suggestions and sorry to bother you with such a strange issue.
Shane:
The permissions for the files are stored in the file system. This is why you use NTFS when you need permissions as FAT32 doesnt have that option and its size limits. So again it points back to the drive and or the file system.
First thing is get your data off of there as soon as you can, and then, one way or another, do that bad sector check on the drive. Put the drive in the other system and do it there if you can :-)
Shane
recognizer:
After backing up everything and doing a system restore on the machine, chkdsk reports no errors and I'm able to install software, etc as normal (plus the firewall settings I was trying to fix in the first place seem to be cleared up).
I believe what happened was that there was an error in Windows somewhere while Windows Repair was doing one of the first three steps - Reset Registry Permissions, Reset File Permissions, or Reset Service Permissions - and that Windows didn't notify me of this error, meaning that some part of my system was left with crucial permissions not set at all.
Shane:
If the file system did have errors in it and the program was trying to set permissions (Which are store on the file system) then all kinds of things would happen. Which sounds like that is what happened.
Now that you got the file system fixed everything is working like it should. Good to hear you got it back and going. :cheesy:
Shane
Navigation
[0] Message Index
[*] Previous page
Go to full version