WARNING: Update 969947 may prohibit establishment of an RDP session on Windows XP

You have a different problem. Try resetting the RDP session with this:

echo yes | reset session RDP-tcp

If it happens a lot, then you've got a corrupted installation. A
repair/reinstall of the OS should fix it. Unfortunately, I don't know of a
better solution.

"cox" wrote in message
...
David,

Same issue here on a SBS test server. Have not confirmed 100% it is
related only to the 969947 patch. However, I saw the following error
in the event log:

Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1014
Date: 11/11/2009
Time: 3:32:10 PM
User: N/A
Computer: FSERVER
Description:
Cannot load illegal module: C:\WINDOWS\system32\rdpwsx.DLL.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I googled it and someone suggested to take another copy of the
rdpwsx.dll and replace it on the sick machine. I rebooted and it
worked.

I can't say any of these events are related, but I thought I share my
experience anyway.

Cox

Can you check this link (Looks like a similar issue):
http://forums.techarena.in/windows-x...rt/1139973.htm

The last post in the above link says:
Dell technical support sent me this link (among others) this morning:
http://www.nvidia.co.uk/object/winxp_182.08_uk.html
I downloaded and installed that, and it has fixed the problem.


"Susan Bradley" wrote:

If this is occuring on a SBS box that may be something else?

SBS 2003 and DNS patch issues revisited - THE OFFICIAL BLOG OF THE SBS
"DIVA":
http://msmvps.com/blogs/bradley/arch...revisited.aspx


cox wrote:
David,

Same issue here on a SBS test server. Have not confirmed 100% it is
related only to the 969947 patch. However, I saw the following error
in the event log:

Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1014
Date: 11/11/2009
Time: 3:32:10 PM
User: N/A
Computer: FSERVER
Description:
Cannot load illegal module: C:\WINDOWS\system32\rdpwsx.DLL.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I googled it and someone suggested to take another copy of the
rdpwsx.dll and replace it on the sick machine. I rebooted and it
worked.

I can't say any of these events are related, but I thought I share my
experience anyway.

Cox
.

@David: Are you aware of the annual Global Technical Support package benefit
and did you avail yourself of same to get assistance with this? cf.
https://mvp.support.microsoft.com/gp/MVPTechSup
--
~Robear

David Dickinson wrote:
I spent two hours on the phone, including hold times, with Microsoft while
they transferred me to different departments. PC Safety says its a
business
problem since it involves RDP. Business support says its a PC Safety
problem since it involves an update. Then we got disconnected when a
guy's
headsets failed. I can't try again until tomorrow. I am not a happy guy.

I'll post an update when I learn something.


"Susan Bradley" wrote in message
...
You said you had a case open right? If not ping me and I'll get you one.
Can you let me know what they say?

David Dickinson wrote:
I had considered display driver problems, but that's not it. With
969947
installed, the machine freezes during RDP logon. Without 969947, the
machine works fine. There are absolutely not messages in the event log
relating to this issue. The security log doesn't even show the normal
logon attempt messages. As soon as I enter the password to logon in a
remote desktop session, the machine freezes.

"Susan Bradley" wrote in message
...
Recently I had an issue post .net patch that I could not RDP. It was
due to the monitor card software interaction with 951847.

Look in your event log on the workstations and see if you are getting
that error.

After the install of KB951847 (.net family) I found I could not rdp
into
a XP workstation. Updating the driver didn't work but putting in the
registry key did:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session
Manager\Memory Management]

"SessionImageSize"=dword:00000020



Brad Rutkowski's Blog : \SystemRoot\System32\RDPDD.dll failed to load:
http://blogs.technet.com/brad_rutkow...d-to-load.aspx

David Dickinson wrote:
I have two XP Pro SP3 test machines. One has the problem, the other
doesn't. I haven't been able to isolate the cause yet. The machines
have significant differences in their configurations, so it will take
some time.


"Susan Bradley" wrote in message
...
Second machine tested. Can't repro on second box.

