ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

'zowe' is not recognized as an internal or external command

book

Article ID: 240943

calendar_today

Updated On:

Products

Brightside

Issue/Introduction

Zowe command not working after Installing ZOWE via NPM method on windows OS.

C:\>npm install -g prebuild-install

added 59 packages, and audited 60 packages in 12s

7 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

V:\>npm install -g @zowe/[email protected]

added 306 packages, and audited 307 packages in 2m

20 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

 

V:\>zowe --version
'zowe' is not recognized as an internal or external command,
operable program or batch file.

V:\>zowe
'zowe' is not recognized as an internal or external command,
operable program or batch file.

V:\>where zowe
INFO: Could not find files for the given pattern(s).

 

Cause

ZOWE CLI npm path (C:\Users\XXXXXX\AppData\Roaming\npm) is not included in the windows PATH environment variable. 

 

Environment

Release : 3.0

Component : ZOWE COMMAND LINE INTERFACE

Resolution

.Update Windows PATH environment variable to include the ZOWE CLI npm path.

https://api-broadcom-ca-user.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=6pZ+QP5v5Sqm77EFgNmMgw==

https://api-broadcom-ca-user.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=G8XTt1QTkNVsIzrilPGkHg==

Open new CMD window then issue zowe command:

https://api-broadcom-ca-user.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=H3IRJlZozwQ8eZM/eFAM7Q==