MS05-051 and RPCRT4.DLL on W2K3

Hi,

We are seeing situation where MS05-051 is installed yet the RPCRT4.DLL does
not get updated. Anybody know whey this maybe happening?

Thanks

Chris Wood

"Chris Wood" <> wrote in message
news:%230kxYQ$...
> Hi,
>
> We are seeing situation where MS05-051 is installed yet the RPCRT4.DLL does
> not get updated. Anybody know whey this maybe happening?


It's in use? Try stopping the rpcss service.

Or more systematically try checking where all it is in use and stop
all such tasks. E.g. in a cmd window enter:

tasklist /fi "Modules eq rpcrt4.dll"

Hmm... looks like that one is one which would have to be updated during
a boot. Look in the install log. Is that what is happening? Is there something
else (e.g. "security" package) which might be interfering with such an update
during the boot? If so, disable that (or just try doing the update during
a safe mode boot.) Etc. Note: I'm not sure if you can mix modes between
scheduling the update and actually doing it. That would obviously be the
simplest alternative if so. (E.g. just switch to safe mode on the forced boot
to do the update. Then verify that the versions of the modules have changed
after the OS has come up.) If the modules get changed during a safe mode
boot but after a normal boot are restored to their old versions you would then
know that something (e.g. "security" package) was undoing the update.
However, I'd be more inclined to suspect that something might block
the update than actually undo it. That's why I'd try the safe mode boot.
Again, note however, that if the versions *don't change* after a switch to
safe mode during the forced boot I can't draw any such conclusion for you
because I'm not certain that it is supposed to work that way. I would be
more confident of it working by doing the install during a safe mode boot
and then rebooting into safe mode to check it. Certainly a safe mode boot
would minimize the number of tasks active which would be using the problem
module in the first place.


>
> Thanks
>
> Chris Wood



Good luck

Robert Aldwinckle
---

Robert,

See the MS05-051 on W2K3 thread for the answer. Its complicated.

Chris

"Robert Aldwinckle" <> wrote in message
news:...
> "Chris Wood" <> wrote in message
> news:%230kxYQ$...
>> Hi,
>>
>> We are seeing situation where MS05-051 is installed yet the RPCRT4.DLL
>> does
>> not get updated. Anybody know whey this maybe happening?
>
>
> It's in use? Try stopping the rpcss service.
>
> Or more systematically try checking where all it is in use and stop
> all such tasks. E.g. in a cmd window enter:
>
> tasklist /fi "Modules eq rpcrt4.dll"
>
> Hmm... looks like that one is one which would have to be updated during
> a boot. Look in the install log. Is that what is happening? Is there
> something
> else (e.g. "security" package) which might be interfering with such an
> update
> during the boot? If so, disable that (or just try doing the update during
> a safe mode boot.) Etc. Note: I'm not sure if you can mix modes
> between
> scheduling the update and actually doing it. That would obviously be the
> simplest alternative if so. (E.g. just switch to safe mode on the forced
> boot
> to do the update. Then verify that the versions of the modules have
> changed
> after the OS has come up.) If the modules get changed during a safe mode
> boot but after a normal boot are restored to their old versions you would
> then
> know that something (e.g. "security" package) was undoing the update.
> However, I'd be more inclined to suspect that something might block
> the update than actually undo it. That's why I'd try the safe mode boot.
> Again, note however, that if the versions *don't change* after a switch to
> safe mode during the forced boot I can't draw any such conclusion for you
> because I'm not certain that it is supposed to work that way. I would be
> more confident of it working by doing the install during a safe mode boot
> and then rebooting into safe mode to check it. Certainly a safe mode
> boot
> would minimize the number of tasks active which would be using the problem
> module in the first place.
>
>
>>
>> Thanks
>>
>> Chris Wood
>
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
>