Resolved WAN Miniport (IKEv2) Code 31 Error

I'm working on a Toshiba laptop C655-S5132, and a few days after doing a system recovery, I see there is an exclamation point in Device Manager beside of WAN Miniport (IKEv2). I tried the usual trouble shooting routine Windows has to offer, but the driver will not load. It loads in Safe Mode for what it's worth.

This is a Windows 7 (64-bit) Home Premium PC.


I found this on Google, but it seems rather techy...

Broken WAN Miniports​

Has anyone ever successfully dealt with this Code 31 problem before? The computer is working OK, but I can't help but to wonder if this WAN error could be a problem down the road. I'll try running the SFC /scannow command for the time being.

 

scf /scannow found no problems.

 

I have decided to restore am image I made a few days back, but I cannot get the Macrium free rescue disk to see my other computer where the image is stored.

Load error says this...

Error: The network location cannot be reached.​

Are any of you familiar with this brand of imaging software? Making the 52gb image was easy enough, but restoring it from a network location is not. Google has not been my friend.

 

Hi James, Did you do the System Recovery from the Toshiba partition on the HDD?
I did this for my Brother on his Toshiba laptop and I recollect I had to go into Toshiba Downloads afterwards to get a couple of Drivers which were missing/outdated after the Recovery. Neil.

 

No, this was an image I created a few days after accessing the recovery partition. I created the Macrium image in hopes that I could use it instead going through the hassle of bringing the PC up to date manually.

Macrium uses Windows PE 3.1 to create a rescue disk with, and the software is supposed to alert me if there is an unsupported device (such as an NIC, LAN, etc.). If the software needs drivers and can't get them, you are supposed to supply them yourself and somehow use the rescue disk wizard to add them, but I've found no such way to do that yet. The paid version does this automatically.

Upon booting into the rescue disk, I get a message saying that Macrium *may* need ethernet and NIC drivers. I am given the option of locating these related drivers myself, but even after browsing for the correct drivers (I downloaded and extracted the necessary files ahead of time), the software says it cannot locate the .ini files.

I understand the company's need to generate revenue, but after the hassle I have gone through, I doubt I would be inclined to buy this imaging/cloning product. Acronis was never like this.

 

Followup...

Somehow, I managed to get the necessary drivers to load this last go round by letting Windows PE search all of C drive, but the program still could not detect the storage drive on my desktop computer. I even typed in the path, but to no avail.

After booting into Windows, I navigated to the storage drive with Macrium and located the image file. Out of curiosity, I let the program do a verification of the file, and it said that the image was corrupted. Maybe it was an error or something, but all of the actions the past few days have been done wirelessly.

Is it a bad idea to store and restore images wirelessly, or should I have done this with an ethernet cable? I have limited experience in this field, so I have much to learn.

 

I would imagine there is less chance for signal loss using a cable. Neil.

 

I tried resolving the issue with a restore point, but several of them were corrupted and they corrupted the OS as well. I eventually found a good restore point, but the WAN error remained, so I thought I'd be better off restoring an image.

I'll take another look at the link I provided, but I may ditch the whole job and do another recovery if need be. Windows Easy Transfer may have corrupted some things, too, a few days ago according to the Outlook forums. I will not use Easy Transfer again.

This is my 4th Windows 7 PC that I have worked on the past two months, and I much prefer using a dedicated Windows 7 installation disk rather than using built-in recovery partitions. There is too much that can go wrong removing junkware.

 

Tony, I am going to try this fix and see what happens, but I am not sure if I understand the step below I highlighted in red...

So, to remove each non-working miniport, do the following:

• Right click on the non-working miniport, choose "Update Driver ".
• Choose "Browse my computer ".
• In the next window, choose "Let me pick driver from a list ".
• Uncheck "Show compatible hardware ". From the "Manufacturer" list, choose "Microsoft ", and from the "Network Adapter" list, choose "MAC Bridge Miniport ". (It can be any device the user is allowed to uninstall.)
• Back in the device manager; delete the device that just turned into the "MAC Bridge Miniport" device.​

Once done removing the bad miniports, reboot. Don't skip this, it's important. Otherwise, there is a chance things will go bad again.​

I'm trying fix the WAN Miniport - not the MAC Bridge Miniport device. I don't understand the logic here.

 

Got this error message today after running a command prompt to reinstall the broken miniport...

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\******\Desktop>devcon.exe install c:\Windows\inf\netavpna.inf MS_AgileVpnMiniport

This version of C:\Users\******\Desktop\devcon.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher.
​

The steps outlined in the previously posted article did indeed remove broken miniport, but now I have to recheck and make sure I have the 64bit version of devcon.exe.

EDIT: I extracted the incorrect version of devcom.exe., and corrected that mistake. Using the proper command line, Windows reinstalled the broken miniport, but now, it is listed as WAN Miniport (IKEv2) #2.

Wonder why it is named #2?

 

I found the key(s) you were referring to, but I made no registry changes. Right-clicking on the proper miniport > Modify, brought up a box showing the numbers 1 and 2.

Thanks for the help.

 

All values under the registry key Descriptions are the value of 1 on my win 7 computer

 

I doubt you have any broken miniports too.

I believe some of my problems arose after removing junkware. The Best Buy app was the hardest to remove.

 

I never download anything or even buy a computer from Best Buy. I had a bad software experience with them in the past. You are correct I do not have any broken Mini-Ports

 

My relatives like to buy gear from there. They have three laptops and a few tablet PCs from Best Buy, although the one I working with now is the only unit that came preinstalled with the app.

I thought I had the app removed, but it took JRT and some manual cleaning even after uninstalling the app by conventional means.

I hope my folks keep needing my help. I get to make money on the side, and I'm getting valuable experience repairing laptops too. So far, I've replaced a charging jack cable assembly, resoldered another charging jack back to the board, and the added experience of removing/replacing all of the inside components.

 

Lately I've had a run of broken laptop LED screens. One Dell and several HPs. They're easy to fix and a lot more fun than swapping out a system board not that I mind doing the board it's all fun to do.

 

Agreed.

I find it relaxing to a certain extent.

This particular Toshiba Celeron unit has a damaged screen. I am using an external monitor in the mean time, although a replacement screen is available for 55.00. My relative wants to keep this unit for parts, but he is willing to sell it if I want it. So far, I have invested 8.00 in a charger, and 13.00 in a wireless mouse. I may splurge for the screen and offer 150.00 for the laptop - minus the cost of parts.

My biggest vice is the single-core Celeron processor (and 3gb of memory). Outlook 2007 sometimes hangs while waiting for resources when using IMAP accounts. You sometimes have to be patient with other applications too.