none
Win7 + IE10 Slipstream error RRS feed

  • Question

  • I am trying to install a test image with IE10 slipstreamed in and getting an error "Windows could not parse or process unattend answer file [C:\windows\Panther\unattend.xml] for pass [specialize]. A component or setting specified in the answer file does not exist."  I used an original Win7 Ent SP1 image + IE10 and then imported full source as if from original DVD / ISO.  Then created a new sequence and problem still occurs.

    I think it is being caused by:

    <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <IEWelcomeMsg>false</IEWelcomeMsg>
    </component>

    Which I am not sure is a setting I set in MDT setup or a default setting?  This setting has been removed from IE10.

    Tuesday, February 26, 2013 10:10 PM

Answers

  • ok, this was pretty easy to fix actually.

    Right click your task sequence > OSinfo > edit unattend.xml.

    Wait 5 hours for it to process (zzzzz)

    Then in WSIM find Microsoft-Windows-IE-InternetExplorer

    Look for  IEWelcomeMsg > right click and disable "write image value" Save the unattend.

    You should be able to deploy then.


    Thursday, March 7, 2013 10:23 AM
  • Comment out the offending line here's the format below in Deployment Share\Control\Task Sequence ID\Unattend.xml

    Before:  <IEWelcomeMsg>false</IEWelcomeMsg>

    After:  <!-- <IEWelcomeMsg>false</IEWelcomeMsg> -->

    • Proposed as answer by Ran Vijay Bharti Wednesday, November 6, 2013 2:45 AM
    • Marked as answer by Brian Hoyt Tuesday, February 18, 2014 7:52 PM
    Wednesday, November 6, 2013 2:39 AM

