gotenks98

Deploying IE 10 for Windows 7

33 posts in this topic

Sure you made something wrong!

*Edit: look at your dism.log file to find errors!

Edited by myselfidem
0

Share this post


Link to post
Share on other sites

I manually mount the image with my right click .wim

I then ran a small .cmd file with all the updates and the IE10-Windows6.1-x64-en-us.exe in same folder

I pause each step to watch the results

cd %~dp0
IE10-Windows6.1-x64-en-us.exe /x:%~dp0\IE10SLIP
pause
Dism.exe /image:D:\zMountdir /Add-Package /PackagePath:%~dp0
pause
Dism /Image:D:\zMountdir /Add-Package /PackagePath:%~dp0IE10SLIP\IE-Win7.CAB
Dism /Image:D:\zMountdir /Add-Package /PackagePath:%~dp0IE10SLIP\IE-Spelling-NEU.MSU
Dism /Image:D:\zMountdir /Add-Package /PackagePath:%~dp0IE10SLIP\IE-Hyphenation-NEU.MSU
pause
exit

Dismount image saving

Then installed using VMware Workstation

Image above where I showed turning off that update was from there

0

Share this post


Link to post
Share on other sites

I figured it out. The issue is 2 things. One machine integrated from gave me a different error than my windows 8 machine. If I do it from the windows 8 machine it actually gave me an error I could look into using the log files. It ended up being one of the settings in the unattend.xml file that's depreciated. The problem is I never changed that setting it comes default in the answer file. So I had to delete the internet explorer section of the unattended file and re-add it after I updated the catalog file to show IE10. Once I did this it worked using MDT 2012. This problem could have been easier to figure out had I started the integration from the Windows 8 machine. My thoughts are that there is a bug in the Windows ADK that if you do integration from windows 7 it does it differently than windows 8. I got all kinds of weird errors doing this differently on Windows 7.

0

Share this post


Link to post
Share on other sites

Installs for me this way on a running Win 7 via runoncex method so you could do a post install

REG ADD %KEY%\1001 /VE /D "Internet Explorer 10.0.9200.x x64" /f
REG ADD %KEY%\1001 /V 101 /D "CMD /C Start /Wait D:\APPS\IE10_X64\Windows6.1-KB2670838-x64.msu /quiet /norestart" /f
REG ADD %KEY%\1001 /V 102 /D "CMD /C Start /Wait D:\APPS\IE10_X64\Windows6.1-KB2533623-x64.msu /quiet /norestart" /f
REG ADD %KEY%\1001 /V 103 /D "CMD /C Start /Wait D:\APPS\IE10_X64\Windows6.1-KB2731771-x64.msu /quiet /norestart" /f
REG ADD %KEY%\1001 /V 104 /D "CMD /C Start /Wait D:\APPS\IE10_X64\Windows6.1-KB2729094-v2-x64.msu /quiet /norestart" /f
REG ADD %KEY%\1001 /V 105 /D "CMD /C Start /Wait D:\APPS\IE10_X64\Windows6.1-KB2786081-x64.msu /quiet /norestart" /f
REG ADD %KEY%\1001 /V 106 /D "CMD /C Start /Wait D:\APPS\IE10_X64\IE10-Windows6.1-x64-en-us.exe /passive /update-no /closeprograms /norestart" /f
REG ADD %KEY%\1001 /V 107 /D "CMD /C DEL \"%USERPROFILE%\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\Launch Internet Explorer Browser.lnk\"" /f
REG ADD %KEY%\1001 /V 108 /D "REGEDIT /S D:\APPS\IE10_X64\Disable_IE10_Auto_Update.reg" /f

This is working for me but there is one problem. After it kills reloads explorer.exe, IE10 then opens and shows the first-run wizard. Is there any other way to install IE10 where it won't open after install?

0

Share this post


Link to post
Share on other sites

REG ADD %KEY%\1001 /VE /D "Internet Explorer 10.0.9200.x x64" /f

is what I used on a running system

If used in an unattend with xml disabling first run and welcome page it might work

I'll have to start over with my image since I injected IE10 as a test

0

Share this post


Link to post
Share on other sites

Can't disable the first run wizard... so that is out. I have sent this problem along to MS, waiting for an answer. I have a sneaking suspicion that the answer will be to inject it into the image... :rolleyes:

0

Share this post


Link to post
Share on other sites

This tweak works fine for me


;IE10 - Disable first run wizard: 1 to homepage, 2 to welcome page, to enable just to remove the value
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\Main]
"DisableFirstRunCustomize"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Main]
"DisableFirstRunCustomize"=-
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Microsoft\Internet Explorer\Main]
"DisableFirstRunCustomize"=-

