KN Know Zone Lab
PowerShell Basics

How to Extract a ZIP in PowerShell Without Overwrites

Know Zone Lab · Updated 2026-07-19 · 4 min read
How to Extract a ZIP in PowerShell Without Overwrites
SummaryTo extract a ZIP in PowerShell without overwriting existing files, first choose a new destination folder, then run `Expand-Archive -LiteralPath 'C:\Archives\bundle.zip' -DestinationPath 'C:\Temp\bundle-review'`. The destination is created when absent, and `Expand-Archive` does not overwrite existing files by default. Verify both resolved paths before running the command, leave off `-Force`, and inspect extracted files before opening or executing them.
Contents

Extract into a new destination folder

Use Expand-Archive with an explicit ZIP and a fresh destination:

Expand-Archive -LiteralPath 'C:\Archives\bundle.zip' `
    -DestinationPath 'C:\Temp\bundle-review'

Current Microsoft documentation says the destination is created if it does not exist and existing files are not overwritten by default. This example deliberately omits -Force, which would permit overwrites.

These commands use syntax shared by Windows PowerShell 5.1 and current PowerShell 7 releases. The command extracts data; it does not certify that the archive or its contents are safe.

Run the example without administrator rights unless the approved workflow specifically requires elevation. A review folder under a user-controlled temporary or work location should not need system privileges, and elevation increases the damage an incorrect destination can cause.

Verify both paths first

Check that the ZIP exists and the destination does not:

Test-Path -LiteralPath 'C:\Archives\bundle.zip' -PathType Leaf
Test-Path -LiteralPath 'C:\Temp\bundle-review'

The first result should be True. For the fresh-folder workflow, the second should be False. Then inspect the source file:

Get-Item -LiteralPath 'C:\Archives\bundle.zip' |
    Format-List FullName, Length, LastWriteTime

Do not copy these example paths blindly. Choose a destination inside a location you own and intend to use, not a system folder, synced production directory, application installation, or another person's workspace.

The PowerShell basics guides make paths visible before actions because “somewhere under Downloads” is not a rollback strategy.

Do not rely on WhatIf for an absent folder

Expand-Archive exposes PowerShell's -WhatIf common parameter, but Windows PowerShell 5.1 has an important trap in this exact workflow: when the destination is absent, -WhatIf can announce that it would create the directory and then report that the destination does not exist. The preview suppresses the creation that later validation expects.

That means a fresh-folder extraction should not use -WhatIf as its decisive safety check. Verify the source, destination text, destination parent, and Test-Path results instead, then run the command without -Force. A preview against an already existing destination answers a different question and abandons the clean absent-folder assumption used here.

For untrusted or business-critical material, use your organization's isolated inspection and security process rather than extracting directly into an ordinary workstation. No preview can assess malicious content, decompression size, filename tricks, or whether the archive matches what you expected.

Run without Force

When ready:

Expand-Archive -LiteralPath 'C:\Archives\bundle.zip' `
    -DestinationPath 'C:\Temp\bundle-review'

Do not add -PassThru to this cross-version example. Expand-Archive in Windows PowerShell 5.1 does not provide that parameter, although newer PowerShell documentation includes it. Inventory the destination explicitly after extraction so the same workflow behaves in both editions.

If the destination unexpectedly exists, stop. Do not add -Force as a reflex. According to the current command documentation, -Force overwrites existing files. Instead, choose another new folder or inspect, back up, and deliberately reconcile the existing destination through an approved process.

This tutorial does not provide an overwrite command. Keeping important files intact is more useful than winning a disagreement with an error message.

Inventory the extracted tree

List the destination without opening anything:

Get-ChildItem -LiteralPath 'C:\Temp\bundle-review' -Force -Recurse -File |
    Select-Object FullName, Length, LastWriteTime

Look for unexpected executable or script extensions, duplicate-looking names, hidden items, unusual depth, or a total file size that does not fit the expected package. The -File switch excludes directories, whose Length field would otherwise be blank. Do not run an unfamiliar program to discover what it is.

Archives can contain names that display differently across tools or systems. If anything looks wrong, leave the contents untouched and use the relevant security procedure.

Know the command's scope

Expand-Archive handles ZIP archives. Renaming .7z, .rar, .tar, or another format to .zip does not convert it. Use a trusted tool that explicitly supports the real archive type.

Microsoft documents a 2 GB maximum individual file size for the .NET ZIP API used by this cmdlet's implementation. Very large, encrypted, split, malformed, or specialized archives may require another reviewed workflow.

Use -LiteralPath when the filename contains characters such as square brackets that -Path could interpret as wildcard syntax. Literal handling prevents wildcard expansion; it does not validate the source.

Verify before and after

The file-integrity guides explain what checksums can and cannot establish. If the publisher supplies a trusted checksum, use the SHA-256 PowerShell guide before extraction. After extraction, check the package's official manifest or signature if one exists.

Finally, remove the review folder only through a deliberate, separately verified cleanup step after you know its exact contents and retention needs. Extraction is reversible when the destination is fresh. Overwriting somebody's final-final-really-final folder is considerably less charming.

Record the source archive path and destination before closing the session when the work must be audited. That small note distinguishes an intentional review copy from an unexplained directory that another person may later mistake for the authoritative files.

FAQ

Does Expand-Archive create the destination folder?

Yes. Current Microsoft documentation states that `-DestinationPath` creates the target folder if it does not exist. For safety, choose a new, clearly named folder and verify its parent location first. If you omit `-DestinationPath`, PowerShell creates a folder in the current location named after the ZIP, which may be less obvious than an explicit path.

Will Expand-Archive overwrite existing files?

Not by default. The `-Force` parameter permits overwriting existing files, which is why this tutorial deliberately omits it. Extract to a fresh destination instead. If an operational need truly requires replacement, inventory the exact target, back it up, understand which files collide, and use the current documentation; do not add `-Force` merely to silence an error.

Why use LiteralPath instead of Path?

`-LiteralPath` treats the path exactly as entered and does not interpret wildcard characters. That is useful for filenames containing square brackets or other characters with special wildcard meaning. It does not verify that the path is trustworthy or correctly typed, so still use `Test-Path`, `Get-Item`, and a visual review before extracting.

Can Expand-Archive extract formats other than ZIP?

No. Microsoft documents `Expand-Archive` for ZIP archives. Renaming another archive format to `.zip` does not convert it. Use a tool that explicitly supports the real format and obtain it from a trusted source. Be cautious with encrypted, split, malformed, or unexpectedly large archives, and never execute unfamiliar extracted files simply to see what happens.

How do I see what was extracted?

For a workflow that works in Windows PowerShell 5.1 and PowerShell 7, inspect afterward with `Get-ChildItem -LiteralPath 'C:\Temp\bundle-review' -Force -Recurse -File`. Do not add `-PassThru` to a Windows PowerShell 5.1 command because that edition's `Expand-Archive` lacks the parameter. Review extensions, signatures, source, expected names, and security scans before opening or running anything.