Dear Dawid, This is usually caused by TortoiseSVN sending an invalid path to the Subversion libraries. Some questions that may help you along
Do you have your working copy on a local disk or on a network drive? Is it stored in the drive root or in another folder? Can you run repair using the command line client? (You can select to install the command line tools when you install TortoiseSVN). The correct command would be svn cleanup C:\[path]\[to]\[working]\[copy] If you can run the repair using the command line client, you should probably report your findings to the TortoiseSVN Google group: https://groups.google.com/g/tortoisesvn Hope this helps! Daniel Sahlberg Den mån 16 mars 2026 kl 07:49 skrev Dawid Ireno <[email protected]>: > Good evening, > > > > I came across one ugly bug in Tortoise SVN. In my scenario I have a big > repo with binaries and I tried pulling it in serveral rounds part by part. > So I downloaded some of binaries, aborted pulling rest of binaries. Than > the other day I performed cleanup and continued pulling further binaries. > This I have repeated few days in a row. But one day cleanup action > exploaded and broke my local repo copy. Attaching screenshot. > > > > Best regards, > > Dawid >
