thank you very much!!!! i have all edition windows 8.1 pro/core (multi edition) i have Pro wmc x86 and x64 Ent x86 and x64 and i want make AIO how can i make it ??? cauze the most times i search i see make also export and make pro in ProWMC :/
UPDATE You are right: Well s**t I think I found the answer: Spoiler Deployment Image Servicing and Management tool Version: 6.3.9600.17031 Image Version: 6.3.9600.17031 Packages listing: --------------------------------------------------------------------------------------------------- | --------- | --------------- | ------------------ Package Identity | State | Release Type | Install Time --------------------------------------------------------------------------------------------------- | --------- | --------------- | ------------------ Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.3.9600.16384 | Installed | Language Pack | 11/21/2014 8:00 AM Microsoft-Windows-Embedded-EmbeddedLockdown-Package-TopLevel~31bf3856ad364e35~amd64~~7.3.9600.17116 | Installed | Update | 11/21/2014 4:23 PM Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384 | Installed | Foundation | 8/22/2013 2:46 PM Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2920189~31bf3856ad364e35~amd64~~6.3.1.1 | Installed | Security Update | 11/21/2014 4:23 PM Package_for_KB2931358~31bf3856ad364e35~amd64~~6.3.1.2 | Installed | Security Update | 11/21/2014 4:23 PM Package_for_KB2931366~31bf3856ad364e35~amd64~~6.3.1.4 | Installed | Security Update | 11/21/2014 4:23 PM Package_for_KB2932046~31bf3856ad364e35~amd64~~6.3.1.5 | Installed | Feature Pack | 11/21/2014 4:23 PM Package_for_KB2934018~31bf3856ad364e35~amd64~~6.3.1.5 | Installed | Feature Pack | 11/21/2014 4:23 PM Package_for_KB2937220~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2937592~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Feature Pack | 11/21/2014 4:23 PM Package_for_KB2938439~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Feature Pack | 11/21/2014 4:23 PM Package_for_KB2938772~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2939153~31bf3856ad364e35~amd64~~6.3.1.1 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2949621~31bf3856ad364e35~amd64~~6.3.2.0 | Installed | Hotfix | 11/21/2014 4:23 PM Package_for_KB2954879~31bf3856ad364e35~amd64~~6.3.2.0 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2958262~31bf3856ad364e35~amd64~~6.3.1.2 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2958263~31bf3856ad364e35~amd64~~6.3.1.2 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2961072~31bf3856ad364e35~amd64~~6.3.1.1 | Installed | Security Update | 11/21/2014 4:23 PM Package_for_KB2962140~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2965142~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2965500~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2966407~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2967917~31bf3856ad364e35~amd64~~6.3.1.2 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2968599~31bf3856ad364e35~amd64~~6.3.1.1 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2971203~31bf3856ad364e35~amd64~~6.3.1.1 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2973351~31bf3856ad364e35~amd64~~6.3.2.0 | Installed | Security Update | 11/21/2014 4:23 PM Package_for_KB2975061~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 11/21/2014 8:38 AM Package_for_KB2976627~31bf3856ad364e35~amd64~~6.3.1.6 | Installed | Security Update | 11/21/2014 4:23 PM Package_for_KB2976978~31bf3856ad364e35~amd64~~6.3.2.1 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2977629~31bf3856ad364e35~amd64~~6.3.1.4 | Installed | Security Update | 11/21/2014 4:23 PM Package_for_KB2978002~31bf3856ad364e35~amd64~~6.3.1.1 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2978742~31bf3856ad364e35~amd64~~6.3.1.0 | Staged | Security Update | Package_for_KB2981580~31bf3856ad364e35~amd64~~6.3.1.2 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB2987107~31bf3856ad364e35~amd64~~6.3.1.4 | Installed | Security Update | 11/21/2014 4:23 PM Package_for_KB2989647~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 11/21/2014 4:24 PM Package_for_KB2998527~31bf3856ad364e35~amd64~~6.3.1.1 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB3001237~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 11/21/2014 4:23 PM Package_for_KB3003057~31bf3856ad364e35~amd64~~6.3.1.6 | Installed | Security Update | 11/21/2014 4:23 PM Package_for_KB3012199~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 12/21/2014 1:56 PM Package_for_KB3014442~31bf3856ad364e35~amd64~~6.3.1.0 | Installed | Update | 11/21/2014 4:23 PM The operation completed successfully. It is something I am removing in the original wim when I customise it which when saved causes the Servicing Stack to remain in "pending" status. If I slipstream everything into the original untouched install.wim all is right as rain. So, I lost my original files from Nov. 25-the one that works OK-created a new customised "base" install wim thinking I have done nothing different from what I usually do. Obviously, I have deviated and need to pin down what I am removing/modifying SIM does not like. Thanks very much for your attention in this matter murph'-very much appreciated. UPDATE: Got it; I was deleting two reg entries and sxs files relating to the Themes 1 and 2 components that I wasn't before. Created a new custom base install wim-leaving those in, integrated everything on the planet and catalogue creation succeeded.
i have one question about (multi editions) example i have win 7 sp1 with 4 editions x86 is necessarily to do it in four versions ???? if make export one edition and intergrate the updates and after make aio in that exported edition the other Editions who merged them will not need updates??? sorry my english Thanks in advance
Hello murphy78 Sir. You remember you replied to my query at kickass torrents? Please explain here in detail about /resetbase. i have my own Win 8.1 Pro IR4 x86/x64 which i have integrated all updates till date. It has only one index (Pro). Can I do "/cleanup-image /startcomponentcleanup /resetbase" on it? Is "/resetbase" applicable as this has only one (main) index?
You can only do that on boot.wim, winre.wim and non-pending install.wim indexes for 8.1 with update, and for win7 you cannot do it at all. If you integrate offline rather than use sysprep/capture method, you will not be able to resetbase the image. resetbase does exactly what it sounds like. It resets the base files by removing superseded components and making the current ones permanent.
OK, I decided to leave IR4 releases as base and re-integrate updates on latest MSDN Enterprise with Nov2014 rollup (x86 and x64 both) ISOs as base. Can you please provide a list of updates to be integrated on both the architectures and strictly in the order of integrating them? Also Please mention which ones to integrate in boot.wim and winre.wim. Do provide all updates (important and optional) and leave ALL .netfx updates. I will not be integrating .netfx updates in the ISOs. PS: I will be integrating offline. Thanks.
No, that would be doing your job for you. I can teach you how to do it yourself, though. Load each image into a VM. Check Windows Update. Verify MSU/CAB updates in your updates folder to match what is being requested from Windows Update. Integrate them by putting them in a usb flash drive and running the integrate script: Code: @echo off pushd %~dp0 :: BatchGotAdmin :------------------------------------- REM --> Check for permissions >nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system" REM --> If error flag set, we do not have admin. if '%errorlevel%' NEQ '0' ( echo: echo Requesting Administrative Privileges... echo Press YES in UAC Prompt to Continue echo: goto UACPrompt ) else ( goto gotAdmin ) :UACPrompt echo Set UAC = CreateObject^("Shell.Application"^) > "%temp%\getadmin.vbs" echo UAC.ShellExecute "%~s0", "", "", "runas", 1 >> "%temp%\getadmin.vbs" "%temp%\getadmin.vbs" exit /B :gotAdmin if exist "%temp%\getadmin.vbs" ( del "%temp%\getadmin.vbs" ) pushd "%CD%" CD /D "%~dp0" :-------------------------------------- for /f "delims=" %%a in ('dir/b/s *.msu') do ( echo == Installing Updates == %%a start /wait wusa %%a /quiet /norestart ) echo. echo ######################################## echo. echo == Updates installed == echo. shutdown.exe /r /t 0 Reboot and repeat another time. (sometimes updates have pre-requisites) Download missing updates from MS Download Center. If you cannot find one there, try Microsoft Update Catalog (IE) Integrate using the instructions I list on Post 2 of this thread. Start small and just do a single-index. When you successfully integrate an iso with a single index, try adding more.
Thanks Sir. I know this process, I have been doing this since I started integrating. My main motive for the post was to learn about integration in boot.wim and winre.wim and then updating the setup files of the ISO of which I have absolutely no idea. I have been just integrating (add-package) to mounted install.wim and then max compress it and making ISO. I want to integrate fully in all parts of ISO including boot.wim and winre.wim. How to do this? How can I integrate in winre.wim? boot.wim is in sources directory along with install.wim but where's winre.wim? And also which updates are applicable to boot.wim and winre.wim? Sir, I have absolutely no idea about these two files, never touched them. I just want to learn one time each and every step. Take your time to reply Sir but please explain in detail what are they about and how and which updates to integrate in them. Thank you. PS: I just asked for the list of updates to be integrated because I guess you posted those in here [ h**p://forums.mydigitallife.net/threads/58451-Windows-8-1-Update-3-November-Rollup-2014-Released-in-MSDN-Very-Silently-)/page9?p=979424&viewfull=1#post979424 ]. Are these the ones I need to integrate to install.wim? Of these which are the ones to integrate in boot.wim and winre.wim. It would save me a lot of time. I just want to learn about boot.wim and winre.wim and how to determine which updates are applicable to them. And steps after doing add-package to both.
To get at the winre.wim, you gotta un-system/hidden it with attrib. Example: Code: attrib c:\mount\windows\system32\recovery\Winre.wim -s -h You copy the winre.wim to a working folder for later replacement. I try to use a single winre.wim for x64 and a single for x86 versions. If they don't match, they will balloon the size of your iso. After you have your winre.wim, unmount and discard changes to your mounted index. Mount the winre.wim and integrate/resetbase. Then unmount and commit. Re-export the winre.wim to a new winre.wim so that the old datastreams are removed. When you have the winre.wim how you like it, you go around replacing the existing one in each mounted index: Code: attrib c:\mount\windows\system32\recovery\Winre.wim -s -h del /q/f c:\mount\windows\system32\recovery\Winre.wim xcopy /cy c:\workingfolder\winre.wim c:\mount\windows\system32\recovery\ attrib c:\mount\windows\system32\recovery\Winre.wim +s +h You can do this replacement during integration or make a preliminary baseline version. That's what I typically do since it's a pain in the butt to export all the different indexes to an AIO. I did a December list of updates for the newer ISO files a page or two back.
Those are out of date. You can get updated DISM tools by downloading the latest ADK and just checking the tools box. You don't have to download all the WINPE language stuff.
Thanks for the detailed info Sir. What about boot.wim? Same procedure for it also? You also didn't told about which updates to integrate in both. Are all updates need to be integrated or some specific ones? Please tell for both files.
So basically if we are not sure can we just integrate all the available updates to three files (install.wim, winre.wim and boot.wim)?