Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node.exe doesn't report it's own file or product version in 19.0.0 #45078

Closed
ALvanti opened this issue Oct 19, 2022 · 6 comments
Closed

node.exe doesn't report it's own file or product version in 19.0.0 #45078

ALvanti opened this issue Oct 19, 2022 · 6 comments

Comments

@ALvanti
Copy link

ALvanti commented Oct 19, 2022

Version

19.0.0

Platform

Windows x64 and Windows x86

Subsystem

No response

What steps will reproduce the bug?

Installed node.js v19 over the top of an v18
image

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

File and product version data filled out.

What do you see instead?

Lack of file and product version

Additional information

No response

@richardlau
Copy link
Member

This is fixed by #45042 and should be corrected in the next 19.x release.

@brerneto
Copy link

brerneto commented Oct 21, 2022

I just installed 19.0.0 for Windows and there is no node executable. Maybe the next release you'll include it instead of fixing it immediately?

Edit: The zip file contains the binary, the windows installer does not.

@liuxingbaoyu
Copy link
Contributor

No, it includes that file.
But I guess it might not be installed correctly for some reason.
I had this problem too, but after I reinstalled everything worked fine.

@ALvanti
Copy link
Author

ALvanti commented Nov 7, 2022

19.0.1 exhibiting the exact same behavior... ? I thought this was already fixed?
switches /qn /norestart used if that makes any difference.
Capture

@richardlau
Copy link
Member

Should be fixed in 19.1.0.

@BethGriggs
Copy link
Member

As mentioned by @richardlau, #45042 shipped in v19.1.0. Closing, as this should be fixed in v19.1.0+.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants