I apologise for my ignorance, but, what is the advantage of rebuild one edition that is already available?
One reason would be, learning to construct reconstruction builds, as close to official builds as possible, then use this info to build non official builds.
It has not always been available for ex u n e whether download or n finds but has a core or a professional, this you can rebuild for an burning that many do not have the burial and you have not found anywhere, just knowing how to rebuild and learning
Q: How to integrate the following 25398.950 components to 25398 CUs from 25398.1009 froward? Code: <update name="43CAAFED32D80EE5BFA6F58C97B4F8DE3F951119D35374BF42EEB6DD7384066B"> <component> <assemblyIdentity name="microsoft-windows-client-desktop-required-deployment0" version="10.0.25398.950" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </component> </update>
amd64_microsoft-windows-branding-shell-client_31bf3856ad364e35_10.0.20348.1_none_badedf0fd0592395.manifest - original, compressed amd64_microsoft-windows-c..equired-deployment0_31bf3856ad364e35_10.0.20348.1_none_0338861fbc795eeb.manifest - modified, not compressed amd64_microsoft-windows-iorate_31bf3856ad364e35_10.0.20348.1_none_b229311b9de6f047.manifest - original, compressed Specially archive with these files I have attached it, if there are any questions about this So, *.manifest should be compressed or decompressed before making *.cdf? I only decompressed, actually, it wasn't even me who decompressed it, it was already decompressed from uupdump.net amd64_microsoft-windows-c..equired-deployment0_31bf3856ad364e35_10.0.20348.1_none_0338861fbc795eeb.manifest for editing, I did not touch the other .manifest. Is there a program at all that can provide information about what hashes and what files are in a file in a specific *.cat? In the link above to iamaHUN post, the bottom poster has an example *.cdf Thanks, it outputs hashes, but does not show the names of the files the hashes belong to. I have not found this option yet. In Microsoft-Windows-Client-Desktop-Required-Package.ESD from the link above, downloaded from uupdump.net, part of *.manifest is already decompressed Including decompressed amd64_microsoft-windows-c..equired-deployment0_31bf3856ad364e35_10.0.20348.1_none_0338861fbc795eeb.manifest
with all your respects on a Winvos Winpe I'm looking for the little beast my OS is 1.9 GB with errors net 4.5 at the first start after it's good 24h2 still in test mode the shell!!
I don't get it, makecat uses the *.cdf format as a list [CatalogFiles] <hash>1=B:\enterprise\amd64_microsoft-windows-branding-shell-client_31bf3856ad364e35_10.0.20348.1_none_badedf0fd0592395.manifest makecat is designed to automatically determine the hash and write it to *.cat And you suggest manually entering the hash into *.cdf, and how should it look? Please provide an example of the format of such an entry in *.cdf Or do you want to say that the hash that is written according to the iamaHUN instructions is not suitable, and the hash entered manually will allow you to get rid of Error: 0x80092004? I saw many variants of writing *.cdf in the topic from respected gurus, but I have never encountered your variant, give an example of such a record In *.cdf there is only such parameter HashAlgorithms=SHA256 If you meant this parameter, then which one should you choose? It is not SHA256? Then which one? Respected gurus indicate something like SHA256, is this not so?
yes, manually entering the hash for example: [CatalogHeader] Name=update.cat PublicVersion=0x00000001 EncodingType=0x00010001 CatalogVersion=2 HashAlgorithms=SHA256 ResultDir=.\ CATATTR1=0x00010001:OSAttr:2:5.1,2:5.2,2:6.0,2:6.1,2:6.2,2:6.3,2:10.0 [CatalogFiles] e+q80mUA5Y0tHgkJT5X8P1SfsdO5cV+eE3c5yn+je2g=B:\enterprise\amd64_microsoft-windows-branding-shell-client_31bf3856ad364e35_10.0.20348.1_none_badedf0fd0592395.manifest