[VBScript] Aunty Mel's Cheap And Nasty SxS Package Extractor (Updated 2013/09/30)

Code:

@echo off
cd /d %~dp0
set src=C:\Windows\servicing\Packages
cscript /nologo SxSExtract.vbs /U /IMAGE:%src% %src%\Packagename.mum ExtractPackage >log.txt 2>&1

Code:

' Help text.
Sub DisplayHelp
   Call LogBare("CSCRIPT.EXE SXSEXTRACT.VBS [/?,/H,/HELP] [/DEBUG,/V] </ONLINE|/IMAGE:<folder>>")
   Call LogBare("  [/INCLUDERES] [/VICIOUSHACKS] [/UPDATEPACK,/U] <source>.mum [<target>[.cab]]")
   Call LogBare("")
   Call LogBare("Parses a Windows Side-by-Side package manifest file, chases up all the")
   Call LogBare("references, and copies all the files associated with the package.")
   Call LogBare("")
   Call LogBare("  /?,/H,/HELP      Display this help text.")
   Call LogBare("  /DEBUG,/V        Enable verbose debug output.")
   Call LogBare("  /ONLINE          Uses %SYSTEMROOT% (usually C:\Windows) as the root folder to")
   Call LogBare("                   search for associated files.")
   Call LogBare("  /IMAGE:<folder>  Uses <folder> as the root folder to search for associated")
   Call LogBare("                   files instead.")
   Call LogBare("  /INCLUDERES      Extract MUI resources as well, for packages that don't have")
   Call LogBare("                   associated language packs.")
   Call LogBare("  /VICIOUSHACKS    Activates a couple of hacks to the script, for extracting")
   Call LogBare("                   'difficult' packages that don't reference assemblies by")
   Call LogBare("                   exact name.")
   Call LogBare("  /UPDATEPACK,/U   Extract package from another package, where all files are")
   Call LogBare("                   within the same <folder>, as in updates or langpacks.")
   Call LogBare("  <source>.mum     Specifies a package manifest file. Wildcards are not")
   Call LogBare("                   permitted.")
   Call LogBare("  <target>[.cab]   Specifies the target folder for extracted files. If the")
   Call LogBare("                   extension '.cab' is specified, the script will call")
   Call LogBare("                   CABARC.EXE to create a cabinet of the extracted files.")
   Call LogBare("")
   Call LogBare("This script requires both SXSEXPAND.EXE and CABARC.EXE, either in the")
   Call LogBare("current folder or on the system PATH, for full functionality.")
End Sub

Thanks a LOT LOT

 

@abbodi1406
dude, i'm in aur of you sir!
i'm sure that lady super bubble would not mind you inhanseing her work.
thank you so much for updateing and keeping this alive.
i'm very greatful.
I hope that updates will continue in some form?
stay safe!
sorry for any errors, I am using a screen reader due to my blindness.

 

she doesnt mind
how do i know ?
i aksed her

 

for me SxSExport.cmd not works in ltsc 2021 21h2 : /

 

could someone kindly repost a link of ssx v1?
I would be very greatful
Majid

 

@Tito
thank you so much sir!
your a saint.

thank you again.
i'll keep this safe.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

resolved antivirus error ^^ thank @abbodi1406

 

Never knew this existed, will play around with it, thanks a bunch!

 

I forgot to upload

Spoiler: 2023-09-11

- Add support for NT 6.0 packages ("dependentAssembly" node is little different in Vista manifest)

 

You need to login to view this posts content.

 

I couldn't remember who the original author was

 

@abbodi1406 Hello, and thank you in advance for your time. As a Windows internals connoisseur, could you please share your insight on whether this script would actually work to extract the MultiPoint feature installation package from Windows Server 2016 and make it installable on Windows Server 2019? Or is this task inherently impossible, or does it require additional steps or complexity beyond what the script can handle?"

 

@speedxl
i'm that expert

yes, the script can extract almost all packages correctly
weither it would work on another version OS is not guaranteed

 

Search on server essental same as multipoints and package are from server 2016 but work in 2019 / 2022 / 2025

Because essential gui apps are a net framework apps only