forums.wsusoffline.net

Windoze 10 version 1709 Build 16299 64-bit
WU shows KB4043961 "available" and "awaiting download" (I have a metered connection, so it doesn't download automatically).
WSUSOffline shows "no missing update found. Nothing to do!"
WSUSOffline\client\w100-x64\glb\ contains KB4043961
Why doesn't WSUSOffline install it?
(I tried to install it manually, but it contains a number of sub-folders, and clicking on the file only results in Winzip opening it, not installation)

When did you run the download?
What is the signing date/time of .\client\wsus\wsusscn2.cab?

aker wrote:When did you run the download?
What is the signing date/time of .\client\wsus\wsusscn2.cab?

The download was run 10/18/2017 ~16:25 GMT-7:

10/18/2017 16:25:19.45 - Info: Downloaded/validated
http://download.windowsupdate.com/d/msd ... 8e0cb4.cab to ..\client\w100-x64\glb
10/18/2017 16:25:19.45 - Info: Downloaded/validated

I'm not sure what you mean by signing date/time. The wsusscn2.cab was created Wednesday, September 06, 2017, 13:34:13; modified Tuesday, October 17, 2017, 06:18:49; accessed Wednesday, October 18, 2017, 10:35:10. The "Digital Signature Signing Time" is Monday, October 16, 2017 23:06:09

The file that I subsequently obtained from the Windoze Catalog (and installed successfully) is "windows10.0-kb4043961-x64_5fb7d7bf32e79ea9debe8fb51af2a0c2e296e935.msu". It was created, modified, and accessed October 24, 2017 at 18:43:50, 18:44:58, and 18:43:50 respectively. Its "digital signature signing time" is Wednesday, October 11, 2017 22:24:01

The file in the .../w100-x64/glb folder is "windows10.0-kb4043961-x64_80d0155096f809a4f4b4092cfec8341f9d8e0cb4.cab". It was created Wednesday, October 18, 2017, 16:25:21; modified Friday, October 13, 2017, 14:51:07; and accessed Wednesday, October 18, 2017, 16:26:52. Its "digital signature signing time" is Wednesday, October 11, 2017 22:11:35.

Could you recheck now (after rerunning the download part)?
MS pushed a new catalog (signed 2017-10-17 06:06:09 GMT), which just contains internal changes. Maybe this fixes the problem for you.

aker wrote:Could you recheck now (after rerunning the download part)?
MS pushed a new catalog (signed 2017-10-17 06:06:09 GMT), which just contains internal changes. Maybe this fixes the problem for you.

I could, but...Since I already did the update from the file downloaded from the Windoze Catalog (after WSUSO failed to do so), I would not expect WSUSOffline to update anything now, and thus we will never know what the problem was. Hopefully, it won't recur next month