Update generator hangs at Downloading and validating updates 33 of 141 for office.
Please check screenshot.

Thanks
-v
--verbose
Turn on verbose output, with all the available data. The default
output is verbose.
-nv
--no-verbose
Turn off verbose without being completely quiet (use -q for that),
which means that error messages and basic information still get
printed.
-t number
--tries=number
Set number of retries to number. Specify 0 or inf for infinite
retrying. The default is to retry 20 times, with the exception of
fatal errors like "connection refused" or "not found" (404), which
are not retried.
-T seconds
--timeout=seconds
Set the network timeout to seconds seconds. This is equivalent to
specifying --dns-timeout, --connect-timeout, and --read-timeout,
all at the same time.
When interacting with the network, Wget can check for timeout and
abort the operation if it takes too long. This prevents anomalies
like hanging reads and infinite connects. The only timeout enabled
by default is a 900-second read timeout. Setting a timeout to 0
disables it altogether. Unless you know what you are doing, it is
best not to change the default timeout settings.
set DLDR_NVOPT=-nv
set DLDR_NVOPT=-v -t 5 -T 60
hbuhrmester wrote:I don't think, that wget or the download script just hangs, but it may take some time to get a response.
- Most of the wget messages go into the download log, which is the file wsusoffline/log/download.log
- With the option --no-verbose (-nv), wget won't give much feedback. Usually, only successful downloads and errors are reported, but no progress reports.
- Some files are rather large, and you won't get feedback, until they are completely downloaded.
- With standard settings, wget uses 20 tries with a timeout of 900 seconds each. At worst, you have to wait 5 hours before getting a response. The manual pages describe these options like:
Users browsing this forum: No registered users and 376 guests