Forum Discussion
Announcing Windows 10 Insider Preview Build 19587
Just to note - this update (like the last 2-3) is wreaking havoc with certain WPF applications (Visual Studio being one of them) https://developercommunity.visualstudio.com/content/problem/937767/cannot-use-mouse-for-secondary-windows.html. Also I noticed that ever since updating to it, I seem to have problems with VPN connections (Rasphone or the Windows 10 wrapper). I tried doing all of the usual troubleshooting steps (rebuilding the VPN connection, refreshing my IP address, etc) but something is causing fatal errors when creating the TLS client credentials. This wasn't a problem with the previous build on the fast ring. I'm going to wait and see if the next update fixes this before trying anything else.Edit: Disregard the note about VPNs, see my newer reply below.
I use SSTP and PPTP, added them to the Windows 10 from settings rather than using .pbk file, it's working fine
- HotCakeX
I stand corrected; the update didn't break anything. My VPN tunnel actually does work, but for whatever reason it isn't letting me RDP onto a machine unless I use the IP address.
I'm not going to worry about it though since I had this issue before in the past. I cannot remember what I did to get it so machine names are usable. I suspect that what I did was undone by the last fast ring update. I'm not really going to call this a problem anymore since I have had other settings get reset by the fast ring updates.I had no mentioned it...but build 19587 is requiring me to use IP address vs name for several things.
I use WSD so the network file servers show up under "network" just fine....but I can't get to them by clicking on them (need to use IP). I have the same for RDP.....need to use IP.
I did go through and check name resolution and it is working fine from a command prompt...my understanding is that name resolution and connecting are not hard linked, so it is possible for resolution to be ignored during connection.
In my case there was nothing done on the windows machine for WSD.....those changes where all done on the server and automagically worked on windows.
- Spoiler
StephenWhiteD3G wrote:
HotCakeX
I stand corrected; the update didn't break anything. My VPN tunnel actually does work, but for whatever reason it isn't letting me RDP onto a machine unless I use the IP address.
I'm not going to worry about it though since I had this issue before in the past. I cannot remember what I did to get it so machine names are usable. I suspect that what I did was undone by the last fast ring update. I'm not really going to call this a problem anymore since I have had other settings get reset by the fast ring updates.Well hope you remember what you have to do to fix it soon 🙂
HotCakeX
L2TP/IPsec; it's the Cisco Meraki VPN "client" (which I really do not like because it is very sensitive to Windows updates and does other weird things). Also, it tends to misbehave through the Windows 10 UI so I have to fall back on Rasphone.