All replies

  • For clarification, please define "slipstreamed".

    Jason | http://blog.configmgrftw.com

    Tuesday, February 26, 2013 10:40 PM
  • Brian

    Did you follow this?

    http://technet.microsoft.com/en-us/library/jj851192.aspx

    Im guessing this is what was meant by slipstreaming..

    Taken from the above link...

    Preinstalling Internet Explorer 10 on Windows 7 SP1 or Windows Server 2008 SP1

    You can preinstall Internet Explorer 10 on Windows 7 SP1 or Windows Server 2008 R2 with SP1, by slipstreaming Internet Explorer 10 into the operating system image. At this time, Microsoft only supports the English (en-us) version.

    Thanks

    Paul


    Twitter: @iddonline.....Any advice given in these forums should be tested in a non production environment before implementing.

    Tuesday, February 26, 2013 11:34 PM
  • Why slipstream it?  Just run an silent install as an application during capture?

    IE 10 Unattended install

    If not, you can always edit the Unattend.xml using WSIM and remove that key from the Unattend.  If I remember WISM will warn your that that key is deprecated,  but it usually wont error.

     
    Wednesday, February 27, 2013 2:01 AM
  • Yes I followed the above instructions (almost identical to IE9 process).  I slipstream since I know it is going to be in all my future builds so I spend the time once building it into image rather than causing every deployment to take longer.  I try to optimize the speed of deployment as much as possible so anything I can do ahead of time is a plus.  I did edit the unattend.xml and removed it but I was trying to figure out if I was going to have to do that everytime I create a new task sequence or if it was a default setting I could change in deployment config.  Having this in unattend.xml will cause an infinite reboot during deployment and will not allow setup to complete properly.
    Wednesday, February 27, 2013 12:30 PM
  • Do you have much in the unattend?  We have a pretty complicated deployment here and I don't have anything in the unattend at all,  all done through MDT itself.  Maybe the setting that you require to change in the unattend you can move out and just leave it as the default.

    Come to think of it,  you can edit the default unattend (that is used as a template).  You can find the template in your local workstation under C:\Program Files\Microsoft Deployment Toolkit\Templates , remove that key and you will only ever have to do it once!

    On a side note,  I understand your point regarding the slipstream, I'm also working towards streamlining as much as possible.... for gods sake lets just get SP2 ha ha

    EDIT :: Just a reminder though,  if you change the unattend template on your workstation,  it is ONLY for your workstation.  Any other techs working on it will not have it unless you copy it over.
    • Edited by mhouston100 Wednesday, February 27, 2013 8:50 PM
    Wednesday, February 27, 2013 8:49 PM
  • I get this as well. I updated my base image with Internet Explorer 10, syspreped it as usual and copied it up to our deployment share. Deploying gets as far as you before failing.

    My unattend has very little in it & doesn't have any IE stuff in it at all.

    This process always worked previously with IE9.

    Wednesday, March 6, 2013 4:02 PM
  • ok, this was pretty easy to fix actually.

    Right click your task sequence > OSinfo > edit unattend.xml.

    Wait 5 hours for it to process (zzzzz)

    Then in WSIM find Microsoft-Windows-IE-InternetExplorer

    Look for  IEWelcomeMsg > right click and disable "write image value" Save the unattend.

    You should be able to deploy then.


    Thursday, March 7, 2013 10:23 AM
  • you can go to the control folder in your DS and look for the folder with your task sequence id and open the Unattend.xml from there with wsim it will save you time.

    might be that you need to point wsim to the right catalog file then though.


    Thursday, March 7, 2013 11:26 AM
  • Thanks, didn't realise that. Will save lots of time!
    Thursday, March 7, 2013 1:35 PM
  • I'm having the same issue.

    I'm using MDT 2012 and the "IEwelcomeMsg" is already set to false with the "write Image Value" checked.  When I Right Click the "IEwelcomeMsg" I do not get a disable option.  I only see revert change or wrtie image value.

    So in order for me to get a test deployment to work is to delete the whole IE string from the specialized phase.  Only now I've lost my settings.

    Thursday, March 14, 2013 9:55 PM
  • Uncheck the "Write image Value" bit, then it won't enter that into the .xml & deploy fine.

    Thursday, March 14, 2013 9:57 PM
  • Ok will try it.

    =)

    Thursday, March 14, 2013 10:12 PM
  • After Running numerous tests I can confirm that everything is working just fine.

    Thanks for the advice DrCheese, not so stressed out now =)

    Funny how one change via Windows Update can screw up your deployments.

    Friday, March 15, 2013 2:03 AM
  • Hi DrCheese128,

    Thank you for this fix, it pays to google the problem and up pop this thread.

    This is correct answer.


    Please bear in mind, that my answer is based on the details given in your post. The more I get the better the answer, Slan go foill, Paul

    Friday, May 3, 2013 6:58 PM
  • You're welcome. 

    It drives me nuts when I google, find someone with the same problem but no answer!

    I make a point to go back to threads if/when I find a solution and post it to avoid someone else having the same angst as me :P


    Friday, May 3, 2013 7:21 PM
  • Hi,

    Did you get this working by just adding the IE files (and prerequisites) to the Packages sequence in MDT, or did you inject them into an offline WIM with DISM? If I just apply the packages IE10 is not added.

    If I add a new step within the Task Sequence PreInstall Phase after the existing Apply Patches) I get the following error:

    FAILURE ( 5627 ): -2147418113 0x8000FFFF: Run DISM.exe

    Litetouch deployment failed, Return Code = -2147467259 0x80004005

    Failed to run the action: Install Operating System.

    Unknown error (Error: 000015FB; Source: Unknown)

    The execution of the group (install) has failed and the execution has been aborted. An action failed

    Operation aborted (Error: 8004004; Source: Windows)

    Failed to run the last action: Install Operating System. Execution of task sequence failed.

    Unknown error (Error: 00015FB; Source: Unknown)

    Task Sequence Engine failed! Code: enExecutionFail

    Task sequence execution failed with error code 80004005

    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

    Obviously running the second Patch Sequence is causing the problem, but without, the IE 10 update is not applying (I'm assumimg it is running before a prerequisite has been installed).

    Any thoughts would be appreciated......

    Monday, June 3, 2013 8:34 PM
  • Slight update - actually it doesn't look like it is the second Patch Install sequence that was added)!

    I created a new folder under packages and added the 3 IE 10 updates (Microsoft-Windows-IE-Hyphenation-Parent-Package-English neutral neutral 10.2.9200.16437, Microsoft-Windows-IE-Spelling-Parent-Package-English neutral neutral 10.2.9200.16437 and Microsoft-Windows-InternetExplorer-Package-TopLevel neutral amd64 10.2.9200.16521) and get the same error as above (the default packages folder contains all other updates).

    Still stumped!

    Monday, June 3, 2013 9:25 PM
  • Worked for me as well. my feb images worked fine and this may one kept bailing. I just go in and delete this one key using Windows System Image manager.

    1.) go to your deployment share and find the correct task sequence directory. Something like "\\SERVER\deploymentShare\Control\*IMAGENAME*\"

    2.) find the unattend.xml file "\\*SERVER*\deploymentShare\Control\*IMAGENAME*\Unattend.xml"

    3.) once found, open with windows system image manager and navigate to: unattend -> components -> 4 specialize -> x86 microsoft windows ie internetexplorer_neutral (OR AMD64) -> IEWelcomeMsg

    4.) delete the iewelcomemsg key and save

    5. RE run your deployment task from f12 and it should boot fine now.

    Me thinks MS needs to update MDT. Just took a look and there is no update as of today.


    Monday, June 3, 2013 9:52 PM
  • I removed the whole IE Key (sledgehammer approach at the moment) and still no joy. Do you have all packages (post SP1) dumped into a single (default) packages folder?

    Monday, June 3, 2013 10:17 PM
  • Hmm well i dont do any installing of packages that way. The only thing I add is drivers with deployment workbench.

    My imaging process is to use VMware. Start from scratch with a ISO install and then join to domain to apply updates with wsus. Install my applications and such, unjoin from domain, and then take a snapshot in vmware before litetouching.

    I have been reverting to the previous snapshot, and then simply reconnecting to domain and wsauclt detectnow to download patches every few months. Then i make a new snapshot and capture the image, reverting when the image is captured again. VMware has made rolling out images a breeze, as previously I had to image a machine, make a change, then test it, and if it didnt work, back to reimaging. Snapshots in VM is a lifesaver taking a day long process into something I can do in less than an hour.

    So I never installed packages updates or anything else but drivers using WDS. The only thing I provide it when pulling an image from the server is the machine name and domain credentials. I have never had to edit this unattend.xml file before. Although I have edited other ones such as .\control\DomainOUList.xml.

    All custom IE settings are managed using group policy.

    Monday, June 3, 2013 10:29 PM
  • I've had no problems getting IE10 installed Post OS - what I've not seen is if anyone has injected it in via the MDT (also seen people manually running DISM to add it offline).

    I am beginning to think it may not be possible (which is a pain, especially as they made it so easy with IE9).

    Monday, June 3, 2013 10:32 PM
  • Kelvinf, I am trying to do the same thing.  My install.wim is unmodified from the 64-bit Windows 7 Enterprise with SP1 DVD, and I'm trying to use MDT Packages to install Internet Explorer 10.  I imported the .msu files for KB2670838, KB2639308, KB2533623, KB2731771, KB2729094, and KB2786081, as well as IE-Win7.CAB and the hyphenation and spelling packages.  After deployment Control Panel => Windows Update => View installed updates shows that the prerequisites were installed, but Internet Explorer is still version 8, not 10.  ZTIPatches.log indicates that all of my Packages are being added to the deployment, but it doesn't look like it's ever attempting to install IE10.

    One thing I did try is integrating the prequisites into the .wim file, leaving only IE10 itself to be installed by Packages, and that actually worked.  I also tried creating two Packages folders with corresponding Selection Profiles: one called IE10 Prerequisites and one called IE10 Application.  I opened my Task Sequence and changed the default Apply Patches task (at the end of the Preinstall state) to use the IE10 Prerequisites Selection Profile, then added a second Apply Patches task to the beginning of the Postinstall state that uses the IE10 Application Selection Profile.  With these changes and using the original install.wim (without the IE10 prerequisites integrated), after deployment it's still on IE8, however there's a notification to restart following the installation of KB2621440.  I'll try more next week.  Maybe I just need to add a Restart Computer task after the second Apply Patches.

    Friday, June 14, 2013 8:48 PM
  • Just checked my unattend.xml in MDT and IEWelcomeMsg is enabled again after I disabled it a while ago. It doesn't seem to cause a problem anymore even when it's enabled. Does anyone have any idea why? Thanks. 

    Thursday, June 27, 2013 3:30 PM
  • i don't see "write image value" when i select IEWelcomeMsg i only see Action "DefaultAction" Key and Value "false"
    Wednesday, July 24, 2013 9:36 PM
  • DrCheese128, you're my hero.  I was walking down the wrong dark alley far too long.  Followed your steps and presto, deployment completes successfully. 
    Thursday, July 25, 2013 4:35 PM
  • AMAZING!!! Worked like a charm!!! Thank you!

    Alex

    Wednesday, August 14, 2013 6:24 PM
  • DrCheese128, thanks.  It's really very sound of you to come back to the thread and update it with the solution you found.  I share your frustration at sometimes finding an abandoned thread where someone has had the same problem and not updated the thread.

    Disappointed in Microsoft that they wouldn't have released an update for MDT that fixed this automatically, but hey I got DrCheese to help me so all good!

    Monday, September 16, 2013 5:23 PM
  • think i heard someone say they fixed it in MDT 2013 but since 2013 is only a preview....
    Tuesday, September 17, 2013 5:29 PM
  • I can confirm this is fixed in RTW of MDT 2013.
    Friday, November 1, 2013 6:47 PM
  • I'm still having no joy with this and a completely slipstreamed install.

    At the moment I have two Install Updates Offline sections in Preinstall - One installing the IE Pre-Req packages (Selection Profile), and then another for the IE10 CAB (another Selection Profile).

    All runs through until "Setup is applying system settings" at which point it bombs (nothing in any local log until after the reboot).

    Has anyone actually been able to take a vanilla SP1 Image and add IE10 to it (rather than installing post OS deployment)?

    Monday, November 4, 2013 2:41 PM
  • i thought IE10 was a automatic update these days so it should get installed when you run ztiupdates.wsf

    Monday, November 4, 2013 5:23 PM
  • That's not possible (or desirable) on our network. Everything needs to go into the Reference image.
    Monday, November 4, 2013 5:26 PM
  • when you create your reference image you can run the updates so they only need to be downloaded once. then just capture that image and voila you have a  fully updated reference image with IE10.
    Monday, November 4, 2013 10:02 PM
  • We've already done it all manually (or via Application Installs) that wasn't what I wanted to achieve.

    That said, I have not got a fully slipstreamed build working with IE10 going into the Reference image. I've had to create two TS Package sequences (with selection profiles as I detailed above) and the LTIApply.WFS needs to be updated (as per this post - http://superuser.com/questions/600823/how-to-fix-internet-explorer-10-x64-sysprep-using-microsoft-mdt).

    This then allows the normal patching process to complete (including the IE10 pre-reqs), then installs IE10 before carrying on with the remainder of the unattended build (the post details a bug for x64 machines and Sysprep). I'm just in the process of testing whether the cumulative updates will also apply with IE as well.

    Tuesday, November 5, 2013 10:58 AM
  • Comment out the offending line here's the format below in Deployment Share\Control\Task Sequence ID\Unattend.xml

    Before:  <IEWelcomeMsg>false</IEWelcomeMsg>

    After:  <!-- <IEWelcomeMsg>false</IEWelcomeMsg> -->

    • Proposed as answer by Ran Vijay Bharti Wednesday, November 6, 2013 2:45 AM
    • Marked as answer by Brian Hoyt Tuesday, February 18, 2014 7:52 PM
    Wednesday, November 6, 2013 2:39 AM
  • FYI this fix continues to satisfy!

    Thanks!

    Saturday, January 18, 2014 12:22 AM
  • I usually just delete the line which also works.
    Tuesday, February 18, 2014 7:53 PM
  • Hi All,

    I have tried to get my image to work and no matter what I do I get the Windows could not parse error.  I have removed the IE welcome message from the unattend and I still get the error.  I have another image for our desktops that work just fine.  But the one for the laptops does not work at all.  Any ideas as I am out of them at the moment.

    Thanks

    Tuesday, February 25, 2014 4:23 PM
  • Hi All,

    I have tried to get my image to work and no matter what I do I get the Windows could not parse error.  I have removed the IE welcome message from the unattend and I still get the error.  I have another image for our desktops that work just fine.  But the one for the laptops does not work at all.  Any ideas as I am out of them at the moment.

    Thanks

    When you say 'the one for our laptops', do you have a different task sequence to deploy on to your laptops?

    If so, then that task sequence will have it's own unattend.xml and will also need to be edited as above.  It's not clear if you've already done that? (because you refer to just removing the IE welcome message from a single unattend)

    Another post above refers to changing the default/template unattend.xml which will also fix the problem for any new task sequences you create.

    Wednesday, February 26, 2014 7:53 AM
  • If your sure you removed the entry my guess would be driver problems.

    I no longer have this problem at all. Like I dont have to remove the entry or anything. we did upgrade the wds server and are using win8pe and lite touch now. perhaps that has something to do with it. I can't remember how i fixed this. Check for microsoft updates. I assume MS fixed it in the last 9 months sometime.

    Wednesday, February 26, 2014 4:12 PM
  • Hi,

    Thanks for the reply, I have a deployment for our desktops and one for our laptops.  They each have their own deployment share with their own task sequence.  I have gone into the unattend from the task sequence by going to properties>os info> Edit unattend.xml. 

    Then went into the specialized and removed the entry for IE welcome message.

    When I get the error if I hit shift+f10 and open up the unattend.xml file in the c:\windows\Panther folder it still has the IE welcome message line in there and it is set to false.  I also noticed that it doesn't have the right organization or user name in the unattend.  Could it be possible it is mixing up to unattend files or pulling a file from somewhere else?

    But if I go to the unattend in the deployment share it has the right info in it? 

    Wednesday, February 26, 2014 6:20 PM
  • I think that you have not yet correctly edited the specific unattend.xml file for your laptop task sequence.  I may be wrong, but that's what the problem sounds like.

    See here for a clear primer on the role of unattend.xml and customsettings.ini

    each Task Sequence has its own Unattend.xml file associated with it, whereas Customsettings.ini applies to the Deployment Share globally.

    Does that point you in the right direction?

    Thursday, February 27, 2014 8:04 AM
  • Hi Guys,

    I figured out what the issue was. We had moved our deployment services to a new server and there were some pointers still pointing it to the deployment share on the old server.  I guess we missed changing this deployment share. So I was editing the right unattend.xml file but the server was pulling the old one from the old server. I made the changes this morning and it is all working correctly now.  Thanks for everyone's help on this appreciated all the responses.

    Friday, February 28, 2014 3:33 PM
  • Great news, well fixed! 
    Friday, February 28, 2014 5:06 PM
  • I am still getting this error with MDT2013. However, I do not have any IE entries in my unattend file.
    Saturday, April 5, 2014 9:28 PM
  • This worked like a charm. I tried everything and even tried to recreate the image and start over. Thank You!
    Monday, May 5, 2014 3:26 PM
  • Hi just wondering if you got yours working. I am getting Copyprofile error ( cannot parse unattend.xml) in Mdt 2013. ADk 8.1 on my win 7 deployments that worked fine in MDT 2012 u 1 and WAIK. THANKS.
    Sunday, May 18, 2014 2:59 PM
  • Thanks, DrChesse128.
    Tuesday, September 9, 2014 1:02 PM
  • :) Y'all welcome
    Thursday, September 11, 2014 8:35 AM
  • This worked for me. Thanks DrCheese128
    Thursday, October 23, 2014 6:26 PM
  • Thanks!!!
    Friday, May 29, 2015 9:51 AM
  • Worked perfectly on MDT 2012 server for win7 x64 deployment

    Thank you for such a great fix.

    +++++++++++++++

    Update :

    The following also worked for me: (Although for IE 11)

    On the MDT Server add the Component:

    amd64_Microsoft-Windows-IE_InternetExplorer_11.2.96001784

    Then uncheck the "Write Image Value" for DisableWelcomePage

    This also worked.

    • Edited by Paulo Ducato Tuesday, October 6, 2015 2:41 PM Update
    Thursday, August 20, 2015 10:58 AM
  • Kelvinf, I am trying to do the same thing.  My install.wim is unmodified from the 64-bit Windows 7 Enterprise with SP1 DVD, and I'm trying to use MDT Packages to install Internet Explorer 10.  I imported the .msu files for KB2670838, KB2639308, KB2533623, KB2731771, KB2729094, and KB2786081, as well as IE-Win7.CAB and the hyphenation and spelling packages.  After deployment Control Panel => Windows Update => View installed updates shows that the prerequisites were installed, but Internet Explorer is still version 8, not 10.  ZTIPatches.log indicates that all of my Packages are being added to the deployment, but it doesn't look like it's ever attempting to install IE10.

    One thing I did try is integrating the prequisites into the .wim file, leaving only IE10 itself to be installed by Packages, and that actually worked.  I also tried creating two Packages folders with corresponding Selection Profiles: one called IE10 Prerequisites and one called IE10 Application.  I opened my Task Sequence and changed the default Apply Patches task (at the end of the Preinstall state) to use the IE10 Prerequisites Selection Profile, then added a second Apply Patches task to the beginning of the Postinstall state that uses the IE10 Application Selection Profile.  With these changes and using the original install.wim (without the IE10 prerequisites integrated), after deployment it's still on IE8, however there's a notification to restart following the installation of KB2621440.  I'll try more next week.  Maybe I just need to add a Restart Computer task after the second Apply Patches.


    I'm in the same boat, I have a vanilla Win7 Pro SP1 install.wim that DID install IE11 via MDT Packages & a standard Task Sequence! I had what I believe an un-related issue: spell-check suddenly stopped working? In an effort to troubleshoot that I ripped out all MDT Packages & downloaded new & imported. Now IE11 failed to install twice on the same PC. Noticed in systeminfo/Installed-Windows-Updates it had all the prerequisites (kb2847882)!? I sensed a disturbance in the force & believed the package install order was the culprit, however I see no way to order the packages in MDT? I ended up manually editing the Packages.xml & PackageGroups.xml (DeploymentShare\Control) files to make sure these were at the end (in this order, you'll need to reference the GUID's):IE-Win7.CAB, KB2849697-x86.cab, & KB2849696-x86.cab. Lo & behold same PC that failed twice installed IE11 fine (spell-check still broken) on the 3rd try! So it does appear to be an ordering issue, I am a bit worried something as simple as clicking the column title (Name) in MDT Packages may re-sort it & cause it to break again. So at best this is a ghetto solution & doesn't appear to be the proper fix so I'd love it if Microsoft could update their article:
    https://technet.microsoft.com/en-us/library/dn338139.aspx

    I think the proper gunky solution is to put prereq's in MDT Packages, put IE.exe in Applications & app a Task Sequence Step to force install it as detailed here:
    http://deploymentresearch.com/Research/Post/327/Adding-Internet-Explorer-11-to-your-Windows-7-SP1-reference-image

    Wednesday, January 27, 2016 9:41 PM