Preparing and Installing Internet Explorer 10

After extensive research, planning, testing, and analysis, you must roll out your installation of Internet Explorer 10 to your users. This section describes the steps to follow when you are ready to deploy Internet Explorer 10.

Migrate Group Policy Objects from older versions of Internet Explorer

To ensure continuity in the user experience from earlier versions of Internet Explorer to Internet Explorer 10, be sure to migrate Group Policy Objects that continue to be applicable to Internet Explorer 10. For example, migrating the Compatibility View Group Policy will ensure that intranet sites designed for Internet Explorer 9 continue to display properly in Internet Explorer 10.

Check vendor support statements for third-party add-ons, applications, and code libraries

Some third-party vendors have released new versions of their add-ons, applications, or code libraries for greater compatibility with Internet Explorer 10.

Selecting the right version of Internet Explorer 10

Internet Explorer 10 is pre-installed on Windows® 8 and Windows Server 2012, and available for download for on Windows 7 SP1 and Windows Server 2008 R2 with SP1. The following table lists the Setup file name for each supported operating system.


The file names listed in the table are for the U.S. English language versions of Internet Explorer 10. The file names for other language versions vary according to the language code. See System Requirements and Language Support for more information about the available languages, based on operating system.

Operating system Architecture File name

Windows 7 SP1

32-bit (x86) or 64-bit (x64)

IE10-Windows6.1-x86-en-us.exe and IE10-Windows6.1-x64-en-us.exe

Windows Server 2008 R2 with SP1

64-bit only


All versions of Internet Explorer 10 can be downloaded from the Internet Explorer Downloads site.

Signing custom browser package files

Digital signatures identify the source of programs, and guarantee that the code has not changed since it was signed. Depending on the operating systems that users are running and how their security levels are set, Internet Explorer 10 may prevent users from (or warn them against) downloading programs that are not digitally signed.

We recommend you digitally sign the cabinet (.cab) files created by the Internet Explorer Customization Wizard 10, and any custom components you want to distribute with Internet Explorer 10. If you have a digital certificate, the Internet Explorer Customization Wizard 10 can sign these files automatically.

For more information about digital signatures, see Description of digital certificates.

To digitally sign .cab files and custom components:

  1. Obtain a digital certificate.

  2. When you run the Internet Explorer Customization Wizard 10, specify your digital certificate information.

Preparing the distribution sources

Depending on the type of deployment you select for your organization, you may need to prepare one or more of the following distribution methods:

  • Windows Update or Windows Server Update Services (WSUS)

  • Hyperlink in email or webpage

  • Shared network folder

  • Active Directory and Group Policy


If you plan to distribute Internet Explorer 10 through the Group Policy software installation, you must use a Windows Installer package (.msi file). These packages can be created using Internet Explorer Administration Kit 10 (IEAK 10).

Installing Internet Explorer 10

The following sections provide details about how to install Internet Explorer 10 in your organization.

Installing using System Center Configuration Manager

If you are using System Center Configuration Manager to deploy Internet Explorer 10, we suggest following these steps:

To install using System Center Configuration Manager

  1. Download the prerequisites for your version of the operating system. For more information about prerequisites, see System Requirements and Language Support.

  2. Download the installer from the Internet Explorer 10 home page.

    The installers on this page do not need Internet connectivity if the prerequisites are already installed.

  3. Add the prerequisites to your System Center Configuration Manager bundle.

  4. Add the Internet Explorer 10 installer to the System Center Configuration Manager bundle.

    If you want Internet Explorer 10 to install without user interaction, run the installer with the /quiet command. For example: IE10-Windows6.1-en-us-x86.exe /quiet.

Avoiding an additional reboot when installing prerequisites

If a reboot is still required after the prerequisites are installed, extract the Internet Explorer 10 .cab file from the Internet Explorer 10 installer, and then replace the instructions shown in step 4 with the following steps:

  1. Open a command window running as Administrator, and then run the following command: IE10-Windows6.1-en-us-x86.exe /x:[destination folder]

    Where destination folder is the location you selected for storing the .cab file.

    This command extracts the .cab file, for example,, placing it in your selected destination folder.

Installing using Windows Update or Windows Server Update Services

Internet Explorer 10 is published as a download through Windows Update, so in organizations where users receive updates directly from Windows Update, Internet Explorer 10 may already have been downloaded to user's computers.

