The term 'cl' is not recognized... (checked similar topics)

[murilojones]

Hey guys, I am stuck in the video of the VS code installation. So I know the common issue for this error, after checking other similar posts, but it doesn’t seem to apply here.

First this is the error I am getting:

Important to know: I have installed Visual Studio Community 2019, I have checked the same boxes as the instructor did when doing it.

I installed VS code. I checked the same boxes as the instructor did also.

I have opened VS code through “Developers Command Prompt for VS2019” and then typing “code”

When Code is opened the screen is different from the instructor, as everytime I open through developers prompt, it opens with some file in it: “cli.js”

I tried just ignoring this and going to terminal>new terminal, typing cl and pressing enter

and also tried closing this file first before doing it… anyway gives me the same result.

It was happening yesterday, today I uninstalled VS code, VS community 2019 and tried installing again. Same result.

Please help me.

terminal log:
cl : The term ‘cl’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the
name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

• cl
• ~~
  • CategoryInfo : ObjectNotFound: (cl:String) , CommandNotFoundException
  • FullyQualifiedErrorId : CommandNotFoundException

edit: I also noticed that when I type code in the developers command prompt, and press enter, the prompt window shows some stuff that the instructor does not show:

[DanM]

Are you the person on Discord that got this sorted?

[murilojones]

Yes!

So, If anyone has this same problem, I figured that if you run Developers command prompt as an administrator, you will end up with a prompt showing the C:\Windows\System32>

if you change directory to the one Visual Studio is installed (in my case: C:\Program Files (x86)\Microsoft Visual Studio\2019) and then entering the “code” command opening visual code, it will fix this.

I tried not running the prompt as an administrator, to see if only changing directory would do it, but it don’t.