0 Replies Latest reply on Feb 6, 2017 10:06 PM by VeilCloud

    cmd.exe - bug or by default - Application Manager


      I open cmd.exe and you try to open a file from the prompt e.g. c:\temp>Newfile.txt or c:\temp>myfile.xlsx it will not launch the files without using the responsible file executable in front of the file path e.g. c:\temp>notepad.exe newfile.txt or c:\temp>msexcel.exe myfile.xlsx, is this a bug or default behaviour?


      I would think that file type association would handle this and launch the required executable for the file being opened but it looks like it thinks cmd.exe is the executable responsible to launch the file of which it wouldn't open any files without specifying the executable responsible for that file type.


      Any assistance or guidance much [email protected]