I just pushed an update that removes the right-click context menu integration and adds SHA-256 post-copy verification.
Why remove the context menu?
The context menu worked by spawning a short-lived process on right-click that queried Explorer's COM interface to find out what you'd selected. The problem: that process raced against Explorer's own foreground state. Most of the time it was fine. Sometimes especially if the menu opened quickly or the system was under load it grabbed the previous selection instead of the current one. You'd right-click a folder, hit Quick Copy, and it would silently queue the wrong folder for copy. I can't ship a file operation tool that fails silently like that. So I pulled it until I can make it reliable.
What was added instead: SHA-256 verification
After a copy finishes, RoboExtension can optionally re-read every destination file and compare SHA-256 hashes against the source. Any file with a mismatched hash is flagged in a results dialog, listed with its error, and offered a one-click re-copy. Enable it in Settings "Verify files after copy (SHA-256)". It's off by default because it roughly doubles elapsed time on large jobs but when you're archiving irreplaceable files, migrating drives, or copying over a network you don't fully trust, it's the only real confirmation that your copy actually worked.
Hey PH! 👋 I'm the solo developer behind RoboExtension.
The problem that broke me: copying a folder with thousands of small files mixed with large ones in Windows Explorer. Jobs that take days — with no assurance they'll finish. One locked file stalls everything. A vague error appears. You don't know how far it got, what actually made it through, or whether starting over will even help. So you babysit it, retry it, and lose days you won't get back.
I benchmarked every alternative I could find — TeraCopy, FastCopy integrate with Explorer like RoboExtension does, and Robocopy covers the CLI side. The integrations work, but on mixed small-and-large file workloads the gains weren't what I needed. And none of them handle locked files the way I wanted — identify the locking process, let me retry or skip, and keep going.
So I built RoboExtension. It integrates with your existing Explorer shortcuts so nothing changes about how you work. The performance numbers surprised even me during development — small-file copies run up to 10× faster than Explorer, and same-volume moves are up to 406× faster. The move gains in particular don't scale with file count or size, which is why the number looks absurd but is real.
Happy to answer any questions about how it works, what it doesn't handle yet, or the benchmarking methodology. What file operation frustrates you most on Windows?
RiteKit Company Logo API
@ghiffaryr The silent file drop issue is a nightmare scenario that probably affects way more people than realize it. Your approach of building into existing Explorer shortcuts makes a lot of sense — adoption friction is usually what kills productivity tools. Curious if you've had users test this in enterprise environments where file integrity auditing is critical, or if that's still on the roadmap.
@osakasaul Yeah, I just shipped this file verification!