Hi,

we have update the following components in our environment:

Jenkins - 2.462.2 -> 2.479.2 

AKS - 1.29.7 -> 1.31.5

With the current status our pipeline fails (randomly) when we execute multiple stages on a Windows node pool. We use the same pod definition for all the stages in the pipeline. 
In this specify case the checkout with pipeline scm plugin will raise the the error: "java.io.IOException: Unable to create C:\jenkins\remoting\jarCache\0A\4F282D2E63CBDDB7E53F7F9E48103F.jar from C:\jenkins\remoting\jarCache\0A\4F282D2E63CBDDB7E53F7F9E48103F.jar25673425160852021tmp"

-------------
Checking the file system we have seen some differences.
When the stage is executed correctly the C:\Jenkins folder content is:

while in case of a failure the content is:
 

We are struggling to understand the cause. The pod - cloud-node-manager-windows-xxx which it should be managed by Kubernetes have the exact file system posted in the failure scenario.

Our Windows pods mount 2 volumes: