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.

Windows 8.1 mobile broadband may not auto-reconnect after it resumes from connected standby


View products that this article applies to.

Symptoms

A Windows 8.1-based device may not automatically resume its mobile broadband connection after it's awakened from an overnight period in connected standby. When this occurs, the mobile broadband connection (under Settings/Networks/View Connection Settings) may be unresponsive to user input.

This behavior may occur even though the Connect automatically check box is selected in the mobile broadband settings.

↑ Back to the top


Resolution

To resolve this issue, we have released a hotfix that has a prerequisite.

Hotfix information

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 this specific problem.

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, submit a request to 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 you do not see your language, it is because a hotfix is not available for that language.


Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to 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 8.1 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 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 8.1/Windows Server 2012 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.3.960 0.17 xxxWindows 8.1 and Windows RT 8.1RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. 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 8.1
File nameFile versionFile sizeDateTimePlatform
Ndisuio.sys6.3.9600.1767648,64008-Feb-201501:15x86
Wmbclass.sys6.3.9600.17676222,72008-Feb-201501:15x86
For all supported x64-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Ndisuio.sys6.3.9600.1767660,41608-Feb-201501:57x64
Wmbclass.sys6.3.9600.17676267,26408-Feb-201501:56x64
For all supported Windows RT 8.1
File nameFile versionFile sizeDateTimePlatform
Ndisuio.sys6.3.9600.1767649,66408-Feb-201500:40Not applicable
Wmbclass.sys6.3.9600.17676205,82408-Feb-201500:39Not applicable

Additional file information

Additional file information for Windows 8.1
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_285d9f774011eb4126443786dd2b1e13_31bf3856ad364e35_6.3.9600.17676_none_db340117e70d4d16.manifest
File versionNot applicable
File size695
Date (UTC)08-Feb-2015
Time (UTC)14:45
PlatformNot applicable
File nameX86_microsoft-windows-ndisuio_31bf3856ad364e35_6.3.9600.17676_none_009d8bb5026ddaf2.manifest
File versionNot applicable
File size6,589
Date (UTC)08-Feb-2015
Time (UTC)02:34
PlatformNot applicable
File nameX86_netwmbclass.inf_31bf3856ad364e35_6.3.9600.17676_none_619f86ac753951f9.manifest
File versionNot applicable
File size2,122
Date (UTC)08-Feb-2015
Time (UTC)02:34
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1
File propertyValue
File nameAmd64_d4ec06829d03ff989e082b59cd97abcd_31bf3856ad364e35_6.3.9600.17676_none_9f4522358cd283e0.manifest
File versionNot applicable
File size699
Date (UTC)08-Feb-2015
Time (UTC)14:45
PlatformNot applicable
File nameAmd64_microsoft-windows-ndisuio_31bf3856ad364e35_6.3.9600.17676_none_5cbc2738bacb4c28.manifest
File versionNot applicable
File size6,593
Date (UTC)08-Feb-2015
Time (UTC)04:03
PlatformNot applicable
File nameAmd64_netwmbclass.inf_31bf3856ad364e35_6.3.9600.17676_none_bdbe22302d96c32f.manifest
File versionNot applicable
File size2,126
Date (UTC)08-Feb-2015
Time (UTC)04:03
PlatformNot applicable
Additional files for all supported Windows RT 8.1
File propertyValue
File nameArm_6c62c23875ab866c79707cf8c6cb2a4e_31bf3856ad364e35_6.3.9600.17676_none_72dcb24304363d42.manifest
File versionNot applicable
File size695
Date (UTC)08-Feb-2015
Time (UTC)14:45
PlatformNot applicable
File nameArm_microsoft-windows-ndisuio_31bf3856ad364e35_6.3.9600.17676_none_009ffe0d026af9b8.manifest
File versionNot applicable
File size6,589
Date (UTC)08-Feb-2015
Time (UTC)01:24
PlatformNot applicable
File nameArm_netwmbclass.inf_31bf3856ad364e35_6.3.9600.17676_none_61a1f904753670bf.manifest
File versionNot applicable
File size2,122
Date (UTC)08-Feb-2015
Time (UTC)01:24
PlatformNot applicable

↑ Back to the top


Workaround

To work around this issue, manually select Connect on the mobile broadband interface. If the mobile broadband connection does not respond to user input, you may have to restart the computer or device in order to recover. If you have administrator rights, you can also use one of the following workarounds:
  • Use Device Manager to disable and then re-enable the Mobile Broadband Adapter.
  • Stop and restart the WWAN AutoConfig Service in Service Manager.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kbautohotfix, kbhotfixserver, kbqfe, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3036606
Revision : 1
Created on : 1/7/2017
Published on : 3/11/2015
Exists online : False
Views : 258