i would advise to use wsl2 for openwrt compilation (or for big buildroot in general as the io perf is bad on plain wsl)
that would also fix any sort of problem....
another idea would be to just add to the whitelist the entire openwrt dir... (no way you can get a virus from that)
I build in a WSL2 instance on a routine basis. (OP wasn't exactly clear as to whether he's using WSL1 - lots of people just say WSL when they are running WSL2...)
The only issue is that you need to remove some stuff from PATH that "make package/install" considers "dangerous"
if defender is scanning wsl compilation process then it's definitely wsl1
about path there is a config in windows to disable the appending of windows PATH to wsl PATH still i don't have that problem
You should end up with a 'Linux' icon in Explorer that you can use to access any WSL2 drives. Alternatively typing \\wsl.localhost into that path/address bar should get you to the same place.
Note that sometimes if you started with WSL1 and upgraded to WSL2, there's a registry key needed related to plan9fs or something like that for \\wsl$ to work
As for moving, you need to use wsl --export to crate the tar.gz, then wsl --terminate to remove it, then you can move it wherever you want via wsl --import. This is helpful for those (like me) who want to build on something other than the boot drive. Be sure to designate WHICH distro you are doing this to via wsl -d <distro> if you have more than 1 WSL distro setup.
EDIT: Because no one (including me) actually addressed part of the OP. Faked is used by fakeroot, which the build environment uses when it does it's thing. Your error is saying it can't find it, it just happens to have an unfortunate name. Follow the Wiki instructions to ensure that you have properly setup the build environment, and see if that doesn't fix the issue