When trying to add package to Windows with dism this error appear any idea what can done to bypass it or what it means? thx
That would logically mean that you're trying to add package that does not support the archtecture of the image that you are using.
i think your problem is that you're trying to add package from non matching editions and i don't know if there is a trick that allows to do that from different windows editions. I myself am not aware of any so i can't help you with this unfortunately, hope someone will bring you additionnal information about this.
Server's WindowsServerBackupSnapin (BLB-UI-Package) is a good example for porting to Client. It needs Server RSAT feature. And RSAT depends on Server-Gui-Mgmt-Package And Server-Gui-Mgmt-Package depends on Server-Shell-Package And Server-Shell-Package depeds on ServerCore-Package Phew.... Same things happen to your case - Porting some complicated Client packages to Server Core. To the best of my knowledge, two ways people usually do to conquor it: 1. Play tricks - registry/mum/cat/sign/register etc. For example: Win32Calc. 2. Expand the Main-package and install the Sub-Package(s). For example: The Server Core doesn't eqip with IE and IE UI. But the following Sub-package of IE UI exists: InternetExplorer-Package-ua
I don't know why some people use it. I normally let Dism do its job. https://forums.mydigitallife.net/th...windows-10-final-possible-alternatives.61061/
I also alwayes wanted to do a deep dive into this issue, but as described it can become pretty complicated.
I just understand that it related to dependency / parent if its not, im still not seeing the big picture too
The Package was successfully installed ,Deceptive add registry, "mum/cat", Whether they can be deleted?
Play tricks - registry/mum/cat/sign/register etc. The Package was successfully installed, Whether they can be deleted?
What were to be removed? Those tricks? If the package was successfully installed, and the corresponding feature was in place when "dism /image:X:\MOUNT /get-features", e.g. WindowsServerBackup, then just leave them alone.