Note: The Internet Explorer 11 desktop application will be retired and go out of support on June 15, 2022 (for a list of what's in scope, see the FAQ). The same IE11 apps and sites you use today can open in Microsoft Edge with Internet Explorer mode. Learn more here.

Symptoms

Consider the following scenario:

  • You have a DirectAccess server.

  • You have a client computer that's running Windows 8.1 Enterprise with DirectAccess policies configured.

  • You have a proxy manually set up on this client computer only in Internet Explorer.

  • You connect the client computer to the domain network and then restart the computer.


When you log back in to the domain network in this scenario, the network connectivity status icon displays limited connectivity.

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote 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 update in Windows 8.1, you must first have update 2919355 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

The English (United States) 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 notesImportant Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" 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.

    Version

    Product

    Milestone

    Service branch

    6.3.960 0.17 xxx

    Windows 8.1

    RTM

    GDR

  • 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 8.1 and Windows Server 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 name

File version

File size

Date

Time

Platform

Ncsi.dll

6.3.9600.17822

273,408

05-May-2015

14:28

x86

Nlaapi.dll

6.3.9600.17415

65,536

29-Oct-2014

01:01

x86

Nlasvc.dll

6.3.9600.17550

314,880

06-Dec-2014

01:28

x86

Nlasvc.ptxml

Not applicable

4,075

21-Aug-2013

23:41

Not applicable

For all supported x64-based versions of Windows 8.1

File name

File version

File size

Date

Time

Platform

Ncsi.dll

6.3.9600.17822

360,448

05-May-2015

14:31

x64

Nlaapi.dll

6.3.9600.17415

86,016

29-Oct-2014

01:24

x64

Nlasvc.dll

6.3.9600.17550

391,680

06-Dec-2014

01:41

x64

Nlasvc.ptxml

Not applicable

4,075

22-Aug-2013

06:46

Not applicable

Nlaapi.dll

6.3.9600.17415

65,536

29-Oct-2014

01:01

x86

Wow64_nlasvc.ptxml

Not applicable

4,075

21-Aug-2013

23:41

Not applicable

For all supported Windows RT 8.1

File name

File version

File size

Date

Time

Platform

Ncsi.dll

6.3.9600.17822

252,416

05-May-2015

14:32

Not applicable

Nlaapi.dll

6.3.9600.17819

68,456

05-May-2015

18:58

Not applicable

Nlasvc.dll

6.3.9600.17819

275,968

03-May-2015

14:54

Not applicable

Nlasvc.ptxml

Not applicable

4,075

21-Aug-2013

23:35

Not applicable

Additional file information for Windows 8.1

Additional files for all supported x86-based versions of Windows 8.1

File property

Value

File name

X86_391dab97c6878ec2ad1d0f0b2a07f962_31bf3856ad364e35_6.3.9600.17822_none_7accc0f6a83426b4.manifest

File version

Not applicable

File size

694

Date (UTC)

05-May-2015

Time (UTC)

19:03

Platform

Not applicable

File name

X86_microsoft-windows-nlasvc_31bf3856ad364e35_6.3.9600.17822_none_fc648bf826550bb3.manifest

File version

Not applicable

File size

54,122

Date (UTC)

05-May-2015

Time (UTC)

19:06

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 8.1

File property

Value

File name

Amd64_57d1878172a3819121be67dc54a9d8f3_31bf3856ad364e35_6.3.9600.17822_none_f4ef2c54c47bdd84.manifest

File version

Not applicable

File size

698

Date (UTC)

05-May-2015

Time (UTC)

19:03

Platform

Not applicable

File name

Amd64_eb5f00b2cd5b70fc735c01d13db4702e_31bf3856ad364e35_6.3.9600.17822_none_1b693593ceda114e.manifest

File version

Not applicable

File size

698

Date (UTC)

05-May-2015

Time (UTC)

19:03

Platform

Not applicable

File name

Amd64_microsoft-windows-nlasvc_31bf3856ad364e35_6.3.9600.17822_none_5883277bdeb27ce9.manifest

File version

Not applicable

File size

54,126

Date (UTC)

05-May-2015

Time (UTC)

19:11

Platform

Not applicable

File name

Wow64_microsoft-windows-nlasvc_31bf3856ad364e35_6.3.9600.17822_none_62d7d1ce13133ee4.manifest

File version

Not applicable

File size

46,773

Date (UTC)

05-May-2015

Time (UTC)

19:11

Platform

Not applicable

Additional files for all supported Windows RT 8.1

File property

Value

File name

Arm_dc9f830ac64b6b832b60294edec587b1_31bf3856ad364e35_6.3.9600.17822_none_8b0cfda5e58eee66.manifest

File version

Not applicable

File size

694

Date (UTC)

05-May-2015

Time (UTC)

19:03

Platform

Not applicable

File name

Arm_microsoft-windows-nlasvc_31bf3856ad364e35_6.3.9600.17822_none_fc66fe5026522a79.manifest

File version

Not applicable

File size

54,122

Date (UTC)

05-May-2015

Time (UTC)

19:03

Platform

Not applicable


Status

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

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×