Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesNode.js lets you run JavaScript outside the browser, and npm gives you access to a huge ecosystem of packages for building apps, tools, scripts, and development workflows. On Windows 11, the easiest setup is usually the official Node.js installer, which installs both Node.js and npm together and can automatically configure the system PATH.
This guide walks through choosing the right Node.js version, downloading and running the Windows installer, verifying that both node and npm work from the terminal, and setting up a simple npm-based workflow. It also covers common Windows 11 issues such as commands not being recognized, PATH problems, outdated npm versions, and version mismatches.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Node.js Logo - Node JS - Nodejs Programmer Software Engineer T-Shirt | $19.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Check System Requirements and Choose a Node.js Version
Before installing Node.js on Windows 11, confirm that your system is ready and decide which Node.js release line you want to use. Windows 11 is fully supported by current Node.js releases, and in most cases the setup is straightforward: you need a 64-bit Windows installation, a user account with permission to install software, and a working internet connection to download the installer. Most modern Windows 11 PCs meet these requirements by default.
To check your system type, open Settings, go to System > About, and look for System type. It should say 64-bit operating system. Node.js for Windows is distributed as an MSI installer, and the standard download from the official website is designed for 64-bit systems. You should also make sure Windows is reasonably up to date, since current Node.js versions depend on modern Windows components and security updates.
#1 Best Overall
- Node.js Programming design. Node.js logo for Nodejs programmers.
- Node JS logo design.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Choose between LTS and Current
The Node.js website usually offers two main download options: LTS and Current. For most Windows 11 users, the LTS version is the best choice. LTS stands for Long Term Support, which means the release is maintained for stability, security fixes, and compatibility over a longer period. This is ideal if you are learning Node.js, building production applications, following tutorials, or working with common frameworks such as Express, Next.js, NestJS, Vite, or React tooling.
The Current version includes newer features sooner, but it may change more frequently and can expose compatibility issues with some npm packages. It is better suited for developers who specifically need the newest Node.js features or want to test packages against upcoming runtime behavior. If you are unsure, install the LTS version first. You can always change versions later using a version manager or by installing a different release.
| Option | Best for | Recommended for beginners |
|---|---|---|
| LTS | Stable development, tutorials, production apps, common npm packages | Yes |
| Current | Testing newest features and upcoming Node.js changes | No, unless required |
Check whether Node.js is already installed
If you have used JavaScript tools before, Node.js may already be installed on your PC. Open Windows Terminal, Command Prompt, or PowerShell, then run node -v and npm -v. If both commands return version numbers, Node.js and npm are already available. If Windows says the command is not recognized, Node.js is either not installed or its installation folder is not included in the PATH environment variable.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →When an older version is already installed, compare it with the version recommended on the official Node.js download page. Older Node.js releases can cause package installation errors, framework warnings, or unsupported engine messages when running modern development tools. If you plan to follow current tutorials or start a new project, use an active LTS version. Keeping Node.js on an actively supported release helps avoid problems with package compatibility, security updates, and npm behavior on Windows 11.
Download Node.js for Windows 11
Once you know which Node.js release line you want to use, download the Windows installer from the official Node.js website. Open your browser and go to https://nodejs.org. The homepage usually detects Windows automatically and shows a recommended download button for the current LTS version. For most Windows 11 users, the LTS installer is the best choice because it is stable, widely supported by npm packages, and suitable for development work, learning, automation scripts, and production-like local setups.
Click the Windows Installer option to download the .msi file. On most modern Windows 11 PCs, you should choose the 64-bit installer, often labeled as x64. If you are using an ARM-based Windows device, such as some Snapdragon-powered laptops, check whether the Node.js downloads page offers a suitable ARM64 build. You can confirm your system type by opening Settings, selecting System, then About, and looking at System type.
Choose the right download from the Node.js website
- LTS: Recommended for most users because it prioritizes stability and package compatibility.
- Current: Includes newer features sooner, but may be less ideal if you need maximum compatibility with tutorials, frameworks, or existing projects.
- Windows Installer (.msi): Best for a standard Windows 11 setup because it installs Node.js, npm, and the required PATH entries through a guided wizard.
- Windows Binary (.zip): Useful for portable or custom setups, but not recommended for beginners because you must configure paths manually.
If you need a specific Node.js version rather than the default button on the homepage, open the Download or Previous Releases page on the Node.js website. This is useful when a project requires a particular major version, such as Node.js 18, 20, or 22. In that case, download the matching Windows .msi installer for your system architecture. Avoid downloading Node.js installers from third-party software sites, as they may be outdated, repackaged, or bundled with unwanted tools.
After the download finishes, locate the installer in your Downloads folder. The filename will usually include the Node.js version and architecture, such as node-v20.x.x-x64.msi. You do not need to download npm separately when using the official Windows installer; npm is bundled with Node.js and will be installed as part of the setup. Keep the installer available until you have completed the installation and verified both node and npm from the Windows Terminal or Command Prompt.
Install Node.js and NPM Using the Windows Installer
After downloading the Windows installer from the official Node.js website, run the .msi file to start the setup wizard. Windows may show a security prompt asking whether you want to allow the installer to make changes to your device. Select Yes to continue. The Node.js Setup Wizard will open and guide you through the installation process for both Node.js and npm, since npm is bundled with the standard Node.js installer for Windows.
On the welcome screen, select Next, then review and accept the license agreement. When prompted to choose an installation location, the default path is usually best for most users:
- C:\Program Files\nodejs\
Keeping the default location makes troubleshooting easier because many guides, tools, and environment settings expect Node.js to be installed there. If you choose a custom folder, make sure it is a location your Windows user account can access without permission issues.
Recommended Free Tools
Select the Installation Features
The setup wizard will show a list of components to install. For a normal Windows 11 setup, leave the default selections enabled. These typically include the Node.js runtime, npm package manager, documentation shortcuts, and the option to add Node.js to your system PATH. The PATH option is especially because it lets you run commands such as node and npm from Command Prompt, PowerShell, Windows Terminal, or Visual Studio Code.
- Node.js runtime: Installs the Node.js executable used to run JavaScript outside the browser.
- npm package manager: Installs npm so you can download and manage packages.
- Online documentation shortcuts: Adds quick links to Node.js documentation.
- Add to PATH: Allows Windows terminals to recognize Node.js and npm commands.
You may also see an option to install additional tools for native modules, often involving Python and Visual Studio Build Tools. These tools are not required for basic Node.js and npm usage. However, some npm packages compile native code during installation. If you plan to work with packages that depend on native add-ons, you can select this option, but it may take longer and download extra components.
Complete the Installation
Click Next, then select Install. The installer will copy files, register Node.js, install npm, and update your Windows environment variables. This usually takes less than a minute on most Windows 11 systems. When the wizard finishes, select Finish. If you selected additional build tools, a separate script or PowerShell window may open to continue installing those dependencies.
Before testing the installation, close any open Command Prompt, PowerShell, Windows Terminal, or code editor windows. Then reopen your terminal. This refreshes the environment so Windows can detect the updated PATH setting. You are now ready to verify that Node.js and npm were installed correctly by checking their versions from the command line.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallVerify Node.js and NPM Installation
After the Windows installer finishes, verify that both Node.js and npm are available from the command line. Open a new terminal window so Windows loads the updated environment variables. You can use Windows Terminal, Command Prompt, or PowerShell. If you had a terminal open during installation, close it and open a fresh one before running any checks.
Run the following commands one at a time:
- node -v checks the installed Node.js version.
- npm -v checks the installed npm version.
Each command should print a version number. For example, Node.js may return something like v22.11.0, while npm may return something like 10.9.0. The exact numbers depend on the Node.js release you installed, but both commands should complete without an error. If you installed the LTS version, the Node.js version should match the LTS release shown on the official Node.js download page.
Confirm Where Node.js and NPM Are Installed
If the version commands work, you can also confirm which executable Windows is using. This is useful when you have installed Node.js before, used a version manager, or have mulle development tools on the same machine. In Command Prompt, run:
- where node
- where npm
In PowerShell, the same commands usually work, but you can also use Get-Command node and Get-Command npm. A standard installer setup commonly points to a path such as C:\Program Files\nodejs\node.exe. If you see several results, Windows will use the first one listed. That can affect which Node.js version runs when you type node.
Test Node.js with a Simple Command
Version checks confirm the tools are found, but a quick runtime test confirms Node.js can execute JavaScript. In your terminal, run:
node -e “console.log(‘Node.js is working’)”
If Node.js is installed correctly, the terminal prints Node.js is working. You can also start the interactive Node.js prompt by typing node and pressing Enter. At the > prompt, type 1 + 2 and press Enter. It should return 3. To exit, type .exit or press Ctrl + C twice.
Check NPM with a Basic Command
To confirm npm can read its configuration and connect to its default registry settings, run:
Free tools Windows power users keep installed
One-click scans. No signup required.
- npm config get registry
- npm help
The registry command should usually return https://registry.npmjs.org/. The help command should display npm usage information. At this stage, you do not need to install any packages yet; you are only confirming that npm starts correctly and can access its configuration.
If the Commands Are Not Recognized
If Windows returns ‘node’ is not recognized or ‘npm’ is not recognized, restart the terminal first. If that does not work, restart Windows. The installer normally adds Node.js to the system PATH, but the current shell may not have refreshed. If the issue continues, open Settings, search for Environment Variables, and check that C:\Program Files\nodejs\ appears in the Path variable. After making changes, open a new terminal and run node -v and npm -v again.
Update NPM and Configure Basic Settings
After confirming that Node.js and npm run from PowerShell, Windows Terminal, or Command Prompt, it is a good idea to check whether npm itself has a newer stable release. The Node.js installer includes npm, but npm can be updated independently. Open a new terminal window and run the update command below. Using a fresh terminal ensures Windows loads the latest PATH settings created during installation.
Update npm globally:
npm install -g npm@latest
When the command finishes, verify the active version:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →npm -v
If the version number changes, the update worked. If Windows still reports the old version, close every open terminal window and open a new one. In some cases, you may also need to restart Windows Terminal or your code editor because integrated terminals often keep the old environment variables until the application is relaunched.
Set your npm package defaults
npm stores user-level preferences in a configuration file named .npmrc. You do not need to edit this file manually for basic setup; the npm config command can update it for you. These settings are useful when you create new projects with npm init, because npm can prefill common package metadata.
- Set your author name:
npm config set init-author-name "Your Name" - Set your author email:
npm config set init-author-email "[email protected]" - Set the default license:
npm config set init-license "MIT" - View all current settings:
npm config list - Check one setting:
npm config get init-author-name
For most Windows 11 users, the default npm registry should remain unchanged. You can confirm it with npm config get registry. The standard value is https://registry.npmjs.org/. If you previously used a company registry, school proxy, or mirror service, package installs may fail or pull from the wrong source. To restore the default registry, run npm config set registry https://registry.npmjs.org/.
Check the global package location
Global npm packages install command-line tools that can be used from any folder. On Windows, the global npm location is commonly under your user profile, such as C:\Users\YourName\AppData\Roaming\npm. To inspect it, run:
npm config get prefix
If you install a global package and Windows says the command is not recognized, the global npm folder may not be in PATH. The official Node.js installer usually handles this automatically, but user-level PATH entries can be changed by other development tools. You can also avoid many global PATH issues by using npx, which runs package binaries without permanently installing them globally.
Create a clean project folder setting
Before installing packages, choose a simple workspace location such as C:\Users\YourName\projects or C:\dev. Avoid placing active Node.js projects inside protected folders like C:\Program Files, because npm may run into permission problems when creating node_modules or updating lock files. A normal user-owned folder keeps installs predictable and reduces the need to run the terminal as administrator.
You now have an updated npm installation and a basic configuration ready for project work. The next step is to create a small test project, install a package locally, and confirm that npm can download dependencies and run package commands correctly on Windows 11.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Install and Test Your First NPM Package
After Node.js and npm are working on Windows 11, the next step is to create a small project and install a package from the npm registry. This confirms that npm can create project metadata, download dependencies, write to the local project folder, and run package scripts correctly. Use a normal user folder such as Documents or Desktop rather than protected locations like C:\Program Files.
Open Windows Terminal, PowerShell, or Command Prompt, then create a new project folder. The following commands create a folder, move into it, and generate a default package.json file:
mkdir npm-test
cd npm-test
npm init -y
The package.json file is the control file for a Node.js project. It stores the project name, version, scripts, and dependency list. The -y option accepts npm’s defaults so you can start quickly. You can open the folder in Visual Studio Code with code . if the VS Code command-line launcher is installed.
Install a package locally
For a simple test, install cowsay, a small command-line package that prints text in a speech bubble. Run this command inside the npm-test folder:
npm install cowsay
When the install finishes, npm adds the package to node_modules, records the dependency in package.json, and creates or updates package-lock.json. The lock file stores exact package versions so the same dependency tree can be restored later with npm install.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Run the package with npx
You can test the installed package without installing it globally by using npx. Run:
npx cowsay "Node.js and npm are working on Windows 11"
If everything is configured correctly, the terminal displays the message inside an ASCII cow speech bubble. This confirms that npm installed the package and that Node.js can run the package executable from the project’s local dependencies.
Add a reusable npm script
Most Node.js projects use scripts so common commands can be run consistently. Open package.json and add a script named test:cowsay. Your scripts section should look similar to this:
"scripts": {
"test:cowsay": "cowsay \"Hello from npm scripts\""
}
Save the file, then run the script from the terminal:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsnpm run test:cowsay
This workflow is the basis for many JavaScript projects on Windows 11. Instead of typing long commands directly, you place them in package.json and run them with npm run. Build tools, test runners, linters, formatters, and development servers commonly work this way.
Local packages vs global packages
| Install type | Command | Best use |
|---|---|---|
| Local | npm install package-name |
Project dependencies that should be listed in package.json |
| Global | npm install -g package-name |
Command-line tools you want available across many folders |
| Temporary runner | npx package-name |
Running a package command without manually managing a global install |
For most projects, prefer local installs. They make your project easier to share because another developer can clone the folder and run npm install to restore the same dependencies. Use global installs only for tools you intentionally want available from any terminal location.
Troubleshoot Common Node.js and NPM Issues on Windows 11
Most Node.js and npm problems on Windows 11 come from PATH configuration, mulle Node.js installations, permissions, proxy settings, or cached package data. Start troubleshooting in a fresh Command Prompt or PowerShell window, because terminals opened before installation may not detect updated environment variables. Run node -v and npm -v first to confirm whether Windows can find both commands.
Fix “node is not recognized” or “npm is not recognized”
If Windows shows a message such as node is not recognized as an internal or external command, the Node.js installation folder is probably missing from PATH. Open Settings → System → About → Advanced system settings → Environment Variables. Under System variables, select Path, choose Edit, and confirm that the Node.js folder exists, typically:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →- C:\Program Files\nodejs\
- %AppData%\npm for globally installed npm command-line tools
If either entry is missing, add it, save your changes, close all terminal windows, and open a new one. Then run where node and where npm to see which executable Windows is using. If the output lists old paths, uninstall older Node.js versions or move the current Node.js path higher in the PATH list.
Resolve version conflicts and broken npm installs
Version mismatches can happen when Node.js was installed by the official Windows installer, a package manager, or a version manager at different times. Use where node to find duplicate installations. Keep one primary installation method whenever possible. If npm reports unusual errors after an upgrade, clear the npm cache with npm cache verify. For persistent cache issues, use npm cache clean –force, then retry the install command.
| Problem | Command or action |
|---|---|
| Check Node.js version | node -v |
| Check npm version | npm -v |
| Find active Node.js path | where node |
| Find active npm path | where npm |
| Validate npm cache | npm cache verify |
Handle permissions, script, and network errors
If npm fails while installing global packages, try using a normal user-level workflow instead of relying on administrator access. For project tools, prefer local installs with npm install package-name inside your project folder, then run commands through npx or package scripts. If PowerShell blocks a command from a globally installed tool, the execution policy may be restricting scripts. Run PowerShell as your user and check the policy with Get-ExecutionPolicy. A common user-level setting is Set-ExecutionPolicy RemoteSigned -Scope CurrentUser.
For network errors such as ETIMEDOUT, ECONNRESET, or certificate-related failures, test your internet connection and check whether a corporate proxy, VPN, firewall, or antivirus tool is intercepting npm traffic. You can view npm proxy settings with npm config get proxy and npm config get https-proxy. If incorrect values are set, remove them with npm config delete proxy and npm config delete https-proxy. After making changes, restart the terminal and run npm ping to confirm npm can reach the registry.
Frequently Asked Questions
Does installing Node.js on Windows 11 automatically install npm?
Yes. The official Node.js Windows installer includes npm by default, so you do not need to install npm separately. After installation, open a new Command Prompt or PowerShell window and run node -v and npm -v to confirm both tools are available.
Should I install the LTS or Current version of Node.js?
Most Windows 11 users should install the LTS version because it is more stable and better supported by popular npm packages. The Current version includes newer features, but it may introduce compatibility issues in some projects. Choose Current only if you specifically need the latest Node.js features.
What should I do if Windows says node or npm is not recognized?
Close and reopen Command Prompt, PowerShell, or Windows Terminal first, because PATH changes often require a new terminal session. If that does not work, check that Node.js is installed in a folder such as C:\Program Files\nodejs\ and that this folder is included in your system PATH environment variable. You can also rerun the Node.js installer and make sure the option to add Node.js to PATH is enabled.
Can I install multiple versions of Node.js on Windows 11?
The official installer is best for a single Node.js version, but developers who switch between projects often use a version manager. On Windows, common choices include nvm-windows or Volta. These tools let you install and switch Node.js versions without manually uninstalling and reinstalling Node.js each time.
Where are npm packages installed on Windows 11?
Packages installed for a project are stored in that project’s node_modules folder and listed in package.json. Global packages are installed in npm’s global directory, which you can check with npm root -g. For most development work, prefer local project installs so dependencies stay tied to the specific project.
Bottom Line
Installing Node.js on Windows 11 with the official installer is the simplest way to get both Node.js and npm ready for development. After installation, verify everything with node -v and npm -v, then create a test project with npm init to confirm your workflow is working.
If commands are not recognized or versions look wrong, restart your terminal, check your PATH settings, or reinstall the LTS version from the official Node.js website. Once Node.js and npm are working correctly, you can start installing packages, running scripts, and building JavaScript projects on Windows 11 with confidence.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
