Skip to main content

Resolving Mini WAN Miniport Code 31 Errors on Windows 8.1

After a recent Windows update I could no longer connect to one of my VPNs using the native Windows VPN connectivity (i.e. not a client like Cisco AnyConnect). When I tried to connect from the networking charm (I think that's what they call the bar on the right-hand side of the screen) it would hang for a while but never connect, and after that happened when I clicked on the networking icon on the lower right the charm bar wouldn't even come back.

I figured it might be a driver issue so I opened up Device Manager and sure enough, under the network adapters section there were yellow exclamation marks next to every one of the WAN Miniports that show up after you try to connect to a VPN.

I found varying reports of how to fix the problem but here's what worked for me.

  1. Try to connect to a VPN that will cause things to error out (the WAN Miniports didn't even show up in the network adapter list for me until I did this)
  2. Open Device Manager
  3. Expand "Network adapters"
  4. Right-click every one of the WAN Miniport devices (I even did the ones that didn't have a yellow exclamation point next to them) and do the following:
    1. Click "Update Driver Software"
    2. Click "Browse my computer for driver software"
    3. Click "Let me pick from a list of device drivers on my computer"
    4. Uncheck the "Show compatible hardware" box
    5. Under Manufacturer choose Microsoft
    6. Under Network Adapter choose "Microsoft KM-Test Loopback Adapter" (technically from what I understand you can pick anything that you can uninstall, but this one worked consistently for me)
    7. Click "Next"
    8. Ignore the "blah blah might be incompatbile" warning and click OK
    9. After Device Manager refreshes, right click the Microsoft KM-Test Loopback Adapter and click "Uninstall"
  5. After you've done that for every one of the WAN Miniports listed, reboot the machine. If you don't do this things won't be fixed.
That cleaned things up for me. We'll see if it works on subsequent reboots.

Comments

Pasha MESH said…
Thank you. Your instructions helps me to solve VPN PPTP connection issue.

It's works even without reboot.
Thomas said…
You are my personal hero and you really saved my day! Thanks for your tutorial.

My Network settings / Share center was freezing for 5–10 minutes everytime I opened it. I lived with this for quite some time, but now I needed to use vagrant / homestead and it would hang as well, because it tries to set network connections at some time.

When I fixed the WLAN Miniport issues, everything worked again.

One hint: You should really really do this for ALL WLAN Miniport entries. If after reboot it doesn't work, do it again for the entries that didn't work.

I finally succeeded with this absurd workaround after a long time of research and approximately one million reboots today. Just another reason to finally get rid of my windows partition.

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…