- Joined
- Aug 31, 2015
- Messages
- 4,808
- Trophies
- 3
- Age
- 23
- Location
- Budakeszi, Hungary
- Website
- sites.google.com
- XP
- 10,626
- Country
EDIT: This problem is currently resolved, so you don't have to reply.
Today my WiFi started freaking out: it randomly refused to connect to my home network with the above message. I'm using a USB adapter (Mercusys MW300UM). The network works fine on any other device.
Event Viewer shows me an error with WLAN-AutoConfig with the message “WLAN Extensibility Module has failed to start. / Module Path: C:\WINDOWS\system32\Rtlihvs.dll / Error Code: 126.”
I've tried restarting the PC, restarting the router, reinstalling the driver, plugging the adapter into a different port, and restarting the WLAN AutoConfig service. So far, nothing has worked.
Does anyone have any ideas?
EDIT:
...Oh, neat.
Installing a 90-minute Windows update seems to have fixed it. Alarm's over, boys.
EDIT 2 - Electric Boogaloo:
So after a couple of restarts it seems to be at it again. Only difference is that Event Viewer isn't showing any errors anymore...
EDIT 3:
An update seems to have fixed this issue, thankfully.
Today my WiFi started freaking out: it randomly refused to connect to my home network with the above message. I'm using a USB adapter (Mercusys MW300UM). The network works fine on any other device.
Event Viewer shows me an error with WLAN-AutoConfig with the message “WLAN Extensibility Module has failed to start. / Module Path: C:\WINDOWS\system32\Rtlihvs.dll / Error Code: 126.”
I've tried restarting the PC, restarting the router, reinstalling the driver, plugging the adapter into a different port, and restarting the WLAN AutoConfig service. So far, nothing has worked.
Does anyone have any ideas?
EDIT:
...Oh, neat.
Installing a 90-minute Windows update seems to have fixed it. Alarm's over, boys.
EDIT 2 - Electric Boogaloo:
So after a couple of restarts it seems to be at it again. Only difference is that Event Viewer isn't showing any errors anymore...
EDIT 3:
An update seems to have fixed this issue, thankfully.
Last edited by smileyhead,