Windows Forum

Ask something
Discussion Locked

Warning on latest MS Patch for XP!

0 helpful
11 replies

by cglrcng9

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is not a question, but a dire warning! Do not under any circumstance apply the latest ADODB.stream patch to WIN XP as it will hammer the entire XP OS useless (My own 40 GB dual boot Maxtor HD only shows now as a 6 MB disk).

The patch worked fine on Win98SE and Win ME, but they must have loaded the wrong patch on the XP update portion of Windows Update. After updating with the patch using Windows Update the XP OS would not even boot into Safe Mode, just a constant reboot loop. Tried to effect a repair, the console said it wasn't possible (though I could reboot into the D:\ partition containing Win98SE. Tried fixing the MBR, no go, tried fixboot, it took out the NTLDR. Tried re-installing XP, the C:\ partition only shows as 6MB instead of 20 GB, though the D:\ partition still shows as 20GB. Now due to the NTLDR being wiped out I can't even reach the D:\ partition (Win98SE) side to burn the latest file changes and additions, links, etc.

Also installed the drive as a slave and it only shows as a 10 MB drive w/ the Recycle Bin as the only file there.

So fair warning to all...DO NOT INSTALL THAT PATCH!

11 replies

by pctech

Thank you for the warning. I have already installed the patch that you mention here and have not experienced any of these problems. I run XP Pro as the only installed OS. What I have experienced is a "svchost.exe LOCAL SERVICE" running that I can not shut down. Ending the process only lasts for 1-2 seconds and it restarts itself. Sometimes it will put multiple instances of this service running when I shut it down. I DO NOT know that there is a direct link between the Windows patch and this service being ran as a svchost service. This was not happening before I installed the patch. I have ran regedit, sysedit, msconfig, virus scans, and spyware scans. HiJack this shows nothing unusual but, CWShredder says that an application has tried to disable it when it launches but that it is still functional. Still, it finds nothing. I have seen two other XP systems with this exact syptom. I know one has the new patch and I will check the other.
Thanks for the heads up.

by pctech

An update.
I did a roll back to a previous date before the installation of the patch and it made no difference concerning the malware I am confronted with. The patch was not the issue.

by gigelul

For me works fine this patch.
Using a dual boot system (WinXP and Linux) with 4 partition (2 for WinXP and 2 for Linux), no problem for the moment.

by wcp

OS: Windows XP Pro SP1

Installed the patch yesterday (July 3, 2004) and have not had any problems.

It must be coincident on yours.

by oasisdiver

I have 2 computers first with XP Pro SP1 150GB hard drive and the second XP Home SP1 80GB hard drive and I have downloaded the patch on both and have had no bad effects what so ever.

by cglrcng9

OK, I now know a lot more about what I faced, and it may or may not affect but only a few....The installed OS was an early release (OEM edition) of XP Home that refused to actually accept the SP1 express (it showed installed as far as individual patches, but always still showed up as needing to be installed via Windows Update again next trip there).

I have reinstalled that same OS on a test unit and did the SP1 install then reapplied the patch and the same thing happens. (also changed my system to XP Pro in the Dual Boot system and the patch worked just fine there). I would still warn those that were unsucessful in installing SP1 on XP Home to be very careful applying that DAODB.stream patch (especially if there was a warning @ the end of the SP1 install that the version you have is not the correct version to apply SP1 and to contact Microsoft to do just exactly that. We are working on the replacement of my OS disk right now so they can investigate that particular problem.

I felt it better to warn of my experience than allow others to suffer the same fate.

This discussion is closed to new replies.