0

Share this post


Link to post
Share on other sites

An install with IE10 injected and xml disabling those things writes to the reg here. Most things related in xml will be written here

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\UnattendBackup\ActiveSetup\DisableFirstRunWizard]

"DisableFirstRunWizard"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\UnattendBackup\ActiveSetup\DisableWelcomePage]

"DisableWelcomePage"=dword:00000001

0

Share this post


Link to post
Share on other sites

Hmm, good information, fully tested and working here now.

I don't bother with applying every single patch individually, based my testing only order required is to make sure prerequisites are handled first (otherwise it will fail during IE 10 steps), then Internet Explorer 10, then Hyphenation/Spelling, followed by everything else. My base image is now 6 packages (prerequisites), IE 10, 62 critical, and 31 optional updates to get a Windows 7 image requiring no Windows update patches (not counting KB2533552 and Malicious Software Removal Tool)


dism /Image:.\mount /Add-Package /PackagePath:.\updates\prereq
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Win7.CAB
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Hyphenation-NEU.MSU
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Spelling-NEU.MSU
dism /Image:.\mount /Add-Package /PackagePath:.\updates\crit
dism /Image:.\mount /Add-Package /PackagePath:.\updates\opt

As for welcome screen/first run, this is working fine (as it has since GA release for IE8/IE9/IE10)


<settings pass="specialize">
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64">
<DisableFirstRunWizard>true</DisableFirstRunWizard>
<Home_Page>about:blank</Home_Page>
</settings>

0

Share this post


Link to post
Share on other sites

Hmm, good information, fully tested and working here now.

I don't bother with applying every single patch individually, based my testing only order required is to make sure prerequisites are handled first (otherwise it will fail during IE 10 steps), then Internet Explorer 10, then Hyphenation/Spelling, followed by everything else. My base image is now 6 packages (prerequisites), IE 10, 62 critical, and 31 optional updates to get a Windows 7 image requiring no Windows update patches (not counting KB2533552 and Malicious Software Removal Tool)


dism /Image:.\mount /Add-Package /PackagePath:.\updates\prereq
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Win7.CAB
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Hyphenation-NEU.MSU
dism /Image:.\mount /Add-Package /PackagePath:.\updates\ie10\IE-Spelling-NEU.MSU
dism /Image:.\mount /Add-Package /PackagePath:.\updates\crit
dism /Image:.\mount /Add-Package /PackagePath:.\updates\opt

As for welcome screen/first run, this is working fine (as it has since GA release for IE8/IE9/IE10)


<settings pass="specialize">
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64">
<DisableFirstRunWizard>true</DisableFirstRunWizard>
<Home_Page>about:blank</Home_Page>
</settings>

This is what I am trying to do but I keep getting failures on the updates when it gets like 30+ updates in. It keeps saying the image is no longer serviceable. I have to basically start over if I get this.

0

Share this post


Link to post
Share on other sites

This is what I am trying to do but I keep getting failures on the updates when it gets like 30+ updates in. It keeps saying the image is no longer serviceable. I have to basically start over if I get this.

I can't say exactly what the issue is here... there is significant patch overlap once you start integrating IE... I believe you can end up breaking the image by trying to push a patch that was for previous version of IE into an image that already has a newer version integrated. For reference, these are the current set of patches used in my image to bring it fully up to date (at least until patch Tuesday tomorrow):

Pre-Req:

windows6.1-kb2533623-x64.msu

windows6.1-kb2639308-x64.msu

windows6.1-kb2670838-x64.msu

windows6.1-kb2729094-v2-x64.msu

windows6.1-kb2731771-x64.msu

windows6.1-kb2786081-x64.msu

Critical:

windows6.1-kb2479943-x64.msu

windows6.1-kb2491683-x64.msu

windows6.1-kb2506014-x64.msu

windows6.1-kb2506212-x64.msu

windows6.1-kb2509553-x64.msu

windows6.1-kb2511455-x64.msu

windows6.1-kb2532531-x64.msu

windows6.1-kb2536275-x64.msu

windows6.1-kb2536276-v2-x64.msu

windows6.1-kb2544893-x64.msu

windows6.1-kb2552343-x64.msu

windows6.1-kb2560656-x64.msu

windows6.1-kb2564958-x64.msu

windows6.1-kb2570947-x64.msu

windows6.1-kb2579686-x64.msu

windows6.1-kb2584146-x64.msu

windows6.1-kb2585542-x64.msu

windows6.1-kb2604115-x64.msu