Susan Bradley wrote:

Not repro-ing that here.

XP sp3

tommydokc wrote:
we're having the exact same problems here on several machines. I've
had to boot to safe mode to get it uninstalled then everything is
back to normal. I would advise to disable the download of that
update at this point.



"David Dickinson" wrote:

I tested KB969947 on a Windows XP Professional SP3 machine that is
reserved for testing. After installing that update, I could not
log on to it in a Remote Desktop session. In fact, the machine
had
frozen and could not even be accessed with its keyboard or mouse,
and the hard drive light flashed in a repeating pattern over
several minutes. However, after restarting the machine, I could
log
on to it locally. After uninstalling that update, RDP sessions
were
successful. I reinstalled it and tested again, and RDP sessions
failed. After uninstalling, they worked.

Test this update thoroughly before deploying it! I've notified
Microsoft about the issue, but the help that is available at this
time told me that Microsoft Enterprise will have to deal with it,
and I have to wait until normal business hours tomorrow to contact
them.

I haven't yet tested this update on other versions of Windows, but
I hope no adminstrators have large networks using automatic
updates. I'm just hoping that this isn't the disaster that it
could
be.

David Dickinson
eveningstar at mvps dot org

NOTE: This message has been cross-posted to
microsoft.public.windowsupdate, microsoft.public.security,
microsoft.public.microsoft_update_catalog, and
microsoft.public.windowsxp.security_admin.
.

@PA Bear: Yes, thanks, I do know about the benefits. But I haven't been an
MVP since 2002, when my business expanded and I just couldn't keep up with
the forums. Not being an MVP anymore, I don't qualify for the package. But
now that I've been able to delegate some of my more tedious
responsibilities, I hope to have more time to spend here. I'd forgotten how
much I enjoyed it.


"PA Bear [MS MVP]" wrote in message
...
@David: Are you aware of the annual Global Technical Support package
benefit and did you avail yourself of same to get assistance with this?
cf. https://mvp.support.microsoft.com/gp/MVPTechSup
--
~Robear

David Dickinson wrote:
I spent two hours on the phone, including hold times, with Microsoft
while
they transferred me to different departments. PC Safety says its a
business
problem since it involves RDP. Business support says its a PC Safety
problem since it involves an update. Then we got disconnected when a
guy's
headsets failed. I can't try again until tomorrow. I am not a happy
guy.

I'll post an update when I learn something.


"Susan Bradley" wrote in message
...
You said you had a case open right? If not ping me and I'll get you
one.
Can you let me know what they say?

David Dickinson wrote:
I had considered display driver problems, but that's not it. With
969947
installed, the machine freezes during RDP logon. Without 969947, the
machine works fine. There are absolutely not messages in the event log
relating to this issue. The security log doesn't even show the normal
logon attempt messages. As soon as I enter the password to logon in a
remote desktop session, the machine freezes.

"Susan Bradley" wrote in message
...
Recently I had an issue post .net patch that I could not RDP. It was
due to the monitor card software interaction with 951847.

Look in your event log on the workstations and see if you are getting
that error.

After the install of KB951847 (.net family) I found I could not rdp
into
a XP workstation. Updating the driver didn't work but putting in the
registry key did:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session
Manager\Memory Management]

"SessionImageSize"=dword:00000020



Brad Rutkowski's Blog : \SystemRoot\System32\RDPDD.dll failed to load:
http://blogs.technet.com/brad_rutkow...d-to-load.aspx

David Dickinson wrote:
I have two XP Pro SP3 test machines. One has the problem, the other
doesn't. I haven't been able to isolate the cause yet. The machines
have significant differences in their configurations, so it will take
some time.


"Susan Bradley" wrote in message
...
Second machine tested. Can't repro on second box.

Susan Bradley wrote:

Not repro-ing that here.

XP sp3

tommydokc wrote:
we're having the exact same problems here on several machines.
I've
had to boot to safe mode to get it uninstalled then everything is
back to normal. I would advise to disable the download of that
update at this point.



