SXSEXP: Usage SXSEXP < Source File > < Destination File > SXSEXP < Source Directory > < Destination Directory > SXSEXP /d < Source File > < Source Delta File > < Destination File > Code: @echo off pushd "%~dp0" sxsexp\sxsexp64.exe SXS_Original SXS_Expand pause simple let's do it with CMD commands: Code: C:\>mkdir works-SxS C:\>copy sxsexp64.exe works-sxs C:\>mkdir works-sxs\sxs_original C:\>mkdir works-sxs\sxs_output C:\>copy sxs .manifest files to sxs_original C:\>start sxsexp64.exe sxs_original sxs_output
This is Capabilities of 26100.1.240331-1435.ge_release_CLIENT_ENTERPRISES_OEM_A64FRE_en-us.iso. Code: App.StepsRecorder~~~~0.0.1.0 | Installed Browser.InternetExplorer~~~~0.0.11.0 | Installed DirectX.Configuration.Database~~~~0.0.1.0 | Installed Hello.Face.20134~~~~0.0.1.0 | Installed Language.Basic~~~en-US~0.0.1.0 | Installed Language.Handwriting~~~en-US~0.0.1.0 | Installed Language.OCR~~~en-US~0.0.1.0 | Installed Language.Speech~~~en-US~0.0.1.0 | Installed Language.TextToSpeech~~~en-US~0.0.1.0 | Installed MathRecognizer~~~~0.0.1.0 | Installed Media.WindowsMediaPlayer~~~~0.0.12.0 | Installed Microsoft.Wallpapers.Extended~~~~0.0.1.0 | Installed Microsoft.Windows.MSPaint~~~~0.0.1.0 | Installed Microsoft.Windows.Notepad~~~~0.0.1.0 | Installed Microsoft.Windows.PowerShell.ISE~~~~0.0.1.0 | Installed Microsoft.Windows.Sense.Client~~~~ | Installed Microsoft.Windows.SnippingTool~~~~0.0.1.0 | Installed OneCoreUAP.OneSync~~~~0.0.1.0 | Installed OpenSSH.Client~~~~0.0.1.0 | Installed Print.Management.Console~~~~0.0.1.0 | Installed VBSCRIPT~~~~ | Installed WMIC~~~~ | Installed Q: What if System Language Pack and all Language Feature Packs were removed?
What tools can unpack *.cat files? In particular, I am interested in Microsoft-Windows-Security-SPP-Component-SKU-ServerAzureStackHCICor-License-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat It is necessary to know the list of files in order to create a new *.cat with the edited one using makecat.exe DefaultPpd-ServerAzureStackHCICor-ppdlic.xrm-ms, whose hash has changed and needs to be written into the new *.cat Or maybe someone knows if there is another way to get the list of files needed to create a new one in makecat.exe Microsoft-Windows-Security-SPP-Component-SKU-ServerAzureStackHCICor-License-Package~31bf3856ad364e35~amd64~~10.0.26100.1.cat. Thank you.
Not manifest file, dude... but the mui files Code: autopilotdiag.dll.mui bcdboot.exe.mui mofcomp.exe.mui mofd.dll.mui ncprov.dll.mui tpmcoreprovisioning.dll.mui winmgmtr.dll.mui winspool.drv.mui wmiapres.dll.mui wmiapsrv.exe.mui wmiutils.dll.mui We need file in the "n" folder to expand file from the "f" folder. But I didn't found the file in system32\en-US. That's why the error keep telling "unvouched error". The simple way to passing the error, we can remove the component from the MUM file. Untouched mum: Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1369.mum Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v3"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package" version="10.0.25398.1369" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> <package identifier="Microsoft-Windows-Client-Desktop-Required-Package" releaseType="Language Pack"> <parent disposition="detect" integrate="delegate"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package" version="10.0.25398.1369" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </parent> <update name="EC4935EFA744575125C94E8D930B754E01C472623A45B8FEFAC51FD75C272858"> <component> <assemblyIdentity name="microsoft-windows-client-desktop-required-deployment0" version="10.0.25398.1189" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </component> </update> <update name="2DCF4F276F568D8827EE9D1C292BDE209B8DE8CF9C8B95F793C16362D15A8BC7"> <package integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package00" version="10.0.25398.469" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="8103ba68184ad282234e95fdbdfb10e4"> <package integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package01" version="10.0.25398.1369" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> </package> </assembly> After remove (modding): Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v3"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package" version="10.0.25398.1369" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> <package identifier="Microsoft-Windows-Client-Desktop-Required-Package" releaseType="Language Pack"> <parent disposition="detect" integrate="delegate"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package" version="10.0.25398.1369" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </parent> <update name="2DCF4F276F568D8827EE9D1C292BDE209B8DE8CF9C8B95F793C16362D15A8BC7"> <package integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package00" version="10.0.25398.469" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="8103ba68184ad282234e95fdbdfb10e4"> <package integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package01" version="10.0.25398.1369" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> </package> </assembly> I think this method is easier than having to change the update package name in the mum file. But that is not what we want. because the mui files will not get update.
About server to client convertion i am investigated 20348.1_ServerDatacenter_to_Professional_amd64_en-US.7z. I could not get it to work. Because 1.xml desire windows-client-desktop-required package to install professional mum but there is no such package because there is no client edition. But people can get it to work as pp03 do. Why did i do because i converted 20279.1 language package to 20348.1 package perfectly and it did not work. I am investigated why it does not work all day. It complaints about client desktop package and mostly deployment packages. But it can be intagrated again by 20348.1_ServerDatacenter_to_Professional_amd64_en-US.7z When i looked 20279.1 language package i saw also it was edited. I was thinking language packs are original from microsoft beta leaks. Everything was edited that there is a client probably built without a client package, also maybe missing lots of another packages. I was thinking my new language pack mod fail because of my faults but now thinking it is because someone mod everything. The biggest mystery is how dism allow to install professional edition mum without client desktop required package for me. At sources folder there are all edition and edition specific esds. Maybe i can combine professional mum with datacenter mum to be accepted to use professional esds but how will it be different just adding licensing package on datacenter and show it professional edition I have give up (also not interested any 20348 and 25398 clients) and understood i was right on that but bored and spend a few good times. In such builds everthing is modded for daily uses. I learned a just few good things.
About client 20348, I have also given up. I once had the files and they were lost with a damaged hard disk. But I still remember how to convert it, it's not much different from 25398. But I can't update it..!! And about client 25398, I did it when I really didn't have anything else to do.
Feature update to Microsoft server operating system, version 21H2 (20348.1) amd64 Microsoft-Windows-Client-Desktop-Required-Package.ESD Code: uupdump.net/findfiles.php?id=2ba1d737-a36b-415b-a630-85bd5146d77d&q=esd