An
unusual installation path can also cause problems with the script DownloadUpdates.cmd or Cscript.exe in particular.
Scripts can be broken by overly long installation paths or by unusual characters in the path. Cscript seems to be more sensible to such problems, because it runs in a different environment: Sometimes Cscript doesn't seem to find the current working directory or files within it, while the rest of the script runs fine.
Both UpdateGenerator.exe and UpdateInstaller.exe check for common problems with the installation path. They both ensure, that:
- the path is no longer than 192 characters
- the path does not contain the characters !%&()^+,;=
But there may be some corner cases, which are not easily detected.
So, what is the installation path to the wsusoffline directory?
Does it reside on a network drive?
WSUS Offline Update does run from a network drive, but you should assign it a drive letter, not just mount it as a network resource with UNC notation. For the installation part, network drives must be mounted
twice, once as a regular user and once with Administrator privileges.
Is WSUS Offline Update running in a virtual machine?
I didn't try that, but it should work fine. But some users create fancy configurations with some parts of WSUS Offline Update
inside the virtual machine, and some parts
outside. Such configurations may not work.
Problems with the installation part can be avoided by copying the directory wsusoffline directly onto the C: drive, so that the path to the UpdateGenerator is:
- Code: Select all
C:\wsusoffline\UpdateGenerator.exe
Then run it from that directory.