"David Dickinson" wrote:

I tested KB969947 on a Windows XP Professional SP3 machine that
is
reserved for testing. After installing that update, I could not
log on to it in a Remote Desktop session. In fact, the machine
had
frozen and could not even be accessed with its keyboard or mouse,
and the hard drive light flashed in a repeating pattern over
several minutes. However, after restarting the machine, I could
log
on to it locally. After uninstalling that update, RDP sessions
were
successful. I reinstalled it and tested again, and RDP sessions
failed. After uninstalling, they worked.

Test this update thoroughly before deploying it! I've notified
Microsoft about the issue, but the help that is available at this
time told me that Microsoft Enterprise will have to deal with it,
and I have to wait until normal business hours tomorrow to
contact
them.

I haven't yet tested this update on other versions of Windows,
but
I hope no adminstrators have large networks using automatic
updates. I'm just hoping that this isn't the disaster that it
could
be.

David Dickinson
eveningstar at mvps dot org

NOTE: This message has been cross-posted to
microsoft.public.windowsupdate, microsoft.public.security,
microsoft.public.microsoft_update_catalog, and
microsoft.public.windowsxp.security_admin.
.

We have a similar problem. If I login (without RDP), the machine
freezes. In safe mode it is possible to uninstall the update. Than the
problem is solved. In this department we have about 20 PC's. Only 4 of
them got this phenomenon. At one of this PC I was unable to start the
safe mode. Only the Recovery Console gave me the possibility to
uninstall the patch.

David Dickinson schrieb:
I tested KB969947 on a Windows XP Professional SP3 machine that is
reserved for testing. After installing that update, I could not log on
to it in a Remote Desktop session. In fact, the machine had frozen and
could not even be accessed with its keyboard or mouse, and the hard
drive light flashed in a repeating pattern over several minutes.
However, after restarting the machine, I could log on to it locally.
After uninstalling that update, RDP sessions were successful. I
reinstalled it and tested again, and RDP sessions failed. After
uninstalling, they worked.

Test this update thoroughly before deploying it! I've notified
Microsoft about the issue, but the help that is available at this time
told me that Microsoft Enterprise will have to deal with it, and I have
to wait until normal business hours tomorrow to contact them.

I haven't yet tested this update on other versions of Windows, but I
hope no adminstrators have large networks using automatic updates. I'm
just hoping that this isn't the disaster that it could be.

David Dickinson
eveningstar at mvps dot org

NOTE: This message has been cross-posted to
microsoft.public.windowsupdate, microsoft.public.security,
microsoft.public.microsoft_update_catalog, and
microsoft.public.windowsxp.security_admin.

"Stefan Ikas" wrote in message
...
We have a similar problem. If I login (without RDP), the machine freezes.
In safe mode it is possible to uninstall the update. Than the problem is
solved. In this department we have about 20 PC's. Only 4 of them got this
phenomenon. At one of this PC I was unable to start the safe mode. Only
the Recovery Console gave me the possibility to uninstall the patch.

Let me make sure that I understand you: your machine freezes when you login
locally and /not/ in an RDP session? And the problem is with KB969947?

This is a new symptom, and a very interesting one.


David Dickinson schrieb:
I tested KB969947 on a Windows XP Professional SP3 machine that is
reserved for testing. After installing that update, I could not log on
to it in a Remote Desktop session. In fact, the machine had frozen and
could not even be accessed with its keyboard or mouse, and the hard drive
light flashed in a repeating pattern over several minutes. However,
after restarting the machine, I could log on to it locally. After
uninstalling that update, RDP sessions were successful. I reinstalled it
and tested again, and RDP sessions failed. After uninstalling, they
worked.

Test this update thoroughly before deploying it! I've notified Microsoft
about the issue, but the help that is available at this time told me that
Microsoft Enterprise will have to deal with it, and I have to wait until
normal business hours tomorrow to contact them.

