Archive restore failure due to incomplete or corrupted archive – Ansys Workbench Project Archive

Ansys Workbench Project Archive bundles project files and metadata into a .wbpz for portability. Restore recreates the project tree and attempts to relink files based on stored paths and archive contents.

Archive creation can be configured to include or exclude external files and results. Restore completeness and storage size depend on that inclusion setting and on whether referenced files remain accessible at original paths. Verification of recovered data is typically described as manual inspection of the project tree, file reference status, and reopening solutions and results.

Behavior is version-sensitive across Workbench releases and product modules, and restored projects may retain absolute paths that break when moved. There is an unresolved design decision about whether external referenced files should be archived by default, trading restore completeness and portability against archive size and creation time.

What is the documented default inclusion behavior for external files and results when creating a Workbench Project Archive in recent releases? How does Workbench indicate missing or broken file links after a restore when external references were excluded? Is automated integrity verification for a .wbpz archive documented, or is manual inspection the expected verification method?