RocketCopy v2.01.2 - Fast File Copy for Windows =============================================== RocketCopy is a standalone (single-file) Windows utility for high-speed file copying. No installation required. Supported systems: Windows 7 (64-bit) and Windows 10 (64-bit). WHAT CHANGED IN VERSION 2.01.2 A maintenance release. Every change here is about jobs that stop early, and about the delete box - the way files are copied is untouched: - Cancelling no longer creates the empty folders that had not been reached yet at the destination. On a large tree that used to leave thousands of empty folders behind; folder timestamps and permissions are still applied to the folders that did land. - Closing the window while a delete, or an "Empty Recycle Bin", is still running now asks you first. Answering Yes keeps the window up until the job has finished; the run is still accounted for in the log if you close it. - "Empty Recycle Bin" now empties only the Recycle Bin of the account you are logged in as - it no longer touches the bins of other accounts on the same machine. - A broken link inside the source tree is now counted and reported as a failure, instead of quietly dropping out of the run. - Dialog boxes open on the monitor the main window is on, and stay inside that monitor's usable area. - Long deletes write a progress line to the log every 30 seconds, so you can see that the job is still moving. - Fixed: on very deep paths the last-modified time could not be read, so those files were re-copied in full on every run instead of being recognised as already present. - Activation can now also be confirmed with the author's license server, for the standard kind of registration code (see LICENSE below). Offline codes keep working exactly as before, with no connection at all. (Version 2.01.1 fixed the bottom row of buttons falling off the screen on a 1920x1080 desktop; that fix is included here.) BEFORE YOU RUN IT: SMARTSCREEN, ANTIVIRUS, CHECKSUMS - Windows may block the download, or warn you the first time you start the program. Edge or Chrome can say "rocketcopy.exe isn't commonly downloaded"; Windows SmartScreen can show "Windows protected your PC" with an unknown publisher. Both are the standard warning for software that is not signed with a commercial code-signing certificate yet - it is not a virus warning, and nothing about the file changed to cause it. To continue: in the browser pick "Keep" (or "Keep anyway"), and in the SmartScreen window click "More info", then "Run anyway". Windows remembers that choice for this file. - Please scan the file with your own antivirus before the first run. Download it, then right-click the file and choose "Scan with..." your antivirus (or upload it to VirusTotal), and start it only after the scan comes back clean. - The program publishes two checksums, so you can confirm the file arrived complete and unmodified. File size 9,387,096 bytes. - MD5: 92c527547d512196d0ef56e507c6a010 - SHA-256: f9d1a82e86b8ea91b714d86fccd65e346a3b498b082f7bc71d1c02c0057df22f - To compare on your own machine, open Command Prompt (Win+R, type cmd) and run certutil -hashfile rocketcopy.exe MD5 or the same command with SHA256. Either value matching is enough; MD5 is quick and catches a truncated download, SHA-256 is the stronger one. The same three values are printed on the download page. - These checksums change whenever the program is rebuilt, so always take them from this readme or the download page of the same release - an older copy of the readme will show different numbers for a different build. WHY IT EXISTS Windows' built-in copy is extremely slow with huge numbers of small files - even on an SSD. RocketCopy hands the actual byte copying to Windows itself and only does the queueing and bookkeeping, with several copies running side by side (the program calls them "ways"). THE MAIN WINDOW (one window, two panes) The window is split into two panes that look the same and both accept drag-and-drop straight from Explorer: - Left pane = the source items. Drop as many files and folders as you want, in one go or in several goes. Buttons: "Add Files...", "Add Folder...", "Remove selected", "Clear" - and clicking an entry then pressing Delete removes it too. - Right pane = the destination folder. Drop one folder into it, or pick one with "Add Folder..." underneath. Buttons: "Add Folder...", "Clear". When both sides have something, "Start Copy" lights up at the bottom right. The bottom row also holds "Register", "About", "Install menu", "Uninstall menu" and "cancel". That row is anchored to the bottom of the window and is laid out first, so it stays visible even when the desktop is small (1920x1080 with 125% scaling, for instance) - the window is sized to the usable desktop area with the taskbar excluded. COPY SETTINGS (group "Copy settings (kept for next time)") - Copy engine: Kernel copy - Windows copies the bytes itself. - How many at once: Automatic (4 ways, recommended) / 8 ways / 16 ways. "ways" = how many files are being copied at the same time. - Resume (OFF by default) - a small square tick box on the right of the Copy mode dropdown, so it takes no extra space in the window. Tick it and a big file (64 MB and up) that was interrupted carries on from where it stopped instead of being written again from the beginning; while the run lasts, the partial file sits next to the destination as a hidden ".rcpart" file. Cancelling asks whether to keep that partial file for the next run. Leave it unticked and every interrupted file is simply written again in full. - Copy mode: Copy (default) or Move - in Move mode the source file is deleted only after its copy has fully landed at the destination, and source folders are removed once they are empty (same as Explorer's Move). Any folder that still holds a file that did not copy is kept. What "cancelling midway never loses data" means: in Move mode the program first writes the whole file to the destination, confirms it is really there, and only then goes back and deletes the source. So whenever you press cancel, the worst case is "that file exists in full at the destination and still at the source" - both sides have a copy. There is never a moment where the source is gone and the destination copy is incomplete. Files already copied stay as they are; the ones not finished keep their source untouched. In Copy mode the question does not arise at all, because the source is never touched. - If file exists: Ask before overwriting (default), Overwrite, Skip (leave the file at the destination untouched, and keep the source as well) or Keep both (write the incoming file under a new name such as "name (2).ext", so nothing is lost). How "Ask before overwriting" behaves: the first clash opens a dialog. While you read it, RocketCopy counts - by name only, without comparing contents - how many files in this run already exist at the destination. If that is just the one file, pressing Yes carries on without asking again. If there are more, a second dialog tells you how many and warns you that the contents were NOT compared, only whether the names are the same; Yes overwrites them all, No stops the run right there and writes the list of same-name files into the same folder as the executable (rocketcopy_same_names.txt), so you can go and see exactly which names matched. - Verify byte-by-byte (off by default) - after copying, the copy is read back from the destination drive and compared with the source. A file that does not match is counted as a failed file, is named in the log, and in Move mode its source is left alone. Two kinds are deliberately left out: files you told the program not to touch by choosing "Skip", and files that were already compared during the check described under RESUME (reading them a second time would only make the run slower). - Keep original dates and times (OFF by default) - when ticked, both files and folders get the same creation / last modified / last accessed times as the source instead of the current time. Ticking it makes the run a little longer, and the completion report shows that extra time separately, so you can see what it cost. - Copy NTFS permissions (OFF by default) - when ticked, the permission list (ACL) of each source file and folder is applied to the copy, instead of the copy simply inheriting the permissions of the folder it lands in. Handy when the source was set up so that only certain people or accounts may read it. It only works when the destination is on an NTFS drive; on FAT/exFAT sticks the permissions cannot be stored, and the completion report tells you how many items could not be set. Only the permission list is copied - ownership, the group and the audit settings are left alone (changing those needs privileges an ordinary user does not have). Accounts are carried over by their Windows identifier, not by their name: an account that does not exist on the computer reading the copy is shown as a bare identifier instead of a name, and the entry still applies - this is what you should expect when a copy made on one computer is opened on another. - Write a run log (ON by default) - see "FILES WRITTEN NEXT TO THE EXE". - Write a detailed log (OFF by default) - one line per file, with your file names and the destination paths. Turn it on when you need to send the log to support; leave it off and the log stays free of file names. - Reset settings - puts every setting above back to its built-in default (the list is just below). Use it if the program seems to remember something wrong. DEFAULT SETTINGS (exactly what "Reset settings" restores) Parallelism ................ Automatic (4 ways, recommended) Copy mode .................. Copy If file exists ............. Ask before overwriting Verify byte-by-byte ........ off Keep original dates/times .. off Copy NTFS permissions ...... off Resume .................... off Write a run log ............ ON <- the only setting that is on out of the box Write a detailed log ....... off Not touched by that button: the Delete box's thread count (it lives only for the current run), the Find box, and the source/destination lists you have already filled in. WHAT IS REMEMBERED BETWEEN RUNS Stored in the registry, under HKEY_CURRENT_USER\Software\RocketCopy\Settings: the way count, "Write a run log", "Keep original dates and times" and "Copy NTFS permissions" (plus the resume switch described under RESUME), and one path: the destination folder you last chose in the right-click box, kept so it can be filled in for you next time. Nothing else is stored, and apart from that one folder what is stored is nothing but "which choice you made last time" - no file names. To wipe it completely, delete the key itself; Reset settings only puts those options back to their factory values and leaves the remembered folder alone. Not stored: Copy mode, "If file exists", "Verify byte-by-byte" and the detailed log keep the value you picked only while the program is running; close it and reopen it and they are back at their defaults (Copy / Ask before overwriting / off / off). No settings file is written next to the exe, and none is read either - this version only ever looks at the registry. LINK AND CLOUD FOLDERS (junctions, symlinked folders, mount points, OneDrive-style cloud placeholders) A folder that is really a pointer to somewhere else is not followed - its contents are not copied, and no empty stand-in folder is created at the destination. This is deliberate: Windows ships several self-referring links (for example "Documents and Settings" pointing back at "Users"), and following them makes a copy run around in circles and duplicate whole folders into themselves. Cloud placeholder folders are skipped for the same reason and with the same wording, because they are pointers too. RocketCopy never hides this from you: the number of such folders that were not followed is reported on its own line, both in the completion report and in the run log ("Link and cloud folders: N folder(s) that are links or cloud placeholders ..."). Exception: if you pick such a linked folder yourself, as a source item, it is copied like any other source - the contents of the folder it points at are copied to the destination under that item's name. Picking a link is a choice the program honours, not something it skips. One thing to watch: if the folder the link points at is ALSO inside what you are copying this time, its contents end up at the destination twice - once through the link item, once through the real location. If you do not want that, drag the real folder instead of the link. RESUME The small tick box on the Copy mode row switches the "carry on from the middle" mode. Re-running an interrupted job is safe either way, but "safe" does not mean the same thing in the two modes: - In Move mode, and whenever "Verify byte-by-byte" is ticked, a file that is already at the destination is read back and compared byte by byte before it counts as done. Anything that does not match is rewritten in full, so a half-written file - or one that has the same size but different contents - is never accepted as "already there". - In plain Copy mode with verification OFF the check is the cheap one: size plus last-modified time, no read-back. A destination file with the same size but different contents can still be skipped, as long as its last-modified time is not older than the source's. If "same size" must always mean "same bytes" for you, tick "Verify byte-by-byte". With the tick box on, a big file (64 MB and up) does not start from zero - it continues from the end of the hidden ".rcpart" file written next to the destination, and the completion report tells you how many files carried on and how many bytes that saved. Cancelling midway asks whether to keep that partial file for the next run. A partial file is only carried on when the source still matches what it was: the size and the last-modified time are recorded alongside it, and the next run compares them with the source as it is now. If either has changed, the partial file is thrown away and the file is written again from the beginning, so a half-copied file is never finished with bytes from a different version of the source. One difference worth knowing: in Move mode, and whenever "Verify byte-by-byte" is ticked, a file that already sits at the destination is read back and compared byte by byte before it counts as done. In plain Copy mode with verification OFF the check is the cheap one - size and last-modified time, no read-back - so a destination file with the same size but different contents can still be skipped. Tick "Verify byte-by-byte" if "same size" must always mean "same bytes" for you. Note that a resumed file is not handed to Windows in one piece: the run that continues it writes the file itself in blocks of a few megabytes, forcing each block to disk before the next one, so that an interruption can only ever lose the block that was in flight. COMPLETION REPORT When a job finishes, a summary window shows which engine and how many ways/threads ran, the route it took (from which source folder to which destination), how many files were processed and how many failed - files and folders counted separately - the total size, how long the copying took, the average speed, the scan time (a plain copy without verification does not scan first, so it says "none"), the keep-dates time if that switch was ticked, and anything that was skipped, rewritten, cancelled or failed. If the run had to clear a write-protected (read-only or hidden) file at the destination to overwrite it, that count is reported too, so nothing is changed quietly. Its heading reads "Copy complete" or "Move complete" according to the mode you used, and a cancelled run says so instead of claiming success. The error messages here are in plain words, easy to read. When a run has failures, the window also carries the "Write the failed items to rocketcopy_failed.txt" tick box described under FILES WRITTEN NEXT TO THE EXE. FAST DELETE BOX (bottom right of the main window) The box in the bottom right corner deletes files and folders - it does not copy them. It is a permanent delete: whatever you drop in there does NOT go to the Recycle Bin, and there is no way to get it back. The box says so on screen, in red, all the time. How it works: 1. Drop files and folders into it (or press Add Folder... under it). Nothing is deleted at this moment - they are only listed. 2. The box shows what is waiting, with full paths and a count, and the Delete button carries that count (Delete 2, Delete 7 ...). 3. Press Delete, check the list in the confirmation box, and confirm. Only then does anything get removed. 4. Clear empties the waiting list without deleting files. Under the box you can pick how many threads the delete uses (4/8/16; 8 by default). Deletion is parallel - it is the same engine the copy side uses, so a big tree deletes quickly too. If something cannot be deleted, it is listed in the log with its full path, marked [ERR]. Speed is the point of this box: pick 8 or 16 threads and a folder holding tens of thousands of files is gone in seconds, where Explorer needs minutes. It needs no registration code - it works during the trial and after the trial ends. The "Empty Recycle Bin" button next to it is a different thing: it empties the Recycle Bin you already have in Windows. It has nothing to do with the box above and it does not touch anything you have not already deleted yourself. If you only want files gone temporarily, use Windows Explorer instead - this box always deletes for good. EMPTY RECYCLE BIN (next to the Fast Delete box) The "Empty Recycle Bin" button sits right next to the Fast Delete box. It does one thing: it empties the Recycle Bin that Windows itself maintains - the one your files go into when you delete them the normal way in Explorer. One click and everything currently sitting in the Recycle Bin is gone for good, freeing that space at once. This is a different feature from the Fast Delete box above. The box deletes files directly and permanently without ever touching the Recycle Bin; this button only acts on what is already in the Recycle Bin, and it never deletes a file you have not previously sent there yourself. Use it to reclaim the space held by files you deleted earlier through normal Windows deletes, without opening the Recycle Bin and clearing it by hand. It is the quick way to give that space back: one click, one confirmation, and the bin is empty - no opening the Recycle Bin, no clicking through it by hand. Like the Fast Delete box above, this button needs no registration code: it works during the trial and after the trial ends. WAYS TO LAUNCH 1. Double-click the exe: drag your files and folders into the left pane (or use "Add Files..." / "Add Folder..." under it), drag the destination folder into the right pane (or use "Add Folder..." under it), then press "Start Copy". 2. Right-click one or more selected files / folders / a drive in Explorer: "RocketCopy to..." - a small "copy them to where?" box opens first. The sources are already in, so all you do is pick the destination folder ("Browse..." or type the path) and press "Start Copy"; the run uses your saved settings. Press "More options" in that box to open the full main window instead (the old behaviour) when you want to change the settings. 3. Send to -> RocketCopy: same as above, from the Send to submenu. Which one to use: "RocketCopy to..." is the handiest for everyday use (it shows up on files, folders and drives). If a large multi-select through "RocketCopy to..." stalls or loses part of your selection, switch to "Send to -> RocketCopy" - Explorer hands every selected item over in one go there, so it is steadier for multi-select. Choosing several items at once (or launching several of them together) opens ONE window holding all of them - not one window per item. RIGHT-CLICK MENU Install and uninstall are built into the app: press "Install menu" or "Uninstall menu" at the bottom of the main window. It writes only into your own (current-user) part of the registry, so no admin rights are needed. "Uninstall menu" removes the "rocketcopy" entry and nothing else: the verbs named exactly rocketcopy under * / Directory / Drive / AllFilesystemObjects (plus the cascaded submenu older builds may have written), and the rocketcopy.lnk in Send to. Those are exactly what "Install menu" writes. The release build's file name carries no version number, so this one entry is all there is - version numbers are not considered. Versioned leftovers and anything turbocopy (the old product name) are NOT touched; they are only listed in the result box under "left untouched on purpose", so you know they are there. Note: the menu entries point at the exe's full path. After moving to a new version, press "Install menu" again - otherwise the right-click entry still points at the old exe (do not delete that old exe, or the menu turns into a dead link). FILES WRITTEN NEXT TO THE EXE - Settings: the registry key HKEY_CURRENT_USER\Software\RocketCopy\Settings (no settings file next to the exe any more) - Log: rocketcopy_log.txt - written while "Write a run log" is ticked (it is ticked by default). Untick it and no log file is opened or created at all. The log is PLAIN TEXT, so you can open it in Notepad and read it yourself. It records program status only: the version, licence state, which engine and how many ways/threads you used, the file count and total size, elapsed and scan time, the link and cloud folders that were not followed, and the system error code behind every failure (the on-screen message keeps the wording plain and leaves the number out, so the number lives here). Every error line starts with [ERR], so you can search the file for problems. By default it does not list the paths of what you copied - any drive letter or UNC path is replaced with before writing - and it keeps one short line naming the items of that run (the first eight names, then a count of the rest; names only, no folder levels), so you can tell which job a log block belongs to. The exception, and it is there to help you: when an item fails - it could not be copied, it failed the byte-by-byte check, or in a move its source could not be removed - that failing item IS named in the log, with its full path and drive letter, because otherwise you cannot tell which file on which drive went wrong. That line is marked [ERR] too. Everything else in the log is de-identified: apart from the [ERR] lines, the names in that one "Copy route" line, and a relative path on the line written when a resumed partial copy is continued, no line carries paths. If you also tick "Write a detailed log" on the main window, the log additionally gets one line per copied file, with the destination's full path - that is the only setting under which the log holds the names of the files you copied. It is off by default; leave it off and the log stays short. If you cannot solve a problem yourself, email this file to rocketcopy26@outlook.com - it is plain text, so open it in Notepad first and look through the [ERR] lines: those carry your own paths (and, in a crash file, your Windows account name). Delete anything you would rather not send before you attach it. You may delete the file at any time; the app simply starts a new one. When it grows past 10 MB it is rotated to rocketcopy_log.1.txt. - Fast delete box (bottom right): see "FAST DELETE BOX" above. - Failed items: rocketcopy_failed.txt - appears only after a run in which something did not copy. The completion box then carries a tick box ("Write the failed items to rocketcopy_failed.txt") that is ticked by default; untick it and nothing is written. Unlike the log, this file DOES contain the full paths of the failed items, with the reason for each one and the route of the job, because its whole purpose is to let you find those files again. Delete it whenever you no longer need it. If the program folder cannot be written to, the file lands in your Windows temp folder instead. - Full copy record: rocketcopy_details.txt - only when you ask for it. The completion box carries a tick box ("Write the full copy record to rocketcopy_details.txt"), OFF by default. Tick it and you get, for that one run, the complete list of every source path, the totals, the timing and every failure with its reason, all with full paths. Each run overwrites the previous file. If the program folder cannot be written to, it lands in your Windows temp folder. - Same-name files: rocketcopy_same_names.txt - only when you answer No to the bulk overwrite prompt (see "If file exists"). It lists the pairs whose names already exist at the destination - source path and destination path, one pair after another - so you can compare them yourself. Name match only: the contents were not compared. Each run overwrites the previous file. - Crash evidence: rocketcopy_crash.txt - only appears if the program ever stops unexpectedly, and its job is to say where it stopped. Being an evidence file, it is not de-identified: a stack trace can contain paths. Note its limits - a small class of crashes that kill the process while it holds an internal lock leaves nothing but a one-line banner. LICENSE (Shareware) 30-day full-feature trial. After the trial, a registration code is required for copying. - The two delete features are NOT part of what the trial gates: the Fast Delete box and the "Empty Recycle Bin" button keep working after the 30 days are up - no code, no time limit, no nag screen. Same speed, same thread options, before and after the trial ends. - Each registration code activates one computer, and is bound to it. - Your machine ID is built from public hardware identifiers. It does not use your disk serial numbers, and it does not use your computer name. Renaming your PC, swapping or adding drives, or reinstalling Windows never breaks activation; only replacing the CPU or the motherboard changes the machine ID, and then the program has to be activated again - that is a fresh activation, not a new purchase. The machine ID is shown in the About dialog. - Each registration code is issued by the author against the machine ID of that one computer, so a code only works on the computer it was issued for. - Paste the whole code in one go; accidental line breaks, spaces or tabs inside it are ignored. - There are two kinds of registration code, and they behave differently: - An offline code is checked entirely inside the program, on your own computer. It needs no account and no connection, and nothing about it is sent anywhere - it works on a machine with no network at all. If that is what you need, ask for an offline code at rocketcopy26@outlook.com. - A standard code is confirmed with the author's license server when you activate it, and the program re-confirms the license with that server from time to time afterwards. Only the code and an installation identifier are involved - never your files. If the server cannot be reached, an already-activated copy keeps working; it is not disabled on the spot. The Privacy Policy shipped with the program has the details. THIRD-PARTY COMPONENTS AND COPYRIGHT RocketCopy ships as a single-file Windows executable. The following third-party components are bundled inside it. Each is redistributed under a licence that permits inclusion in a closed-source commercial application, and none of them places your own code under any copyleft obligation: - CPython 3.8 - Copyright (C) 2001-2026 Python Software Foundation (Python Software Foundation Licence) - Tcl/Tk 8.6 - Copyright (C) the Tcl/Tk community (Tcl/Tk Licence, BSD-style) - OpenSSL 1.1 - Copyright (C) 1998-2026 The OpenSSL Project (Apache-2.0) - libffi - Copyright (C) the libffi authors (MIT Licence) - Microsoft Visual C++ runtime - redistributable under the Visual Studio redistributable licence The full licence notices, including the build-time components, are published on the Third-Party Notices page of the website: https://rocketcopy.pages.dev RocketCopy itself - Copyright (C) 2026 Long Time No See Studio. All rights reserved.