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, April 21, 2017 11:48 PM | 12 votes
I was attempting to setup an incoming VPN connection so I could securely connect to a remote machine of mine (non-domain). In Network Connections I go to File -> New Incoming Connection. I select the user, check off 'Through the Internet', then click 'Allow Access'.
I get the error:
Windows could not create your connection
Incoming connections depend on the Routing and Remote Access Service, which was unable to start. For more information, check the system event log.
In the System event log I have Event 7024:
The Routing and Remote Access service terminated with the following service-specific error:
General access denied error
In services, Routing and Remote Access is set to start automatic, but it is stopped. When I try to start it I get the following error:
The Routing and Remote Access service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
I'm running Windows 10 Pro x64 version 1703 build 15063.138
Is this a bug or am I missing something?
Regards Nick
All replies (46)
Monday, April 24, 2017 6:24 AM ✅Answered | 2 votes
Hi Nick,
First of all, please run SFC /SCANNOW command to scan and fix corrupted user profile.
After that, confirm that it log on as Local System account instead of Local Service account to run this service.
1. Open service MMC snap-in.
2. Right Routing and Remote Access service, and click “properties”.
3. Click “Log on” tab , and assign a local System account for running this services as below:
Besides that, please also confirm its dependencies services running fine:
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, April 24, 2017 1:06 PM | 1 vote
Hi Karen
I follow your suggestions put the problem still persist.
ERROR (when trying to start Routing and Remote Access service):
The Routing and Remote Access service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
Regards Nick
Wednesday, April 26, 2017 7:27 AM | 1 vote
Latest news
I found out that the problem exist on machines running 1703 (Redstone 2) version. I check for PRO and HOME editions. From the other hand in a machine running 1607 (Redstone 1) I can create New Incoming Connection with no problem.
Wednesday, April 26, 2017 3:35 PM | 6 votes
I have the same problem as Nick. I can confirm that this is a problem of the Creator's Update, as I run version 1703 too. Problem is that 10 days have already passed and I can't restore to previous version. Tried another pc thought (not one of mine), not having creator's update, is able to create New Incoming Connection.
So, please fix it. I need that connection, as do Nick I suppose.
Wednesday, April 26, 2017 6:14 PM | 1 vote
Have to chime in, saw the exact same error on my desktop after upgrading to 1703 and trying to recreate the VPN access.
Out of curiosity, tried creating an incoming VPN connection on my laptop after upgrading, same error, so it has to be a wider issue.
Thursday, April 27, 2017 2:08 AM | 2 votes
Been trying to find some way to work around this. If anybody has found a workaround, PLEASE share it! Can re-create issue 100% and can say with 100% certainty it is a bug in 1703. Tuesday update failed to fix. My client went to Paris earlier this week and had tested the VPN at the end of March. Microsoft, you're making me look bad, but making Microsoft look worse! What does it take for Microsoft to fix something that they with 100% certainty, broke?
j/s...
Thursday, April 27, 2017 5:40 AM | 3 votes
Hi all,
We have received this feedback and we are working on this problem.
Please check and install available Windows Updates on time。
Meanwhile, submit this feedback via the built-in Feedback app. We also would submit it via our own channel.
Hope it could be fixed soon.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, May 1, 2017 9:02 PM | 1 vote
Hi I also have the same problem, any update from Microsoft ?
Sunday, May 7, 2017 1:47 PM | 1 vote
Bobtelco,
I think Karen_Hu is politely suggesting that we all submit our concern/complaint through the Feedback App built into W10 in order to generate support within MS for elevating this issue to a higher priority. I have done so and hope others will too.
I am a one-person consulting business and rely on being able to access my office desktop from my remote laptop and my smart phone. I pay a dynamic DNS service to keep a URL assigned to my desktop IP, which my provider seems to change on a random basis. Without a VPN server on my office desktop, this effort and expense are useless and wasted. I don't really need third-party VPN software, but may have to resort to that soon.
Let's hope we can get MS to address this issue soon.
Regards,
Bob
Monday, May 8, 2017 1:34 AM | 2 votes
not work，please solve this！it is not working！
Monday, May 15, 2017 1:27 PM | 1 vote
Hi,
I would just like to add i am also having this issue, my machine updated to 1703 last night, since then i am unable to VPN into my home machine, the device in Network adapters is gone, and i am unable to add it back. Can anyone confirm if they have got any workaround/fix for this yet?
Thanks
Monday, May 15, 2017 5:09 PM | 1 vote
the issue is still there and i'm still waiting for Microsoft to fix this
Friday, May 19, 2017 9:01 PM | 3 votes
I can confirm that after almost a month after installing the creators update (win 10 pro x64) on several machines here, i still can't use the built-in vpn connection from windows ...
I use the vpn connection in conjunction with vnc for secure remote desktop connection but also to be able to securely print remote and to be able to get to my data from a remote location.
Now, we also have SSH when the linux subsystem is installed, but that isn't working properly too; so i can't use that either as a security layer between the remote locations and the internet.
If microsoft isn't going to fix the "Routing and Remote Access" service anytime soon, i'll probably have to throw in another kind of solution (a linux box serving vpn services to get remote network access again?) because I can't wait forever for a solution, and with the current rate they release malware & virusses i'm not going to put my data at risk by installing an older version of win10 and placing that box at the front door of my home-network.
BoGy from .BE ;technician for everyone. Help should be available for everyone, not just 4 those with big wallets!
Wednesday, May 24, 2017 11:14 PM | 2 votes
Same issue here, Microsoft didn't solved this flaw yet.
Thursday, May 25, 2017 3:02 PM | 1 vote
Just joining the chorus to let MS know we really want and need this fix.
Bob
Friday, May 26, 2017 6:53 PM | 4 votes
Can we start a drinking game where everyone takes a drink each time a Microsoft support person tells someone to run the useless sfc /scannow?
Why do you guys keep on flogging this useless pointless solution in every thread?
I also have this problem, now on three machines - all fresh installs with different hardware.
This is absolutely a bug that MS needs to address.
Saturday, June 3, 2017 1:00 PM | 1 vote
Finally i found the thread for this problem here! I have this issue since begin of april, were i installed a server with the creators.
It is nearly 2 months now and it is getting ridiculous... Now my other machines are getting this sh* creators update and if this happens i lose vpn access completely. (I am running the vpn over a other machine atm)
thx microsoft.
Monday, June 5, 2017 10:45 AM | 3 votes
ok, so i contacted Microsoft Support. after 20 minutes of trying to explain the fault. i have been informed the development team have received the feedback and are working on a fix.
Lets see how this goes.
Monday, June 5, 2017 12:00 PM | 2 votes
Thank you, Matthew!
Monday, June 5, 2017 8:06 PM | 1 vote
Happy to see some activity in this thread. I hope the information you received was correct. Not hearing anything back from Microsoft, it's easy to doubt they are working on this problem. Thanks for the status report.
Bob
Tuesday, June 6, 2017 1:59 PM | 1 vote
Got the same problem, please fix it.
Jacob
Tuesday, June 6, 2017 2:01 PM | 1 vote
Hi Karen,
the problem still persists, any update?
Jacob
Tuesday, June 6, 2017 6:48 PM | 1 vote
Hello,
I'd just like to add that I'm having the same problem as well. Have used the feedback hub and reproduced the error.
Update:
Installed update from today, error persists.
Tuesday, June 6, 2017 7:15 PM | 1 vote
I cannot believe such a huge bug have passed all preview rings to get to final release. I did a couple of fresh installs because i could not believe such a bug would be possible in a final release, then blamed my ethernet card drivers and other peripherials, tried countless posted solutions for other windows versions, but nothing... till i came here and finally saw some work is beeing done, very very late, but beeing done.
Thursday, June 8, 2017 1:34 AM | 1 vote
Just tried with the latest Windows updates as well. Definitely a bug with the OS. This obviously isn't an isolated problem, so I hope it gets fixed soon.
Monday, June 12, 2017 11:13 PM | 4 votes
Hello
I suspect this my be related to the split of services with SVCHOST that took place, some apps and features may not work properly with this change.
In this case it's rasman and remoteaccess that used to be in the same hosted process if I am reading this properly.
See this blog
so to combine them let's try something like this from an elevated cmd prompt to see if that helps.
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\ rasman /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\ remoteaccess /v SvcHostSplitDisable /t REG_DWORD
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
Tuesday, June 13, 2017 1:19 AM
Hi Darrell,
Just tried your solution (I copied your lines but put HKLM into <> because of syntax errors) but it only returns an error message that the system cannot find the file specified.
Tuesday, June 13, 2017 9:09 AM | 1 vote
Hello
I suspect this my be related to the split of services with SVCHOST that took place, some apps and features may not work properly with this change.
In this case it's rasman and remoteaccess that used to be in the same hosted process if I am reading this properly.
See this blog
so to combine them let's try something like this from an elevated cmd prompt to see if that helps.
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\ rasman /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\ remoteaccess /v SvcHostSplitDisable /t REG_DWORD
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
Hi Darrell,
Thanks for this, i have just tried the solution and was able to create the VPN again, however when trying to connect i get the following error.
"The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properly"
i can also see in Properties for Incoming Connection on my host machine that there is no Devices showing in 'allow incoming connections on these devices"
Any help around this please?
Thanks
Tuesday, June 13, 2017 9:11 AM
Sorry just tried to recreate the incoming connection again and it worked this time. strange
Thanks for the workaround. Hopefully this gets fixed in a future update, however this workaround is currently working for me!
Thanks again
Tuesday, June 13, 2017 4:23 PM | 2 votes
Hello,
I accidently added a space before rasman and remoteaccess on each line, try removing that space and see if that works for you now.
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
Tuesday, June 13, 2017 8:10 PM | 6 votes
Hello!
I'll just write it right!
- Run the command prompt as administrator.
- Enter the command
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\rasman /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
3. Enter the command
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\remoteaccess /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
4. Restart your system
5. Done!
Thank you, Darrell Gorter!
Wednesday, June 14, 2017 10:17 AM
Works like a charm!
God bless you, Darrell.
Monday, June 19, 2017 3:18 PM
Hello,
I accidently added a space before rasman and remoteaccess on each line, try removing that space and see if that works for you now.
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
Darrell, I'm glad to have your workaround and will test it tonight. It would be great if Microsoft could release a supported fix to help with this, since they broke it.
Tuesday, June 20, 2017 8:07 AM | 1 vote
So ive had this enabled now for a week with no issues to report so far. Just keeping everyone updated encase they are on the fence to try this or not.
Cheers
Thursday, June 22, 2017 8:19 AM
Hi Darrell,
I run the commands and the Routing and RAS service is now running.
But I still receive this error, when I want to etablish the VPN Connection:
The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properly.
Any ideas to solve the problem?
Kind regards.
Marc
Thursday, June 22, 2017 3:48 PM
Hello,
I suspect that is completely separate issue. here is a blog with that error listed however
https://blogs.technet.microsoft.com/rrasblog/2009/08/12/troubleshooting-common-vpn-related-errors/
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
Sunday, July 9, 2017 9:54 PM
Hello!
I'll just write it right!
- Run the command prompt as administrator.
- Enter the command
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\rasman /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
3. Enter the command
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\remoteaccess /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
4. Restart your system
5. Done!
Thank you, Darrell Gorter!
I found this thread and solution, implemented it successfully. However it only worked once and only for a day.
I was able to create the incoming connection and successfully establish a VPN connection.
However the next day it was gone and I can once again not create the incoming connection because RRAS will not start. The reg keys are still in place and I have rebooted a few times. Any ideas?
Sunday, August 6, 2017 12:58 AM
Hi,
Any good news on this? I´ve tried the registry keys with no luck... Acces denied on starting Remote Access Service.
The problem started on 1703 too.
Saturday, August 26, 2017 10:45 PM
Hi all,
in my experience, the SvcHostSplitDisable reg works "sometimes". Any other idea?
Dr. Gianluigi "Zane" Zanettini - http://www.zane.it
Monday, September 4, 2017 8:11 AM | 1 vote
Seems that Microsoft has stopped working on this. The issue persists for 5 month now. Time to finde alternatives for creating a incoming VPN connection.
Some recommendations?
Saturday, September 9, 2017 4:54 AM
Perhaps a Class Action Law suit for removal of necessary functionality (that I originally paid for) - I lost this when I was forcibly "upgraded/raped" from 7 to 10.. I foolishly didn't roll back - big mistake. Hey Microsoft you went public in 1986.. and you're still pushing out broken Beta's.. Really?
Wednesday, September 13, 2017 2:38 PM
Hi All. this is what worked for me after a few days of trying and failures:
- Create a .bat file with this content:
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\rasman /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\remoteaccess /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
pause
2. Run the .bat file of prev step as administrator
3. restart "Routing and Remote Access" from services!
4. done ... get it a try and tell if it worked or not!
My OS version is: Windows 10 Enterprise RS 2 1703, build 15063.608
Tuesday, September 19, 2017 10:31 AM
Since the duration to solve this topic gets redicolus the best solution for me was to go away from microsoft. I used this cheap router:
Asus RT-AC51U AC750
With it you can easy configure a PPTP connection which can be connected over the standard microsoft vpn client (this surprisingly still works). Just swtich the PPTP as the security mode.
Friday, October 20, 2017 11:41 AM
Hey to everyone!
I hope you all see this, since there's a problem bothering all of us!
After the Fall Creator's Update, everything seems to work smoothly by now! I managed to create the New Incoming Connection. Since it is very early for the update I download it separately from Microsoft's site so you may want to do the same.
There isn't any statement from MS for this problem that is fixed with this update, but everything seems to work.
Cheers!
Sunday, October 22, 2017 12:46 PM
Since the duration to solve this topic gets redicolus the best solution for me was to go away from microsoft. I used this cheap router:
Asus RT-AC51U AC750
With it you can easy configure a PPTP connection which can be connected over the standard microsoft vpn client (this surprisingly still works). Just swtich the PPTP as the security mode.
it seems to be working again now, but i'm in the same lane as you; the ridiculous long wait time enforced me to look for other, sustainable (working with same client, not needing monthly payment, compatible with MS-networking) solutions and i also bought myself a new modem/router. I'm on vdsl2+ so i couldn't just go with a cheap router-solution. So i ended up with a Fritz!Box 7430 modem/router/voip which now also replaces my SIP-telephony hardware (was using Siemens Gigaset).
Now i can keep using the handsets from my gigaset, since they can connect to my fritzbox (DECT), i have vpn-connectivity which is way safer than the pptp solution that windows provides (using IPSEC XAuth with PSK now).
now since it's working again in windows; i now have 2 vpn connections to my network; 1x ptpp from win and 1x ipsec from the modem. (pptp is not using the default 1723 tcp port; but the router forwards the data to that port on the windows machine).
I'm glad i have a viable solution and now have a back-up in case things get fluked again. But if i'm really 100% honest; I really wish it never had to come this way; it wasn't cheap and the savings on electricity from the fewer devices i need will never make up the cost of the device.
So in the end i'm glad to have security, but it should never have come this far in the first place.
BoGy from .BE ;technician for everyone. Help should be available for everyone, not just 4 those with big wallets!
Thursday, April 4, 2019 10:30 PM
I have done everything described in this article. I have both registry entries but incoming connection fails. ANy updates on this?