Can someone explain this odd (anti)pattern?
Very occasionally, and really only with very process-bound organizations, I run into a Policy that states that software must be installed onto D: and not C:.
No one is ever able to explain what benefit this creates.
OTOH, one lesson I've learned from 30 years in this world is that disregarding norms often exposes you to failures and issues due to brittle code or assumptions made by other tools or whatever.
Consequently, from MY POV, a policy like "apps must go on D:" should have a VERY clear benefit for it to be worth the additional hassle & loss of standardization that it brings.
What is that benefit?
(Now, again, I'm the vendor. If you want to install our tool on the Q: drive it's your choice. Our tool doesn't care. It just seems weird and wrongheaded to me and I wonder what the motivation is beyond "that's policy.")