winlogon.exe fails. uxtheme.dll faults

[Guest]

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

 

[Guest]

Try replacing the uxtheme.dll file.
http://www.dll-files.com/dllindex/download.php?uxthemedownload0UKkVCaMgR

 

[Guest]

Thanks!
The original and new files have different lengths, and FC shows that they
differ (a lot), but they have the same version number (6.0.2900.2180).

How can I swap the old and new uxtheme.dll files? I cannot rename the old
file while the system is running because of dependency. (PROCEXP's
Dependency Walker shows that COMDLG32.DLL depends on UXTHEME.DLL.)

Regards, Bob

 

[Guest]

1) Download the file and extract in a handy location (eg: your Desktop). This
should create a new uxtheme.dll file in that location.
2) Go to C:WINDOWSSystem32 and rename uxtheme.dll to uxtheme.dll.old
3) Put the new uxtheme.dll into C:WINDOWSSystem32
4) If you get any warnings from Windows stating that an original system file
has been replaced, you must click "Cancel", otherwise the new uxtheme.dll
will be replaced with the original one.
5) Reboot

 

[Guest]

I followed your suggestions, and it seemed to work. But when I copied the
new file into system 32, what appeared was the old file.

After step two's rename, there is an entry for the new name
"uxtheme.dll.old", as expected, and also an entry for the old name
"uxtheme.dll", as if the rename did a copy. When I try to delete
uxtheme.dll.old, I get a message saying the file uxtheme.dll is in use. The
rename has created some kind of link.

Using the "copy" command in a Command window, when I copy the new file from
another directory to system32\uxtheme.dll, it asks whether I wish to
overwrite. I answer yes, and there is no error complaint, but the file in
system32 is then the old file, as if the copy did nothing.

The old file will not yield its place. (The spell checker I used on this
message suggests replacing "uxtheme" with "exhume". Delightful.)

Same results using an Explorer window, and drag/drop.

Is there a bit somewhere I can toggle to make the commands work?

1) Download the file and extract in a handy location (eg: your Desktop). This
should create a new uxtheme.dll file in that location.
2) Go to C:WINDOWSSystem32 and rename uxtheme.dll to uxtheme.dll.old
3) Put the new uxtheme.dll into C:WINDOWSSystem32
4) If you get any warnings from Windows stating that an original system file
has been replaced, you must click "Cancel", otherwise the new uxtheme.dll
will be replaced with the original one.
5) Reboot

....

 

[mhc]

I followed your suggestions, and it seemed to work. But when I copied the
new file into system 32, what appeared was the old file.

After step two's rename, there is an entry for the new name
"uxtheme.dll.old", as expected, and also an entry for the old name
"uxtheme.dll", as if the rename did a copy. When I try to delete
uxtheme.dll.old, I get a message saying the file uxtheme.dll is in use. The
rename has created some kind of link.

Using the "copy" command in a Command window, when I copy the new file from
another directory to system32\uxtheme.dll, it asks whether I wish to
overwrite. I answer yes, and there is no error complaint, but the file in
system32 is then the old file, as if the copy did nothing.

The old file will not yield its place. (The spell checker I used on this
message suggests replacing "uxtheme" with "exhume". Delightful.)

Same results using an Explorer window, and drag/drop.

Is there a bit somewhere I can toggle to make the commands work?

The instructions you were given would have worked on Windows 2000 but
not on Windows XP. Here's what you do. Reboot your system to get to a
known state. Put the new copy of uxtheme.dll in the
windows\system32\dllcache directory. Rename the uxtheme.dll file in the
windows\system directory to uxtheme.old. You will again notice that
Windows has replaced the uxtheme.dll file, BUT it will be with your file!

Now reboot your system again, and Windows will be using your uxtheme.dll
file. You can then delete the uxtheme.old file -- and any other versions
of the file you have created.

 

[Phil Swallow]

Hi Thanks for this thread. I have winlogon.exe error associated apparently with uxtheme.dll.

When I try to do what you suggest - replace uxtheme.dll in c:/windows/system32 - the system keeps replacing the dll file. Eventually I got the new version in before it replaced it - however it overwrote the new one with the old one!

Any thoughts? TIA

Phil

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com