G
Guest
I get the response "error code 0x000006ba RPC server is unavailable" - how
do I correct this problem?
(e-mail address removed)
do I correct this problem?
(e-mail address removed)
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
P
Pop`
Herb said:I get the response "error code 0x000006ba RPC server is unavailable"
- how do I correct this problem?
(e-mail address removed)
Start the RPC (Remote Procedure Call) service. Set it to Manual or
Automatic. If it's already set to manual, set it to Automatic. If you
don't know how, post back. Either it or one of its dependents are unable to
run.
Pop
G
Gerry Cornell
Herb
You receive a "The RPC server is unavailable" error message when you open
Disk Management in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;884564
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
You receive a "The RPC server is unavailable" error message when you open
Disk Management in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;884564
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
G
Guest
I'll give it a try -sounds too easy to be real!
Herb
Herb
G
Guest
Nope - starting all rpcs on automatic and it still won't runn sfc /scannow
W
WTC
Herb said:I get the response "error code 0x000006ba RPC server is unavailable"
- how do I correct this problem?
This /may/ help you even though the article is for Windows 2000..
Windows File Protection may not start
http://support.microsoft.com/kb/296241
Trusted root certificates that are required by Windows Server 2003, by
Windows XP, and by Windows 2000
http://support.microsoft.com/kb/293781/
G
Guest
link to mspage gets a this page isn't working response
J
Joe
Herb said:link to mspage gets a this page isn't working response
Both the links work.. Could you possibly have something such as a
firewall, or maybe even malware blocking the MS site?
W
WTC
Herb,
The page is working fine for me. So I quoted a large section from KB296241 for you.
<a very big quote from KB296241>
When you attempt to use the sfc /scannow command, the command may not work, and you may receive the following error message:
Windows File Protection could not be initiate a scan of protected system files. The specific code is 0x000006ba [The RPC Server is unavailable.].
Back to the top
CAUSE
This behavior can occur if the certificate for VeriSign time stamping has been removed from the computer. This certificate is listed as: "Issued To: No Liability Accepted, (c)97 VeriSign, Inc.".
To determine whether this certificate has been removed from the system, follow these steps: 1. Locate a Windows 2000-based computer that exhibits these symptoms.
2. Click Start, click Run, type mmc, and then click OK.
3. In the Microsoft Management Console, click Console, and then click Add/Remove Snap-in.
4. In the Add/Remove dialog box, click Add.
5. Click Certificates, and then click Add.
6. Click Computer Account, and then click Next.
7. Click Local Computer, and then click Finish.
8. Click Close, and then click OK.
9. In the console tree, double-click Certificates (Local Computer).
10. Double-click Trusted Root Certificate Authorities, and then click Certificates.
11. In the details pane, locate the No Liability Accepted certificate. If the certificate is missing, follow the steps in the "Resolution" section to export the certificate from another workstation and import it.
Back to the top
RESOLUTION
To resolve this behavior, the certificate needs to be restored to the original location. To export the certificate from a Windows 2000-based computer, follow these steps: 1. Locate a Windows 2000-based computer.
2. Click Start, and then click Run.
3. In the Open box, type: MMC.
4. When Microsoft Management Console (MMC) is displayed, click Console, and then click Add/Remove Snap-in.
5. On the Add/Remove window, click Add.
6. When the list of available snap-ins are displayed, click Certificates, and then click Add.
7. Click Computer Account.
8. Click Next.
9. Click Local Computer, and then click Finish.
10. Click Close, and then click OK to close out the Add/Remove Snap-in window.
11. Under Console Root, double-click Certificates (Local Computer).
12. Double-click Trusted Root Certificate Authorities, and then double-click Certificates.
13. In the right pane, the installed certificates are displayed. Scroll down the list until you locate the No Liability Accepted certificate.
14. Right-click this certificate, click All Tasks, and then click Export.
15. On the Export Wizard, click Next, click DER encoded Library X.509, and then click Next.
16. In the File name box, enter a file name to save the file (for example, C:\Cert). A .cer extension is added to the file name.
17. Transfer this file to the computer that is receiving the error message.
When the file is transferred to the computer that is receiving the error message, follow these steps to import the file: 1. Click Start, and then click Run.
2. In the Open box, type: MMC.
3. When the MMC starts, click Console, and then click Add/Remove Snap-in.
4. On the Add/Remove Window, click Add.
5. When the list of available snap-ins are displayed, click Certificates, and then click Add.
6. Click Computer Account.
7. Click Next.
8. Click Local Computer, and then click Finish.
9. Click Close, and then click OK to close out the Add/Remove Snap-In window.
10. Under Console Root, double-click Certificates (Local Computer).
11. Right-click Trusted Root Certificate Authorities, click All Tasks, and then click Import.
12. On the wizard, click Next, and then locate the file that you transferred from the other computer. (You may have to change the "Files of Type" field to display the X.509 certificates.)
13. When the file is selected, click Next.
14. Place the certificate in the Trusted Root Certificate Authorities Store, and then click Next.
15. Click Finish. A dialog box is displayed that indicates if the import operation had been successful or not.
16. When the certificate has been transferred, restart the computer, and then observe if the behavior is resolved.
Back to the top
MORE INFORMATION
For more information about Trusted Root certificates, click the following article numbers to view the articles in the Microsoft Knowledge Base:
293781 (http://support.microsoft.com/kb/293781/) Trusted root certificates that are required by Windows Server 2003, by Windows XP, and by Windows 2000
222193 (http://support.microsoft.com/kb/222193/) Description of the Windows File Protection feature
</a very big quote from KB296241>
The page is working fine for me. So I quoted a large section from KB296241 for you.
<a very big quote from KB296241>
When you attempt to use the sfc /scannow command, the command may not work, and you may receive the following error message:
Windows File Protection could not be initiate a scan of protected system files. The specific code is 0x000006ba [The RPC Server is unavailable.].
Back to the top
CAUSE
This behavior can occur if the certificate for VeriSign time stamping has been removed from the computer. This certificate is listed as: "Issued To: No Liability Accepted, (c)97 VeriSign, Inc.".
To determine whether this certificate has been removed from the system, follow these steps: 1. Locate a Windows 2000-based computer that exhibits these symptoms.
2. Click Start, click Run, type mmc, and then click OK.
3. In the Microsoft Management Console, click Console, and then click Add/Remove Snap-in.
4. In the Add/Remove dialog box, click Add.
5. Click Certificates, and then click Add.
6. Click Computer Account, and then click Next.
7. Click Local Computer, and then click Finish.
8. Click Close, and then click OK.
9. In the console tree, double-click Certificates (Local Computer).
10. Double-click Trusted Root Certificate Authorities, and then click Certificates.
11. In the details pane, locate the No Liability Accepted certificate. If the certificate is missing, follow the steps in the "Resolution" section to export the certificate from another workstation and import it.
Back to the top
RESOLUTION
To resolve this behavior, the certificate needs to be restored to the original location. To export the certificate from a Windows 2000-based computer, follow these steps: 1. Locate a Windows 2000-based computer.
2. Click Start, and then click Run.
3. In the Open box, type: MMC.
4. When Microsoft Management Console (MMC) is displayed, click Console, and then click Add/Remove Snap-in.
5. On the Add/Remove window, click Add.
6. When the list of available snap-ins are displayed, click Certificates, and then click Add.
7. Click Computer Account.
8. Click Next.
9. Click Local Computer, and then click Finish.
10. Click Close, and then click OK to close out the Add/Remove Snap-in window.
11. Under Console Root, double-click Certificates (Local Computer).
12. Double-click Trusted Root Certificate Authorities, and then double-click Certificates.
13. In the right pane, the installed certificates are displayed. Scroll down the list until you locate the No Liability Accepted certificate.
14. Right-click this certificate, click All Tasks, and then click Export.
15. On the Export Wizard, click Next, click DER encoded Library X.509, and then click Next.
16. In the File name box, enter a file name to save the file (for example, C:\Cert). A .cer extension is added to the file name.
17. Transfer this file to the computer that is receiving the error message.
When the file is transferred to the computer that is receiving the error message, follow these steps to import the file: 1. Click Start, and then click Run.
2. In the Open box, type: MMC.
3. When the MMC starts, click Console, and then click Add/Remove Snap-in.
4. On the Add/Remove Window, click Add.
5. When the list of available snap-ins are displayed, click Certificates, and then click Add.
6. Click Computer Account.
7. Click Next.
8. Click Local Computer, and then click Finish.
9. Click Close, and then click OK to close out the Add/Remove Snap-In window.
10. Under Console Root, double-click Certificates (Local Computer).
11. Right-click Trusted Root Certificate Authorities, click All Tasks, and then click Import.
12. On the wizard, click Next, and then locate the file that you transferred from the other computer. (You may have to change the "Files of Type" field to display the X.509 certificates.)
13. When the file is selected, click Next.
14. Place the certificate in the Trusted Root Certificate Authorities Store, and then click Next.
15. Click Finish. A dialog box is displayed that indicates if the import operation had been successful or not.
16. When the certificate has been transferred, restart the computer, and then observe if the behavior is resolved.
Back to the top
MORE INFORMATION
For more information about Trusted Root certificates, click the following article numbers to view the articles in the Microsoft Knowledge Base:
293781 (http://support.microsoft.com/kb/293781/) Trusted root certificates that are required by Windows Server 2003, by Windows XP, and by Windows 2000
222193 (http://support.microsoft.com/kb/222193/) Description of the Windows File Protection feature
</a very big quote from KB296241>
G
Guest
Went through these processes and the Certificate is present. Set it for all
functions, restarted and sfc /scannow still won't run!
--
Herb
functions, restarted and sfc /scannow still won't run!
--
Herb
WTC said:Herb,
The page is working fine for me. So I quoted a large section from KB296241 for you.
<a very big quote from KB296241>
When you attempt to use the sfc /scannow command, the command may not work, and you may receive the following error message:
Windows File Protection could not be initiate a scan of protected system files. The specific code is 0x000006ba [The RPC Server is unavailable.].
Back to the top
CAUSE
This behavior can occur if the certificate for VeriSign time stamping has been removed from the computer. This certificate is listed as: "Issued To: No Liability Accepted, (c)97 VeriSign, Inc.".
To determine whether this certificate has been removed from the system, follow these steps: 1. Locate a Windows 2000-based computer that exhibits these symptoms.
2. Click Start, click Run, type mmc, and then click OK.
3. In the Microsoft Management Console, click Console, and then click Add/Remove Snap-in.
4. In the Add/Remove dialog box, click Add.
5. Click Certificates, and then click Add.
6. Click Computer Account, and then click Next.
7. Click Local Computer, and then click Finish.
8. Click Close, and then click OK.
9. In the console tree, double-click Certificates (Local Computer).
10. Double-click Trusted Root Certificate Authorities, and then click Certificates.
11. In the details pane, locate the No Liability Accepted certificate. If the certificate is missing, follow the steps in the "Resolution" section to export the certificate from another workstation and import it.
Back to the top
RESOLUTION
To resolve this behavior, the certificate needs to be restored to the original location. To export the certificate from a Windows 2000-based computer, follow these steps: 1. Locate a Windows 2000-based computer.
2. Click Start, and then click Run.
3. In the Open box, type: MMC.
4. When Microsoft Management Console (MMC) is displayed, click Console, and then click Add/Remove Snap-in.
5. On the Add/Remove window, click Add.
6. When the list of available snap-ins are displayed, click Certificates, and then click Add.
7. Click Computer Account.
8. Click Next.
9. Click Local Computer, and then click Finish.
10. Click Close, and then click OK to close out the Add/Remove Snap-in window.
11. Under Console Root, double-click Certificates (Local Computer).
12. Double-click Trusted Root Certificate Authorities, and then double-click Certificates.
13. In the right pane, the installed certificates are displayed. Scroll down the list until you locate the No Liability Accepted certificate.
14. Right-click this certificate, click All Tasks, and then click Export.
15. On the Export Wizard, click Next, click DER encoded Library X.509, and then click Next.
16. In the File name box, enter a file name to save the file (for example, C:\Cert). A .cer extension is added to the file name.
17. Transfer this file to the computer that is receiving the error message.
When the file is transferred to the computer that is receiving the error message, follow these steps to import the file: 1. Click Start, and then click Run.
2. In the Open box, type: MMC.
3. When the MMC starts, click Console, and then click Add/Remove Snap-in.
4. On the Add/Remove Window, click Add.
5. When the list of available snap-ins are displayed, click Certificates, and then click Add.
6. Click Computer Account.
7. Click Next.
8. Click Local Computer, and then click Finish.
9. Click Close, and then click OK to close out the Add/Remove Snap-In window.
10. Under Console Root, double-click Certificates (Local Computer).
11. Right-click Trusted Root Certificate Authorities, click All Tasks, and then click Import.
12. On the wizard, click Next, and then locate the file that you transferred from the other computer. (You may have to change the "Files of Type" field to display the X.509 certificates.)
13. When the file is selected, click Next.
14. Place the certificate in the Trusted Root Certificate Authorities Store, and then click Next.
15. Click Finish. A dialog box is displayed that indicates if the import operation had been successful or not.
16. When the certificate has been transferred, restart the computer, and then observe if the behavior is resolved.
Back to the top
MORE INFORMATION
For more information about Trusted Root certificates, click the following article numbers to view the articles in the Microsoft Knowledge Base:
293781 (http://support.microsoft.com/kb/293781/) Trusted root certificates that are required by Windows Server 2003, by Windows XP, and by Windows 2000
222193 (http://support.microsoft.com/kb/222193/) Description of the Windows File Protection feature
</a very big quote from KB296241>
W
WTC
Herb,
I now suggest you should perform a repair install of Windows XP.
How to Perform a Windows XP Repair Install
http://www.michaelstevenstech.com/XPrepairinstall.htm
How to perform an in-place upgrade (reinstallation) of Windows XP
http://support.microsoft.com/kb/315341
--
William Crawford
MS-MVP Windows Shell/User
I now suggest you should perform a repair install of Windows XP.
How to Perform a Windows XP Repair Install
http://www.michaelstevenstech.com/XPrepairinstall.htm
How to perform an in-place upgrade (reinstallation) of Windows XP
http://support.microsoft.com/kb/315341
--
William Crawford
MS-MVP Windows Shell/User
Herb said:Went through these processes and the Certificate is present. Set it for
all
functions, restarted and sfc /scannow still won't run!
--
Herb
WTC said:Herb,
The page is working fine for me. So I quoted a large section from
KB296241 for you.
<a very big quote from KB296241>
When you attempt to use the sfc /scannow command, the command may not
work, and you may receive the following error message:
Windows File Protection could not be initiate a scan of protected system
files. The specific code is 0x000006ba [The RPC Server is unavailable.].
Back to the top
CAUSE
This behavior can occur if the certificate for VeriSign time stamping has
been removed from the computer. This certificate is listed as: "Issued
To: No Liability Accepted, (c)97 VeriSign, Inc.".
To determine whether this certificate has been removed from the system,
follow these steps: 1. Locate a Windows 2000-based computer that exhibits
these symptoms.
2. Click Start, click Run, type mmc, and then click OK.
3. In the Microsoft Management Console, click Console, and then
click Add/Remove Snap-in.
4. In the Add/Remove dialog box, click Add.
5. Click Certificates, and then click Add.
6. Click Computer Account, and then click Next.
7. Click Local Computer, and then click Finish.
8. Click Close, and then click OK.
9. In the console tree, double-click Certificates (Local Computer).
10. Double-click Trusted Root Certificate Authorities, and then
click Certificates.
11. In the details pane, locate the No Liability Accepted
certificate. If the certificate is missing, follow the steps in the
"Resolution" section to export the certificate from another workstation
and import it.
Back to the top
RESOLUTION
To resolve this behavior, the certificate needs to be restored to the
original location. To export the certificate from a Windows 2000-based
computer, follow these steps: 1. Locate a Windows 2000-based computer.
2. Click Start, and then click Run.
3. In the Open box, type: MMC.
4. When Microsoft Management Console (MMC) is displayed, click
Console, and then click Add/Remove Snap-in.
5. On the Add/Remove window, click Add.
6. When the list of available snap-ins are displayed, click
Certificates, and then click Add.
7. Click Computer Account.
8. Click Next.
9. Click Local Computer, and then click Finish.
10. Click Close, and then click OK to close out the Add/Remove
Snap-in window.
11. Under Console Root, double-click Certificates (Local Computer).
12. Double-click Trusted Root Certificate Authorities, and then
double-click Certificates.
13. In the right pane, the installed certificates are displayed.
Scroll down the list until you locate the No Liability Accepted
certificate.
14. Right-click this certificate, click All Tasks, and then click
Export.
15. On the Export Wizard, click Next, click DER encoded Library
X.509, and then click Next.
16. In the File name box, enter a file name to save the file (for
example, C:\Cert). A .cer extension is added to the file name.
17. Transfer this file to the computer that is receiving the error
message.
When the file is transferred to the computer that is receiving the error
message, follow these steps to import the file: 1. Click Start, and then
click Run.
2. In the Open box, type: MMC.
3. When the MMC starts, click Console, and then click Add/Remove
Snap-in.
4. On the Add/Remove Window, click Add.
5. When the list of available snap-ins are displayed, click
Certificates, and then click Add.
6. Click Computer Account.
7. Click Next.
8. Click Local Computer, and then click Finish.
9. Click Close, and then click OK to close out the Add/Remove
Snap-In window.
10. Under Console Root, double-click Certificates (Local Computer).
11. Right-click Trusted Root Certificate Authorities, click All
Tasks, and then click Import.
12. On the wizard, click Next, and then locate the file that you
transferred from the other computer. (You may have to change the "Files
of Type" field to display the X.509 certificates.)
13. When the file is selected, click Next.
14. Place the certificate in the Trusted Root Certificate
Authorities Store, and then click Next.
15. Click Finish. A dialog box is displayed that indicates if the
import operation had been successful or not.
16. When the certificate has been transferred, restart the
computer, and then observe if the behavior is resolved.
Back to the top
MORE INFORMATION
For more information about Trusted Root certificates, click the following
article numbers to view the articles in the Microsoft Knowledge Base:
293781 (http://support.microsoft.com/kb/293781/) Trusted root
certificates that are required by Windows Server 2003, by Windows XP, and
by Windows 2000
222193 (http://support.microsoft.com/kb/222193/) Description of the
Windows File Protection feature
</a very big quote from KB296241>
--
William Crawford
MS-MVP Windows Shell/User
Herb said:link to mspage gets a this page isn't working response
--
Herb
:
I get the response "error code 0x000006ba RPC server is unavailable"
- how do I correct this problem?
This /may/ help you even though the article is for Windows 2000..
Windows File Protection may not start
http://support.microsoft.com/kb/296241
Trusted root certificates that are required by Windows Server 2003, by
Windows XP, and by Windows 2000
http://support.microsoft.com/kb/293781/
G
Guest
I only have a Toshiba OEM disc, which does not offer the repair function.
What if I were to purchase a new XP Home or XP PRo sp2 system disk and
attempt a repair or upgrade with one of these? Alternatively, could I wait
and do an install of the upcoming VISTA system over the old home xpsp2 now on
thne drive?
--
Herb
What if I were to purchase a new XP Home or XP PRo sp2 system disk and
attempt a repair or upgrade with one of these? Alternatively, could I wait
and do an install of the upcoming VISTA system over the old home xpsp2 now on
thne drive?
--
Herb
WTC said:Herb,
I now suggest you should perform a repair install of Windows XP.
How to Perform a Windows XP Repair Install
http://www.michaelstevenstech.com/XPrepairinstall.htm
How to perform an in-place upgrade (reinstallation) of Windows XP
http://support.microsoft.com/kb/315341
--
William Crawford
MS-MVP Windows Shell/User
Herb said:Went through these processes and the Certificate is present. Set it for
all
functions, restarted and sfc /scannow still won't run!
--
Herb
WTC said:Herb,
The page is working fine for me. So I quoted a large section from
KB296241 for you.
<a very big quote from KB296241>
When you attempt to use the sfc /scannow command, the command may not
work, and you may receive the following error message:
Windows File Protection could not be initiate a scan of protected system
files. The specific code is 0x000006ba [The RPC Server is unavailable.].
Back to the top
CAUSE
This behavior can occur if the certificate for VeriSign time stamping has
been removed from the computer. This certificate is listed as: "Issued
To: No Liability Accepted, (c)97 VeriSign, Inc.".
To determine whether this certificate has been removed from the system,
follow these steps: 1. Locate a Windows 2000-based computer that exhibits
these symptoms.
2. Click Start, click Run, type mmc, and then click OK.
3. In the Microsoft Management Console, click Console, and then
click Add/Remove Snap-in.
4. In the Add/Remove dialog box, click Add.
5. Click Certificates, and then click Add.
6. Click Computer Account, and then click Next.
7. Click Local Computer, and then click Finish.
8. Click Close, and then click OK.
9. In the console tree, double-click Certificates (Local Computer).
10. Double-click Trusted Root Certificate Authorities, and then
click Certificates.
11. In the details pane, locate the No Liability Accepted
certificate. If the certificate is missing, follow the steps in the
"Resolution" section to export the certificate from another workstation
and import it.
Back to the top
RESOLUTION
To resolve this behavior, the certificate needs to be restored to the
original location. To export the certificate from a Windows 2000-based
computer, follow these steps: 1. Locate a Windows 2000-based computer.
2. Click Start, and then click Run.
3. In the Open box, type: MMC.
4. When Microsoft Management Console (MMC) is displayed, click
Console, and then click Add/Remove Snap-in.
5. On the Add/Remove window, click Add.
6. When the list of available snap-ins are displayed, click
Certificates, and then click Add.
7. Click Computer Account.
8. Click Next.
9. Click Local Computer, and then click Finish.
10. Click Close, and then click OK to close out the Add/Remove
Snap-in window.
11. Under Console Root, double-click Certificates (Local Computer).
12. Double-click Trusted Root Certificate Authorities, and then
double-click Certificates.
13. In the right pane, the installed certificates are displayed.
Scroll down the list until you locate the No Liability Accepted
certificate.
14. Right-click this certificate, click All Tasks, and then click
Export.
15. On the Export Wizard, click Next, click DER encoded Library
X.509, and then click Next.
16. In the File name box, enter a file name to save the file (for
example, C:\Cert). A .cer extension is added to the file name.
17. Transfer this file to the computer that is receiving the error
message.
When the file is transferred to the computer that is receiving the error
message, follow these steps to import the file: 1. Click Start, and then
click Run.
2. In the Open box, type: MMC.
3. When the MMC starts, click Console, and then click Add/Remove
Snap-in.
4. On the Add/Remove Window, click Add.
5. When the list of available snap-ins are displayed, click
Certificates, and then click Add.
6. Click Computer Account.
7. Click Next.
8. Click Local Computer, and then click Finish.
9. Click Close, and then click OK to close out the Add/Remove
Snap-In window.
10. Under Console Root, double-click Certificates (Local Computer).
11. Right-click Trusted Root Certificate Authorities, click All
Tasks, and then click Import.
12. On the wizard, click Next, and then locate the file that you
transferred from the other computer. (You may have to change the "Files
of Type" field to display the X.509 certificates.)
13. When the file is selected, click Next.
14. Place the certificate in the Trusted Root Certificate
Authorities Store, and then click Next.
15. Click Finish. A dialog box is displayed that indicates if the
import operation had been successful or not.
16. When the certificate has been transferred, restart the
computer, and then observe if the behavior is resolved.
Back to the top
MORE INFORMATION
For more information about Trusted Root certificates, click the following
article numbers to view the articles in the Microsoft Knowledge Base:
293781 (http://support.microsoft.com/kb/293781/) Trusted root
certificates that are required by Windows Server 2003, by Windows XP, and
by Windows 2000
222193 (http://support.microsoft.com/kb/222193/) Description of the
Windows File Protection feature
</a very big quote from KB296241>
--
William Crawford
MS-MVP Windows Shell/User
link to mspage gets a this page isn't working response
--
Herb
:
I get the response "error code 0x000006ba RPC server is unavailable"
- how do I correct this problem?
This /may/ help you even though the article is for Windows 2000..
Windows File Protection may not start
http://support.microsoft.com/kb/296241
Trusted root certificates that are required by Windows Server 2003, by
Windows XP, and by Windows 2000
http://support.microsoft.com/kb/293781/
W
WTC
Answered inline:
Well this choice is up to you but if you do purchase a Windows XP disc from
a retail store, make sure the disc is genuine and the retail store is a
reputable dealer. I am not sure if OEM versions allow you to perform repair
or upgrade installs but I definitely know retail versions do.
Genuine Microsoft Software - How to Tell
http://www.microsoft.com/resources/howtotell/en/default.mspx
If you have Windows XP Pro installed then do not purchase a Windows XP Home
CD because you cannot downgrade from Pro when using the repair or upgrade
method. If you have Windows XP Home installed then you can purchase either
Home or Pro.
Another question is: do you really need Windows XP Pro? Most users do not
require Windows XP Pro since they do not need to encrypt data, run a MS web
server, some enhanced security features or have more the 5 concurrent tcp
connections.
Windows XP Comparision Guide
http://www.microsoft.com/windowsxp/pro/howtobuy/choosing2.mspx
An upgrade retail version of Windows XP should suffice. If you ever need to
reinstall Windows XP, you may need to use the Toshiba recovery cd first then
upgrade with your purchased XP copy unless you have a qualifying product.
Upgrading from Previous Versions of Windows
http://www.microsoft.com/windowsxp/pro/upgrading/matrix.mspx
If you do this, make sure your computer can run Vista.
There is a link on the following page to check if your computer is ready for
Vista.
http://www.microsoft.com/windowsvista/getready/default.mspx
--
William Crawford
MS-MVP Windows Shell/User
Herb said:I only have a Toshiba OEM disc, which does not offer the repair
function. What if I were to purchase a new XP Home or XP
PRo sp2 system disk and attempt a repair or upgrade with one
of these?
Well this choice is up to you but if you do purchase a Windows XP disc from
a retail store, make sure the disc is genuine and the retail store is a
reputable dealer. I am not sure if OEM versions allow you to perform repair
or upgrade installs but I definitely know retail versions do.
Genuine Microsoft Software - How to Tell
http://www.microsoft.com/resources/howtotell/en/default.mspx
If you have Windows XP Pro installed then do not purchase a Windows XP Home
CD because you cannot downgrade from Pro when using the repair or upgrade
method. If you have Windows XP Home installed then you can purchase either
Home or Pro.
Another question is: do you really need Windows XP Pro? Most users do not
require Windows XP Pro since they do not need to encrypt data, run a MS web
server, some enhanced security features or have more the 5 concurrent tcp
connections.
Windows XP Comparision Guide
http://www.microsoft.com/windowsxp/pro/howtobuy/choosing2.mspx
An upgrade retail version of Windows XP should suffice. If you ever need to
reinstall Windows XP, you may need to use the Toshiba recovery cd first then
upgrade with your purchased XP copy unless you have a qualifying product.
Upgrading from Previous Versions of Windows
http://www.microsoft.com/windowsxp/pro/upgrading/matrix.mspx
Alternatively, could I wait
and do an install of the upcoming VISTA system over the old
home xpsp2 now on thne drive?
If you do this, make sure your computer can run Vista.
There is a link on the following page to check if your computer is ready for
Vista.
http://www.microsoft.com/windowsvista/getready/default.mspx
--
William Crawford
MS-MVP Windows Shell/User
WTC said:Herb,
I now suggest you should perform a repair install of Windows XP.
How to Perform a Windows XP Repair Install
http://www.michaelstevenstech.com/XPrepairinstall.htm
How to perform an in-place upgrade (reinstallation) of Windows XP
http://support.microsoft.com/kb/315341
--
William Crawford
MS-MVP Windows Shell/User
Herb said:Went through these processes and the Certificate is present. Set it
for
all
functions, restarted and sfc /scannow still won't run!
--
Herb
:
Herb,
The page is working fine for me. So I quoted a large section from
KB296241 for you.
<a very big quote from KB296241>
When you attempt to use the sfc /scannow command, the command may not
work, and you may receive the following error message:
Windows File Protection could not be initiate a scan of protected
system
files. The specific code is 0x000006ba [The RPC Server is
unavailable.].
Back to the top
CAUSE
This behavior can occur if the certificate for VeriSign time stamping
has
been removed from the computer. This certificate is listed as: "Issued
To: No Liability Accepted, (c)97 VeriSign, Inc.".
To determine whether this certificate has been removed from the
system,
follow these steps: 1. Locate a Windows 2000-based computer that
exhibits
these symptoms.
2. Click Start, click Run, type mmc, and then click OK.
3. In the Microsoft Management Console, click Console, and then
click Add/Remove Snap-in.
4. In the Add/Remove dialog box, click Add.
5. Click Certificates, and then click Add.
6. Click Computer Account, and then click Next.
7. Click Local Computer, and then click Finish.
8. Click Close, and then click OK.
9. In the console tree, double-click Certificates (Local
Computer).
10. Double-click Trusted Root Certificate Authorities, and then
click Certificates.
11. In the details pane, locate the No Liability Accepted
certificate. If the certificate is missing, follow the steps in the
"Resolution" section to export the certificate from another
workstation
and import it.
Back to the top
RESOLUTION
To resolve this behavior, the certificate needs to be restored to the
original location. To export the certificate from a Windows 2000-based
computer, follow these steps: 1. Locate a Windows 2000-based computer.
2. Click Start, and then click Run.
3. In the Open box, type: MMC.
4. When Microsoft Management Console (MMC) is displayed, click
Console, and then click Add/Remove Snap-in.
5. On the Add/Remove window, click Add.
6. When the list of available snap-ins are displayed, click
Certificates, and then click Add.
7. Click Computer Account.
8. Click Next.
9. Click Local Computer, and then click Finish.
10. Click Close, and then click OK to close out the Add/Remove
Snap-in window.
11. Under Console Root, double-click Certificates (Local
Computer).
12. Double-click Trusted Root Certificate Authorities, and then
double-click Certificates.
13. In the right pane, the installed certificates are displayed.
Scroll down the list until you locate the No Liability Accepted
certificate.
14. Right-click this certificate, click All Tasks, and then
click
Export.
15. On the Export Wizard, click Next, click DER encoded Library
X.509, and then click Next.
16. In the File name box, enter a file name to save the file
(for
example, C:\Cert). A .cer extension is added to the file name.
17. Transfer this file to the computer that is receiving the
error
message.
When the file is transferred to the computer that is receiving the
error
message, follow these steps to import the file: 1. Click Start, and
then
click Run.
2. In the Open box, type: MMC.
3. When the MMC starts, click Console, and then click Add/Remove
Snap-in.
4. On the Add/Remove Window, click Add.
5. When the list of available snap-ins are displayed, click
Certificates, and then click Add.
6. Click Computer Account.
7. Click Next.
8. Click Local Computer, and then click Finish.
9. Click Close, and then click OK to close out the Add/Remove
Snap-In window.
10. Under Console Root, double-click Certificates (Local
Computer).
11. Right-click Trusted Root Certificate Authorities, click All
Tasks, and then click Import.
12. On the wizard, click Next, and then locate the file that you
transferred from the other computer. (You may have to change the
"Files
of Type" field to display the X.509 certificates.)
13. When the file is selected, click Next.
14. Place the certificate in the Trusted Root Certificate
Authorities Store, and then click Next.
15. Click Finish. A dialog box is displayed that indicates if
the
import operation had been successful or not.
16. When the certificate has been transferred, restart the
computer, and then observe if the behavior is resolved.
Back to the top
MORE INFORMATION
For more information about Trusted Root certificates, click the
following
article numbers to view the articles in the Microsoft Knowledge Base:
293781 (http://support.microsoft.com/kb/293781/) Trusted root
certificates that are required by Windows Server 2003, by Windows XP,
and
by Windows 2000
222193 (http://support.microsoft.com/kb/222193/) Description of the
Windows File Protection feature
</a very big quote from KB296241>
--
William Crawford
MS-MVP Windows Shell/User
link to mspage gets a this page isn't working response
--
Herb
:
I get the response "error code 0x000006ba RPC server is
unavailable"
- how do I correct this problem?
This /may/ help you even though the article is for Windows 2000..
Windows File Protection may not start
http://support.microsoft.com/kb/296241
Trusted root certificates that are required by Windows Server 2003,
by
Windows XP, and by Windows 2000
http://support.microsoft.com/kb/293781/
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.