Jump to content
Posted 08 December 2008 - 08:51 PM
Posted 09 December 2008 - 04:20 AM
Here is my story. I have screwed my pc up a little bit through my own stupid choices; like trying to delete programs without knowing what they are.
Posted 09 December 2008 - 07:10 PM
Posted 10 December 2008 - 07:47 PM
Posted 11 December 2008 - 04:39 AM
Posted 11 December 2008 - 07:11 AM
Posted 11 December 2008 - 08:03 PM
Hi Crazy O
Did you try the second link for the repair instructions? When you did the scan, did you use a recovery disk? If you don't have a recovery disk, you can find the download links at the following website which is in German, but you'll see the links - one for 32, the other for 64bi - in the first post. If you click on this link you'll see that the access to this forum is delayed by an intermediate window encouraging you to register for the forum which then goes away and transfers you on to the forum. Since this requires a download, if you decide to make this, you'll need to create the ISO disk on a different computer. http://www.go-vista.de/forum/systemtools/vista-recovery-cd/
The content of the above link states basically - that when your Vista no longer runs smoothly, you can repair it with the installation disk. Some manufacturers however, don't deliver computers with either an installation or a repair disk. Because of this, this forum offers the two options for a recovery disk. These must be burned with an ISO image capability of something like Nero. You cannot use it to install Vista, but only for repair.
Posted 12 December 2008 - 03:59 AM
Posted 13 December 2008 - 01:43 PM
Posted 15 December 2008 - 11:44 AM
Posted 20 December 2008 - 12:47 PM
Posted 08 January 2009 - 10:19 PM
findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txtat the command line. The problem is that what this command does is find strings in CBS.log starting with that phrase in quotes, and then redirect these strings into another file called sfcdetails.txt (it will create the file if it doesn't exist yet), inside the working directory--meaning whatever directory you are in within the command prompt window when you execute the command. If your command prompt starts with
C:\Windows\System32at the beginning of the line before the cursor, then that is your working directory, and where sfcdetails.txt will be stored if it isn't there already. Most people giving this advice, and Microsoft's article, neglect to mention this. (Also, in my case--on the contrary to Microsoft's article--sfcdetails.txt does not already exist on my C: drive, even though I've run SFC at least a few times.)
Edited by hotshot309, 08 January 2009 - 10:21 PM.
0 members, 0 guests, 0 anonymous users