I added the packages with /Add-Package to both install.wim and winre.wim and after I committed the changes this is what I get when running /Get-Packages. This is just the offline image, it's not installed yet through the regular Windows setup routine. Spoiler Code: C:\Program Files (x86)\PowerCmd>dism /image:D:\WinUA\Win811x64\Mount /Get-Packages Herramienta Administración y mantenimiento de imágenes de implementación Versión: 6.3.9600.16384 Versión de imagen: 6.3.9600.17031 Lista de paquetes: Identidad del paquete : Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~es-ES~6.3.9600.16384 Estado : Instalado -> Translation: Installed Tipo de lanzamiento : Language Pack Hora de instalación : 22/08/2013 11:34 p. m. Identidad del paquete : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384 Estado : Instalado -> Translation: Installed Tipo de lanzamiento : Foundation Hora de instalación : 22/08/2013 02:46 p. m. Identidad del paquete : Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14 Estado : Instalación pendiente -> Translation: Installation pending Tipo de lanzamiento : Update Hora de instalación : 03/04/2014 06:19 a. m. Identidad del paquete : Package_for_KB2919442~31bf3856ad364e35~amd64~~6.3.1.8 Estado : Instalado -> Translation: Installed Tipo de lanzamiento : Update Hora de instalación : 03/04/2014 06:07 a. m. Identidad del paquete : Package_for_KB2932046~31bf3856ad364e35~amd64~~6.3.1.5 Estado : Instalación pendiente -> Translation: Installation pending Tipo de lanzamiento : Feature Pack Hora de instalación : 03/04/2014 06:24 a. m. Identidad del paquete : Package_for_KB2937592~31bf3856ad364e35~amd64~~6.3.1.0 Estado : Instalación pendiente -> Translation: Installation pending Tipo de lanzamiento : Feature Pack Hora de instalación : 03/04/2014 06:27 a. m. Identidad del paquete : Package_for_KB2938439~31bf3856ad364e35~amd64~~6.3.1.0 Estado : Instalación pendiente -> Translation: Installation pending Tipo de lanzamiento : Feature Pack Hora de instalación : 03/04/2014 06:29 a. m. Identidad del paquete : Package_for_KB2949621~31bf3856ad364e35~amd64~~6.3.2.0 Estado : Instalación pendiente -> Translation: Installation pending Tipo de lanzamiento : Hotfix Hora de instalación : 03/04/2014 06:30 a. m. Are those "installation pending" status normal? I mean, will they get installed when doing the Windows installation? Someone posted that he added /Prevent-Pending t the packages when adding them but I'm not sure if I need to do that as well. I'm used to installing updates with WSIM and pkgmgr but this is the first time I'm adding packages with DISM. Any advice on this is greatly appreciated. Thanks!
WINPE images are always pending. They made a shortcut for the WINPE that allows the Spring 2014 update to resetbase though. It only works on winpe images like winre.wim or boot.wim.
Very normal you can run /resetbase command on winre.wim image, and you will notice that all packages will be status: Installed for install.wim, yes they will get installed when doing the Windows installation
Thanks for clarifying that to me. Another thing I'm not sure about is the need to recapture install.wim and winre.wim on the computer I installed them. Is there any benefit other than smaller images size?
No, you don't have to do apply -> go into audit mode -> resetbase -> sysprep -> recapture sequence if you don't mind the image size. The whole point of the ADK note is to complete pending actions and to clean up the superseded components to reduce the size of the final image before you finish building custom images.
That's what I thought. At the moment, I will leave at that until I the Spanish ISOs with Update 1 are released. Then I would implement my customizations and do it the right way, including resetbase, cleanup, etc.
@murphy78. I know you posted this somewhere, but, cannot find it; could you please tell me which boot.wim the Microsoft DaRT 8.1 Tools Pack gets copied to. I will save your instructions this time. Thanks
@murphy78 Could you please explain what MS is doing: 10 days ago "final" Win81U1.iso has been released to Tehnet for download, but two days ago MS released another 6 updates for that "final" version and today they announced that there is something wrong and stopped downloading, pending urgent release of the patch for that problem. When there will be possibility to download clean final Win81U1.iso? Thank you for attention.
Every time ms has a hiccup, all the tech sites and social media make a huge deal out of things. There's a SSL bug with server 2003/2008 that has a security flaw in this patch. They'll probably either v2 something or just release an additional patch to fix said bug. On the patches available, you have to realize that this is just an updated version of Windows 8.1, it's not Windows 8.2 They purposefully do not add defender updates, malicious software scan registry flags, flash players, and camera codecs. So on top of that, yes, there's a security fix that wasn't included that is part of the 2919355 pack that I wish was included, but wasn't. I'm personally going around sysprepping things so I have good baseline versions of things with all the hotfixes included and resetbase'd. They ALSO did a F***TON of office patches this month. I have no idea what those are about but even the Visio x64 update alone is like 500 megs... I have no idea if that's a messup or a feature addition thing... It's weird because they JUST did sp1 for office 2013 and then released these huge patches.
Started running into my old friend the setup failure on x64 esd versions. This only happens with my pre-activated versions, so I'm assuming there's some sort of memory cache problem where it's not correctly keeping track of existing files when exporting to esd. I've changed my 20 iteration for /l loop to export to a temporary new wim file and then export that temporary wim file to the final esd. In between I delete the temporary wim file so that it's impossible for the cache memory to mistake the data stream contents. Here's an example: Code: for /l %%x in (1, 1, 20) do ( dism /export-image /sourceimagefile:c:\temp\x64\install.wim /sourceindex:%%x /destinationimagefile:c:\temp\x64\install2.wim /compress:max /checkintegrity dism /export-image /sourceimagefile:c:\temp\x64\install2.wim /sourceindex:1 /destinationimagefile:c:\win81x64\sources\install.esd /compress:recovery /checkintegrity del c:\temp\x64\install2.wim ) Edit: Nope, that didn't work either... Hmm I got an idea. You know how servers are sometimes underclocked to add stability? I'll try something similar... It's literally the only thing left that I can think of... edit2: nope... failing again... It's rare but it happens. It doesn't seem to happen on completely different indexes, but when combined with same-flag indexes (a la pre-activated index) it fails... I'll have to resort to using .wim files and baseline versions like I do with my win7 versions. I was hoping not to, but I guess the only other alternative would be to not have any pre-activated indexes at all.
Hey people can throw in an oem folder or activate using MTK after install. I would prefer an unactivated index and an esd version to keep the size down. Are you making a new superaio v4? I am looking forward to your releases.
I am waiting for the rest of the server 2012 r2 versions to see if they will get an update. Last time they took a bit before they released the other ones. Yes I'll definitely do a SuperAIO v4 for it when I get them though...
