Sunday, December 11, 2022

CAB file that is exported by using the Wsusutil.exe command is displayed as 0 KB on a Windows Server 2012-based WSUS server - Microsoft Support [MS]


Consider the following scenario:

  • You have a Windows Server Update Services (WSUS) server that is running Windows Server 2012.

  • You use the Wsusutil.exe command-line tool to synchronize software update metadata on the WSUS server. For example, you run the following command:

    wsusutil.exe export export.log

  • The command is completed without error.

In this scenario, the file size of the exported package file ( is displayed as 0 kilobytes (KB).


This issue occurs because the metadata.txt file within the exported CAB file exceeds the limit of 2 gigabytes (GB).

Note CAB files have an internal limit of 2 GB for included files.


This hotfix is also available at Microsoft Update Catalog.

Hotfix information

To resolve this issue, install the hotfix that is described in this article. Then, use the following syntax to export or import update metadata by using the GZIP file format:

wsusutil.exe export export.xml.gz export.log

wsusutil.exe import import.xml.gz import.log
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must be running Windows Server 2012.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces all previously released updates for WSUS 3.0 Service Pack (SP2).  For more information about WSUS 3.0 SP2, click the following article number to view the article in the Microsoft Knowledge Base:

2734608 An update for Windows Server Update Services 3.0 Service Pack 2 is available (KB2734608)

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 file information notesImportant Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:




    Service branch

    6.2.920 0.20 xxx

    Windows Server 2012



  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2012

File name

File version

File size

















Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about the Wsusutil.exe command-line tool, go to the following Microsoft website:

General information about the Wsusutil.exe command-line tool For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

No comments:

Post a Comment

Search This Blog

About data segments that use Mobile Device IDs - Google Ads Help [gg-google-ads-en]

About data segments that use Mobile Device IDs To provide a comprehensive and consolidated view of your Audiences and make audien...