I think it will be hard for us to help here.
The reason why resource-disposer is not able to delete things might be found in your Jenkins logs (not the job logs) or the agent logs.
What you should try is log on to a windows machine as the user that is running the builds and try to delete the things manually. Maybe you have some files with wrong ownership.
Virus scanners can also make problems though I would assume that the resource disposer has some retry mechanism.
The problem with Windows file system is that files that are opened by a process can’t be deleted usually, so maybe you might also want to use something like ProcessExplorer and check if any process holds open files handles on the things that should be deleted.
I’ve tried using the user that connects the agents to the controller, and it was able to delete the folders manually.
We are facing this issue on both of our Windows and Linux agents.
May I ask if you are aware where exactly are the Logs located that I should look for on inside of the controller server? to find issues related to the resource-disposer
I would expect that those errors are logged to the default Jenkins log or the agent log.
For the Jenkins log it depends a bit how you run jenkins, e.g. when you run it as a systemd service in Linux you should be able to see the logs with journalctl -u jenkins
The agent logs are accessible from the UI
