Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 187
  • Last Modified:

VPN does not work after installing Hyper-V in Win 8.1 PRO

I installed Hyper V and I guess this was the source of the problem. I cannot use or configure nor delete the VPN connections. If I try to do something in the Network Connections  a pop up tell me "An unexpected error occured". If I click on the Virual Switch or the Local Area Connction sometimes I get this message the first time round, but the second time the Connection Properties pop open.

The application log shows following error:
Faulting application name: svchost.exe_RasMan, version: 6.3.9600.16384, time stamp: 0x5215dfe3
Faulting module name: rasppp.dll, version: 6.3.9600.16384, time stamp: 0x5215efd5
Exception code: 0xc0000005
Fault offset: 0x000000000002a630
Faulting process ID: 0xd30
Faulting application start time: 0x01cfd443d78d261d
Faulting application path: C:\WINDOWS\System32\svchost.exe
Faulting module path: C:\WINDOWS\system32\rasppp.dll
Report ID: 5cd88709-4037-11e4-bf03-4061869227c3
Faulting package full name:
Faulting package-relative application ID:

System Log:
The Windows Management Instrumentation service terminated unexpectedly. It has done this 6 time(s).
The Remote Access Connection Manager service terminated unexpectedly. It has done this 7 time(s).
The User Profile Service service terminated unexpectedly. It has done this 4 time(s).
The Server service terminated unexpectedly. It has done this 7 time(s).
The Application Information service terminated unexpectedly. It has done this 3 time(s).
The Server service terminated unexpectedly. It has done this 7 time(s).
The Computer Browser service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service.

There are actually quite a number of services that fail.
I also noticed a long time out period before the errors are logged (See system log).

Any Ideas on how to fix this issue are appreciated.
  • 3
  • 3
1 Solution
Hyper-V is not known for destroying installations, but... you can always be in bad luck.
Do the usual three steps of troubleshooting the system files:
-sfc /scannow
->scans for corrupt system files and trys to repair those
-if sfc fails: do an inplace upgrade
->that means you put in your setup DVD/USB Stick and start windows setup and select upgrade. This will repair windows but keep files, installations and settings.
-if even that doesn't work, do a refresh.
->a refresh will not keep your installed programs and settings but your files and will definitely repair windows as it is close to a reinstallation.
Lorenzo08Author Commented:
Hi McKnife
thanks for your suggestions. I have done sfc /scannow already and I also did a Windows Defender Offlince scan (just in case...) sfc says all is OK.
I have to check how that upgrade works for me since I upgraded online to Win 8 then to Win 8.1 from Win 7. Tricky things can happen with the licence key.

I thought of maybe deleteting all network stuff and set it up from scratch.
Your problem is maybe deeper than the network stuff. System services would not fail just because of vpn software corruptions.

An in place upgrade would usually solve it. You would Need to use an 8.1 ISO. This can be installed with a generic key. Google for "windows 8.1 generic kms" and you have it. After repairing, use your win8 key in exchange for the generic one and activate.
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Lorenzo08Author Commented:
Thanks for your input. I will try that. However, at the moment I have to finish some stuff first. I will give you feedback later.
Lorenzo08Author Commented:
Hi again, I spent some time trying to solve this issue. Microsft does not make it easy and after swearing a lot I managed to get this working fine again. There are a number of Webpages offering solutions and I tried some of them, only to restore the registry and start over again.

The problem (that the VPN connections don't work anymore)  stemmed from some WAN Miniports not working. I.e. Win, for some obscure reason, cannot load the drivers. To find out, one needs to open the "Device Manager" and enable "show hidden devices" in the View tab. Updating the drivers doesn't cut it. Windows refuses, because these drivers are locked.

In order to remove the faulty WAN Miniports, or whatever shows up with a yellow triangle, one needs to replace the driver with an Generic "deletable" one.

Right click thefaulty item.
Select update driver software.
Browse for driver software on my computer.
Select "Let me pick from a list of device drivers on my computer".
Select "Network Adapters" (You can press N to go directly there).
Unclick "Show compatible Hardware".
Select "Microsoft" and on the left pane "Generic Mobile Broadband Adapter" or something else that is generic.
Click "Next".
Ignore the warning and install the driver.
In Device Manager select that Generic whatever..., right click and uninstall it.

Repeat for each device that has a problem.

After you deleted all the faulty devices open a command shell with elevated rights "Command prompt (Admin)"
Run the "Add Hardware Wizzard" from the command prompt Hdwwiz.exe (The wizzard is not executable from any menu in Win8.x, only MS knows why!!!

Click next.
Click on "install the hardware that I manuall select from a list (Advanced)".
Click next.
Select "Network Adapters" then "Microsoft" in the left pane and select the Adapter or WAN Miniport you want to install in right pane.
Click next.

Repeat for all Adapters or miniports that need to be re-installed.

Now reboot the system

Open the "Command Prompt" again, run "netsh int ip reset c:\resetlog.txt" and reboot once more.

Check that all drivers work OK and that all Network Connections are OK.

You might see several greyed out entries of the same item with #2 #3 etc. in the device managers hidden devices list. Another one of those MS idiosyncrasies. Just ignore them. Apparently every time you add a driver the OS increases the count and the reference stays there.

Hope this helps some other poor souls save some time and nerves.
Guy Hengel [angelIII / a3]Billing EngineerCommented:
I've requested that this question be deleted for the following reason:

Not enough information to confirm an answer.

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now