Saving Disabled in Vista Home Basic

Suddenly Vista Home Basic does not save any changes after reboot.

In addition, Check Disk & Memory Diagnostics do not function although it is not known if this type of problem occurred simultaneously with the no change save.

Hopefully someone has experience with these symptoms and will advise remedies.

THANK YOU!

Are you using a user or administrator account.
Go to start,all programs,accessories,command prompt.
Right click and run as administrator.
In the box that opens type
SFC /Scannow
Note the space after the c
If it find any errors run the scan again
If after running it again errors are still showing post back for instructions on how to post the report it has created.

Thank you, your instruction worked great!

Subsequent to the two scans there are errors that could not be fixed.

The notification states....details are included in the CBS.log windir\Logs\CBS\CBS.log For example

C:\Windows\Logs\CBS\CBS.log

It will be tuesday of next week when can return to the challenge again.

Thank you again and look forward to your instructions as to how post the information.

The CBS Log file is 48.0 megabytes, and CBS persist log is 108 MB.
Starting at October 12 and including all to October 19th there must be a thousand pages in the CBS Log file, none of the inforfmation contained in that file is readily decipherable to me. Perhaps it would be better to do a repair to Windows from the Recovery DVDs?

1. Click Start
   
   
   
   , type cmd in the Start Search box, right-click cmd in the Programs list, and then click Run as administrator.
   
   
   
   
   
   If you are prompted for an administrator password or for a confirmation, type your password, or click Continue.
2. Type the following command, and then press ENTER: findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt

Then copy the much smaller .txt file to your desktop and attach it from there to your next reply (it's also much easier to read).

Thanks and Good luck!

danadams said:

Thank you, your instruction worked great!

Subsequent to the two scans there are errors that could not be fixed.

The notification states....details are included in the CBS.log windir\Logs\CBS\CBS.log For example

C:\Windows\Logs\CBS\CBS.log

It will be tuesday of next week when can return to the challenge again.

Thank you again and look forward to your instructions as to how post the information.

Click to expand...

How to retreive the cbs log after system file check is completed :

(1 ) Full version
Right click on cmd ( command prompt ) > Run As Administrator > at the flashing prompt, type
notepad C:\windows\logs\cbs\cbs.log > press Enter key


Note : there is a space between " notepad " and " C "

A notepad will show up with your cbs log.

( 2 ) short version
Right click on cmd ( command prompt ) > Run As Administrator > at the flashing prompt, type
sfcdetails.txt > press Enter key

A notepad will show up with the log.

Hi
Had a bit of a delay as had to uninstall the Windows SDK (it had taken control of the command (shell) and therfore cmd.

Okay, tried both sets of instuctions including that > sign at the end of the first. The first instruction results in a slight delay then a return to the command prompt (C:\Windows\system32. Also tried cbs as CBS with the same result.

The second method (short version) does produce the Notepad but the content is blank.

I had a look at the CBS log on Oct. 19th with Notepad and there was an enormous amount of detail in that log, Oct 12th for example must be 200 pages.

So far I have not succeeded in getting a short file. Thank you very much for your efforts!!!

Am making a list of installed programs and transferring uninstalled programs to DVD disks so can later reinstall and retrieve in the event that it is necessary to repair the operating system.

Still though, there must be a method of finding a short version of the problem.

Thnaks again.

Think of > as being the word "next" don't type it.

danadams said:

Hi
Had a bit of a delay as had to uninstall the Windows SDK (it had taken control of the command (shell) and therfore cmd.

Okay, tried both sets of instuctions including that > sign at the end of the first. The first instruction results in a slight delay then a return to the command prompt (C:\Windows\system32. Also tried cbs as CBS with the same result.

The second method (short version) does produce the Notepad but the content is blank.

I had a look at the CBS log on Oct. 19th with Notepad and there was an enormous amount of detail in that log, Oct 12th for example must be 200 pages.

So far I have not succeeded in getting a short file. Thank you very much for your efforts!!!

Am making a list of installed programs and transferring uninstalled programs to DVD disks so can later reinstall and retrieve in the event that it is necessary to repair the operating system.

Still though, there must be a method of finding a short version of the problem.

Thnaks again.

Click to expand...

There is a BIG misunderstanding .....
That " > " sign means " next step "
Perhaps this would clear the misunderstanding:

Right click on cmd ( command prompt ), next step, click Run As Administrator, next step, at the flashing prompt, type notepad C:\windows\logs\cbs\cbs.log , next step, press Enter key

I hope that clears the meaning of the > sign ?

Open command prompt as administrator and copy and paste the bold type from the post above. It may take a couple of minutes to fill the notepad page. The above is a good method, I have just tried it,works sweet.

The procedure in http://www.vistax64.com/general-discussion/284047-saving-disabled-vista-home-basic.html#post1294136 also works to produce the text file. Just copy the text to enter directly from the post (so you get the spacing correct). Then go to created text file and right click on it and click copy. Then go to the desktop and click paste.

There are many roads to Rome. Choose whichever you prefer and that works and produces a text file of manageable size that you can attach.

I hope this helps.

Good luck!