Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, August 5, 2016 1:05 PM | 5 votes
Our test machine was upgraded to the latest build, Windows 10 Pro 1607. Since applying the update, the remote desktop connection to a RDS farm is not working. It immediately says: Your computer can't connect to the Remote Desktop Gateway server. Contact your network administrator for assistance.
Our RD Gateway server is Windows 2008 R2.
Anyone else seeing this behavior?
All replies (73)
Friday, August 5, 2016 1:53 PM
We have the same Problem
It does not work on Windows 10 Pro and Windows 10 Home after Upgrading to 1607
RD Gatewway server is Server 2012. No Log, no Errors, klicking on a Icon does nothing
Friday, August 5, 2016 2:40 PM
Just tested it on another device, and it had no issues. I'll update this thread with my findings.
Friday, August 5, 2016 9:48 PM
I'm seeing the same thing. was working fine, until I upgraded to build 1607
On client I'm seeing errors in the Event Log Under "Applications and Services Logs" -> Microsoft -> Windows -> "RemoteApp and Desktop Connections" -> Operational
Remote application (XX XX X XX XXXXXXX ) failed to launch on RemoteApp and Desktop connection (hostnamechanged.domain.com). (Error = 0x80080005)
Tried same connection from Winsdow 8.1 client and it worked fine
Friday, August 5, 2016 9:59 PM
Turning off the custom scale factor fixed my problem;
1. Hit the Windows key and then type "display".
2. Tap on the "display settings" link that is found.
You should see the following text in red: "A custom scale factor is set".
3. Click on the text underneath which states "Turn off custom scaling and sign out".
4. Sign back in.
MSTSC should now work with an RDP file passed as a parameter.
Wednesday, August 10, 2016 1:17 PM
Doesnt help for me, still not working on several PCs ...
Wednesday, August 10, 2016 1:26 PM
The issue isn't that RDP won't open. The connection file opens just fine. It's that it won't attempt to connect to the RD Gateway.
Thursday, August 11, 2016 5:54 AM
i have same issue on many notebooks. only on just one notebook with 64bit windows is connecting via RD Gateway ok
Sunday, August 14, 2016 8:39 AM | 1 vote
Small solution is copy files mstsc.exe and mstscax.dll from Windows 1511. Fix it all my notebooks with Windows 10 1607
Sunday, August 14, 2016 6:25 PM
Same here, not working with any of my Win 10 computers with 1607 update ...
Sunday, August 14, 2016 7:06 PM | 4 votes
I can confirm that RD Gateway is not working anymore on at least one 32bit system here, since 1607 was applied. Server is running 2012 R2 "with Update", connections from other (1511) systems to this gateway server are still working fine so its definitely a client issue.
regards
edit - I'm currently off-site and cannot test, maybe someone else can?
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client
Name: RDGClientTransport
Type: Dword
Data: 1
(from
)
Monday, August 15, 2016 12:27 PM
Turning off the custom scale factor fixed my problem;
1. Hit the Windows key and then type "display".
2. Tap on the "display settings" link that is found.
You should see the following text in red: "A custom scale factor is set".
3. Click on the text underneath which states "Turn off custom scaling and sign out".
4. Sign back in.
MSTSC should now work with an RDP file passed as a parameter.
Just wanted to add that this worked for me. Turned it off and re-logged and viola it worked. :)
Thanx for the tip.
Monday, August 15, 2016 1:19 PM
This was not the case for us, as scaling wasn't being used. I have noticed that it does appear to be a 32bit Windows 10 1607 issue. Our 64bit machines are not experiencing the problem.
I'll likely resort to what Karel Tinka mentioned, as a temporary workaround.
Monday, August 15, 2016 1:21 PM
Windows 10 32bit or 64bit? Our 64bit machines are working fine. It appears to be a 32bit issue.
Tuesday, August 16, 2016 3:13 PM
There is no "A custom scale factor is set" in my display settings.
Tuesday, August 16, 2016 3:25 PM
In fact, i have one machine at work (belongs to domain) everything works fine there and I can connect through foreign rdp-gateways -> Windows 10 Enterprise 1607 OS Build = 14393.51
but with my machine at my home-office (very same os, but no domain) I'm unable to connect through rdp-gateways but no problems with direct connections:
Tuesday, August 16, 2016 3:26 PM
Small solution is copy files mstsc.exe and mstscax.dll from Windows 1511. Fix it all my notebooks with Windows 10 1607
That works for me too, but cannot be the solution.
Tuesday, August 16, 2016 3:27 PM
My guess is your home-office machine is 32bit.
Thursday, August 18, 2016 2:08 PM
I am using a Windows 10 64-bit and I am having this problem. I also have tried this on two other computers that are 64-bit and they have the same problem so its not only an issue on 32-bit.
And I do not always get the error message when trying to connect and sometimes I can log on multiple times in a row without any problems, and sometimes I get the error message multiple times in a row. It seems rather random.
Thursday, August 18, 2016 2:11 PM
There is no "A custom scale factor is set" in my display settings.
That probably means that it is already turned off.
Wednesday, September 14, 2016 8:52 PM
Our test machine was upgraded to the latest build, Windows 10 Pro 1607. Since applying the update, the remote desktop connection to a RDS farm is not working. It immediately says: Your computer can't connect to the Remote Desktop Gateway server. Contact your network administrator for assistance.
Our RD Gateway server is Windows 2008 R2.
Anyone else seeing this behavior?
I am seeing the same issue. Ever since the update RDP will not work to remote servers get the gateway error. I have uninstalled the updates and it is not working
Wednesday, September 14, 2016 8:56 PM
This only seems to happen from 32bit editions of Windows 10. Please verify that is what you are running.
Friday, September 16, 2016 2:30 PM
I too have this problem on a headless Windows 10 Pro 32 bit after the update to 1607.
Unfortunately, I do not have a copy of "files mstsc.exe and mstscax.dll from Windows 1511." This is our one and only 32 bit Windows 10 system in the company. :(
Edit: We rolled back to 1511 to solve the 1607 RDP issue on Windows 10 32 bit machines.
Thursday, September 22, 2016 8:23 AM
Same problem. So far I was managing to restore old mstsc.exe and mstscax.dll. I have over 1000 workstations with Win10 and for some this is not fix. HELP
Thursday, September 22, 2016 12:26 PM | 2 votes
This fix (method 1) worked on a 32bit Win10 machine.
https://support.microsoft.com/en-us/kb/2903333
The computer was connecting to a 2012R2 RD Gateway and event id 4625 with status 0xC000035B was logged in the security log on the GW server.
I didn't try method 2 because <5 computers were affected.
Hope this helps.
Saturday, September 24, 2016 3:12 PM | 2 votes
Same problem. 20+ PC's affected. Why wouldnt MS fix this?
Sunday, October 2, 2016 8:44 AM
Just confirming that I'm starting to see the same behavior at a number of sites after in-place upgrades to build 1607.
Taking ownership of mstsc.exe and mstscax.dll and then replacing them with the files from c:\windows.old\windows\system32 works a treat although there's been at least one windows update (this week) that's replaced the files again.
The only common theme I've seen so far is that it's the x86 build of Windows 10 - haven't seen any affected x64 builds (yet).
Have tried all the suggestions in this thread to no avail. There are a bunch of errors in the Microsoft-Windows-TerminalServices-RDPClient/Operational Event Log - I haven't got access to an affected workstation at the moment but when I searched for the errors there were hardly any hits.
If anyone else has access, I'd suggest posting in the event MS are watching / aware.
Monday, October 3, 2016 8:55 AM
I have the same problem on my x64 version of Windows 10.
Restoring an old mstsc.exe + dll enables me to use the RDG again directly from mstsc.exe but not in my Remote Desktop Manager.
Let's hope there will be a fix available soon...
Tuesday, October 4, 2016 12:26 AM
I just noticed the same problem from laptop with 32bit build 1607. The RD Gateway is running 2008 R2. Turning off custom scale fix did not work. I was able to bypass the RD Gateway server and connect directly after setting up a VPN tunnel.
The link posted by PU.Ivicia only mentions Server 2012. Anyone know if that would apply to Server 2008 R2 also? I also didn't see any errors in any of the logs.
Tuesday, October 4, 2016 7:21 AM
Yes, i can confirm.
Problem is with all versions of Remote Dekstop Gateway.
When you copy the files from an older version of Win10 you need to copy the mstsc.exe and mstscax.dll from the System32 and SysWow64 folder.
Tuesday, October 4, 2016 4:44 PM
I haven't seen the issue yet on an x64 client. I did try from a 2nd 32bit Win 10 Pro virtual machine and experienced the same problem. Considering the Anniversary update was released on 8/2 and the 1st post in this thread is 8/5, I'm surprised there is no hot fix or update yet. The work around in PU.Ivicia's link https://support.microsoft.com/en-us/kb/2903333 only mentions Server 2012 Gateway's. Has anyone tried it on Server 2008 R2 yet?
Tuesday, October 4, 2016 5:03 PM
I am experiencing the same problem after several of our work PCs updated to Windows 10 Pro (build 1607) (64-bit). We are running Remote Desktop services on our Windows Server 2012 R2. We have quite a number of Windows 10 computer that will soon, if not already, are in the process of updating to the new build. We require our remote offices to remote in to our remote desktop services to run some critical applications that would be too bandwidth hungry to run the client on local workstations at our remote offices. Microsoft must respond with a fix or this may be the downfall of our remote offices. As a federal contractor, this means a lot if our employee's cannot get back into our accounting system just to name one of the applications that must be ran on Remote Desktop services.
Tuesday, October 4, 2016 5:16 PM
We exerience the same problem:
After updating the clients to Win 10 1607 (64bit) we can not longer access via RDP gateway an not longer support our clients operations.
solution: Turning off the custom scale factor
did not solve the problem
Rolling back to Vers 1511 was not possible.
Tuesday, October 4, 2016 5:50 PM
We have the same issue. I'm really disappointed a fix has not been sent out yet. So far I've only seen this on the 32 bit clients. I was able to stop the update on most machines but some received the update and now are unable to revert back. I had originally been using the workaround by replacing the mstsc files from the older version however more updates came out and replaced the files with the new ones.
Quick note if you edit the local group policy to pause updates and restart the pc it will not install the new feature update. I had a couple of clients that were going to install the update on restart and I configured this setting and chose restart. "Do not choose update and restart"
Tuesday, October 4, 2016 10:22 PM
Just to bring this comment up to the top. It is just 32bit versions of Windows 10 that are affected.
It's complete BS that it hasn't been fixed yet.
Wednesday, October 5, 2016 1:20 PM
Hi,
Just to add to the case: we've also got affected clients. Both 32 bit and 64 bit. Experienced this after an earlier update of Win 10 and was then able to replace the mstsc files in the windir with older ones, but this time that isn't an option.
Hope MS releases an update soon!
Wednesday, October 5, 2016 2:29 PM
I already replied that the issue was also affecting 64bit clients.
Also hoping the fix will be available soon, because the replaced files have been overwritten again...
Friday, October 7, 2016 5:11 AM
I have a 64 bit Windows 10 1607 rdp'ing to Windows 2008 R2 just fine. What is the server you guys are RDP'ing to?
Friday, October 7, 2016 5:11 AM
You have to go back to the 1511 version of the mstsc.dll.
Friday, October 7, 2016 3:55 PM
I can confirm that this is a bug with the 32 bit version of Windows 10 Anniversary update. Microsoft, could you please fix this as replacing the DLL is no longer a feasible solution, since it is wiped out with every update. It should concern you that a portion of your corporate clients can not remote in from home to work anymore... This has gone on since August... it is now Oct 7th as of this posting... still no fix.
Friday, October 7, 2016 6:47 PM
Can confirm on 14393.222 32bit install none of the options in this thread have worked, even going back to 1511 versions of exe, dll, and mui ... This is a pretty serious bug, hoping for a quick resolution from Microsoft. The remote server is a windows 2008r2 remote desktop host (fully up to date) connecting via an SBS 2011 (thus also 2008r2) remote desktop gateway (also fully patched).
Wednesday, October 12, 2016 3:00 PM
I'll chime in as well. I have a client using a 32-bit Windows 10 machine and they connect to a 2012 R2 RDS through an SBS 2011 (basically Server 2008 R2) RDS Gateway. This was working fine until the Anniversary Update was installed recently.
Interestingly, I can use the same machine to successfully connect to a 2012 R2 RDS through a 2012 R2 RDS Gateway (in this case, the gateway is the RDS server).
Professional Services Manager | Vision One IT Consulting | www.v1corp.com
Wednesday, October 12, 2016 3:19 PM
HI try install
https://www.microsoft.com/en-us/store/p/microsoft-remote-desktop/9wzdncrfj3ps
Me helped this solution, scale solution not for my company. Only remote preview it is resovle problem.
Frantisek Molnar
Wednesday, October 12, 2016 5:26 PM
The Remote Desktop App did not work for me. I also installed the new cumulative update KB3194798 this morning and I am still getting the same error.
Client: Win 10 Pro 32bit
Remote Desktop Gateway: Server 2008 R2
Wednesday, October 12, 2016 9:03 PM
We are getting this at a few of our clients who are using Windows 10 Pro 32Bit. We can temporarily fix the issue by rolling back the mstsc.exe and mui files manually but the issue returns within a few days.
Thursday, October 13, 2016 9:01 AM
I have this problem with a Windows 10 machine too.
Occurred after the Anniversary update. I have now patched this up to latest build but error still occurs.
Luckily most of our machines are still on Win 7 - and we use RDP for our CRM.
Anyone found a solution yet?
Thursday, October 13, 2016 11:12 AM | 1 vote
We have this problem too on a Windows 10 1607 x86 machine, which is being used on a daily basis for work heavily relying on this feature to work.
We've already applied the workaround three times. Apparently each new update restores the two original system files and the problem comes back. Last time today, I wasn't even able to locate the old files because Windows.old has been automatically deleted.
We cannot afford to stop the machine while we reinstall x64 (which I understand would solve the issue).
It is blatantly obvious that MS didn't test against the x86 version, and is not monitoring this thread. I phoned them and they said no one has raised the issue before.
This is preposterous. I have had to configure a second machine and I am having the user RDP to this machine to do his work. Unacceptable. I don't understand why this hasn't been fixed yet. VERY disappointed.
Thursday, October 13, 2016 12:51 PM
I have rolled back the build to 1511 and disabled updates temporarily using GPEDIT until MS can fix this. Once rolled back it works fine again!
Thursday, October 13, 2016 4:17 PM
Same problem here, our teachers with W10 home version 32 and 64 bits version can't connect to the Remote Gateway.
MS said that a new patch will be available on Octobre 28th. https://social.technet.microsoft.com/Forums/Windows/en-US/915895e5-2746-49f5-b468-0765d8250d7a/windows-10-1607-update-not-working-with-remote-desktop-gateway-server?forum=win10itprogeneral
Other solution is to install Remote application from Windows Store... but not be a real solution
https://www.microsoft.com/fr-fr/store/p/bureau-a-distance/9wzdncrfj3ps (link in French)
Thursday, October 20, 2016 9:59 AM
Unfortunately the Remote Application from the Windows store give the same error on a Windows 10 32 bits with the anniversary update installed.
Thursday, October 20, 2016 7:19 PM
Hello Guys, I was having similar issues trying to establish an RDP connection to a gateway server on Azure from a Windows 10 version 1607. It seems there was a problem with KB 3194496 and the registry key below. Either set the value of following registry key to 3 and above or delete the value and test the RDP with RD gateway. HKLM\SYSTEM\CurrentControlSet\Control\Lsa\ LMCompatibilityLevel Hope it helps, guys!
Thursday, October 27, 2016 4:36 PM
CJ - Is the Registry change made on the server, and does it apply to both Server 2008 and Server 2012 RD Gateways?
Friday, October 28, 2016 8:07 AM
Released update. check
https://mspoweruser.com/windows-10-build-14393-351-released/
Friday, October 28, 2016 7:54 PM
Thanks Microsoft!! I can confirm that the latest cumulative update did fix the problem on my Windows 10 32 bit test system.
But...
Nearly 3 months from the 1st post in this thread till now. At least it wasn't a big issue for us. It only affected 1 employee that I know of. I did waste some time troubleshooting the issue though.
Monday, November 7, 2016 6:46 PM
This release, KB3197954, has NOT fixed the issue for me. I have numerous 32/64 bit systems that cannot use RDWeb/RemoteApps/RDP into our Server 2012R2. The only thing that works is to copy over the mstsc.exe with an earlier version from 1511. I do have an open case with Microsoft, but it has been almost 1 month and the techs are very slow getting back to me. Things are further complicated every time there is an automatic update.
If anyone at Microsoft is interested, my case number is 116101214792050. We rely heavily on RDWeb/RemoteApps and this issue is keeping us from migrating a Server 2008 R2 system over to Server 2012 R2. Reports of this started early in August. It is now early November. This is taking far too long for Microsoft to fix.
Thanks.
Friday, November 11, 2016 3:10 PM
I also have issues with RDweb/RemoteApps/RDP since I upgraded to the 1607 anniversary update.
My Windows 10 version 1607 build at the moment is 14393.447 (the very latest at this moment). It is a x64 system.
When I try to connect to a Windows 2012 gateway for starting some remoteapps my client log (Microsoft-Windows-TerminalServices-RDPClient/Operational) is filling with strange errors like these;event 1033
Component name:CAAUDPClientChannel, :: 'Connect request 1 failed.' in CAAUDPClientChannel::TryConnectToServer at 1713 err=[0x8007274c], Error code:0x8007274C
+
Component name:CAAUDPClientChannel, :: 'All tries to connect to server failed with no reply ' in CAAUDPClientChannel::TryConnectToServer at 1735 err=[0x8007274c], Error code:0x8007274C
and so on.... can you also have a look at your Windows 10 client in the eventviewer? (see log: Microsoft-Windows-TerminalServices-RDPClient/Operational)
Also on a scratch new Windows 10 client with the anniversary update it is giving those strange errors.
I hope MS can help us soon!
Thursday, November 24, 2016 4:59 PM
I too have experienced this issue-recent Win 10 R 1607 update. I'm running Win 10 32Bit HE OS on an ASUS 2 in 1 laptop/tablet. My issue is not server based but client based and above patch fixes are for servers. I get a "internal error has occurred" message after a failed connection. Wondering if a patch for clients has been released yet. Tried to do a roll back from a restore point from a time it last worked but it didn't fix issue. Have people had success with replacing the mstsc.exe and mstscax.dll files. Wondering if this might be a security/permissions issue after this security patch update. I have no issue my Win 10 pro systems 64bit after update.
Tuesday, November 29, 2016 4:37 PM | 2 votes
I ran across this same issue and was able to resolve it by creating a new Registry Key:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client
Name: RDGClientTransport
Type: REG_DWORD (DWORD 32-bit Value)
Data: 1
Reference: https://community.spiceworks.com/topic/1099336-windows-10-rds-gateway-error (Matt8657)
Tuesday, December 6, 2016 10:24 PM
This was finally fixed in a recent update!
Thursday, December 22, 2016 1:08 AM
Can you expand on the update that fixed this issue, meaning what specific update that might have resolved it? I just tried to connect to my Gateway Server after fully patching my windows 10 computer (Version 1607 OS Build 14393.576) and I am still receiving the error : Your computer can't connect to the RD Gateway server.
Thursday, January 5, 2017 4:47 PM
I ran across this same issue and was able to resolve it by creating a new Registry Key:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client
Name: RDGClientTransport
Type: REG_DWORD (DWORD 32-bit Value)
Data: 1Reference: https://community.spiceworks.com/topic/1099336-windows-10-rds-gateway-error (Matt8657)
This worked for me! My client was Win10 x64 v.1607 b.14393.576. RDP Gateway usage was actually working fine after the August and October updates, but actually broke after an update in mid December! Thank you!
Thursday, January 12, 2017 12:55 PM | 2 votes
FYI we noticed that the Windows 10 anniversary build update 1607 stopped our published remote app RDP shortcuts from working on these updated clients (previous versions of Windows 10 and Windows 7 worked with no issue). The problem manifested itself as a certificate error when trying to run the RDP file to run the remote app with the message "The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator."
The remote app wizard auto generated the remote app RDP file we were using and did not enable the values in the RDP file to be edited. However, by removing the signscope and signature sections from the RDP file we were then able to set the authentication level setting from 2 to 0 in the RDP file and launch the application without issue on Windows 10 anniversary build - problem solved. As this is related to the Windows 10 anniversary build update and RDP issues my search had brought me to this and threads referenced within so I wanted to post this information here as it may be of help to some.
Friday, February 3, 2017 5:43 PM | 1 vote
FYI we noticed that the Windows 10 anniversary build update 1607 stopped our published remote app RDP shortcuts from working on these updated clients (previous versions of Windows 10 and Windows 7 worked with no issue). The problem manifested itself as a certificate error when trying to run the RDP file to run the remote app with the message "The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator."
The remote app wizard auto generated the remote app RDP file we were using and did not enable the values in the RDP file to be edited. However, by removing the signscope and signature sections from the RDP file we were then able to set the authentication level setting from 2 to 0 in the RDP file and launch the application without issue on Windows 10 anniversary build - problem solved. As this is related to the Windows 10 anniversary build update and RDP issues my search had brought me to this and threads referenced within so I wanted to post this information here as it may be of help to some.
Resolved my issues. Thanks
Thursday, March 2, 2017 1:33 AM | 1 vote
FYI we noticed that the Windows 10 anniversary build update 1607 stopped our published remote app RDP shortcuts from working on these updated clients (previous versions of Windows 10 and Windows 7 worked with no issue). The problem manifested itself as a certificate error when trying to run the RDP file to run the remote app with the message "The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator."
The remote app wizard auto generated the remote app RDP file we were using and did not enable the values in the RDP file to be edited. However, by removing the signscope and signature sections from the RDP file we were then able to set the authentication level setting from 2 to 0 in the RDP file and launch the application without issue on Windows 10 anniversary build - problem solved. As this is related to the Windows 10 anniversary build update and RDP issues my search had brought me to this and threads referenced within so I wanted to post this information here as it may be of help to some.
May I ask how to " removing the signscope and signature sections from the RDP file we were then able to set the authentication level setting from 2 to 0 in the RDP file" ? thanks!
Tuesday, May 9, 2017 2:21 PM
Is there news here. We are still facing the same issue as it is descibed form ERUANTANE.
Client is Windows 10 64-bit 1706.14393.1066
RD-Gateway is Windows Server 12
Wednesday, June 21, 2017 1:09 AM
This issue still affects our environment.
Win 10 x64 (we don't have any 32 bit machines).
Server 2008R2 Gateway.
Tuesday, June 27, 2017 7:14 PM
This issue also affects our environment.
Windows 10 x64 version 1703
Server 2012 R2 Gateway
It still works on my Windows 10 x64 1607 machine however.
Saturday, July 22, 2017 7:05 PM
There is a hotfix included in the update October 27, 2016 — KB3197954 (OS Build 14393.351).
After the installation of this hotfix you may connect via RDS without issues.
Saturday, July 29, 2017 9:35 AM
I believe RDP as stoped working for home version.
I tested after latest upgrades, in home and pro version.
HOME - not working
PRO - all working fine as before
Saturday, July 29, 2017 9:36 AM
I believe RDP as stoped working for home version.
I tested after latest upgrades, in home and pro version.
HOME - not working
PRO - all working fine as before
NOTE: it does not work for receiving RDP
Monday, November 20, 2017 8:52 AM | 1 vote
This fix (method 1) worked on a 32bit Win10 machine.
https://support.microsoft.com/en-us/kb/2903333
The computer was connecting to a 2012R2 RD Gateway and event id 4625 with status 0xC000035B was logged in the security log on the GW server.
I didn't try method 2 because <5 computers were affected.
Hope this helps.
that worked for me...
Sunday, February 25, 2018 4:52 PM
:-) after few hours of looking for an fix, this solves it. Why is this answer not in the MS help pages!!! Thanks, you made my day!!
Friday, April 20, 2018 3:35 PM
Adding the registry corrected the problem immediately on my Windows 10 Pro 64 bit computer.
Thanks Dennissc!
John Salfer
Tuesday, May 15, 2018 4:00 PM
Confirmed working.
Copied both files from \system32 folder