windows6.1-kb2618451-x64.msu

windows6.1-kb2619339-x64.msu

windows6.1-kb2620704-x64.msu

windows6.1-kb2620712-x64.msu

windows6.1-kb2621440-x64.msu

windows6.1-kb2631813-x64.msu

windows6.1-kb2644615-x64.msu

windows6.1-kb2645640-x64.msu

windows6.1-kb2653956-x64.msu

windows6.1-kb2654428-x64.msu

windows6.1-kb2656356-x64.msu

windows6.1-kb2656411-x64.msu

windows6.1-kb2659262-x64.msu

windows6.1-kb2660649-x64.msu

windows6.1-kb2661254-x64.msu

windows6.1-kb2667402-v2-x64.msu

windows6.1-kb2676562-x64.msu

windows6.1-kb2685939-x64.msu

windows6.1-kb2690533-x64.msu

windows6.1-kb2691442-x64.msu

windows6.1-kb2698365-x64.msu

windows6.1-kb2705219-v2-x64.msu

windows6.1-kb2712808-x64.msu

windows6.1-kb2718704-x64.msu

windows6.1-kb2727528-x64.msu

windows6.1-kb2729452-x64.msu

windows6.1-kb2736233-x64.msu

windows6.1-kb2736422-x64.msu

windows6.1-kb2742599-x64.msu

windows6.1-kb2743555-x64.msu

windows6.1-kb2749655-x64.msu

windows6.1-kb2753842-v2-x64.msu

windows6.1-kb2756921-x64.msu

windows6.1-kb2757638-x64.msu

windows6.1-kb2769369-x64.msu

windows6.1-kb2770660-x64.msu

windows6.1-kb2778344-x64.msu

windows6.1-kb2779562-x64.msu

windows6.1-kb2785220-x64.msu

windows6.1-kb2789645-x64.msu

windows6.1-kb2790113-x64.msu

windows6.1-kb2790655-x64.msu

windows6.1-kb2799494-x64.msu

windows6.1-kb971033-x64.msu

Optional:

windows6.1-kb2506928-v2-x64.msu

windows6.1-kb2515325-x64.msu

windows6.1-kb2529073-x64.msu

windows6.1-kb2541014-x64.msu

windows6.1-kb2545698-x64.msu

windows6.1-kb2547666-x64.msu

windows6.1-kb2563227-x64.msu

windows6.1-kb2574819-x64.msu

windows6.1-kb2592687-x64.msu

windows6.1-kb2603229-x64.msu

windows6.1-kb2640148-v2-x64.msu

windows6.1-kb2647753-v4-x64.msu

windows6.1-kb2660075-x64.msu

windows6.1-kb2685811-x64.msu

windows6.1-kb2685813-x64.msu

windows6.1-kb2699779-v2-x64.msu

windows6.1-kb2709630-x64.msu

windows6.1-kb2709981-v2-x64.msu

windows6.1-kb2719857-x64.msu

windows6.1-kb2726535-x64.msu

windows6.1-kb2732059-v5-x64.msu

windows6.1-kb2732487-v2-x64.msu

windows6.1-kb2732500-v2-x64.msu

windows6.1-kb2739159-x64.msu

windows6.1-kb2750841-x64.msu

windows6.1-kb2761217-x64.msu

windows6.1-kb2762895-x64.msu

windows6.1-kb2763523-x64.msu

windows6.1-kb2773072-x64.msu

windows6.1-kb2786400-x64.msu

windows6.1-kb982018-v3-x64.msu

0

Share this post


Link to post
Share on other sites

Also if you inject too many times you will get those errors. Start over with fresh install.wim.

I inject monthly updates but after 3-4 times I start fresh and inject all at once. I have 122 64 bit msu total now

0

Share this post


Link to post
Share on other sites

Your listing of updates will come in handy. I think I have almost as many if separating them out like that. What I will do is put all the critical updates separate and save the images in sections, like 30 updates at a time.

0

Share this post


Link to post
Share on other sites

Well I got the answer I thought I would... And there seems no real way to make IE 10 not open itself at the end of setup... and the recommended method is to inject it in the image. This makes sense since it is required for certain parts of the channel to not even offer IE8 or 9 and use IE10 across the board.

0

Share this post


Link to post
Share on other sites

I have no trouble if all prerequisite updates are integrated and IE10 integrated.

And add inside Autounattend.xml these values for Windows 7 x86:


<settings pass="specialize">
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DisableFirstRunWizard>true</DisableFirstRunWizard>
<DisableWelcomePage>true</DisableWelcomePage>
</component>

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.