SBS 2003 - KB 835734 - Repeating Install.....

Can't get this one to go away. Install history shows that it has installed
correctly about 100 times. (Green Check)

I have tried unistalling it and reinstalling it in Safe Mode. I have also
tried uninstalling the updates around it in history and then reinstalling
them.

Any other tips on ending the loop?

John

John,

Can you confirm that these files listed below match the ones on the system :

File name File version File size Date Time Platform
Dlvrimf.dll 5.2.2651.1 50,176 08-Apr-2004 23:33 x86
Imbdlvres.dll 5.2.2651.1 40,448 24-Mar-2004 22:05 x86

If yes, then the update is installed. The only suggestion would be to
search the registry for 835734 and check the " IsInstalled " Value. It
should be set to 1 to show that the update is installed.

MowGreen [MVP 2003-2006]
===============
*-43-* FDNY
Never Forgotten
===============


John wrote:

> Can't get this one to go away. Install history shows that it has installed
> correctly about 100 times. (Green Check)
>
> I have tried unistalling it and reinstalling it in Safe Mode. I have also
> tried uninstalling the updates around it in history and then reinstalling
> them.
>
> Any other tips on ending the loop?
>
> John
>
>

Thanks for the response.

> File name File version File size Date Time Platform
> Dlvrimf.dll 5.2.2651.1 50,176 08-Apr-2004 23:33 x86
> Imbdlvres.dll 5.2.2651.1 40,448 24-Mar-2004 22:05 x86

Both match.

> If yes, then the update is installed. The only suggestion would be to
> search the registry for 835734 and check the " IsInstalled " Value. It
> should be set to 1 to show that the update is installed.

I do not have an "IsInstalled " Value available to change for this or any of
my other Windows Updates. I do see this showing up in entries for Windows
components.....

The entries that do exist in 835734 registry entries match up to entries for
updates that have been installed and are not looping.

John

Found the reason on the SBS 2003 group in another person post.

<snip>
For the benefit if all, the problem is that these pop files are not on
the C:\ drive, Lesa (like many var/vaps) installed the SBS over many drives.

Thus for now the option is to go into MU and click that "ignore" this
patch button as one option if it's really bothering folks.

Otherwise I expect that a detection logic fix will need to take place.

Her box is actually patched. It's just MU is a little lost right now.
<snip>

Not sure what MU is but I did tell the Automatic Update not to inform me
about that update again.

John


"John" <> wrote in message
news:...
> Thanks for the response.
>
>> File name File version File size Date Time Platform
>> Dlvrimf.dll 5.2.2651.1 50,176 08-Apr-2004 23:33 x86
>> Imbdlvres.dll 5.2.2651.1 40,448 24-Mar-2004 22:05 x86
>
> Both match.
>
>> If yes, then the update is installed. The only suggestion would be to
>> search the registry for 835734 and check the " IsInstalled " Value. It
>> should be set to 1 to show that the update is installed.
>
> I do not have an "IsInstalled " Value available to change for this or any
> of my other Windows Updates. I do see this showing up in entries for
> Windows components.....
>
> The entries that do exist in 835734 registry entries match up to entries
> for updates that have been installed and are not looping.
>
> John
>

> Not sure what MU is but I did tell the Automatic Update not to inform me
> about that update again.
>
> John

DOH! I thought MU was Microsoft Update but I did not see it in the the
Control Panel. I did not realize it was stuck to my start bar.

John

Glad to see you've found what the issue is, John. An SBSer informed me
that the update was "horked" and that detection fails when the
"standard" drive configuration is different.
Hopefully, the detection issue will be resolved soon.

MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============

John wrote:
> Found the reason on the SBS 2003 group in another person post.
>
> <snip>
> For the benefit if all, the problem is that these pop files are not on
> the C:\ drive, Lesa (like many var/vaps) installed the SBS over many drives.
>
> Thus for now the option is to go into MU and click that "ignore" this
> patch button as one option if it's really bothering folks.
>
> Otherwise I expect that a detection logic fix will need to take place.
>
> Her box is actually patched. It's just MU is a little lost right now.
> <snip>
>
> Not sure what MU is but I did tell the Automatic Update not to inform me
> about that update again.
>
> John
>
>
> "John" <> wrote in message
> news:...
>
>>Thanks for the response.
>>
>>
>>>File name File version File size Date Time Platform
>>>Dlvrimf.dll 5.2.2651.1 50,176 08-Apr-2004 23:33 x86
>>>Imbdlvres.dll 5.2.2651.1 40,448 24-Mar-2004 22:05 x86
>>
>>Both match.
>>
>>
>>>If yes, then the update is installed. The only suggestion would be to
>>>search the registry for 835734 and check the " IsInstalled " Value. It
>>>should be set to 1 to show that the update is installed.
>>
>>I do not have an "IsInstalled " Value available to change for this or any
>>of my other Windows Updates. I do see this showing up in entries for
>>Windows components.....
>>
>>The entries that do exist in 835734 registry entries match up to entries
>>for updates that have been installed and are not looping.
>>
>>John
>>
>
>
>