'yarn' is not recognized as an internal or external command, operable program or batch file.

[rhtpandeyIN]

nodejs version: 7.4.0
OS: Windows 7

I installed yarn by using yarn.msi file, and it installed successfully. But when I tried to check yarn version on my system I got following error:
'yarn' is not recognized as an internal or external command,
operable program or batch file.

At first glance I thought it may issue of incorrect PATH or may be PATH is not set by msi. Then I checked my system PATH and I found correct PATH is already there.

Solution: the problem was one extra "\" was missing after bin.
before : C:\Program Files (x86)\Yarn\bin (Not working)
After : C:\Program Files (x86)\Yarn\bin\ (Working)

Please look into the issue. Thanks.

[lubojanski]

nodejs version: 6.5.0 and 7.4.0

Got the same problem,
now the default path was: C:\Program Files (x86)\Yarn.bin
Tried without dot and with/without slash, didn't work.

edit:
installed it by npm install yarn -g

[yfain]

I don't use Windows, but if you install yarn locally, you should run its local version:
./node_modules/.bin/yarn

[rhtpandeyIN]

@yfain , I installed yarn through .msi (windows installer) file, and as per my understanding it should install globally by that, because it (yarn installation directory path) also got registered into the system path automatically. Hence it should recognize as an external command. Although when I changed path like above mentioned way, it got worked.

[locorocorolling]

Same issue as @rhtpandeyIN on windows 7 with node 6.9.1, fixed with same solution

[OutsourcedGuru]

Same issue as @rhtpandeyIN on Windows 7 Professional with node v6.9.5. Opened new command shell hoping that path would have been added—it wasn't. Manually added path to each invocation and it seems to work. I would expect an MSI to update the global path for a Windows install.

[jameswilson281]

Same issue as @rhtpandeyIN on Windows 8.1 with node v7.7.1

[fjoshuajr]

Same issue as @rhtpandeyIN on Windows 7 Ultimate x64 with node v6.9.5. Solved with the same solution.

[trondstroemme]

Same issue as @rhtpandeyIN on Win 10 Pro 64-bit. Resolved as per @lubojanski 's last comment.

[1j01]

Is it possible the solution of adding a backslash is working (for some people) merely by triggering some sort of update? (That the installer isn't, for some reason?) I see a lot of entries in PATH that leave off the backslash including git, nvm, nodejs, and Windows system paths. Does it still work if you change it back?

(#1648 is an older, if somewhat less descriptive issue for this problem.)

[ctcoulter]

posted this on the other read.. if anyone else is running into this issue, might help:

I was bashing my head against this one for a while. Hopefully this helps someone out.

The problem I had was that the installer placed the Yarn files in two locations that were both in my path. > The wrong one was being picked up when trying to execute.

C:\Program Files\nodejs\yarn.cmd
C:\Program Files (x86)\Yarn\bin\yarn.cmd

I just moved the files out of my nodejs directory and it worked. The error message about the path not > being found is most likely due to the %~dp0 from the nodejs directory not being in the right location.

EDIT: to add to this, just went and compared the two that were generated.. the one generated in the nodejs directory had:

@"%~dp0\..\..\Users\chris\AppData\Local\Yarn\config\global\node_modules\.bin\yarn.cmd" %*

The "node_modules" does not exist in my Yarn\config\global directory.

The yarn.cmd generated in the Yarn directory had the following (which does exist):

node "%~dp0\yarn.js" %*

I made sure that there weren't any yarn.cmd files on my hard drive at all before reinstalling via the MSI, so they were both definitely generated by the MSI installation. It might just be some kind of path configuration on my machine that caused it to generate two... but hopefully that's helpful.

[Daniel15]

Hmmm... This is very strange... The trailing backslash shouldn't matter, and the current MSI has worked fine on various VMs I've tested it on, as well as on my Windows build server (which is running Windows Server 2012).

Is it possible the solution of adding a backslash is working (for some people) merely by triggering some sort of update? (That the installer isn't, for some reason?)

@1j01 This is a pretty interesting theory! We're using WiX to build the installer, and a looooot of apps use it (Node.js uses it as well, for example). I wonder if we're hitting some bug in WiX.

[rodrigoBerlochi]

I see also the same issue after installing Yarn v0.24.6
Node v6.9.0
'yarn' is not recognized as internal or external command :(
I used the msi installer for Windows.

[Daniel15]

@rodrigoBerlochi Can you please check your path and ensure c:\Program Files (x86)\Yarn\bin was added to it?

[TrevorScrews]

I'm getting this error when trying to run yarn in powershell. The path that was added is to my AppData folder. I changed it to the c:\Program Files (x86)\Yarn\bin and still got this error. When running from the command line, it works. I didn't try from command line until the path was changed, so I'm not sure if it would have worked with the other path or not.

Node: 6.8.0
Yarn: 0.27.5