Sometimes, the Parent-package is just a wrapper which is Uninstallable. Occasionally, there are Sub-packages that are NOT installable due to lack of some other Parent-package(s) or Feature(s).
this method seem to be work with 16299.15 build (server 1709), i tried with server insider build 17093.1000 with package and mainfest from windows 10 enterprise build 17093.1000 when installing Microsoft-Windows-Client-Features-WOW64-Package.mum it Error: 5 Access is denied.. Did anyone try with this build ????
then try eddo guide i didnt test it on that version did u copy the man* files and the mum cat to extracted esds ? without overwriten the files?
When I try to add packages with dism my package folder is "Read Only". So I can't write to it. Any suggestions? Tried permissions, WinPE, Safemode.
How did you extract the winsxs directory from the wim? I use 7zip for the purpose, this way the extracted files have full permissions and you haven't to mess with permissions and ownership like on a directory properly extracted using dism
cd %~d0%~p0 dism /image:\ /add-package:\Client:Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~en-US~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Client-Features-WOW64-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Client-Features-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~en-US~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~en-US~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Client-ShellLauncher-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Client-ShellLauncher-Package~31bf3856ad364e35~amd64~en-US~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Desktop-Shared-Drivers-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Desktop-Shared-Drivers-Package~31bf3856ad364e35~amd64~en-US~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Embedded-ShellLauncher-Package~31bf3856ad364e35~amd64~en-US~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Embedded-ShellLauncher-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Client-EmbeddedExp-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-Client-EmbeddedExp-Package~31bf3856ad364e35~amd64~en-US~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-ShellExperienceHost-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum dism /image:\ /add-package:\Client:Microsoft-Windows-ShellExperienceHost-Package~31bf3856ad364e35~amd64~en-US~10.0.16299.15.mum dism /image:\ /add-package:\Client:WindowsTH-KB2693643-x64.cab dism /image:\ /add-package:\Client:microsoft-windows-netfx3-ondemand-package.cab An error occurred trying to open - D:\Client: bla bla bla I took ownership of D:\Client and still no good
some of the packages are not included in the client dir or the client esd mb u extract the other esds to another dir ?
Buddy has got her all fixed with gui. Today he's adding NetFx35, IE, Server Manager, and latest updates.When hes done should be a nice usable os.
extracted other esd's into D:\enter folder. All folders, and mums are almost installed. Just a few more additions and shes ready.
Why can't I extract mum, cab files from esd? Data error with 7zip... Please provide detailed extraction method. Thank.