phermi
asked on
Error during installation of Vista service pack 1: Error Code: 0x80073712
The complete error message is:
Error code: 0x80073712. See http://go.microsoft.com/fwlink/?LinkId=101139 for details.
The link suggests the following actions:
1) Check for Updates - DONE. All updates are in.
2) Check for disk errors - DONE. No errors found, no bad sectors.
3) Run sfc /scannow ---> HERE IS THE PROBLEM (see below)
4) Run Vista memory diag too - DONE. No errors
sfc / scannow produce the attached report and my question is what it means and how it can be fixed.
Thanks in advanced.
sfcdetails.txt
Error code: 0x80073712. See http://go.microsoft.com/fwlink/?LinkId=101139 for details.
The link suggests the following actions:
1) Check for Updates - DONE. All updates are in.
2) Check for disk errors - DONE. No errors found, no bad sectors.
3) Run sfc /scannow ---> HERE IS THE PROBLEM (see below)
4) Run Vista memory diag too - DONE. No errors
sfc / scannow produce the attached report and my question is what it means and how it can be fixed.
Thanks in advanced.
sfcdetails.txt
ASKER
ebjers:
Thanks. I do not understand your reply. What error is not the complete error message?
What I attached are the SR records from the C:\Windows\Logs\CBS\CBS.lo g
The link you provided is for Vista Home and in any case, the pending.xml file does not exist on my system.
Thanks. I do not understand your reply. What error is not the complete error message?
What I attached are the SR records from the C:\Windows\Logs\CBS\CBS.lo
The link you provided is for Vista Home and in any case, the pending.xml file does not exist on my system.
Look in the event viewer for red X from the time you tried to install SP1 there should be more information there.
to open the event viewer click start and type eventvwr in the search bar
eb
to open the event viewer click start and type eventvwr in the search bar
eb
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check your event log and you should see a more detailed error message, cut and past the entire thing please.
eb