Vitaliy Leschenko

I rolled back my servers (on my test cluster) to 10.0.17763.1294 and can say that all windows pods are reachable after reboot. ``` PS C:\Users\v.leschenko> kubectl get nodes -owide NAME...

/assign @andyzhangx

As I see in logs SMBUnmount calls twice: ``` I0629 21:49:06.107793 8176 safe_mounter_windows.go:117] SMBUnmount: local path: c:\var\lib\kubelet\pods\333c440a-ffc8-421e-9d45-e04aff8a9d34\volumes\kubernetes.io~csi\pv-smb\mount I0629 21:49:41.004132 8176 safe_mounter_windows.go:148] Remove directory: c:\var\lib\kubelet\pods\dec84d2f-d2e2-4f1e-ab72-1a3a5dd33845\volumes\kubernetes.io~csi\pv-smb\mount I0629 21:49:43.479884 8176 safe_mounter_windows.go:117] SMBUnmount: local...

@andyzhangx currently we run unit tests with old `csi-proxy`: https://acs-mirror.azureedge.net/csi-proxy/v1.1.1/binaries/csi-proxy-v1.1.1.tar.gz Can you build new `csi-proxy` to try run tests on both of proxies?

> @vitaliy-leschenko does this PR depend on master branch csi-proxy? No, but I want to be 100% sure.

You have to use Windows Server 2022 images. Windows 11 supports to run it in hyperv and process isolation level.