Is there some way for nvm4w to identify if CMD is crashing before doing anything?

[idlist]

I just experienced a very frustrating issue that nvm4w does not work on my machine, and the error message is merely:

exit status 1:

and nothing more.

If setting the nodejs symlink to a folder that requires previlege, the error message would become:

exit status 1:
exit status 1:

After searching for some moment (~2hrs) I realized that it is because the cmd.exe of my computer is crashing immediately when I start it, and I never noticed it as I use PowerShell daily but not CMD.

Then I searched for another hour to find that it's that I previously installed Anaconda and uninstalled it that caused this problem
(source). After fixing my CMD, nvm4w works again normally, but the whole investigation still takes a full night of mine... and thus this question.

The thing is the tool can be used in PowerShell, but still requires a working CMD. Without a properly-working CMD, nvm use would simply crash without any error message, and there are some chance to cause CMD not working properly.

Though the cause might not be the same, I believe discussion#996 faced a similar situation of mine, so I'm here to raise this discussion.