I haven't yet tested this update on other versions of Windows, but I hope
no adminstrators have large networks using automatic updates. I'm just
hoping that this isn't the disaster that it could be.

David Dickinson
eveningstar at mvps dot org

NOTE: This message has been cross-posted to
microsoft.public.windowsupdate, microsoft.public.security,
microsoft.public.microsoft_update_catalog, and
microsoft.public.windowsxp.security_admin.

Yes you are right! If I uninstall this update the machine is OK. To be
sure that patch make this problem, I installed this patch again and the
problem was back: PC is frozen.

David Dickinson schrieb:
"Stefan Ikas" wrote in message
...
We have a similar problem. If I login (without RDP), the machine
freezes. In safe mode it is possible to uninstall the update. Than the
problem is solved. In this department we have about 20 PC's. Only 4 of
them got this phenomenon. At one of this PC I was unable to start the
safe mode. Only the Recovery Console gave me the possibility to
uninstall the patch.

Let me make sure that I understand you: your machine freezes when you
login locally and /not/ in an RDP session? And the problem is with
KB969947?

This is a new symptom, and a very interesting one.


David Dickinson schrieb:
I tested KB969947 on a Windows XP Professional SP3 machine that is
reserved for testing. After installing that update, I could not log
on to it in a Remote Desktop session. In fact, the machine had
frozen and could not even be accessed with its keyboard or mouse, and
the hard drive light flashed in a repeating pattern over several
minutes. However, after restarting the machine, I could log on to it
locally. After uninstalling that update, RDP sessions were
successful. I reinstalled it and tested again, and RDP sessions
failed. After uninstalling, they worked.

Test this update thoroughly before deploying it! I've notified
Microsoft about the issue, but the help that is available at this
time told me that Microsoft Enterprise will have to deal with it, and
I have to wait until normal business hours tomorrow to contact them.

I haven't yet tested this update on other versions of Windows, but I
hope no adminstrators have large networks using automatic updates.
I'm just hoping that this isn't the disaster that it could be.

David Dickinson
eveningstar at mvps dot org

NOTE: This message has been cross-posted to
microsoft.public.windowsupdate, microsoft.public.security,
microsoft.public.microsoft_update_catalog, and
microsoft.public.windowsxp.security_admin.

On Nov 12, 2:59*am, Stefan Ikas wrote:
Yes you are right! If I uninstall this update the machine is OK. To be
sure that patch make this problem, I installed this patch again and the
problem was back: PC is frozen.



Yep, we are having the problem in a major way here. The majority of
our workstations all share the same ghost image and its been affecting
them all. We are doing both the removal of the update and loading an
update to our video drivers and so far its working just fine for us.
We are using ATI video cards and loading the R186683.exe update from
Dell for them. We've been loading critical security updates using WSUS
for about 4 years now and so far this is the first one that has bombed
out totally. Guess 4 years with no bombing out in a Microsoft world
isn't too bad eh? :-)

(New to posting-apologies if I break etiquette)
I concure with "Nort"s issue/solution...
We have Dell Optiplex 745/755's - XPProSP3 w/ATI Radeon HD2400 video cards.
FYI - Dell website drivers not helpfull with this (out of date as of 12Nov09)
- AMD had the latest on their website
(http://game.amd.com/us-en/drivers_ca...xp/radeonx-xp).
Uninstalled Security Update KB969947 (VIA SafeMode) rebooted - installed
latest video drivers - restarted PC's - Re-Installed SU KB969947 (Held
Breath) and things are running very well at this point. This has affected 5
PC's so far (Updates installed on 11Nov09 causing initial issue - my "clue")
Waiting for my other 30+ 745/755 PC's to install the update and freeze -
Doing this Reactivily, not Proactive at this point. (Staffing-but that's
another post :-)
Thanks for the help folks...
Wouldn't have attempted the AMD Website Driver fix without this
posting/string for information.

"Nort" wrote:

I have seen a problem where after installing 969947, the PC will
lockup shortly after you login. I was able to uninstall the update in
safe mode.

