No patches Installed

Re: No patches Installed

Postby hbuhrmester » 24.10.2017, 17:26

Then the error still is different...

Actually, the script XSLT.vbs is running, and the message "XSLT uses MSXML 6.0" is from this code block within the script:

XSLT.vbs, lines 35 - 43
Code: Select all
Set objXML = CreateObject("MSXML2.DOMDocument.6.0")
If Err.Number = 0 Then
  Set objXSL = CreateObject("MSXML2.DOMDocument.6.0")
  WScript.Echo("XSLT uses MSXML 6.0")
  Set objXML = CreateObject("MSXML.DOMDocument")
  Set objXSL = CreateObject("MSXML.DOMDocument")
  WScript.Echo("XSLT uses MSXML 3.0")
End If

The error is in line 47 of the script XSLT.vbs:

XSLT.vbs, line 47
Code: Select all
objXML.load strXMLFileName

This probably means, that the script could not load the file package.xml in your local TEMP directory. Are there any error messages like this?

Code: Select all
ERROR: Unable to load XML file 'package.xml'

This can be caused by virus scanners temporarily blocking access to the file. We had some error reports like this before, but then there are usually more error messages mentioning the file package.xml itself. For example, the ownership of the file could be temporarily changed to "SYSTEM", and then even administrators could not read or remove the file. One user even used a Linux live CD, to remove the file package.xml, but administrators should be able to take over the ownership of the file again and then remove the file. This may be the result of an "On-Access" virus scanner, which just takes too long to completely and recursively scan the file I once compared this file to an "archive bomb".

This problem also seems to trigger a "Download failure", unlike your case, where the script seems to run through without detecting any errors.

Are there files like or package.xml in your personal temporary folder? They are usually removed by the script DownloadUpdates.cmd, when they are no longer needed. The personal TEMP directory would be:

Code: Select all

Do these files have any unusual properties, like a changed ownership or missing read permissions? Can you delete these files?

Try to make an exception in your virus scanner for these files (or the complete TEMP directory) and try again.

The WSUS catalog file could also be damaged or missing. But this is usually checked by the script DownloadUpdates.cmd, if the option /verify is used. Then the digital file signature of the file will be verified with Sysinternals Sigcheck, and damaged files will be removed. If the file is completely missing, then the script will exit with a proper error message.

But you could also verify this manually, just to be sure: Find the file wsusoffline/client/wsus/ and open the properties dialog. Open the "security" tab and verify the digital file signature of the file.

For comparison, please post the contents of the file wsusoffline/client/md/hashes-wsus.txt
Posts: 244
Joined: 11.10.2013, 20:59


Return to Installation / Updating

Who is online

Users browsing this forum: No registered users and 7 guests