- This topic has 5 replies, 3 voices, and was last updated 9 months, 3 weeks ago by .
-
Posts
-
Since updating to the new version i am unable to download a .cab file for offline updates.
If I manually go: TOOLS > DOWNLOAD MICROSOFT OFFLINE SCAN FILE. I get a continuous loop of “Digital signature validation failed” status’s. I have tried on 3 different networks wiht and without proxy. 5g networks etc. All have the same errors when trying to download the .cab file.If I use a old .cab file it works fine but that will not have the latest patching information.
You can download it manually in your browser from http://go.microsoft.com/fwlink/?LinkID=74689
Microsoft recently made a change to how that download link behaves. This caused our existing code that handles the download to stop functioning properly, and it’s why you’re now seeing errors all of a sudden. It will be fixed in the next release of BP. For now please download it manually using the provided link, and then put it in your local BP cache folder.
Hi guys,
I get the same issue and fixed it with a manual download. However and to cover any further problem would it be possible to raise a warning inside BP when such occurs? Something like “not able to download the new cab file”?
My problem: the cab file is configured to be reused, on purpose for my environments. For some previous patching this issue was unnoticed, servers simply output “no applicable update”. As we use filtering etc. this is not completely weird (and happen sometimes) but here we missed some important KB. A simple warning would help.
thx!
@booster – If you have an older WsusScn2.cab file in the cache folder at the time you start the search for updates in offline mode, and then if BP fails to download the new file like it is currently doing, then if you review the ‘All Messages’ log you’ll see the following:
07/12 11:14:02> Windows Update: WsusScn2.cab file copy complete
07/12 11:14:02> Windows Update: Copying WsusScn2.cab file from local cache to target working directory…
07/12 11:14:02> Windows Update: Queued WsusScn2.cab file copy from local cache to target working directory…
07/12 11:14:02> Windows Update: Initializing copy of WsusScn2.cab file from local cache to target working directory…
07/12 11:14:02> Windows Update: Local download complete (Files downloaded: 0. Files located in cache: 1. Files excluded by filter: 0. Files initiated by another row: 0. Failures: 0)
07/12 11:14:01> Windows Update: Executing WsusScn2.cab downloader…
07/12 11:14:01> Windows Update: Queued WsusScn2.cab downloader…
07/12 11:14:01> Windows Update: BEGIN (Offline mode: Check for available updates)
07/12 11:14:01> Windows Update: Queued…You can see: Files downloaded: 0. Files located in cache: 1, which indicates that it did not download a newer WsusScn2.cab file but instead used the existing one that was in the cache folder.
Your best bet is to either remove the old cache file before doing a new run, or manually make sure you have the latest file in place before doing a new run, or just review the log for the line I mentioned above so that you can see if an older file was used or if a new file was downloaded.
And yes, we will look at adding some type of additional warning. I think it’s already supposed to be providing such a warning, but this particular failure occurs in an unexpected way that broke our previously working download code altogether, so the failure wasn’t caught in the expected way and consequently did not warn properly.
- You must be logged in to reply to this topic.