You've created a new image, captured it and attempted deployment and received the 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."
Alternatively, you've just made a new MDT Task Sequence and slipstreamed updates into it and received the same error.
Symptoms
- Infinitely looping on first boot
- Windows has encountered a problem, press ok to restart.
- C:\Windows\Panther\Unattend.xml Error (described above)
The cause of this is simple, it's internet explorer 10.0 which you have installed either within the image or slipstreamed into the image.
Fix [SOLVED]
Actually simple, but only if you know where to look and since you've probably scrolled down and ignored everything I said above, I'll get to the point, follow these instructions:
- In your MDT Deployment Workbench, go to your list of task sequences.
- Right click the task sequence you are using to deploy out your new image with IE 10.
- Go to the properties of this task sequence.
- Choose the OSInfo tab and click "Edit Unattend.xml"
- Wait about a year for it to load up the catalogue.... (depending on your machine speed, this can take quite a while, this opens the Windows System Image Manager (WSIM)
- Go to Unattend -> Components -> Specialize
- Choose the Microsoft-Windows-IE-InternetExplorer-Neutral from the list
- Find IE-WelcomeMessage
- The Status should say false, if it doesn't make sure it does.
- Right click this value and in the context menu (the right click menu) UNTICK "write image value" (See Image for a visual aid)
EDIT [17-11-2013 - MDT 2013]
Having spoken with some of my colleagues I have ascertained that by using MDT 2013 they have not encountered this issue, however if you need to maintain support to deploy Windows XP images then you will not be able to upgrade.
Thanks for the post. I've been trying to work out what was going on. I'm going to try this out. Then I'll let you know the results. I've been trying to update our image with Office 2013 and IE 10 along with all the updated available to August, but kept on getting as described above.
ReplyDeleteYeah it worked a treat! Fantastic stuff.
ReplyDeleteThanks for the feedback, glad to know it worked.
DeleteYet another reason I hate Microsoft. They made IE 10 part of Windows Updates but did not test it enough, and did not have any information on this error. Good work MS.
ReplyDeleteFantastic! Works a treat thank you so much, it's been driving us insane!!
ReplyDeleteGotta love step by step solutions.
Thanks for the fix, why could they not go with a silent fail rather than crash Windows install. This was also happening to me on the capture task as well.
ReplyDeleteThank you! This was getting me really insane. I've lost count on the number of times i have rebuilt my ref-image. Had no thought that IE10 could be the problem. Thanks again for the blogpost! :)
ReplyDeleteThank you VERY MUCH.
ReplyDeleteThis is a huge bug and might I add time wasting issue. Trying the solution now, if it works this should be front page news.
ReplyDeleteThese settings worked for us, thank you so much for sharing!
ReplyDeleteI had to delete that entire line from the XML file on the Deployment Server in the Task Sequence for the image being deployed.
ReplyDeleteDaniel can you tell me where exactly or how you deleted the line. My xml file already reads false. I'm kind of new at this so I'm not sure where to delete the line you are refering to.
DeleteGetting the same error. I am unable to open the unattend.xml via MDT but if I manually edit the XML the welcome message is already set to false:
ReplyDeletehttp://myjmm
false
Any ideas?
Removing the entire section fixed my issue:
ReplyDeletehttp://removedforposting
false
But, is there another way to set the homepage to what we want by default for all users (not GPO becuase I want the users to be able to change itf they want)
I know you can add a post step but not sure how to go about it.
Worked great, thanks! After reviewing logs and xml files over and over I didn't find anything that would even remotely think to change that settings. Great post.
ReplyDeleteThanks very much! I had used this old guide to start using WDS, and quickly realized that I should roll updates into my reference image. I ran into this exact problem, something that the MSFT Accelerator team should solve themselves! Thanks!
ReplyDeleteDidn't work for me get an error when trying to the Edit Unattend.xml "unable to generate a catalog for an x86 operating system image while running on an x64 operating system. Retry the operation from an x86 operating system"
ReplyDeleteThat is correct Brad, in order to create a catalog for an x86 wim you will need to add the adk to an x86 Windows 7 machine.
DeleteCopy your new wim file to this machine and you can then open it in the wsim tools and generate the catalog from here.
Once you have an updated catalog you can place this in your deploymentshare in the same folder as your wim file and you will be able to edit the unattend.xml from the osinfo tab.
Marc, any chance we can see a post on this in the near future. It is an absolute pain since all modern server operating systems are x64 only. There are still some occasions where I need to push out x86 (processor limitations etc) and ideally want them to have IE10 or higher.
DeleteI will look into writing a quick post on this in the next couple of days (work permitting) My advice would be to build a W7x86 VM and use this to generate the catalogs.
DeleteIf you are licensed for Server 2012 Standard or higher then you will have licensing to run at least 4 machines on the license, this could include your host machine and then running Hyper-V with a W7 x86 machine within it.
Alternatively you could take a snapshot of your machine just prior to running sysprep, take your capture image and then once you have a wim you could revert to your pre-sysprep snapshot and install the adk onto that machine then generate the catalog here.
As promised here is a brief document outlining how to create your own x86 .clg file.
Deletehttp://primaryschooltech.blogspot.co.uk/2013/11/creating-catalog-from-custom-x86-wim.html
Marc,
ReplyDeleteMy MDT server is on a VM x64 system, so I won't be able to do that. I'll just have to recreate the Windows 7 image and remove the IE10 update before I do the Capture part.
Thanks for your help!
Brad please see my reply above, in essence I would recommend you create a W7x86 vm and put the adk into that, then you can generate your catalog from here, no need to remove IE10
DeleteAny information on IE11 into an image? Will I need to do this fix for that as well? We are building a new image next week at our high school and unsure whether or not to brave IE11 for Windows 7. Thanks.
ReplyDeleteWe have not tried IE11 just yet, I imagine the IT Magician will have a post in the very near future if there are any issues as he has a little more time to play with these things.
DeleteIE11 doesn't work with the unattend.xml As far as I have tested. But I couldn't figure out which setting makes is corrupt.
DeleteThanks man, it worked great. This issue was about to drive me NUTS! Now I can enjoy my christmas vacation in peace... :)
ReplyDeleteJanne L, Sweden
Hi IT m8s!
ReplyDeleteI just wanna say that in MDT2013 it still can be som trouble with this error message..
A tip for u all, when you open the WIM file and choose to edit the unattended.xml file just run "Validate Answer File" under Tools to see what error you got! ;-) and then change and save. Best regards Mattias O, Sweden
Thanks!!! After trying different solutions and spending time figuring out, your solution worked!!
ReplyDeleteRBA, US
Thank you. This worked great for me. And thanks for letting us know that it takes a long time for the catalog file to build otherwise I would have thought it was hung up (took about 45 minutes).
ReplyDeleteThanks for this!
ReplyDeleteAlso an issue with IE11 in my case. But this fixed it
This is not the solution anymore, the problem is back, now this time we cannot unwrite the value, since its not even written
ReplyDeleteThis still works for me with IE11 and Win7. Have to untick that value on every image I capture, but it works without fail.
ReplyDelete