Install directory permissions broken on non-English Windows systems #39224
Comments
targos
added
install
|
Similar. Cannot upgrade from 14.17.1 to 14.17.2
|
|
I also have the same problem, could you help me |
|
Also just encountered this issue. Neither the long term support, nor the latest version work and give the same error message as in the images shared by DvdGiessen and web2933. |
For what it's worth: I encountered the same issue when trying to upgrade from 14.17.1 LTS to 14.17.2 LTS, x64 version of the installer. Operating system is Windows 10 Home Edition, version 20H2, 64 bit. Language is German. Just making a guess here, but the problem may be related to commit d0b449d which includes a fix for "CVE-2021-22921: Windows installer - Node Installer Local Privilege Escalation (Medium)". At least that is the only change mentioned in the changelog for 14.17.2 and 16.4.1 that references installation on Windows systems. |
|
Same problem here with both msi installers (32 and 64 bit) and Windows in spanish |
|
I can confirm it must be a recent change: 16.4.0 and older still work, only 16.4.1 produces this issue. |
|
Is it possible to download the bug free version? Or is there any workaround? |
|
How about using https://github.com/coreybutler/nvm-windows to install Node.js? |
Thinking about that, i could bypass this error by installing a previous release: https://nodejs.org/download/release/v14.17.1/ |
The old versions are still available, for example: |
|
I got the same problem when trying to install the x64 versions 4.17.2 LTS and 16.4.1 on Windows 10 Home Single Language (21H1) (Brazilian Portuguese). But I managed to install normally the 4.17.1 version that I downloaded at: https://nodejs.org/dist/v14.17.1/node-v14.17.1-x64.msi |
|
/cc @kumarak @nodejs/platform-windows And @nodejs/releasers because I think we'll want to publish a new release as soon as this is fixed. |
|
A stupid workaround is to create a user called "Authenticated Users". The new user can be removed right after the setup. 🤦 |
|
Installed 16.4.0 for now. Awaiting a fix. |
|
I confirm, both 14.17.2 and 16.4.1 are unable to install on a French windows 10 system due to the lack of an 'Authenticated Users' group. |
same with Hungarian windows |
|
Hello, really the problem was solved when creating the user "Authenticated Users", however, in my case, I needed to install node via command line with chocolatey. |
|
Confirm too on Windows 7 (Russian Version). |
|
I've spent a day trying to install 14.17.2. I even reinstalled windows with no result. I think it is a bad idea to keep it updated |
|
The problem does appear to have been introduced in e817ba7 (fix for CVE-2021-22921) on non-English Windows. There are a few folks investigating the issue. Once an amended patch is available we will issue a new release for each release line. |
|
same problem here |
Muito obrigado !! Funcionou muito bem a instalação com essa linha de comando |
|
Muito OBRIGADOOO !!! Excelente dica. |
|
I had the same issue yesterday and "installed" it via binaries, added to path and run |
Well known user account names are localized on Windows. Look up the "Authenticated Users" user by its security identifier to get the localized name. PR-URL: nodejs#39241 Fixes: nodejs#39224 Refs: nodejs@e817ba7 Refs: https://hackerone.com/reports/1211160 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com>
Well known user account names are localized on Windows. Look up the "Authenticated Users" user by its security identifier to get the localized name. PR-URL: #39241 Fixes: #39224 Refs: e817ba7 Refs: https://hackerone.com/reports/1211160 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com>
Well known user account names are localized on Windows. Look up the "Authenticated Users" user by its security identifier to get the localized name. PR-URL: #39241 Fixes: #39224 Refs: e817ba7 Refs: https://hackerone.com/reports/1211160 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com>
Ne is mondd, kiégek....mire rájöttem mi a gond:D |
|
node-v16.4.0-x64 : working |
|
Run the command prompt as an administrator and ctrl+c/ctrl+v: |
|
Same problem with 14.17.2 LTS ! |
You are right @Eduardo-Carregoza, Thanks 👌🏽 |
|
👋 The release team are aiming to get releases out later today to fix the regression with the Windows installer. I suggest folks wait for those, rather than create dummy users. |
|
Fixed releases for 12.x and 14.x are out. Waiting on 16.x but shouldn't be too long. |
|
https://nodejs.org/dist/v14.17.3/node-v14.17.3-x64.msi - successfully installed ✔ |
|
16.4.2 is now available, and works on non english systems! |
Well known user account names are localized on Windows. Look up the "Authenticated Users" user by its security identifier to get the localized name. PR-URL: nodejs#39241 Fixes: nodejs#39224 Refs: nodejs@e817ba7 Refs: https://hackerone.com/reports/1211160 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com>
Well known user account names are localized on Windows. Look up the "Authenticated Users" user by its security identifier to get the localized name. PR-URL: nodejs#39241 Fixes: nodejs#39224 Refs: nodejs@e817ba7 Refs: https://hackerone.com/reports/1211160 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Beth Griggs <bgriggs@redhat.com>
It works thanks Thadeu |
and others
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
It always reproduces as far as I can tell.
What do you see?
Additional information
I presume this bug was introduced in e817ba7.
Core issue seems to be that Windows localizes names of built-in users and groups. On my non-English Windows system, there does not exist a group called "Authenticated Users". It exists using a localized name. Hence, the solution implemented in that commit will never work on non-English Windows systems.
Instead, we should probably use a SID to reference the correct group. See https://support.microsoft.com/kb/243330.
EDIT: Presumably also affects v14.17.2 and v12.22.2, as these seem to include this same change. Haven't checked.
EDIT2: To clarify; this completely breaks Node.js installs, make it unable to complete installation, and when upgrading will leave Node.js in a broken state.
The text was updated successfully, but these errors were encountered: