you don't have to recapture the sys inside the VM. i always mount the VM HDD to a drive letter on the host machine and then recapture the sys to a folder with an extracted windows ISO directly on the host. -andy-
Thank you very much for this nice explanation. Mount the vm hdd, very smart, dont thought on this before. Last question, when i make the dism cleanup, before i shutdown via syspre dialog or when exactly?
After integrating updates from WHDownloader, to satisfy Windows Update it was needed to integrate KB2965500, KB2968599 and KB2978668. I wonder why WU still asking for updates that are supersseded or old...every month I find myself with the same situation... Thank you abbodi1406 for your hard work to updating the lists every month.
You might as well do it before sysprep. Sysprep clears all the user generated data, but it doesn't run servicing stuff like dism cleanup. You could do it after capture, offline, but you'd have to make sure there were no pending updates/feature-changes.
Thank you very much! What means pending exactly? How to prevent that anything goes pending? BTW: Sorry for my much questions and my poor English. I have to learn. (both )
"Pending" in this case means the slipstreamed updates are not installed yet and won't be until OS is installed. All this was answered previous page. You do not understand then?, in which case, time to go to M$ technet and start reading until you do understand. There is NO way to prevent pending in install wims without going through sysprep and audit mode or completing a fresh install-NONE. To completely remove any pending operations before capture one must reboot in "Generalize" while in Audit mode, hitting Ctrl+shift+F3 when completed to reenter Audit Mode and, then, "Generalize" "Shutdown".
I understand the word, but no the context. Why some updates are on "pending". How i can prevent/change to "installed", the sense of slipstreaming is to have no pendings. That is what i mean, its confusing me... Okay so i just need sysprep in audit mode and i have finished? But nevermind, im just happy to have solution for dism-cleanup. Greez
You can't, neither anyone prevent that pending status unless sysprep blah blah blah. M$ does things this way, why? I don't know you should go deeper in TechNet and ask those experts directly.
I may understand the need for KB2978668 since it share the same component version with august rollup but KB2965500 and KB2968599 are deeeply fully directly superseded, MS !
So the debt lye on Microsoft, okay. (seriously) I know many such strange things, they can be better. Then all my things are finished, really thanks at all members for help! Okay then lets the show begin, I start my new project. Greez Just another lol, sorry: At the install begin i can choose language stuff. The settings for this gonna be also removed by sysprep??
I have to disagree with this, since components may have actions that are actually run at sysprep, if found defined like below in the packages integrated
You can specify this in your unattend.xml in the sysprep folder to have all that immediately when booting to Audit Mode in Sysprep. By entering copy profile into that xml file I think these settings will be retained-cannot remember for sure. You must remove this unattend.xml if you run an Autounattend.xml; more info available in the ADK help files. You may ensure these personal settings by specifying such in the Autounattend.xml file which I place at the root of the Windows install medium-again keeping the copy profile entry here also to make this your Default profile. There is no difference in the structure of Autounattend and Unattend other than placement of the file and file name. Some entries are not executed in Sysprep vs Live Install. If you mount the wim using WSIM and create an answer file there, expand the right hand wim column and go through the entries, right click to discover what is allowed in Sysprep>Generalize before going into Audit Mode. Create the answer file, rename it to Unattend.xml from Autounattend.xml and place it in the Sysprepfolder of your mounted image. This is assuming the OS already has your language file in the wim.
LOL, no kidding-even after reading the servicing methods on the website specified earlier in this thread, I still have trouble wrapping my head around M$'s way of doing things in this regard.
It wouldn't even be the 100th time I was openly wrong To clarify, it doesn't do what he was attempting to do. I'm going to just stop putting my foot in my mouth now, when there are people who actually know what's going on.
The pending updates thing is just one big peeve of offline integration. You either need to sysprep/capture a vm install, or just learn to deal with the extra bloated backup files. Well, technically, they're not even backup files until the pending updates get processed. As far as the language, those are decided by lang.ini files and the associated language packs installed on the boot.wim and install.wim. If you want my advice, don't add any different language packs in an attempt to change language. It will extremely bloat the OS and make installs take up to a minute longer per language. Plus it will really increase the size of your footprint. I'm finding my articulation abilities failing me today. Let me just say that I've tested this extremely extensively when Win8 came out and it's not worth it to add more languages unless you are sure you are going to use both. I definitely wouldn't advise making some sort of 5 or 9 language iso.