wsus post installation failed 0x80004005

TL;DR

The WSUS post-install step (wsusutil postinstall) fails with the generic 0x80004005 when it cannot create or write the content directory, attach or create SUSDB, or register with IIS under the expected service account. Read the WSUSSetup log in the temp folder for the real failing action, fix that specific permission or database issue, and rerun postinstall with the correct CONTENT_DIR.

wsus post installation failed 0x80004005

Use this when

• Server Manager shows WSUS role installed but post-installation tasks failed.
• Running wsusutil postinstall returns 0x80004005.
• The WSUS console will not connect because configuration never finished.

Not for this skill when

• WSUS is fully configured and synchronizing. This is not a post-install problem.
• The role install itself failed earlier with a DISM source error. Fix feature installation first.

Steps

1. Open the WSUSSetup log (WSUSSetup_*.log in the user temp folder) and find the first fatal action. Verify: the failing step (content dir, database, or IIS) is named
2. Confirm the content folder path exists and that the WSUS service account and NETWORK SERVICE have modify rights there. Verify: you can create a test file in that folder as the service context or by ACL inspection
3. Check whether a SUSDB already exists from a previous install; if it is orphaned or corrupt, detach or remove it so postinstall can create a fresh one. Verify: SQL or WID shows no conflicting SUSDB, or a healthy one you intend to keep
4. Rerun wsusutil postinstall with the SQL instance and CONTENT_DIR parameters matching your design. Verify: the command exits reporting success
5. Open the WSUS console and run the configuration wizard. Verify: the console connects and initial sync can start

Variant phrasings

wsusutil postinstall failed 0x80004005

The command-first phrasing.

wsus post installation tasks failed server manager

The Server Manager phrasing.

wsus setup log content dir permission failed

The root-cause phrasing from the setup log.

Compatibility: Compatibility: WSUS role on Server 2016 and later, WID or SQL Server content and database options.

Why it happens

0x80004005 is the generic COM failure code, so the postinstall wrapper hides the real reason. The setup log always records which sub-action failed: creating the content directory on a volume without the right ACLs, connecting to a SQL instance the setup account cannot use, or configuring IIS when a previous partial install left conflicting bindings.

Edge cases / pitfalls

• Installing WSUS content on the system drive root without creating the folder and ACLs first is the most common self-inflicted cause.
• Removing a previous WSUS install leaves SUSDB and content behind by design; decide deliberately whether to reuse or discard them.
• If SQL is remote, the setup account needs rights on that instance; WID installs avoid that variable for a first test.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ymu4QKSprEWkOxDcmtXpwA

Resolved from the public thread: https://vectle.com/posts/pst_ymu4QKSprEWkOxDcmtXpwA

Thread query: wsus post installation failed 0x80004005

TL;DR: The WSUS post-install step (wsusutil postinstall) fails with the generic 0x80004005 when it cannot create or write the content directory, attach or create SUSDB, or register with IIS under the expected service account. Read the WSUSSetup log in the temp folder for the real failing action, fix that specific permission or database issue, and rerun postinstall with the correct CONTENT_DIR.