Cannot automatically connect to a mobile broadband network after you unblock a PIN-based mobile broadband device in Windows 7 or Windows Server 2008 R2
You set a mobile broadband network profile to automatically connect on a computer that is running Windows 7 or Windows Server 2008 R2.
You connect a personal identification number (PIN)-enabled mobile broadband device to the computer, or you enable an embedded PIN-based mobile broadband device on the computer.
You click the Connect to a Network icon in the notification area on the right side of the taskbar.
In the list of available wireless networks, you select the mobile broadband connection, and then you click Connect.
When you are prompted to enter a PIN code to unblock the mobile device, you type a correct PIN code.
In this scenario, the computer does not automatically connect to the mobile carrier network as expected.
Notes
If you unblock the mobile network device by typing the correct PIN code before you set the mobile broadband network profile to automatically connect, the computer registers and connects to the mobile carrier network.
If you detach a non-embedded mobile broadband device, and then reattach it after you unblock the device by typing the correct PIN code, the computer registers and connects to the mobile carrier network.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If your language is not listed, a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running one of the following operating systems:
Windows 7
Windows 7 Service Pack 1 (SP1)
Windows Server 2008 R2
Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to go to the article in the Microsoft Knowledge Base:
Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.1.760
0.17xxx
Windows 7 and Windows Server 2008 R2
RTM
GDR
6.1.760
0.21xxx
Windows 7 and Windows Server 2008 R2
RTM
LDR
6.1.760
1.17xxx
Windows 7 and Windows Server 2008 R2
SP1
GDR
6.1.760
1.22xxx
Windows 7 and Windows Server 2008 R2
SP1
LDR
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Wwanprotdim.dll
8.1.7600.17094
40,960
09-Aug-2012
18:31
x86
Wwansvc.dll
8.1.7600.17094
186,368
09-Aug-2012
18:31
x86
Wwan_profile_v1.xsd
Not applicable
6,201
10-Jun-2009
21:42
Not applicable
Wwanprotdim.dll
8.1.7600.21296
40,960
09-Aug-2012
23:17
x86
Wwansvc.dll
8.1.7600.21296
186,368
09-Aug-2012
23:17
x86
Wwan_profile_v1.xsd
Not applicable
6,201
10-Jun-2009
21:42
Not applicable
Wwanprotdim.dll
8.1.7601.17925
40,960
10-Aug-2012
04:28
x86
Wwansvc.dll
8.1.7601.17925
186,368
10-Aug-2012
04:28
x86
Wwan_profile_v1.xsd
Not applicable
6,201
10-Jun-2009
21:42
Not applicable
Wwanprotdim.dll
8.1.7601.22083
40,960
10-Aug-2012
04:30
x86
Wwansvc.dll
8.1.7601.22083
186,368
10-Aug-2012
04:30
x86
Wwan_profile_v1.xsd
Not applicable
6,201
10-Jun-2009
21:42
Not applicable
Wwanadvui.dll
8.1.2.0
163,328
14-Jul-2009
01:16
x86
Wwanconn.dll
8.1.7600.17094
196,608
09-Aug-2012
18:31
x86
Wwanmm.dll
8.1.2.0
674,304
14-Jul-2009
01:16
x86
Wwanpref.dll
8.1.2.0
39,424
14-Jul-2009
01:16
x86
Wwanadvui.dll
8.1.2.0
163,328
14-Jul-2009
01:16
x86
Wwanconn.dll
8.1.7600.21296
196,608
09-Aug-2012
23:17
x86
Wwanmm.dll
8.1.2.0
674,304
14-Jul-2009
01:16
x86
Wwanpref.dll
8.1.2.0
39,424
14-Jul-2009
01:16
x86
Wwanadvui.dll
8.1.2.0
163,328
14-Jul-2009
01:16
x86
Wwanconn.dll
8.1.7601.17925
196,608
10-Aug-2012
04:28
x86
Wwanmm.dll
8.1.2.0
674,304
14-Jul-2009
01:16
x86
Wwanpref.dll
8.1.2.0
39,424
14-Jul-2009
01:16
x86
Wwanadvui.dll
8.1.2.0
163,328
14-Jul-2009
01:16
x86
Wwanconn.dll
8.1.7601.22083
196,608
10-Aug-2012
04:30
x86
Wwanmm.dll
8.1.2.0
674,304
14-Jul-2009
01:16
x86
Wwanpref.dll
8.1.2.0
39,424
14-Jul-2009
01:16
x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
To work around this issue, remove the detachable mobile broadband device, unblock the device by using the PIN code, and then reattach the device to the computer. After you do this, the computer connects to the network automatically. Or, you can change the autoconnect setting of the mobile broadband network profile from Always to Only when not roaming. After the computer connects to the network, you can reset the autoconnect setting to Always.
Back to the top