This has only occurred on PC's with an ATI Radeon HD 2400 series
cards. Upgrading to the latest version of the driver (9.1, released
10/22/2009) and then reapplying the 969947 update seems to fix the
issue.

Just my .02


On Nov 11, 3:09 pm, Susan Bradley wrote:
You said you had a case open right? If not ping me and I'll get you
one. Can you let me know what they say?

David Dickinson wrote:
I had considered display driver problems, but that's not it. With
969947 installed, the machine freezes during RDP logon. Without 969947,
the machine works fine. There are absolutely not messages in the event
log relating to this issue. The security log doesn't even show the
normal logon attempt messages. As soon as I enter the password to logon
in a remote desktop session, the machine freezes.

"Susan Bradley" wrote in message
...
Recently I had an issue post .net patch that I could not RDP. It was
due to the monitor card software interaction with 951847.

Look in your event log on the workstations and see if you are getting
that error.

After the install of KB951847 (.net family) I found I could not rdp
into a XP workstation. Updating the driver didn't work but putting in
the registry key did:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session
Manager\Memory Management]

"SessionImageSize"=dword:00000020

Brad Rutkowski's Blog : \SystemRoot\System32\RDPDD.dll failed to load:
http://blogs.technet.com/brad_rutkow.../04/systemroot....

David Dickinson wrote:
I have two XP Pro SP3 test machines. One has the problem, the other
doesn't. I haven't been able to isolate the cause yet. The machines
have significant differences in their configurations, so it will take
some time.

"Susan Bradley" wrote in message
. ..
Second machine tested. Can't repro on second box.

Susan Bradley wrote:

Not repro-ing that here.

XP sp3

tommydokc wrote:
we're having the exact same problems here on several machines.
I've had to boot to safe mode to get it uninstalled then
everything is back to normal. I would advise to disable the
download of that update at this point.

"David Dickinson" wrote:

I tested KB969947 on a Windows XP Professional SP3 machine that
is reserved for testing. After installing that update, I could
not log on to it in a Remote Desktop session. In fact, the
machine had frozen and could not even be accessed with its
keyboard or mouse, and the hard drive light flashed in a
repeating pattern over several minutes. However, after restarting
the machine, I could log on to it locally. After uninstalling
that update, RDP sessions were successful. I reinstalled it and
tested again, and RDP sessions failed. After uninstalling, they
worked.

Test this update thoroughly before deploying it! I've notified
Microsoft about the issue, but the help that is available at this
time told me that Microsoft Enterprise will have to deal with it,
and I have to wait until normal business hours tomorrow to
contact them.

I haven't yet tested this update on other versions of Windows,
but I hope no adminstrators have large networks using automatic
updates. I'm just hoping that this isn't the disaster that it
could be.

David Dickinson
eveningstar at mvps dot org

NOTE: This message has been cross-posted to
microsoft.public.windowsupdate, microsoft.public.security,
microsoft.public.microsoft_update_catalog, and
microsoft.public.windowsxp.security_admin.
.

.

On Nov 12, 9:59*am, PhilBatesNY
wrote:
(New to posting-apologies if I break etiquette)
I concure with "Nort"s issue/solution...
We have Dell Optiplex 745/755's - XPProSP3 w/ATI Radeon HD2400 video cards. *
FYI - Dell website drivers not helpfull with this (out of date as of 12Nov09)
- AMD had the latest on their website
(http://game.amd.com/us-en/drivers_ca...xp/radeonx-xp). *
Uninstalled Security Update KB969947 (VIA SafeMode) rebooted - installed
latest video drivers - restarted PC's - Re-Installed SU KB969947 (Held
Breath) and things are running very well at this point. *This has affected 5
PC's so far (Updates installed on 11Nov09 causing initial issue - my "clue") *
Waiting for my other 30+ 745/755 PC's to install the update and freeze -
Doing this Reactivily, not Proactive at this point. (Staffing-but that's
another post :-)
Thanks for the help folks...


