Unable to print after applying 826939 or 328310

After applying q328310 hotfix (or q826939 security rollup) to some
computers running Windows XP Pro English SP1 the users are unable to
print to any installed printer, no matter local or network. No errors
are recorded to Event Log, the Print Spooler service appears to be
running. After removing the above hotfixes everything returns back to
normal.

Has anyone seen this problem already? What could be the cause of the
problem?

This problem was seen a while ago and the suggest fix was to run

sfc /scannow

from the Start, Run command.

Cari
www.coribright.com

"serge" <serge-home@yandex.ru> wrote in message
news:1066710078.715337@ns3.mir-omsk.ru...
> After applying q328310 hotfix (or q826939 security rollup) to some
> computers running Windows XP Pro English SP1 the users are unable to
> print to any installed printer, no matter local or network. No errors
> are recorded to Event Log, the Print Spooler service appears to be
> running. After removing the above hotfixes everything returns back to
> normal.
>
> Has anyone seen this problem already? What could be the cause of the
> problem?
>

I definently know its 826939. If you just remove this
one , it fixes it.
>-----Original Message-----
>This problem was seen a while ago and the suggest fix
was to run
>
>sfc /scannow
>
>from the Start, Run command.
>
>Cari
>www.coribright.com
>
>"serge" <serge-home@yandex.ru> wrote in message
>news:1066710078.715337@ns3.mir-omsk.ru...
>> After applying q328310 hotfix (or q826939 security
rollup) to some
>> computers running Windows XP Pro English SP1 the users
are unable to
>> print to any installed printer, no matter local or
network. No errors
>> are recorded to Event Log, the Print Spooler service
appears to be
>> running. After removing the above hotfixes everything
returns back to
>> normal.
>>
>> Has anyone seen this problem already? What could be
the cause of the
>> problem?
>>
>
>
>.
>