# Windows 10 – No prompt to overwrite when pasting from .zip file

A copy operation from Explorer's built-in ZIP view may behave differently from a normal folder copy and skip the usual overwrite prompt, so it is worth extracting first when the target matters.

blog

10 Oct 2018 fr

![Windows 10 – No prompt to overwrite when pasting from .zip file](/wp-content/uploads/2018/10/img_5bbda48f9ff7d.png)

[Voir les images (2)](#pf-content-image-1-0)

I ran into an odd **Windows 10** behavior while copying files directly from a **ZIP** archive in File Explorer. The destination already contained folders with the same names, so I expected the normal overwrite prompt. Instead, the copy went ahead as if nothing needed confirmation.

That is the kind of thing that can ruin a quick manual deployment or patch if you are relying on Explorer to warn you before replacing content.

## What normal folder-to-folder copy looks like

That's how it normally looks like…

[!\[Windows copy dialog prompting whether to replace or skip files when pasting over existing files in a normal folder.\](/wp-content/uploads/2018/10/img_5bbda48f9ff7d.png)](/wp-content/uploads/2018/10/img_5bbda48f9ff7d.png)

## What I observed from ZIP

When the source was the built-in Explorer view of a **ZIP** file, I did not get the same prompt. It simply copied.

[!\[Animated Windows 10 example showing files copied from a ZIP archive overwriting existing files without the usual replace prompt.\](/wp-content/uploads/2018/10/Windows10zipOverwrites.gif)](/wp-content/uploads/2018/10/Windows10zipOverwrites.gif)

## Safer way to handle this

If the contents matter, do not copy directly from the ZIP view into a live folder and assume Explorer will protect you.

A safer approach is:

1. Extract the ZIP to a temporary folder first.
2. Review the extracted structure.
3. Copy from the normal extracted folder into the destination.

That gives you more predictable copy behavior and makes it easier to compare the source and destination before anything is replaced.

## Practical advice

- Avoid direct ZIP-to-production-folder copy operations for scripts, configs, or website assets.
- If you are updating existing content, test with a disposable folder first.
- If you need deterministic behavior, use a tool or script that makes collisions explicit instead of relying on Explorer's built-in archive view.

This post describes behavior I observed on **Windows 10 version 1809**. Even if newer builds behave differently, the workflow advice still stands: extract first, then copy.

## Projets associés

Projets liés aux tags, catégories et au contenu de cet article.

[Tous les projets](/fr/projets/)

Recherche des projets associés...

[Retour au blog](/blog)

## Articles associés

- [Windows 10 – Microsoft Store, Edge, Windows Updates, Microsoft Outlook not able to connect with error 0x80072EE7, 0x80070005](/fr/blog/windows-10-microsoft-store-edge-windows-updates-microsoft-outlook-not-able-to-connect-with-error-0x80072ee7-0x80070005/)
- [Windows 10 – You’ll need the internet for this 0xCAA7004 or 0xCAA30194 or 0x80072EFD](/fr/blog/windows-10-youll-need-the-internet-for-this-0xcaa7004-or-0xcaa30194/)
- [Getting Windows 10 build version from Active Directory](/fr/blog/getting-windows-10-build-version-from-active-directory/)

<!-- PowerForge markdown artifact sha256:65B1A5868D4CABAB549ACA6AA4BEF00F4A70DCCFAF703B48D87D701EA3B8CAF2 -->
