Security → Q329414 Microsoft patch problems fixed!

For those of you caught in an endless loop regarding the MDAC patch, at Windows Update, Microsoft has found the problem and is fixing it now. Here's Microsoft's post on the Windows Update NG:

Microsoft
Tuesday, December 03, 2002 11:14 AM
microsoft.public.windowsupdate
Re: Q329414 MDAC 2.1 Borked! Stuck in endless loop..

Hi,

Microsoft has isolated the problem with Windows Update and after tomorrow
the Windows Update should no longer get in a loop of continually expecting
to install Q329414.

Best regards,

Dan Kirby
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

If you want to fix the problem yourself now, what Microsoft learned was that the patch does install, but the registry key that Windows Update checks to determine if you need the patch does not update. You can see for yourself if this is your problem by going to C:\Program Files\Common Files\SYSTEM\MSADC. Then look at properties of msadce.dll and the version number. If your version number is 2.53.6202.0 or above the patch is installed, but your registry key is not updated.

Attached is the file from Microsoft, posted by a user at Windows Update NG, who was on the phone earlier today with Microsoft, which fixes the problem. I am assuming this is the same fix that will be on Windows Update on Thursday.

__________________________________________________
Attached is the file from Microsoft, posted by a user at Windows Update NG, who was on the phone earlier today with Microsoft, which fixes the problem. I am assuming this is the same fix that will be on Windows Update on Thursday.
___________________________________________________

i'm not gunna be the first one to download THAT ...

Good news. This means I have the patch installed, and just my registry is in a bit of a mess. Oh well, who cares. I no longer use Windows Update anyway.

Didnt M$ stop using the letter "Q" on all the newest patches?

It appears this fix has been referred to on multiple occasions in the NG...

To accomplish this, you can edit the registry.
Press Start > Run, and type regedit
Click OK
Navigate in the left pane to HKEY_LOCAL_MACHINE > Software > Microsoft > Updates
Click the + next to this
Look for Q329414-21 in the left pane
If this isn't present, click Edit > New > Key, if it is present, just click it.
In the right pane, check for a value alled "IsInstalled". If this is there, change it to 1. Otherwise, add a new DWORD Value (Edit > New > DWORD Value), call it "IsInstalled" (without the quotes) and set it to 1 (0x00000001).

thanks mele, your registry patch did the trick! no more annoying critical update popups in the middle of my work! hooray! thumbs-up from randy! :)

Even though I have this patch already, I still want to know where in the registry it is? Thanks for the info;)

hmm, mine says "IsInstalled"=dword:00000001 and the version number of msadce.dll is 2.53.6202.0. This was the results after doing the update back on 11/21 and Windows Update has not brought this up since. WinME.

said by bluepoint:

---

It looks like the xx in Q329414-xx folder in the Registry depends on Win OS or we can compare to find out.
Win2k here.

---

XX=25 on my win 98se

said by 59678178:

---

XX=25 on my win 98se

---

What is your msadce version?

said by bluepoint:

---

What is your msadce version?

---

2.53.6202.0

Okay thanks NYTom, now if dp can confirm xx=25 then looks like the reg path depends on the msdce version and not the OS.

Now after loading the patch i have a -21 AND a -25....what gives? did i do something wrong?

I can confirm 25

Well guys, as you saw from my screen shot http://www.dslreports.com/forum/remark,5204365~root=security,1~mode=flat;iframe=1#5205695 Mele's registry hack worked for me, and I'm a happy camper now: I'm not about to mess with it, now that I'm free of that da_n annoying windows critical update popup which appeared on my screen on two different computers, over and over and over: it's gone now, that is until the next MS screwup .