- About a month after I fixed my “SIM PIN2” error on the LTE card installed inside my new laptop, I started experiencing the following error when attempting to connect:
“Can’t connect to this network. Enter an apn and try again.”
If you have this problem or are generally looking how to override a Windows 10 default driver, I may be able to help.
I eventually determined that there was a Windows 10 update titled “2018-01 Cumulative Update for Windows 10 Version 1709 (KB4056892)” that had overwritten the Sierra Wireless drivers I had to apply in my “SIM PIN2” post to correct equally bad Microsoft drivers from a base Windows 10 install. But every time I tried to apply the Sierra Wireless drivers again, or even a newer version I found on the laptop manufacturer’s support site, Windows wouldn’t allow it, claiming that the driver update is “not better than the software you currently have installed.” Why doesn’t Windows 10 let me make that determination?
The laptop manufacturer’s Tier 2 support finally helped. The key to tricking Windows 10 into conformance appears to be:
- Uninstall device from Device Manager (Device Manager -> Find device in question -> right click on it and select “Uninstall Device”).
- Uninstall device drivers from Windows 10 (Add or Remove Programs -> Find device driver in question -> select “Uninstall”). There may be multiples.
- Reboot Windows 10 (this was the key step I was missing).
- Install new device drivers.
For my scenario, I deleted the “Sierra Wireless EM7455” device under “Modems,” rebooted, and then installed the Sierra Wireless device drivers provided by my laptop manufacturer. This solved the LTE APN error by removing a few generic device drivers that Microsoft tried to force upon me rather than allow me to use the vendor’s drivers instead. Given how many unanswered forum thread posts there are on my exact APN error message, I hope the above will work for others too.
SIDE NOTE: This is my second post in a personal experiment with crowdsourced Knowledge Centered Service (KCS). I have emailed the laptop manufacturer and Microsoft to request that they publish a self-service solution for this issue so that my post is duplicative and can be removed. Fingers crossed…