To prevent excessive network traffic and to provide greater control over the packages installed on users' computers, larger organizations may elect to use Windows Server Update Services (WSUS). WSUS lets you download a single copy of updates for Microsoft products and cache them on local servers. Users' computers can then be configured to receive updates directly from one or more WSUS servers rather than through Windows Update.

Approving Internet Explorer in WSUS

  1. Open your WSUS administration website (typically accessed through http://WSUSServerName/WSUSAdmin/), where <WSUSServerName> is the name of your WSUS computer.

  2. In the To Do list, select Review synchronization settings.

  3. In Tasks, select Synchronize now to synchronize your WSUS server with Windows Update.

  4. In the navigation bar at the upper right of the page, select Updates to switch to the list of available updates.

  5. Using Search, in the Contains text box, type Internet Explorer 10 to filter the list of updates.

  6. Click Apply.

  7. Select the appropriate Windows Internet Explorer 10 for (Your OS) in the list of updates.

  8. In Update Tasks, select Approve for installation.

  9. In the Approval column, click the link for each computer group that you want to configure, and select the approval level.

  10. Click OK to apply the approval.

Importing from Microsoft Update catalog into WSUS

Any computer that has the WSUS administrative console installed, whether or not it is a WSUS server, can be used to import Internet Explorer 10 release from the catalog site. You must be logged on to the computer as an administrator to import the hotfixes.

To access the Microsoft Update catalog site

  1. In the WSUS administrative console, select either the top server node or the Updates node, and in the Actions pane click Import Updates.

    A browser window will open at the Microsoft Update Catalog website.

  2. Install the Microsoft Update Catalog ActiveX® control so you can access updates from this site.

  3. Search for Internet Explorer 10 on the site and add the updates to your basket.

When you've finished browsing, go to the basket and click Import to import your updates. To download the updates without importing them, clear the Import directly into Windows Server Update Services checkbox.

Installing using a flat network share

A flat network share is a folder or folder tree that is accessible to network users. It contains the files necessary to install Internet Explorer 10. Installation can be as simple as placing a single version of the installer file in a shared folder, or as complex as creating separate subfolders for multiple architectures and operating system versions. If you work in a multilingual organization, you may want to provide separate folders to hold different language versions.


This media type is used when you build custom browser packages on a local area network (LAN), or when you plan to distribute your packages from a LAN. You can then direct users to the designated directory on your LAN, and they can run the Setup program directly from that location.

Using IEAK 10

If you selected the Full Installation Package type in the Internet Explorer Customization Wizard 10, the wizard places all of the installation files in the \build_directory\Flat folder. With IEAK 10, you can use any language version of the customization wizard to create localized custom packages of the browser in any language that Internet Explorer is shipped in.

Manually creating the flat network share

Internet Explorer 10 uses a single executable file for installation. To create a flat network share manually, copy the file into a folder and make that folder available to network users. To support multiple architectures or operating systems, create subfolders for your installation files that are clearly labeled by operating system and architecture.

Installing using Active Directory and Group Policy

Deploying software in this manner is generally recommended only for smaller organizations, with a small number of applications to deploy using a Group Policy Object (GPO). This is due to the limitations of targeting and reporting not provided natively with this approach. Additionally, GPO delivered software depends upon .msi installation files, and many software packages are not available with .msi installation file definitions. For more information about GPO and software deployments, see: Group Policy Planning and Deployment Guide.

You can make software available to users in Windows Control Panel. By using Add or Remove Programs, users can manage software on their own computers. However, you can control what software is available to users in Add or Remove Programs by using Group Policy settings.

Add or Remove Programs includes an active web link for each application, which provides users with the support information they need to install certain applications. However, you can overwrite the default link by using the software installation extension of Group Policy. The support link then corresponds to your internal product support resources.

You can also have this link point to a support page. This resource could include information such as an FAQ about a specified application, a help desk article about using the application, or instructions for requesting support. This can save time for both users and help desk personnel.

Troubleshooting the Setup process

To troubleshoot Setup:

  • Review the IE10_main.log file in the Windows folder. Each installation creates a log file, which collects information about that particular installation. If an IE10_main.log file already exists, Setup appends the existing log file.

  • Make sure the download URLs that you specify during Setup are the same as the URLs for the download server.

  • See Appendix A: Troubleshooting in this deployment guide. This section provides information about commonly reported issues and solution strategies.

See Also


Customizing Internet Explorer 10