Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Registration fails when you use a third-party Connection Manager app on a Windows 8.1-based device

Registration fails when you use a third-party Connection Manager app on a Windows 8.1-based device

View products that this article applies to.

Symptoms

Assume that you have a Windows 8.1-based device with a Mobile Broadband (MBN) adapter (a built-in 4G adapter, or an LTE or UMTS USB stick). However, instead of the Windows built-in tool, you use a third-party Connection Manager application to manage your connection, such as one from your independent software vendor (ISV) or the manufacturer of the MBN adapter.  

In this situation, consider the following scenarios.
  • Scenario 1

    You're in location that's not covered by your home provider, and therefore, you're roaming. In the Connection Manager application, you select the 4G and Automatic Registration options.
     
  • Scenario 2

    You blocked your PIN while the Connection Manager application was configured to automatically select an operator. Then, you unblocked your PIN by entering your personal unblocking key (PUK). Finally, you try to manually select an operator.
In both of these scenarios, the Connection Manager application freezes, and registration with the provider network fails. When this issue occurs, you have to restart the Wireless WAN service (WWANSVC) or your computer.

↑ Back to the top

Cause

The Connection Manager application uses SetRegisterMode to change the registration mode for the mobile broadband network. However, the WWANSVC does not forward the rejection notice from the roaming network to the application. You expect WWANSVC to send an OnSetRegisterModeComplete notice to update the Connection Manager application about the status of the registration.

↑ Back to the top

Resolution

Important
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

To resolve the issue, disable the Automatic Connection Engine. To do this, set the AutoConfig registry key as follows:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WwanSvc\AutoConfigName: fEnabled
Type: REG_DWORD
Value: 0
possible values: 1 = enabled (default)
0 = disabled

For the setting to take effect, you must restart the WWANSVC.

↑ Back to the top

More Information

Scenario 1 occurs when the following conditions are true:
  • The roaming network offers 4G, 3G, and 2G.
  • The WWANSVC tries to connect to 4G (as requested by the application).
  • The operator of the roaming network rejects the registration request (for example, because the roaming contract allows only 3G).
  • The MBN adapter forwards the rejection by signaling WwanRegisterStateDeregistered to the WWANSVC.
  • The WWANSVC does not update the application by sending OnSetRegisterModeComplete notice.
Therefore, the Connection Manager application is not notified of the status of the connection.

↑ Back to the top

Keywords: kbexpertiseadvanced, kbsurveynew, kbtshoot, kb

↑ Back to the top

Article Info
Article ID : 3097526
Revision : 1
Created on : 1/7/2017
Published on : 10/16/2015
Exists online : False
Views : 257