CAB created or very small Hello i extract WinPE-SRT-Package. Have now 7,7 MB. Structure i see OK, or after DISM to ADK image DISM write after 30% - The source files could not be found. I use Bubles in Windows 7. After start in Windows 8 (i have admin permision and UAC disable) error 740
Hello, I tried to extract winpe-srt-package from an windows 8.1 with update image and it's not working. I get only a cab file with a size of 7kb. I tried to run the script as a system account but the same result. Anyboby can help? Thank you.
I am working on a issue for expanding the Manifest files. And I was wondering from where did you get the source file to apply delta for windows manifests. Basically I am concerned about the second parameter input in below API. BOOL WINAPI ApplyDeltaW( DELTA_FLAG_TYPE ApplyFlags, LPCWSTR lpSourceName, LPCWSTR lpDeltaName, LPCWSTR lpTargetName );
My problem is reading of Manifest files, which are compressed in Win 8.1. I was trying to expand these files using MSDelta APIs, but I am stuck with the source file input for ApplyDeltaW API. Any help is appreciated.
It's a resource in WCP.DLL. Because I wanted my tool to work on as many versions of Windows as possible, I copied said resource into my tool. Feel free to chop into it with Resource Hacker FX or similar.
Not working for Win10TP files, it said: I/O error - input file uses unknown SxS BDC method. The starting bytes of files I tried is "DCS[0x01]"
You mean the files in C:\Windows\WinSxS\Backup yeah, apparently they changed the compression method for these but those files are used only by sfc.exe utilty to fix corruption errors, so not a big deal a guess
No I mean places like x86_microsoft-windows-font-truetype-aldhabi_31bf3856ad364e35_6.4.9841.0_none_1f12bf451885bd3c or x86_microsoft-windows-ehome-font_31bf3856ad364e35_6.4.9841.0_none_5a00ee43571e7b2c, those are not expended during installation
"Microsoft decided to save disk space by compressing parts of WinSxS that aren't being used" Does this mean that these compressed files can be deleted without any issues since they are not being used? or Does this mean that Windows will automatically uncompress them when these files need to be used?
It's still registered and cataloged by the system and will cause problems when processing the files if they are missing. It's generally considered unsafe to manually delete or modify things in the WinSxS folder. You are better off running cleanmgr.exe and selecting the system files button. That will remove superseded updates, but leave the option to uninstall previous versions.
The number of compression methods appears to be multiplying - there's also a 'D1' compression method, as it turns out. Maybe I should update this tool... [wink]
I really would like to see some progress here. I still think this is still one of a kind "hack" for Windows since the Vista basement. Unfortunatly not enough people seem to understand what is possible with repacking cabs. - The last ingredient to get a real benefit from it would be if someone find's a good way to compromise sppsvc in some parts. - In in this case I'm still going with some rootkit/bootloader like konboot to glitch some protected registry values.
KNARZ! Despite appearances (I haven't posted on this topic since October), I am still poking it with a stick in my spare time, hoping something interesting will fall out, honest! Quite frankly, I can't figure what 'S1' compression actually is... though I have established a few things - most, unfortunately, in the category of 'what S1 isn't', which I will cut-and-paste now, in the hopes that inspiration/an epiphany will strike one (or more!) of you which you'll be willing to share. From my notes: On the bright side, 'D1' compression was easy, and I have an unreleased version of this tool that handles it (well, should - as with all my code, it isn't very well tested). If I don't have a flash of inspiration in the next few days and beat S1, I'll just tidy it up and release it: