ifernandezcalvo thanks again!

As per your suggestion, I updated my start shell script to:

#!/bin/bash
nohup /home/jenkins/jdk8/bin/java -jar /home/jenkins/jenkins.war --httpPort=8081 --extractedFilesFolder=/tmp > /home/jenkins/jenkins.log 2>&1 &

Now the extra winstone jars are cleaned up on startup, I also tested a safeRestart and again there was only 1 winstone jar file (for the running Jenkins).

So it's solved for me, cheers!

This issue is happening with my current Jenkins build 2.156 on windows. Is there any solution for windows for this. 

Disk is getting full, due to so many winstone*.jar in C:\...\AppData\Local\Temp folder

shashankkulsh Did you read the comment before yours? there you have the solution *--extractedFilesFolder=c:\TMP-FOLDER-PATH*

Is there any plan to fix this? Seems wonky that Jenkins knows where to write the jar, but not where to go to delete it.

I just had my Windows 2012R2 Jenkins 2.257 server fall to its knees for the second time in a week after something threw a spanner at Jenkins (started as a service). Jenkins was convinced that it needed to restart itself, which failed due to address already in use, so try again and again and again, dumping a new copy of winstone#.jar each time until out of disk space.

This bizarre behavior seems to be the result of how the Jenkins service is created by default, first failure: restart, second failure: restart, subsequent failures: restart.

For now I've set subsequent failures to 'take no action' - hopefully this will ease the pain.