It is not clear based on the bug report if you're using the git command line implementation or if you're using the jgit implementation in your project definition. Can you clarify which you are using?
When I use Git plugin 2.0 and git client plugin 1.4.4 and I restrict the job to only run on windows and I add "Wipe out repository & force clone" as an additional action in the git configuration for that job, the first execution of the job succeeds, then all subsequent executions fail with a report that one of the pack files in the git repository is held open by another process and cannot be deleted.
The steps I used to define that failing job:
0 - Configure jgit as an available git implementation in the global configuration
1 - Create a new Jenkins job (I named mine jgit-windows)
2 - Configure the Jenkins job to use Git for SCM
3 - Enter https://github.com/MarkEWaite/check_git.git as the Git URL
4 - Switch from the git command line to jgit as the git executable
4 - Add "Checkout to specific local branch" to the branch master-local as part of the git configuration
5 - Restrict the job to only run on Windows
6 - Add "Wipe out repository & force clone" as part of the git configuration
7 - Save the job
Once the job has been saved, run it twice. The first run will succeed, the second run will fail with a report that pack file is busy