angbob
2007-09-03 17:52:02 UTC
Windows XP Home SP2
My computer is part of a two-machine network. The other machine is not
running. There are no remote connections. Booting has worked fine for
months. A few days ago, I installed UltraVNC, the remote desktop program. I
started it once, but merely exited.
Approximately since then, when I boot, I get a failure from winlogon.exe:
Source: Application Error
Event ID: 1000
Faulting application , version 0.0.0.0, faulting module uxtheme.dll, version
6.0.2900.2180, fault address 0x00002da3.
Source: Application Error
Event ID: 1004
Faulting application winlogon.exe, version 0.0.0.0, faulting module
uxtheme.dll, version 6.0.2900.2180, fault address 0x00002da3.
http://support.microsoft.com/kb/828664/en-us suggests corrupted Terminal
Services Data, and it lists files updated by a hotfix.
The versions of the files on my system are all newer than the ones listed in
the table, "Windows XP, 32-bit editions".
The list under "Symptoms" mentions winlogon.exe, but does not mention
uxtheme.dll.
How do I figure out whether Terminal Services is the problem?
Any thoughts at all on what to look for?
Regards, Bob
My computer is part of a two-machine network. The other machine is not
running. There are no remote connections. Booting has worked fine for
months. A few days ago, I installed UltraVNC, the remote desktop program. I
started it once, but merely exited.
Approximately since then, when I boot, I get a failure from winlogon.exe:
Source: Application Error
Event ID: 1000
Faulting application , version 0.0.0.0, faulting module uxtheme.dll, version
6.0.2900.2180, fault address 0x00002da3.
Source: Application Error
Event ID: 1004
Faulting application winlogon.exe, version 0.0.0.0, faulting module
uxtheme.dll, version 6.0.2900.2180, fault address 0x00002da3.
http://support.microsoft.com/kb/828664/en-us suggests corrupted Terminal
Services Data, and it lists files updated by a hotfix.
The versions of the files on my system are all newer than the ones listed in
the table, "Windows XP, 32-bit editions".
The list under "Symptoms" mentions winlogon.exe, but does not mention
uxtheme.dll.
How do I figure out whether Terminal Services is the problem?
Any thoughts at all on what to look for?
Regards, Bob