Error when you open a SharePoint Document Library in Windows Explorer or map a network drive to the library after you install Internet Explorer 10

Work anywhere from any device with Microsoft 365

Upgrade to Microsoft 365 to work anywhere with the latest features and updates.

Upgrade now

Introduction

This article describes issues that occur after you install Internet Explorer 10 on a Windows 7-based, Windows 8-based, Windows Server 2008 R2-based or Windows Server 2012-based computer.

Symptoms

Issue 1

Consider the following scenario:

  • You select the Keep me signed in option, and then you log on to a SharePoint server.

  • You access the data in a SharePoint Document Library.

  • You try to map a network drive to the SharePoint Document Library.

In this scenario, the operation fails, and you receive the following error message:

The mapped network drive could not be created because the following error has occurred:

Access Denied. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site, and select the option to login automatically.

Issue 2

Assume that you access the date in a SharePoint Document Library. Then, you click Open with Explorer View when you view a SharePoint Document Library in Internet Explorer 10. In this situation, the operation fails, and you receive one of the following error messages.

Error message 1

Your client does not support opening this list with Windows Explorer.

Error message 2

We're having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again.

Notes

  • These issues occur only when the SharePoint server is configured for cookie-based authentication, such as SharePoint Online.

  • You may encounter a similar issue when you use other Web Distributed Authoring and Versioning (WebDAV) servers that are configured for cookie-based authentication.

Resolution

To resolve this issue in Windows 8 or Windows Server 2012, install update rollup 2903938, or install the hotfix that is described in this article. For more information about how to obtain update rollup 2903938, click the following article number to view the article in the Microsoft Knowledge Base:

2903938 Windows RT, Windows 8, and Windows Server 2012 update rollup: December 2013
To resolve this issue in Windows 7 SP1 or Windows Server 2008 R2 SP1, install the update or the hotfix that is described in this article.

Update information

How to obtain this update

Windows Update

This update is available from Windows Update. This update is also available at Microsoft Update Catalog.

Microsoft Download Center

The following files are available for download from the Microsoft Download Center:

Operating system

Update

All supported x86-based versions of Windows 7

Download Download the update package now.

All supported x64-based versions of Windows 7

Download Download the update package now.

All supported x64-based versions of Windows Server 2008 R2

Download Download the update package now.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1), Windows Server 2008 R2 SP1, Windows 8 or Windows Server 2012. For more information about how to obtain a Windows 7 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, 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.

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 note

  • 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

    SR_Level

    Service branch

    6.1.760
    1.18xxx

    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) that are installed for each environment are listed separately in the "Additional file information for Windows 7" section. 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 7

File name

File version

File size

Date

Time

Platform

Davclnt.dll

6.1.7601.18201

81,920

4-Jul-13

11:51

x86

Davclnt.dll

6.1.7601.22376

89,088

4-Jul-13

11:54

x86

Mrxdav.sys

6.1.7601.18201

115,712

4-Jul-13

9:48

x86

Mrxdav.sys

6.1.7601.22376

116,736

4-Jul-13

10:01

x86

Webclnt.dll

6.1.7601.18201

205,824

4-Jul-13

11:57

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Davclnt.dll

6.1.7601.18201

102,400

4-Jul-13

12:50

x64

Davclnt.dll

6.1.7601.22376

110,592

4-Jul-13

12:10

x64

Mrxdav.sys

6.1.7601.18201

140,800

4-Jul-13

10:11

x64

Mrxdav.sys

6.1.7601.22376

141,824

4-Jul-13

9:54

x64

Webclnt.dll

6.1.7601.18201

259,584

4-Jul-13

12:57

x64

Webclnt.dll

6.1.7601.22376

264,704

4-Jul-13

12:16

x64

Mrxdav.sys

6.1.7601.18201

115,712

4-Jul-13

9:48

x86

Mrxdav.sys

6.1.7601.22376

116,736

4-Jul-13

10:01

x86

Davclnt.dll

6.1.7601.18201

81,920

4-Jul-13

11:51

x86

Davclnt.dll

6.1.7601.22376

89,088

4-Jul-13

11:54

x86

Webclnt.dll

6.1.7601.18201

205,824

4-Jul-13

11:57

x86

Webclnt.dll

6.1.7601.22376

209,408

4-Jul-13

11:59

x86

Windows 8 and Windows Server 2012 file information notesImportant Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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" 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.2.920 0.16 xxx

    Windows 8 and Windows Server 2012

    RTM

    GDR

    6.2.920 0.20 xxx

    Windows 8 and Windows Server 2012

    RTM

    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 8 and Windows Server 2012" 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

File name

File version

File size

Date

Time

Platform

Davclnt.dll

6.2.9200.16700

86,016

26-Aug-2013

22:28

x86

Davclnt.dll

6.2.9200.20808

86,016

27-Aug-2013

04:20

x86

Webclnt.dll

6.2.9200.16700

199,168

26-Aug-2013

22:29

x86

Webclnt.dll

6.2.9200.20808

199,168

27-Aug-2013

04:22

x86

For all supported x64-based versions of Windows 8 and of Windows Server 2012

File name

File version

File size

Date

Time

Platform

Davclnt.dll

6.2.9200.16700

104,448

27-Aug-2013

05:19

x64

Davclnt.dll

6.2.9200.20808

104,960

27-Aug-2013

05:16

x64

Webclnt.dll

6.2.9200.16700

227,840

27-Aug-2013

05:21

x64

Webclnt.dll

6.2.9200.20808

227,840

27-Aug-2013

05:18

x64

Davclnt.dll

6.2.9200.16700

86,016

26-Aug-2013

22:28

x86

Davclnt.dll

6.2.9200.20808

86,016

27-Aug-2013

04:20

x86

Davclnt.dll

6.2.9200.16700

86,016

26-Aug-2013

22:28

x86

Davclnt.dll

6.2.9200.20808

86,016

27-Aug-2013

04:20

x86

Webclnt.dll

6.2.9200.16700

199,168

26-Aug-2013

22:29

x86

Webclnt.dll

6.2.9200.20808

199,168

27-Aug-2013

04:22

x86


Status

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

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Need more help?

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

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×