Can/Should Powershell tell you about missing DLLs when running exectuables?

[Thomasedv]

Sorry if this is too odd of a question. Quick backstory, first time using the Rust language and I compiled a program that worked when I ran Cargo Run. But running the executable in PowerShell did absolutely nothing. Turns out, the cargo run command made some folders with dll files available that normal execution did not.

Since it was a command line program I never clicked to run it, but when I did or ran it in CMD, Windows actually gave me a dialog telling me about missing dlls for the executable. Had it done so in PowerShell I'd save a lot of troubleshooting. And I'd rather not have to go to CMD just to check this when PowerShell is such a better program to just use in all other aspects.

So, this logic may be both Windows specific, rely on old obscure Windows logic, and a extremely specific request that may be unreasonably tough to implement. Is it worthy of being a feature in PowerShell? I'd love to have it just because it's new for me to deal with issues like this and the last thing I expected was for CMD to inform me while PowerShell did not.