The docs say that python -m venv c:\path\to\myenv will do a lot; on my system it does nothing.
Could it be that it is confused by my almost empty 5TB drive? No, it doesn’t work on my much smaller primary drive, either. It doesn’t crash, doesn’t give any error messages or other kind of messages at all. It just appears to work and then doesn’t.
What behaviour are you expecting? What happens instead?
You say it “does nothing” but that seems unlikely. I’m not using
Windows, so I suppose this is possibly a Windows issue, but this is what
I get:
[steve ~]$ ls tmp/thing/
[steve ~]$ python3 -m venv tmp/thing/
[steve ~]$ ls tmp/thing/
bin include lib lib64 pyvenv.cfg
Notice that the venv command itself has no output.