OK I've looked it over and it seems like they contain different binary files. I think they are some sort of delta patches, but the express versions only contain one small file, where the non-express contains many. View attachment 30541 *EDIT: THIS INFO IS INCORRECT. arseny92 explains in a few posts*
The 0 file actually is empty in the express version. No matter, no sense trying to figure this M$ idiocy out. Thanks for your input-much appreciated. It is the only "cab" M$ update downloads for this "secondary" install. The other three KB's are updated using single mum files etc. This will all iron out somewhere, somehow I'm sure.
Use expand.exe to extract cbs cabs. 7zip etc. do not know how to interpret directive files correctly, which are used in the CAB format to implement directory structure preservation during cab creation with makecab.exe or cabarc. The above extract-out is the result of an incorrect extraction: a proper one does not include numbered files and _manifest_.cix.xml but sxs component folders. Shall I remind of post 889939?
for proper WU bookkeeping since the WU update entry of all these updates is expressed as a single bundle update in history etc., it needs to re-evaluate the version chains of the affected components to avoid servicing confusions. Please read the articles )) p.s.: if one wants to try to understand a bit more of this BDC/PSF stuff, I recommend installing a wsus server, downloading some updates through it, and simply lookup in it's data folder and it's log file
Oh, okay. Yah I used 7zip. This is why I'm really glad you and abbodi1406 are around. One can only get so far on assumptions alone.
Hey arseny92 or abbodi1406, I was wondering why Windows Update likes to download cab files that are renamed to something like 10fc020ab727fda2737dfaaa7e I've opened up the files and they just seem to be cab files, so why the weird names?
No, I mean, the filename is only one big long hash or whatever. It doesn't have any file extension or prefix.
I think it's just a random generated name, not tied to the file or update or system WU like to play the hard way it's not just cab files, also text files and any file downloaded and not included in a CBS folder (sandbox), which also have the same naming scheme
In my C:\Windows\SoftwareDistribution\Download folder, I have a 39kb file named "c3248eb572cb5f82e63ce9c6d73cfbf39b1052ae" (among others). Checking the SHA-1 hash of that file, it's C3248EB572CB5F82E63CE9C6D73CFBF39B1052AE, so the file name is the same as the hash. Where are the files you're referring to located? If they're in that folder, check the hash to see if it matches the name.
Yah those were the exact files I was referring to, I was just wondering why they would possibly name them that only by their hash.