Now we are having some sproadic issues with Network Cards and Printers
due to this. We are having to remove the drivers for the network cards
and parallel ports and let Windows reinstall them before they will
work properly. Wow, they did a bangup job this time!

Jeez... same problem here and spent hours trying to figure out why no rdp.
John

tommydokc wrote:
we're having the exact same problems here on several machines. I've had to
boot to safe mode to get it uninstalled then everything is back to normal. I
would advise to disable the download of that update at this point.



"David Dickinson" wrote:

I tested KB969947 on a Windows XP Professional SP3 machine that is reserved
for testing. After installing that update, I could not log on to it in a
Remote Desktop session. In fact, the machine had frozen and could not even
be accessed with its keyboard or mouse, and the hard drive light flashed in
a repeating pattern over several minutes. However, after restarting the
machine, I could log on to it locally. After uninstalling that update, RDP
sessions were successful. I reinstalled it and tested again, and RDP
sessions failed. After uninstalling, they worked.

Test this update thoroughly before deploying it! I've notified Microsoft
about the issue, but the help that is available at this time told me that
Microsoft Enterprise will have to deal with it, and I have to wait until
normal business hours tomorrow to contact them.

I haven't yet tested this update on other versions of Windows, but I hope no
adminstrators have large networks using automatic updates. I'm just hoping
that this isn't the disaster that it could be.

David Dickinson
eveningstar at mvps dot org

NOTE: This message has been cross-posted to microsoft.public.windowsupdate,
microsoft.public.security, microsoft.public.microsoft_update_catalog, and
microsoft.public.windowsxp.security_admin.

.

No problemo, just checking. Have you seen Kevin Hau's post where he pointed
afflicted users to
http://social.answers.microsoft.com/...f-73e607d8760a ?

QP
The resolution is to boot to safe mode and uninstall the update, then
update the ATI video drivers, then reboot and reinstall the update.
/QP

If no joy, we've got a CSS Security PM who will work with you.
--
~Robear


David Dickinson wrote:
@PA Bear: Yes, thanks, I do know about the benefits. But I haven't been
an
MVP since 2002, when my business expanded and I just couldn't keep up with
the forums. Not being an MVP anymore, I don't qualify for the package.
But
now that I've been able to delegate some of my more tedious
responsibilities, I hope to have more time to spend here. I'd forgotten
how
much I enjoyed it.


"PA Bear [MS MVP]" wrote in message
...
@David: Are you aware of the annual Global Technical Support package
benefit and did you avail yourself of same to get assistance with this?
cf. https://mvp.support.microsoft.com/gp/MVPTechSup
--
~Robear

David Dickinson wrote:
I spent two hours on the phone, including hold times, with Microsoft
while
they transferred me to different departments. PC Safety says its a
business
problem since it involves RDP. Business support says its a PC Safety
problem since it involves an update. Then we got disconnected when a
guy's
headsets failed. I can't try again until tomorrow. I am not a happy
guy.

I'll post an update when I learn something.


"Susan Bradley" wrote in message
...
You said you had a case open right? If not ping me and I'll get you
one.
Can you let me know what they say?

David Dickinson wrote:
I had considered display driver problems, but that's not it. With
969947
installed, the machine freezes during RDP logon. Without 969947, the
machine works fine. There are absolutely not messages in the event
log
relating to this issue. The security log doesn't even show the normal
logon attempt messages. As soon as I enter the password to logon in a
remote desktop session, the machine freezes.

"Susan Bradley" wrote in message
...
Recently I had an issue post .net patch that I could not RDP. It was
due to the monitor card software interaction with 951847.

Look in your event log on the workstations and see if you are getting
that error.

After the install of KB951847 (.net family) I found I could not rdp
into
a XP workstation. Updating the driver didn't work but putting in the
registry key did:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session
Manager\Memory Management]

"SessionImageSize"=dword:00000020



Brad Rutkowski's Blog : \SystemRoot\System32\RDPDD.dll failed to
load:
http://blogs.technet.com/brad_rutkow...d-to-load.aspx

David Dickinson wrote:
I have two XP Pro SP3 test machines. One has the problem, the other
doesn't. I haven't been able to isolate the cause yet. The
machines
have significant differences in their configurations, so it will
take
some time.


"Susan Bradley" wrote in message
...
Second machine tested. Can't repro on second box.

Susan Bradley wrote:

Not repro-ing that here.

XP sp3

tommydokc wrote:
we're having the exact same problems here on several machines.
I've
had to boot to safe mode to get it uninstalled then everything is
back to normal. I would advise to disable the download of that
update at this point.



"David Dickinson" wrote:

I tested KB969947 on a Windows XP Professional SP3 machine that
is
reserved for testing. After installing that update, I could not
log on to it in a Remote Desktop session. In fact, the machine
had
frozen and could not even be accessed with its keyboard or
mouse,
and the hard drive light flashed in a repeating pattern over
several minutes. However, after restarting the machine, I could
log
on to it locally. After uninstalling that update, RDP sessions
were
successful. I reinstalled it and tested again, and RDP sessions
failed. After uninstalling, they worked.

Test this update thoroughly before deploying it! I've notified
Microsoft about the issue, but the help that is available at
this
time told me that Microsoft Enterprise will have to deal with
it,
and I have to wait until normal business hours tomorrow to
contact
them.

I haven't yet tested this update on other versions of Windows,
but
I hope no adminstrators have large networks using automatic
updates. I'm just hoping that this isn't the disaster that it
could
be.

David Dickinson
eveningstar at mvps dot org

NOTE: This message has been cross-posted to
microsoft.public.windowsupdate, microsoft.public.security,
microsoft.public.microsoft_update_catalog, and
microsoft.public.windowsxp.security_admin.
.

cf.
http://social.answers.microsoft.com/...f-73e607d8760a

Stefan Ikas wrote:
Yes you are right! If I uninstall this update the machine is OK. To be
sure that patch make this problem, I installed this patch again and the
problem was back: PC is frozen.

David Dickinson schrieb:
"Stefan Ikas" wrote in message
...
We have a similar problem. If I login (without RDP), the machine
freezes. In safe mode it is possible to uninstall the update. Than the
problem is solved. In this department we have about 20 PC's. Only 4 of
them got this phenomenon. At one of this PC I was unable to start the
safe mode. Only the Recovery Console gave me the possibility to
uninstall the patch.

Let me make sure that I understand you: your machine freezes when you
login locally and /not/ in an RDP session? And the problem is with
KB969947?

This is a new symptom, and a very interesting one.


David Dickinson schrieb:
I tested KB969947 on a Windows XP Professional SP3 machine that is
reserved for testing. After installing that update, I could not log
on to it in a Remote Desktop session. In fact, the machine had
frozen and could not even be accessed with its keyboard or mouse, and
the hard drive light flashed in a repeating pattern over several
minutes. However, after restarting the machine, I could log on to it
locally. After uninstalling that update, RDP sessions were
successful. I reinstalled it and tested again, and RDP sessions
failed. After uninstalling, they worked.

Test this update thoroughly before deploying it! I've notified
Microsoft about the issue, but the help that is available at this
time told me that Microsoft Enterprise will have to deal with it, and
I have to wait until normal business hours tomorrow to contact them.

I haven't yet tested this update on other versions of Windows, but I
hope no adminstrators have large networks using automatic updates.
I'm just hoping that this isn't the disaster that it could be.

David Dickinson
eveningstar at mvps dot org

NOTE: This message has been cross-posted to
microsoft.public.windowsupdate, microsoft.public.security,
microsoft.public.microsoft_update_catalog, and
microsoft.public.windowsxp.security_admin.

Follow-up: See the Known Issues section of
http://support.microsoft.com/kb/969947 (Revised 12 Nov-09)


