Remove all files that you don't need and then remove the corresponding lines from the hashdeep file wsusoffline/client/md/hashes-w100-x64-glb.txt.
Note, that the hashdeep files are CSV-formatted text files. The last column is the relative path to the file; so you'll be able to figure that out.
If you need to recreate the file: lines 3 and 4 of the hashdeep file indicate the directory, from which hashdeep was executed, and the command line, which was executed; for example:
- Code: Select all
## Invoked from: I:\wsusoffline\client\md
## I:\wsusoffline\client\md> ..\bin\hashdeep.exe -c md5,sha1,sha256 -l -r ..\w100-x64\glb
Then just repeat it: In this example, change to the directory
- Code: Select all
I:\wsusoffline\client\md
and the repeat the command
- Code: Select all
..\bin\hashdeep.exe -c md5,sha1,sha256 -l -r ..\w100-x64\glb
Or you could just uncheck the option "Verify installation packages" in the Update Installer, and skip the revalidation with hashdeep.
Why do we need an
integrity database in the first place? WSUS Offline Update was once designed to create custom update CDs/DVDs. It will create an ISO image, which must be burned to writable CD/DVD. But such media are not very
reliable: Some self-burned CDs may be "coasters" and unusable from the start; others may go bad after some time. Then it is fine, if there is a way to verify the files again, before trying to install them.
But optical media are not much used today. Digital file signatures are verified with Sigcheck after download. If you keep the archives on
reliable media like internal/external hard drives, this should be enough. Unfortunately, the Update Generator and the download script don't allow an "uncoupling" of the verification of digital file signatures with Sigcheck and the creation of the integrity database with hashdeep. For reliable media, this might be a useful option.