Hi Johannes, thanks for explaining why re-installing fixed my problem. Although I still can't wrap my head around why it happened in the first place. It could only be caused by Windows moving the base address of one, but not the other thus causing the overlap. Sounds weird. But then again, what do I know what's going on under the hoods when upgrading to Win10. ;) In regards to your question: Yes I am running 64bit Windows, but the 32-bit version of git is the only thing I can download. I just double-checked on the webpage, but there's no option to get a 64 bit download link, and if there was some logic determining whether I should get 32 or 64 bit it puts me in the first bucket for some reason. I haven't considered building from source yet, mostly because the 32bit works fine so far. What would be the benefit? I guess performance when dealing with large repos? If you have a 64bit version available and need feedback let know. Always happy to help out :) Cheers, Christoph -----Ursprüngliche Nachricht----- Von: Johannes Schindelin [mailto:johannes.schindelin@xxxxxx] Gesendet: Tuesday, July 14, 2015 10:37 An: Christoph Murczek Cc: git@xxxxxxxxxxxxxxx Betreff: Re: AW: "unable to remap" error with git svn after upgrade to Win10 Hi Christoph, On 2015-07-13 14:24, Christoph Murczek wrote: > Just wanted to let you know: a re-install of git also fixed the problem. That is probably because your original report (which I do not quote because that was made too inconvenient by top-posting, sorry) suggests that the culprit was overlapping `.dll` ranges that need to be fixed using the `rebase.exe` tool (which is confusingly completely unrelated to `git rebase`), and that step is part of the installing process. BTW assuming that you're on a 64-bit setup (Win10 and all...), why do you stick to the 32-bit version of Git for Windows? Ciao, Johannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html