Error: 0x800c0006, ...\Temp\package.xml not found

[stanis]

Please help. I tryied 7.1, 7.2, and lately 7.3, all of which fail with the same error; see example below. Any suggestions on how to resolve this would be greatly appreciated.

Code: Select all

Determining statical update urls for dotnet x64-glb...
Extracting Microsoft's update catalog file package.xml...
Could Not Find C:\Users\bill\AppData\Local\Temp\package.cab
19:59:43.65 - Determining superseded updates (please be patient, this will take a while)...

Error occurred while loading document 'C:\Users\bill\AppData\Local\Temp\package.xml'.

Code:   0x800c0006
The system cannot locate the object specified.

ERROR: Download failure for dotnet x64-glb.

[WSUSUpdateAdmin]

Pls. delete wsusscn2.cab and retry download.
It seems to be corrupted.
RTW

[aker]

@WSUSUpdateAdmin
Wie wäre es mit einem Prüfbefehl nach dem Extrahieren bei

Code: Select all

%SystemRoot%\system32\expand.exe ..\client\wsus\wsusscn2.cab -F:package.cab "%TEMP%" >nul

?
Da könnte doch entweder ein

Code: Select all

if not exist "%TEMP%\package.cab" goto ExtractFailed

oder ein

Code: Select all

if errorlevel 1 goto ExtractFailed

hin.

Viele Grüsse

[WSUSUpdateAdmin]

Hi.

Wo ist der Gewinn?

Hier wie da landet man schließlich bei

Code: Select all

ERROR: Download failure for dotnet x64-glb.


, und die Ursache erschließt sich aus

Code: Select all

Extracting Microsoft's update catalog file package.xml...
Could Not Find C:\Users\bill\AppData\Local\Temp\package.cab


auch so.

Gruß
Torsten

[aker]

Ausnahmen könnten behandelt werden.
Z.B.
2. Versuch zu extrahieren, falls fehlerhaft löschen von wsusscn2.cab und erneuter Download.
Könnte natürlich auch ganz anders lauten, aber so könnte man den Benutzer gezielt über den Fehler informieren und nicht auf eine Fehlermeldung hoffen, die dieser nicht unbedingt versteht. (Das ist bei MS ja nicht unbedingt gegeben)

Viele Grüsse

[stanis]

Thanks for you're suggestions. Sadly my German isn't what it used to be making it hard to follow some of your posts.

I deleted the "wsusscn2.cab" file (as suggested) but that led to another error (see below). The thought was this file got corrupted. So I tried downloading v7.3 from scratch. Ran UpdateGenerator.exe. It ran for a bit downloading and saving, eventuially failed with the same error. Any other thoughts? Thanks for your assistance.

Code: Select all

Starting WSUS Offline Update download (v. 7.3) for w61-x64 glb...
Cleaning up existing directories...
Verifying integrity of Windows Update Agent installation and catalog files...
..\wsus\wsusscn2.cab: Known file not used
hashdeep64.exe: Audit failed
   Input files examined: 0
  Known files expecting: 0
          Files matched: 2
Files partially matched: 0
            Files moved: 0
        New files found: 0
  Known files not found: 1

ERROR: File integrity verification failure.

Press any key to continue . . .

[aker]

Just delete the content of .\client\md
That should fix that problem

[stanis]

Deleting the .\client\md\* directory contents (basically hashes-wsus.txt) did not resolve the problem. The update generator creates a new one and then fails with the same error code/message.

[WSUSUpdateAdmin]

Please

• Delete ...\client\wsus\wsusscn2.cab or verify it's 30.401.766 Bytes and from Jan 24th, 2012.
• Verify that %SystemRoot%\system32\expand.exe is present
• Switch off verification in UpdateGenerator.
• Re-run download.
• Once it was successful, you may switch on verification again.

RTW

[stanis]

...\client\wsus\wsusscn2.cab was 30,401,766 bytes and last modified Jan 24, 2012 (Tues). Deleted it regardless.
expand.exe (modified July 13, 2009), 65,536 bytes exists under C:\Windows\System32.
Unchecked Verify downloaded updates (the other 5 options are still checked). NOTE: The only other check is for Win7 x64 global.
Ran update generator.
It downloaded a new wsusscn2.cab file and failed with the same error code/message.