.exe files within WSL are cached by Windows?

[JerwuQu]

I'm having an issue with building exe files and running them from within WSL.
It seems as if Windows caches the exe files.
I have not seen this happen for other kinds of files.

Here's a small example that works for me to reproduce the issue:

# Setup a shell for cross-compiling to Windows
nix-shell -p pkgsCross.mingwW64.stdenv.cc

# Build a binary `hello.exe` that prints "1"
printf '#include <stdio.h>\nint main(){printf("1\\n");}' > hello.c
x86_64-w64-mingw32-cc -o hello.exe hello.c
./hello.exe # prints "1"

# Build a binary `hello.exe` that prints "2"
printf '#include <stdio.h>\nint main(){printf("2\\n");}' > hello.c
x86_64-w64-mingw32-cc -o hello.exe hello.c
./hello.exe # still prints "1"! cached?

# (in)sanity check
mv hello.exe hello2.exe
./hello2.exe # prints "2" now!

I have tried flipping the wsl.interop.register on and off (with restart), and running from the Windows explorer yields the same result as well.

It's worth mentioning that this only happens when launched from within the WSL disk (e.g. /home/nixos). When done on a Windows disk (e.g. /mnt/c) it works as expected.

Anyone know what's up?

[JerwuQu]

Turning off most switches in Windows Defender fixed it.