RDP no longer working
We have a few people in the office running SP3 and this morning they were no longer able to RDP into remote systems. They would get the following error;
"The Pre-release version of Remote Desktop Connection has expired. To download the full version of Remote Desktop Connection, go to Windows Update or contact your system administrator"
I've seen nothing on this forum abotu it yet, though there is talk of it on some other forums. It apears to be a problem with SP3 and it only apeared over the weekend, RDP worked fine last week. We've fixed it buy copying the RDP files from an SP2 machine into a new folder (Not System32) and runningit from there. So if it is happenign to you, that is a fix (as is rolling back the date on your system clock I've heard) Mainly I wanted MS to know about this so they can fix it.
McF
All Replies
Did you already installed the Windows XP SP3 RC-Refresh? If not- uninstall the current beta and install the refresh from WU and try again.
I didn't try that for 2 reasons.
1) I've read on other forums that it doens't fix the problem
2) I'm not sure why it would fix it since the refresh came out before RDP stopped working, so why / how could it fix it?
Hello Shaw,
Can you please let us know what XPSP3 build no is installed on the machine. You can find that info by typing winver on cmd prompt.
Have you installed any Test tclient 6.1 on the machine(KB 937468)?
Also please let us know the fileversion of %windir%\system32\mstsc.exe
Thanks,
Atul
- I'm also having the same problem with remote desktop no longer working.
Build 2600.xpsp.071130-1427 : Service Pack 3, v.3264
%windir%\system32\mstsc.exe - file version 6.0.6001.166559 Because of test reasons time bomb was set for mstsc in XPSP3 v.3264. Hence they have stopped working from 7th April 2008.
Please do either of the following options to resolve the problem:
1) Install XPSP3 RC2 or later.
2) If you want to wait for XPSP3 RTM version and dont want to install one now, then you need to replace mstsc.exe and mstscax.dll on your machine with the one present in XPSP3 RC2 release or later.
Thanks,
Atul
hello every one,
i am facing the same issue with RDP,
well i am not really quite aware with what is RC2 or RTM, but i need to get this solved, so in steps how can i make this work.
Evening A.
This is a simple process of removing v3264.
Remember to write down any setting you need for any network routers.
Start by booting to safe mode. This is done by restartibng the system. Pressing the F-8 key prior to the splash screen. Once in safe mode. Pressing start, control panel, add/remove programs, then finding the sp3 icon. Click on remove. Remember to shut down any antivirus programs!
Once the system has completely removed the SP3 and restored your SP2. The fun stuff begins
All the things you required to install the sp3 are required again. Since the SP2 recreated your system from .inf And not just copied everything over from your back up. *This is normal behavior* This allows for programs installed during usage of SP3 to be used. beware this may not always be reliable. *Only has problems ocassionally* Some programs may need re-installation.
Any steps you needed to get SP3 installed may need to be re-applied. The reset.cmd/subac program may need to be ran, the additon to the registry for adding sp3 to enable download. To make things more re-liable for me I install the 2.5 B.I.T. program. This is because it will download in the background and does not stall on slower internet connections * no dial up bit slower DSL connections.
The registry fix to proect certain I.E. errors also needs to be ran, This fix is to prevent internet explorer needs to be added. *I.E. 6,7,8*
For various I.E. issues there is this post located here.
http://www.ie-vista.com/kbase3.html
Covers everything from Sp2, Sp3 and Vista I.E. issues
After rebooting you can then run the windows update and install the latest version of v5503 from windowsupdate
At this point you can restore the RDP functionality you are requesting.
Good luck and post back please what works out for you
Here is a quick work around.
Make a batch file with the following -
echo off
SET ddd=%DATE:* =%
date 01-04-2008
start mstsc /admin
ping 0.0.0.0
date %ddd%Note - the /admin switch is optional
- youyr a smart man
as a note
if your sp3 was intergrated like mine, you cannot remover sp3 beta to upgrade
so, reinstall with sp1 or 2, install sp3 and its good
thanks dude
I am on call and cannot remote into the customer in case I have to troubleshoot issues. This is totally frustrating. Was this tested prior to putting out to the general users....This is terrible of MS. I have to be able to remote to work and now I have to do a bunch of troubleshooting from my PC to fix the issue.
SANDELO wrote: This is terrible of MS. I have to be able to remote to work and now I have to do a bunch of troubleshooting from my PC to fix the issue. Who can you blame but yourself? Read the Terms and Conditions first before installing beta software for testing purposes.
- The fix for this is simple and I came across it by accident. Just rename your mstsc.exe and mstscax.dll to .bak and new files will be created instantly by Windows to replace these files. Worked for me.
- What exactly does this batch file do thanks in advanced.
- so where can i find the RC2 download? i can't seem to find anything on the new connect site.
Revelstone77 wrote: so where can i find the RC2 download? i can't seem to find anything on the new connect site. Revelstone77,
First, read this thread carefully --> http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3061999&SiteID=17
And if you still don't understand, then try here --> http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3182863&SiteID=17
Regards,
Thomas
- Apologies for an error of omission - a 2nd file is needed.
This is MSTSCAX.DLL.
ALONG WITH MSTSC.EXE FILE FROM AN XP MACHINE (SP2),
COPY BOTH TO C:\ OR THE DESKTOP AND RUN THE .EXE FILE.
Until an SP3 release has it corrected you will be able to use Remote Desktop with this remedy.
This isn't even necessary. Just delete the mstsc.exe and mstscax.dll files (or rename them). No fishing necessary...
Glarty
How do you get this batch file to work?. I'm new to batch files, I manage to create it but how do I use it to get RD to work again?..
thanks for your help!
This worked for me.
1. get into safe mode
2. Yes, as suggested previously, get the following files from an xp sp2 machine (xp or home should be ok).
a. mstscax.dll
b. mstsc.exe
Note: Do this on safe mode otherwise windows will just recreate the files even if you replace them or delete them (I just find out about this and thought the clarification was not noted before.)
Its a temporary work around. The reason MS included a date *MStsc * doesnt work any more. Is simple. Ms FT has moved on in image support. Instead of making a Full releaswe candidate survive longer then necesary. The mage for "deployment" has been fixed. *Not something to say to a guy in the same sentance* nevermind. Its simply a matter of the program intention. Tesint purposes ONLY!, as stated in the liscensing term. Not mixing things like KMDF, UMDF in a testing environment. The fain image has fixes in the WSUS part of the operating system and a few performance tweaks, in addition to the HD audio many, many people requested to be added to the LATEST image. I know people are comfortable with some thing but please move on to the latest image with the rest of use. So the feed back loop can be completed! This is the entirepurpose of TESTING!
*This is my request, added support to a initial script. PREPARE a USB/Floopy image of SATA NVIDIA, Intel and raid. So that at least people are not caught with out the proper image/driver available during installation. Or at least some sort of limited internet access concole so the driver can be made available! I relize hardware stardards ar stuck at 2002. But even USB, support, m/b standards are moving on also. At lease bring some level of standards request like a addition to the storage manager to reconize at least a driver is needed to access a RAID array. Small price? Perhaps/ Risk vers rewards also applys here. Yes I can afford to purchase a external IBM floppy disk drive. But not many people in a coperate environment have the resources to add this.
Perhaps its time for me to start my own program/hardware soltuion. Basic set of BIOS image? to create an add on bios patch to simlulate a floopy disk drive in a card reader. ROM only with at least a basic mixed set of drivers. hmmmm A total hardware soltuion?
____________________
100 watt Power Supply? Laughed outta next lan party!
Keith
Hoi ShawMc!
As you can see in this thread a bit down, there is a hint that works easily and properly. As I may add my solution worked like this:
I searched the mstsc.exe and it's dll
There were files under windows\system32 . The exe at 660 KB, the mstac.dll at 2.1MB
Files of the same size are to be found under \windows\servicePackFiles\i386 but namet with lh-prefix: lhmstsc.exe and lhmstscax.dll.
I renamed both of them so that they could not be the source of reinstallation.
I took the smaller mstsc.exe (398KB) and the mstscax.exe (640KB) of the i386 file and copied them into the system32-directory, overwriting anything samenamed in there.
the rdp-program opens properly again.
:-)
Hope it's working well with you, too.
Greets from Dortmund.
P.S.:Thanks to the man who had the idea to rename the new version-files! Can't look for your Name right now.
- You can find the old RDP client at C:\WINDOWS\system32\dllcache\mstsc.exe
- Thanks for nothing!
- Aside from all the bs and misdirection on this thread, the only thing that WORKED for me, was copying the 2 files from another machine that was updated, not installed with sp3 version of xp. The updated machine never had the prob, as sp3 was final version from this page:
http://www.softwarepatch.com/windows/index.html
I suppose upgrading using that version will also eliminate the prob for those who did a complete install rather than upgrade.
That batch shite was useless.
And deleting the files didn't work as it was not an upgrade.
And I found it funny that this guy Thomas was policing people away from this thread, one guy even apologized for
not doing a proper search,
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3360450&SiteID=17
when in fact it was on that thread where I found my answer.
Let the net work, and don't listen to ***s.
~S~ It works, I renamed this two files and now I can use the remote access.
Thanks sbressler
- Guys I tried something better that login windows at the safe mode, just get those two file "From Win XP SP2":
- mstsc.exe
- mstscax.dll
and just copy/paste them at: C:\windows\system32 and chose to replace all the existing files, and that's it !!!
I tried it and it worked for me, anyways if u can't find those files, send me an email to adream_theater@hotmail.com and i'll send them back to you. Fix Do a search for these
mstsc.exe and mstscax.dll
Files found under c:\windwos\system32 can be renamed
Files under c:\windows\servicepackfiles\i386 can be copied into the c:\windows\system32 directory this will fix the problem
Worked for me
You can find the old RDP client at C:\WINDOWS\system32\dllcache\mstsc.exe
That worked fine for me. Just make it a shortcut to your desktop and rename it what you want. Easier than any of the other recommendations. Microsoft should be slapped for making SP3 such a nightmare. Do not install SP3 on a laptop if you don't have your XP disc handy!
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3163197&SiteID=17
Not sure why this would work. I renamed both files ablove and I am still getting the same errors.- I was getting this error message with the final release of SP3.
I just copied the mstsc.exe and mstscax.dll from c:\windows\system32\dllcache to c:\windows\system32 and it works! Now typing mstsc from the run line opens RDC. The start->All programs-> Accessories-> Communication path also works. No need to uninstall anything
I got the info from CastleCops.com just thought I'd share. - OrangeBeard177, please check that the version numbers of mstsc.exe and mstscax.dll are 6.0.6001.18000
- Hmm. Didn't think of that. It's version 5.1.2600.2180 (dang)
How do I correct this?
Now when I try replacing this version with 6.0.6001.18000 it automatically reverts to 5.1.2600.2180.
Have I dug a deeper hole for myself? 5.1.2600.2180 is the original version from SP2. If you apply the public SP3 update, you should get version 6.0.6001.18000. If you did not get that version, then the SP3 updater might not have run to completion successfully: this update is run within a couple of CMD.EXE windows immediately after first login after the SP3 update has re-booted.
The new versions of all the files you need are prefixed by "lh" in the SP3 installation files. You should re-boot into Safe Mode and then do the following in a Command Prompt window:
copy c:\windows\ServicePackFiles\i386\lhmstsc.chm c:\windows\Help\mstsc.chm
copy c:\windows\ServicePackFiles\i386\lhmstsc.exe c:\windows\system32\mstsc.exe
copy c:\windows\ServicePackFiles\i386\lhmstsc.exe c:\windows\system32\dllcache\mstsc.exe
copy c:\windows\ServicePackFiles\i386\lhmstsc.mui c:\windows\system32\en-US\mstsc.exe.mui
copy c:\windows\ServicePackFiles\i386\lhmstscx.dll c:\windows\system32\mstscax.dll
copy c:\windows\ServicePackFiles\i386\lhmstscx.dll c:\windows\system32\dllcache\mstscax.dll
copy c:\windows\ServicePackFiles\i386\lhmstscx.mui c:\windows\system32\en-US\mstscax.dll.mui
This procedure will not however make any modifications to the Windows Installer database which the proper SP3 update would have done.
- I just reinstalled SP3 and now RDC works and it is version 6.0.6001.1800.
Thanks for your help!
Copy files :
mstscax.dll.mui
mstsc.exe
mstsc.exe.mui
Copy shortcut for Remote Desktop
From a computer running XP w/sp2
In Sp3 computer:
Make new folder in C drive :Remote Desktop
Paste files in new folder, do not place in system32
- @robin
Not sure if this thread is dead or not but will your instruction on Vista 32bit client w/ sp1? I have just recently been getting the following error while trying to connect to my Windows Home Server desktop via RDC:
"The system cannot find the file specified. C:\Windows\System32\<LANG_NAME>\ mstsc.exe.MUI"
What I'm not sure of is if it happened because of an update to my Vista client or my WHS box. I'm inclined to think that it was b/c of a recent update to the WHS.
Any thoughts? - So kind of related but kind of not related but same error running RDP7 on Windows XP SP3. I pulled the RDP out of Windows 7 Ultimate Beta to test the new faster RDP7 included with Windows 7. For side by side testing I loaded 2 Windows 7 machines on our Hyper-V server and WAS able to RDP6 and RDP7 to both of them and was just going to show a demo to the boss today of video speed and multi monitor support (the two big ticket items for them holding up our next upgrade) side by side and RDP7 just stopped working giving the "pre-release version has expired".
How do I get the RDP7 client to work again? - >>>>The fix for this is simple and I came across it by accident. Just rename your mstsc.exe and mstscax.dll to .bak and new files will be created instantly by Windows to replace these files. Worked for me.
Can anyone please help? I renamed the files as described above and now I get an error that the file "c:\WINDOWS\system32\<lang_name>\mstsc.exe" cannot be found.
Any suggestions?
- I had the problem "The system cannot find the file specified c:\WINDOWS\system32\<lang_name>\mstsc.exe.MUI" on an XP professional SP3 machine trying to start RDP.
The solution was to copy the files mstsc.exe.mui and mstscax.dll.mui from C:\WINDOWS\system32\en-us from a functioning XP professional SP3 machine to the same directory on the malfunctioning machine. Worked for me. - Thanks Inappa,
Your simple solution copy the files mstsc.exe.mui and mstscax.dll.mui from C:\WINDOWS\system32\en-us solved a big headache for me.
It worked straight up!
JD
