Yeay.... I wasted 2 Days on Data.wim file I created as OEMFolderPath is not supported with Windows 8/8.1. The root contains a "\Windows" Folder and while capturing the ACL also gets saved. This results in a big problem while applying Data.wim to the Image to the System/Image/SystemDrive. - C: becomes not accessable and so on. Now I created it the Data.wim from FAT32 Partition with not problems while applying. Do you also know such problems? I'm using Imagex with /flags /check /compression flags.# How can I prevent this? Except using FAT32 (no ACL support).? I also noticed / found hidden commands/flags in Imagex/Dism: "NOACL" "NOTADMIN" (like the undocumented [ /flags "Edition" ] ) and "MDPAD" <--??? "NoACL" seems to be the command what I'm locking for but unfortunatly I didn't find a way to work with it. "NotAdmin" is applicable with /capture but I'm not sure what it does. "MDPAD" no idea. "flags" parameter seems to be only implemented in Imagex. And there is a hidden DISM command I found: 'get-stagededitions' (works only with core/pro/wmc images as they contain the skus)
I'm not really sure if this is applicable here, but when i was experimenting with upgrades i noticed if the first index of the boot.wim didn't have a "/flag 9" the upgrade would fail. I set most of my boot.wims with the flag 9 just for the heck of it, and maximum compatibility, but have no real idea what it does. I just happened to notice the "one of these wims isn't quite like the other" using wim info.
WIM is kind of special at all. Look at ESD and there are other Flags (not <Flags></Flags>) like <Core> and so on... Seems all proprietary and undocumented. years ago microsoft did a much better job in quality in my opinion. (e.g. bcdedit.exe: they show in help the same flag twice with different description, shutdown.exe the -g parameter is 'missing' therefore we have -r twice (in de-de at least)- copy pasted without changing... microsoft: quality is different.