Do not use Code: INCLUDERES Extract the language/MUI files seperate! - The language dependent MUM won't be applied. As it's a seperate package for DISM. Is kind of right from my investigations... Easiest way is to control all packages if they include other *.MUM files. If so, than you found a superior Package and you can delete the redundant child ones. I can confirm this.
Exxxcellent. Now Smithers, where's my tea? Small suggestion: since all the .mum files are in %ImageRoot%\Windows\Servicing\Packages, how about trimming off the path for display? That way, your window could be much thinner. Bonus huh? Why is this post being thanked?
SuperBubble / Mr. Jinjie, I was wondering if it might be possible to use DISM. As we all know, there is an option to remove a package from an image, for example: Code: DISM /Image:C:\MOUNT /Remove-Package /PackageName:WinPE-MDAC-Package~31bf3856ad364e35~amd64~~6.3.9600.16384 What if we could remove the package from the WIM file directly into a CAB file, for example: Code: DISM /Image:C:\MOUNT /Remove-Package /PackageName:WinPE-MDAC-Package~31bf3856ad364e35~amd64~~6.3.9600.16384 > D:\WinPE-MDAC.cab Is this somehow supported in DISM?
If by DISM, you mean SuperBubbles VBS script combined with the SXSexpander and cabarc, than yes "DISM" could do that. But if you meant the built in Microsoft tool, then no, I do not think that is an available option.
SuperBubble, Thanks for your helpful answers. I don't know if you've noticed, but the new Windows 8.1 Embedded (all versions of it) doesn't offer a catalog anymore. Previous versions (WES7, WES8) had a "catalog" folder inside the ISO, containing CAB packages. So now, in order to extract packages from the Install.WIM of Windows 8.1 Embedded, I have to use your tool. I haven't tested this, but as I understand, it's not trivial to get those packages and inject them into WinPE 5.0. DISM performs some sort of check to block us from doing so.
You're welcome. No, I hadn't noticed, but Windows Embedded was never my thing - always been a WinPE girl, and wrote my own PE builder - which I still use - which, while very manual compared to the Embedded build tools, does pretty much everything I want. My complaint about Embedded (at least the last time I played with it, which was probably around the time of WinFLP) was that it didn't seem to me that there was enough 'ground' between WinPE and full Windows to be worth it, unless deep (but reasonably easy) customisation was important, and memory was at a premium. Bonus edit: Or you need multimedia features - but you'd be surprised how much Windows PE can do with help. The peeps down at reboot.pro seem to have a cottage industry of building almost full-featured Windows based on WinPE. That has obviously changed, as I've heard of quite a few people building things based on Embedded in recent times... I might revisit it over Christmas. Precisely, that's what KNARZ was trying to work around.
Can you give screenshot or upload. Strange that have not seen your nick any of windows pe forums. You use another nick name in here?
To this point, I've been able to modify packages to create custom combinations, working through edition / flavor / sku targets. I definitely encountered the same signature checks as KNARZ has but there are some exceptions that allow flexibility. SuperBubble, I'd love to chat with you about it! Perhaps it has some applicability to your tools. I seem to be unable to PM until I get 5 posts in, but could you shoot me an email maybe? ian at internals.io . I've lurked with a few accounts for a while but find I'm rather poor at keeping up on forums nowadays.