Unable to Perform a System Restore

[shstudent]

Hi All

I am here again trying to get my pc to operate as it used to. I tried to do a System Restore several times, without success. The computer goes through the motion, shuts down, restarts, then gives me the following message:
View attachment System Restore.docx

I'd be grateful for some help with this. I have been trying about two weeks now and think that once the System Restore is achieved, other issues will be resolved.

Thanks much.

 

[whs]

This restore point is apparently no good - maybe corrupted. Can you try other restore points.

 

[shstudent]

Thanks for replying "whs". I've tried others, but have gotten the same result.

 

[whs]

Maybe your VSS service got a dent. Can you run the 2 commands below in an elevated command prompt and post the results. But please in clear text - not a snip of the cmd window.

For that you right click on the cmd window when the results are posted and click on 'Select All'. Then you right click again (any place) and the whole stuff is on the clipboard. Then you just paste it into your answer here.

vssadmin list providers

vssadmin list writers

 

[shstudent]

Hi whs, sorry for the delay. Here is the result of what you instructed:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7


C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error

Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error

Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {188d7390-bcef-4dfa-b428-88a9443ebc53}
State: [5] Waiting for completion
Last error: No error

Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {8d806c17-8ce7-485f-a927-f60d58dacebd}
State: [5] Waiting for completion
Last error: No error

Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {70b2a268-9247-42fb-97f5-06fd323c9b7b}
State: [1] Stable
Last error: No error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {921eaeb1-75d9-468c-aedf-54215e4708ee}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {6bc86204-fe06-4cb0-9237-a0611265418c}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {f2101ab1-aaea-4b4c-b2d6-2cc655ece54c}
State: [1] Stable
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {e8ca0cad-22b8-4073-83b1-006eedbb0d4c}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {c7b2ce40-a3c4-4c0d-8ceb-f66281b242bf}
State: [1] Stable
Last error: No error


C:\Windows\system32>

 

[whs]

Hmm, this is a bit strange. You have 3 .dlls with state 5 which is not normal. You can try to fix that with a startup/repair - or if you are adventurous, you can try this autmatic fix proposed by Macrium. This is an .exe for x64 systems that you have to save some place and then run.

http://updates.macrium.com/reflect/utilities/vssfixx64.exe

Note that I have never used that Macrium fix so I am not 100% certain what it does. It may only address the Provider which is OK in your case.

 

[shstudent]

Hi whs

I tried the automatic fix you proposed but the problems persist. Unfortunately, I did not get an installation disc with the pc.

I then went on to running the "sfc /scannow" in elevated mode (as instructed elsewhere on this site). I did this about three times. The result is that there were errors, some of which were not fixed. I want to post the log file so that you could review it but it is is quite large (106MB). What do you suggest?

Looking forward to your response. Thanks.

 

[whs]

1. Burn a recovery disc from your recovery partition. Look here Control Panel\System and Security\Backup and Restore and then in the left pane you will see.

2. Run a startup/repair: http://www.sevenforums.com/tutorials/681-startup-repair.html