If you’re like me, you like to make sure the latest version of Internet Explorer supported by your organization is baked into the images you push into production, and IE10 on Windows 7 is no different. Whether you’re slipstreaming it into the base image, or (better) using MDT to rebuild your base image and including IE10 into it, Microsoft has provided a handy list of updates that you should have already included before you attempt to install IE10 on Windows 7 without internet access (as most image build environments should be – right? Right????):
How to obtain prerequisite updates for Internet Explorer 10 for Windows 7 that fail to install
That article lists 5 hotfix packages you will need – KB2533623, KB2670838, KB2729094, KB2731771, and KB2786081. However, the astute amongst you have probably noticed that the IE10 installer, when left to it’s own devices during install, actually installs 6 hotfix packages, not 5. That “extra” hotfix package is:
“0x00000050” Stop error after you install update 2670838 on a computer that is running Windows 7 SP1 or Windows Server 2008 R2 SP1
Once you’ve got the hotfixes on a Windows 7 box, you can simply run the IE10 web installer package that you can download here with the proper switches to make it passive (or silent, if you prefer). I prefer passive installers so I can see it going by in MDT, and I use the following command line for the x64 installation package, for reference:
IE10-Windows6.1-x64-en-us.exe /passive /update-no /closeprograms /norestart
As long as you reboot the machine via your task sequence (or whatever packaging tool you’re using to push this down) after installation completes, you’ll end up with a fully-functional IE10, and hotfixes, on the other end of this exercise. If you’re trying to match what IE10 does natively when it installs when integrating it into your own Windows 7 images (and you probably should), you will likely want to install that additional update as well as the required 5.