Cannot find nodejs in Path variable on Windows Runner 22

[denny-snapone]

I set up a simple workflow:
- uses: actions/setup-node@v4
- name: node version
run: node -v

It then has the error:

Run node -v
node -v
shell: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.EXE -command ". '{0}'"
Refreshing environment variables from the registry for powershell.exe. Please wait...
Finished
node : The term 'node' 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 C:\actions-runner_work_temp\ccd1c392-40b0-4647-8d9b-6d156a848202.ps1:2 char:1

• node -v

•   + CategoryInfo          : ObjectNotFound: (node:String) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : CommandNotFoundException
  
  

Error: Process completed with exit code 1.

I check the $env:Path don't have the node path.

[stuartp44]

In most cases, developers should setup their environment as they require it. With this subject, typically you would install node and the version your require as part of your job. If that is not how you want to approach it, you could install it into the AMI by the use of the Packer builds. If installed correctly aka in the path as you correctly pointed out, it would be available for all jobs that run in that runner.