Aunty Mel's Cheap And Nasty SxS File Expander (Updated 2013/09/29)

For Vista maybe, for Win7 no
all RTM packages "6.1.7600.16385" has SP1 packages "6.1.7601.17514"
the SP1 packages include updated components (SP1) and unupdated components (RTM)
the RTM packages will be missing the replaced RTM components

 

possible to convert this tool to powershell ?

 

Anything is possible, who knows

but definitely not me

 

@Dark Dinosaur can you convert this tools to ps1 script ? ( vbs to ps1 )

or @xinso @George King

 

there are some other smarter people here, than me.
i want to enjoy some time. .. & do nothing

 

Does anyone know how to bypass the problem of long paths in powershell, because these solutions, subst + '\\?\' don't work very well, and I already have a more or less working script for SxSExpand.exe, only copied folders and files from the disk created by subst with long paths have the prefix '\\?\' added, so the location is e.g. \\?\C:\SxSv1\Output\amd64\10.0.22621.3593\Microsoft-Windows-EditionSpecific-Professional-Package-amd64-10.0.22621\amd64_microsoft-client-li..e-licensing-service_31bf3856ad364e35_10.0.22621.3527_none_6430a5e6e8953aec

 

Would anyone like to test the new version of the Aunty Mel's Cheap And Nasty SxS Package Extractor v2.0 script in PowerShell?
The script still has a lot of bugs, but it works and can be developed, unfortunately I don't have much time left to improve and develop it further...
Here's what the log from the package extraction looks like...

 

link. plz

 

You need to login to view this posts content.

 

Code:

[INFO ] A New Playground for Windows Package Extraction Enthusiasts ;)
[INFO ] Aunty Mel's Cheap And Nasty SxS Package Extractor v2.0, 2024/06/14
[INFO ] Copyright (C) 2012-2013 Melinda Bellemore. All rights reserved.
[INFO ]
[DEBUG] Settings after initialization:
[DEBUG] MakingCAB: False
[DEBUG] MakingESD: False
[DEBUG] DebugMode: True
[DEBUG] IncludeRes: True
[DEBUG] ViciousHacks: True
[DEBUG] LogToFile: True
[DEBUG] Checking for external tools
[DEBUG] SxSExpandAvailable: True
[DEBUG] CABArcAvailable: True
[DEBUG] WIMLibAvailable: True
[FATAL] Too many parameters.
Error during export.

LTSC 2024.

 

Try turning off debugging. There are still a few things to fix and debugging can probably cause more problems, especially when there are so many parameters passed to the script at once.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

@remek002
tested latest version under my main computer LTSC 2021
another option you can add, select location of pacakage's
could be great. so far so good
or add some local package folder, with another menu use local folder

- pretend to be dino who download package from uup dump,
and want to extract it ...

 

Ok, explain to me exactly what you mean?

I planned to expand the scripts, which is why I added the ability to include a filter so that packages can be easily filtered. I also want to divide the scripts into smaller parts to make them easier to modify and develop because there's already a lot of code in them, and it's easy to make mistakes.

I also had an idea to enable the mounting of WIM/ESD images, allowing these images to be modified, not just extracting packages, but also removing, adding, and generally modifying them. However, that's a distant future plan because I really don't have much time to continue developing and expanding the scripts, scripts have potential, and we could create a pretty good tool for modifying Windows images

 

Add extra folder called Local
So you can put your packages there
And use it online, local, mount, bla bla

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.