Please Help with my Faulty XP Pro Installation.

[creativeimages]

Faulty XP Pro Installation.

Boiling down a problem to the simplest, single issue – my XP professional installation is not correctly installed and is not working correctly. The causes of this situation are faulty tech support, multiple repairs and fixes – almost all made thing worse.

Both Microsoft auto update and Windows Live OneCare state there is an important security update that needs to be installed. When I allow auto update or OneCare to perform the update – it fails. The error messages are as follows:

1. Security Update For Microsoft XML Core Service 4.0 Service Pack2 (kb936181 or kb916281) not installed.
2. Security Update For Cumulative Security Update Internet Explorer for Windows XP (kb936181) not installed.

What is the problem? What should be done? Why?

Thank you.

CreativeImages

[Miz]

I can only tell you what I'd do.

Since you said there have been multiple repairs and fixes, all of them making things worse, I'd just burn everything I don't want to lose to CD (documents, pictures, bookmarks, email, addresses), then wipe the hard drive and reinstall XP from scratch.

How...or whether...you do that depends on what you have to reinstall...an XP installation disk, a recovery/restore disk that came with the computer or a recovery/restore partition on the hard drive.

[creativeimages]

I would like to repair or fix my XP Pro installation, rather than reformat the hard drive and start over. I have discovered that the error is an Error Code: 0x64C.

Microsoft has the following:

BUG: You receive an "ActiveX component can't create object" error message when you Use Windows Script Host to execute remote script
SYMPTOMS
When you try to execute a remote script by using Windows Script Host (WSH) 5.6 on a Windows XP-based computer, you may receive the following error message:
Error: ActiveX component can't create object
Code: 800A01AD
Source: Microsoft VBScript Runtime Error

CAUSE
This behavior can occur if the setup for WSH remote scripting was performed incorrectly on your Windows XP-based system.

RESOLUTION
To resolve this issue, register the WScript object by running the wscript -regserver command from a command prompt or from the Run command on the Start menu.

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION
Steps to reproduce the problem
1. Click Start, point to Programs, point to Accessories, and then click Notepad.
2. Copy the following code, and then paste it into Notepad:
<package>
<job>
<script language="VBScript">
set oController = CreateObject("WSHController")
set oProcess = oController.CreateScript(<Path To Remote Script>, <Server>)
WScript.ConnectObject oProcess, "remote_" oProcess.Execute

While oProcess.Status <> 2
WScript.Sleep 100
Wend
WScript.Echo "Done"

Sub remote_Error
Dim theError
Set theError = oProcess.Error
WScript.Echo "Error - Line: " & theError.Line & ", Char: " & theError.Character & vbCrLf & "Description: " & theError.Description
WScript.Quit -1
End Sub

</script>
</job>
</package>

3. Save the document with the file name RemoteTest.wsf.
4. On the File menu, click New to create a new file.
5. Copy the following code, and then paste it into the new Notepad document:

<package> <job> <script language="VBScript"> set fso = CreateObject("Scripting.FileSystemObject") set fout = fso.CreateTextFile("c:\RemoteTest.txt", true) fout.WriteLine Now fout.Close </script> </job> </package>

6. Save the document with the file name RemoteFile.wsf. When you run the RemoteTest.wsf file, the computer connects to the remote server and runs RemoteFile.wsf. Note that to connect to the remote server, you must supply both the path to the file and the server information.

I do not what to do or where to get this information.

Thank you.