R Rexx New member Joined Apr 5, 2014 Posts 1 Apr 5, 2014 #1 Hello everyone, just before I post my problem, I would like to mention 2 things: 1. I CANNOT access Windows no matter what, all I can do is use command prompt from the boot repair options, therefore please do not suggest anything to do with BEING in actual Windows. 2. I DO NOT have a Windows installation disk and DO NOT have a Windows repair disk. Ok so now onto my problem: Yesterday, I have been cleaning my PC, as it worked slower than usual, I deleted a few empty folders here and there. I am certain I DID NOT touch anything to do with the system folders or the BIOS. Anyway, after I deleted any empty folders in my C: and D: drive, I did a complete (full) system scan with my Avast!anti-virus. It came up with 13 infected files. When I looked into them, they were ALL in the Temporary Internet Files on the C: drive. I tried every option, delete them, quarantine or repair- none of these options worked, EXCEPT for 1- this is the only file that had a number before the .dll part (17 or 19 I think- most or all of these 13 files ended with .dll). This one i was able to delete or repair, I cannot remember which one, I'm pretty sure I deleted it. Moving on, I couldn't do anything to these files, as Avast! said it's error: "Error: The operation is not supported for this type of archive. (42111)" Since I couldn't do anything, I simply left these files alone. I then tried to do a system restore, back to the 1st April, but got the message (paraphrasing): Error: Some files cannot be read or are corrupted/damages, the C: drive cannot be restored." So I switched off my PC and turned it back on. I got prompted to do a CHKDSK, so I let it do it's job (I used to skip this for the past dew days.) Anyway, at step 2/3 I think, between files (this is an approximate amount) 91360-92540, most messages read something along the lines of: "File cannot be read, it may be damaged and is unreadable." The other minority involved the file being moved or couldn't be repaired. My results at the end were: 3086 KB if space on drive 4 KB in 9 indexes 0 KB in damaged sectors 2485 KB used by system 2048 KB used by the event planning thing (such as when to perform a CHKDSK- I forgot the name of this) 597 KB available on drive 513 bytes in each allocation unit 6173 allocation units on drive 1195 available allocation units Could not transfer registered messages into the event planning thing. Error: 50 ..................................................................................................................................................................................................................... I'm sorry if the above names are not full correct, I as have a Polish OS and I tried my best in translating each component. Anyway, after the check finished, the PC restarted and did another CHKDSK with the exact same results and then did it once more. The fourth time it has worked. The options I was offered were either start startup repair or launch Windows normally. I selected the second option with no luck, I couldn't launch Windows successfully and was taken back to the startup repair, which didn't find a problem. As mentioned earlier, I couldn't do a system restore and couldn't access Windows itself. I couldn't restore a system image, as I never created one, and the memory diagnostic did not show any problems (when I attempted to do the full memory scan, it got stuck at 21% (a very common error.) So the only option I was left with (as I had not installation or repair disk) was to try and fix it using command prompt. The beginning of each line started with X:\windows\system32>. My first command was to do another CHKDSK, later a "CHKDSK /f" and "CHKDSK /r", however to no avail. I then typed in the command "sfc /scannow /offbootdir=c:\ /offwindir=d:\windows. After this, I got the message: "Windows Resource Protection found corrupt files but was unable to fix them. Details are included in the CBS.log windir\Logs\CBS\CBS.log. For example, C:\Windows\Logs\CSB\CSB.log." I typed in the command "cd /D %windir%" and pressed enter. Operation successful. Secondly, I typed in "icacls * /T /Q /C /RESET" and the message came up: Successfully processed however many files. Failed processing 0 files. Then I typed in "notepad" so that I could access the log file, from the option of 'open'. I searched through the drives, and went into drive D and located the CBS.log file. Now this is the part I need help with. I CAN copy the CBS file onto the desktop file (remember, I AM NOT IN WINDOWS, ONLY IN STARTUP CMD REPAIR.) On every single forum I wen to, everyone said that you have to take (administrative) possesion of this or a different file so that actual changes can be made to it. So, my question is what do I type into the command now? (NOTE: Please make this as simple as possible for me, since I have ABSOLUTELY no cluse as to what I'm doing, all of this was help from the internet!!!) So now that I know where exactly the CBS file is in, what do I type in? The type of answer I'm looking for is something like this: X:\windows\system32>WHATEVER YOU NEED TO TAKE POSSESION OF THE CBS FILE AND THEN: X:\windows\system32>WHATEVER YOU NEED TO DO TO ACTUALLY FIX THESE CORRUPTED FILES NOW AND ANY OTHER STEPS I NEED TO TAKE (please do this step-by-step using simple language.) Basically, this thread is another one of those, "how do I fix corrupted files on my drive, but the reason I've included so much detail, it because I NEED THIS REPAIRED ASAP, and it will be quicker for me to do this myself, rather than going to PC repair. Any extra info you would like to tell me, feel free. One note I forgot to mention: I have downloaded the iso. repair disk from Microsoft and launched Windows through that- it has repaired 1 or 2 files, the CD contained KB2823324 and KB2782476 . I would be grateful if you can tell me the exact command in CMD, starting with X:\windows\system32> Thanks in advance :) LAST NOTE: I am not able to do a sfc /scannow for some reason, I AM NOT give the option of y or n for next system start check, therefore sfc cannot help me if it's with scannow.