The "Copy, but keep both files" option in Windows 10 is not a standard right-click menu item but rather the result of how File Explorer handles duplicate filenames during copy operations. When you attempt to copy a file that already exists in the destination folder, Windows prompts you with choices: "Skip this file," "Don't ask again and skip," or "Keep both files." This behavior is controlled by system registry settings and can be restored or modified if it has been inadvertently changed.
Understanding the Duplicate File Prompt
When users report missing the ability to keep both files, they are usually referring to the dialog box that appears when copying data. By default, if you drag-and-drop or use copy-paste (Ctrl+C / Ctrl+V) to move a file into a folder where a file with the same name already exists, Windows pauses the operation to ask for your preference. The "Keep both files" option renames the incoming file automatically, typically appending a number like(1) to the filename (e.g., document.txt becomes document (1).txt).
If this prompt does not appear, or if the option is grayed out, it often means that a previous user action selected "Don't ask me again" for this specific scenario. Alternatively, group policies or registry tweaks may have altered the default handling of file collisions. Restoring the prompt ensures you have full control over whether duplicates are overwritten, skipped, or renamed.
Restoring the Default Behavior via Registry
The most reliable way to bring back the duplicate file prompt is to check the Windows Registry. This setting is governed by a key calledNoConfirmFileCopy. If this value is set to 1, Windows will automatically overwrite existing files without asking. Setting it to 0 restores the interactive prompt.
Follow these steps to adjust the registry:
- Press Win + R to open the Run dialog.
- Type
regeditand press Enter to launch the Registry Editor. - Navigate to the following path:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer - If the
Explorerkey does not exist, you may need to create it by right-clicking onPolicies, selecting New > Key, and naming itExplorer. - Look for a DWORD value named
NoConfirmFileCopywithin theExplorerkey. - If it exists, double-click it and change the value data to
0. - If it does not exist, right-click in the empty space, select New > DWORD (32-bit) Value, name it
NoConfirmFileCopy, and set its value to0. - Close the Registry Editor and restart your computer for changes to take effect.
Alternative Methods for Managing Duplicates
While restoring the registry setting fixes the immediate issue, there are other ways to manage file duplication in Windows 10. For instance, some users prefer automatic handling to save time. If you frequently encounter duplicate files and always want to keep both, you can use third-party file management tools that offer advanced renaming strategies. However, for most users, the built-in Windows behavior is sufficient. Another common scenario involves bulk copies. If you are copying multiple folders and one contains a conflict, Windows will pause at the first conflict. If you previously selected "Don't ask again and skip," all subsequent conflicts will also be skipped silently. To undo this global setting, you must reset the registry key as described above. There is no simple checkbox in the Control Panel to revert this; the registry is the primary control point. For more information on automating file movements in Windows 10, you might find our guide on Automatically Move Files/Folders in Windows 10 helpful, as it covers similar automation concepts.Using Command Line Alternatives
If you are comfortable with command-line interfaces, thexcopy or robocopy commands offer granular control over duplicate handling. The robocopy utility, for example, allows you to specify whether to skip, copy, or overwrite files using flags like /XO (exclude older) or /XF (exclude files). While these do not provide a GUI prompt, they are excellent for scripting repetitive tasks where you want predictable outcomes without manual intervention.
Troubleshooting Persistent Issues
In rare cases, even after settingNoConfirmFileCopy to 0, the prompt may not appear. This can happen due to corrupted shell extensions or interference from third-party antivirus software that hooks into the file system. To troubleshoot this:
- Restart Explorer: Open Task Manager, find
Windows Explorer, and restart it. This refreshes the shell interface without a full reboot. - Check Group Policy: If you are on a corporate domain, a Group Policy Object (GPO) might be overriding your local registry settings. Contact your IT administrator to verify if
NoConfirmFileCopyis enforced centrally. - SFC Scan: Run a System File Checker scan by opening Command Prompt as Administrator and typing
sfc /scannow. This repairs any corrupted system files that might affect File Explorer behavior.
Frequently Asked Questions
Why did the "Keep both files" option disappear?
The option disappears because you likely clicked "Don't ask me again and skip" in a previous copy operation. This sets a registry flag that suppresses the prompt for all future duplicates until manually reset.
Does resetting the registry delete my files?
No, changing the NoConfirmFileCopy registry value only affects how Windows prompts you during copy operations. It does not delete, modify, or move any existing files on your hard drive.
Can I make Windows automatically keep both files without asking?
Windows does not have a native setting to auto-rename duplicates silently. You would need to use third-party software or scripts to achieve fully automated duplicate renaming without user interaction.
What happens if I set NoConfirmFileCopy to 1?
Setting the value to 1 makes Windows automatically overwrite existing files with the same name whenever you copy them. This is risky as it permanently deletes the original file in the destination folder.
How do I restore the prompt if I am on a work computer?
If you are on a domain-joined machine, your IT department may enforce settings via Group Policy. In this case, you cannot change the registry yourself; you must request an exception or assistance from your system administrator.