PA Bear [MS MVP] wrote:
cf.
http://social.answers.microsoft.com/...f-73e607d8760a
Stefan Ikas wrote:
Yes you are right! If I uninstall this update the machine is OK. To be
sure that patch make this problem, I installed this patch again and the
problem was back: PC is frozen.

David Dickinson schrieb:
"Stefan Ikas" wrote in message
...
We have a similar problem. If I login (without RDP), the machine
freezes. In safe mode it is possible to uninstall the update. Than the
problem is solved. In this department we have about 20 PC's. Only 4 of
them got this phenomenon. At one of this PC I was unable to start the
safe mode. Only the Recovery Console gave me the possibility to
uninstall the patch.

Let me make sure that I understand you: your machine freezes when you
login locally and /not/ in an RDP session? And the problem is with
KB969947?

This is a new symptom, and a very interesting one.


David Dickinson schrieb:
I tested KB969947 on a Windows XP Professional SP3 machine that is
reserved for testing. After installing that update, I could not log
on to it in a Remote Desktop session. In fact, the machine had
frozen and could not even be accessed with its keyboard or mouse, and
the hard drive light flashed in a repeating pattern over several
minutes. However, after restarting the machine, I could log on to it
locally. After uninstalling that update, RDP sessions were
successful. I reinstalled it and tested again, and RDP sessions
failed. After uninstalling, they worked.

Test this update thoroughly before deploying it! I've notified
Microsoft about the issue, but the help that is available at this
time told me that Microsoft Enterprise will have to deal with it, and
I have to wait until normal business hours tomorrow to contact them.

I haven't yet tested this update on other versions of Windows, but I
hope no adminstrators have large networks using automatic updates.
I'm just hoping that this isn't the disaster that it could be.

David Dickinson
eveningstar at mvps dot org

NOTE: This message has been cross-posted to
microsoft.public.windowsupdate, microsoft.public.security,
microsoft.public.microsoft_update_catalog, and
microsoft.public.windowsxp.security_admin.

Yeah, it works! Thanks!

PA Bear [MS MVP] schrieb:
cf.
http://social.answers.microsoft.com/...f-73e607d8760a


Stefan Ikas wrote:
Yes you are right! If I uninstall this update the machine is OK. To be
sure that patch make this problem, I installed this patch again and the
problem was back: PC is frozen.

David Dickinson schrieb:
"Stefan Ikas" wrote in message
...
We have a similar problem. If I login (without RDP), the machine
freezes. In safe mode it is possible to uninstall the update. Than the
problem is solved. In this department we have about 20 PC's. Only 4 of
them got this phenomenon. At one of this PC I was unable to start the
safe mode. Only the Recovery Console gave me the possibility to
uninstall the patch.

Let me make sure that I understand you: your machine freezes when you
login locally and /not/ in an RDP session? And the problem is with
KB969947?

This is a new symptom, and a very interesting one.


David Dickinson schrieb:
I tested KB969947 on a Windows XP Professional SP3 machine that is
reserved for testing. After installing that update, I could not log
on to it in a Remote Desktop session. In fact, the machine had
frozen and could not even be accessed with its keyboard or mouse, and
the hard drive light flashed in a repeating pattern over several
minutes. However, after restarting the machine, I could log on to it
locally. After uninstalling that update, RDP sessions were
successful. I reinstalled it and tested again, and RDP sessions
failed. After uninstalling, they worked.

Test this update thoroughly before deploying it! I've notified
Microsoft about the issue, but the help that is available at this
time told me that Microsoft Enterprise will have to deal with it, and
I have to wait until normal business hours tomorrow to contact them.

I haven't yet tested this update on other versions of Windows, but I
hope no adminstrators have large networks using automatic updates.
I'm just hoping that this isn't the disaster that it could be.

David Dickinson
eveningstar at mvps dot org

NOTE: This message has been cross-posted to
microsoft.public.windowsupdate, microsoft.public.security,
microsoft.public.microsoft_update_catalog, and
microsoft.public.windowsxp.security_admin.