Upload dism logs. How can we say whats going on. Error 1168. Element not found. The DISM log file is located at C:\WINDOWS\Logs\DISM\dism.log Error: 2, Unable to access the image, Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder. I frequently get error 2 because of C:\programdata\microsoft\windows\startmenu\programs\powershell Folder permissions need to be taken to administators. Needs your dism.log to be checked but i am sure so many errors in there. I do not support adding client packages to server.
2024-08-16 19:14:45, Error CBS Failed to resolve package 'Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~~10.0.20348.1' [HRESULT = 0x80070490 - ERROR_NOT_FOUND] 2024-08-16 19:14:45, Error CBS Failed to resolve child of Package: Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.20348.1 [HRESULT = 0x80070490 - ERROR_NOT_FOUND] 2024-08-16 19:14:45, Error CBS Failed to process single phase execution. [HRESULT = 0x80070490 - ERROR_NOT_FOUND] Your these packages or child needed packages of them does not in source folder. You should edit professional.mum and remove unneeded packages
Code: TRY: Datacenter install.wim & Microsoft-Windows-EditionSpecific-Professional-Package.ESD Microsoft-Windows-EditionSpecific-Professional-WOW64-Package.ESD Microsoft-Windows-Client-Desktop-Required-Package.ESD Microsoft-Windows-Client-Desktop-Required-WOW64-Package.ESD Microsoft-Windows-Client-Features-Package.ESD Microsoft-Windows-Client-Features-WOW64-Package.ESD Microsoft-Windows-EditionPack-Professional-Package.ESD Microsoft-Windows-EditionPack-Professional-WOW64-Package.ESD Microsoft-Windows-RegulatedPackages-Package.ESD Microsoft-Windows-RegulatedPackages-WOW64-Package.ESD Microsoft-Windows-Not-Supported-On-LTSB-Package.ESD Microsoft-Windows-Not-Supported-On-LTSB-WOW64-Package.ESD Microsoft-Windows-Required-ShellExperiences-Desktop-Package.ESD Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package.ESD
There is all packages. All datacenter packages, and all client packages can healthy stay in wim Without conflict?
Datacenter is being converted to Professional, if you look in 1.xml, Datacenter is going to be removed. Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.20348.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.20348.1.mum" /> </package> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ServerDatacenterEdition" version="10.0.20348.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend>
I didn't mean for you to remove packages, you need to add the list of packages and install.wim to files\sources folder.
Strange things. How this work? If datacenter removed and professional installed it will be professional. No more server. How server files kept.