The problem
Windows' own copy tells you it finished. It does not tell you the file that landed is the file that left — and on the things people actually copy, a USB stick, a NAS over wifi, an external disk with a tired cable, that is not a theoretical difference.
The other half is worse. Nine thousand files, one of them open in Excel, and the whole job stops at file four hundred with a dialog and waits. Often overnight, on a machine nobody is sitting at.
What it does
1Every byte is checked
Every byte is hashed on the way out, and the file that lands is read back and hashed again. If the two do not match, the copy failed — and it is reported as failed, not as a success. The source is read once: the hash comes from the same bytes being copied, not from a second pass over the file.
2Nothing gets its real name until it is checked
The copy goes to a working file beside the destination and is renamed only once the hashes match. An interrupted copy leaves an obviously unfinished file rather than a real-looking one that is half a video.
3A move never deletes before it has checked
Copy, verify, then delete — in that order, always. Within one drive a move is a rename: instant, and nothing is copied, which vCopy says rather than reporting "0 bytes" and leaving you wondering.
4One file failing does not end the job
Something open in Excel, something the permissions will not allow, something a colleague deleted while it was running. vCopy collects what went wrong, carries on, and shows the list at the end with a button to try those again.
5Nothing is decided while it is running
The whole plan is shown before a byte moves: how many files, how many bytes, which are already there and whether they look the same, and whether the destination has the room. Any single file can be given its own answer.
6It warns about names Windows cannot open
A path over 259 characters, or a name ending in a space or a dot, can be written and then cannot be opened — not from Explorer, not from the command prompt. Files like that arrive from Linux servers and NAS boxes every day. vCopy says so before it writes, and offers a name that works.
7Four things it simply refuses
A folder copied into itself, a file copied over itself, a junction followed into the rest of the disk, and a destination that is a file where a folder has to go. Each of them destroys data, and none is caught by comparing two paths for equality.
8Checking two folders match
A job of its own, for a copy made by something else or made last year. Every file on both sides is hashed and compared, nothing is changed, and it reports what differs, what is missing and what matched.
Why it is worth it
The obvious move for a copying tool is to stand in front of Explorer's copy, and it is also why people uninstall them — it changes how every drag in Windows behaves, and when something goes wrong nobody knows what to blame. vCopy claims no file types and intercepts nothing.
It catches a truncated write, a disk that filled up, a share that dropped, wrong bytes, and a file that changed while it was read. It cannot promise the data is intact on the platter afterwards, because the read-back may come from Windows' cache — and any tool claiming otherwise on Windows is overstating what it can do.
For a name clash, it is the only choice that cannot lose anything: skip loses the new file, replace loses the old one. A default that loses something is a default somebody finds out about afterwards.
UNC paths, mapped shares and a NAS two folders deep all work, and are exactly where the checking earns its keep.
How you use it
Files or folders, onto the window — or right-click a selection and choose Copy with vCopy.
vCopy works out what would happen and shows it: the count, the size, the room at the far end, and anything that clashes.
Clashing names and names Windows will not be able to open. Each one can be answered on its own.
Pause it, stop it, or leave it. Anything that failed is listed at the end with a button to try those again.
What it needs
| Windows | 10 or 11, 64-bit. Server editions work |
|---|---|
| Installs to | Your user profile — no administrator prompt |
| Needs | Nothing else installed first |
| Network | None — vCopy never connects to anything |
| Works with | Local disks, USB, UNC paths and mapped network drives |
What it will not do, said plainly
It does not replace Explorer's copy. Ctrl+C and Ctrl+V go on doing exactly what they did, and dragging a file in Explorer is unaffected. That is deliberate: a program that quietly stands in front of the operating system's own copy is one nobody can diagnose when a copy goes wrong.
It cannot promise a file is intact on the disk surface afterwards. The read-back that checks a copy may be served from Windows' cache rather than from the device, and there is no way to ask Windows for an uncached read. The write is forced to the device first, so the bytes have certainly been handed over — but a disk that corrupts data after accepting it can still fool this.
It does not resume an interrupted copy from where it stopped. A copy that was stopped is removed and starts again, because a half file that claims to be finished is the thing this program exists to prevent.
See vCopy on your own machine
A short screen-share is usually enough — we open it on your PC, with your files.
Or write to info@issmart.in.
vTouch
vPress
vPDF
vScreen
vBack
vNote
vFTP
vName
vLog
vLogServer
vSys
vCom
vShot
vCmd
vTag
vAudio
vBooks
vOrg
vSize
vPort
vScan
vCon
vAuto
vClean
vShow