Rebase/Cherry-pick with conflict in renamed file

What steps will reproduce the problem?

1. Create a new empty repository.
2. Create a new file "test.txt" and fill it with some random text.
3. Add and commit the file.
4. Create a new branch "Featurebranch".
5. On branch "master" edit the file "test.txt" in line 1 and commit the changes.
6. Checkout "Featurebranch".
7. Edit the file "test.txt" and change something different in line 1, so that it will cause a conflict with the changes in master later. Now rename the file to "test_renamed.txt". Commit both changes as single commit.
8. Now either rebase onto master or checkout master and cherry-pick the commit from Featurebranch. File "test.txt" will be marked as deleted, file "test_renamed.txt" will be marked having a conflict.
9. Mark the conflict as resolved and commit the changes.

What is the expected output? What do you see instead?

The "Git Command Progress" window will show:

git.exe rm --ignore-unmatch [...]

fatal: not removing '.' recursively without -r

git did not exit cleanly (exit code 128)

Also, double clicking on the resolved file "test_renamed.txt" in the "Rebase" window now opens a message:

Failed to checkout file "" of revision to "C:\Users<username>\AppData\Local\Temp\TortoiseGit\FD7A.tmp-03ed335-left".

libgit2 returned: Invalid tree path given

What version of TortoiseGit and Git are you using? On what operating system?

TortoiseGit 2.1.0.0

git version 2.7.4.windows.1

Windows 10 Pro (64bit)

Please provide any additional information below.

After aborting the rebase/cherry-pick, steps 8 and 9 can be done in git bash without problems.