Cannot install 1.2.0 or higher #1255
Replies: 1 comment 3 replies
-
|
Hmm, that is quite odd. I'm not sure what could be causing this, but the InnoSetup installer is clearly not recognizing your accounts as admins. Are you logged in using Active Directory? |
Beta Was this translation helpful? Give feedback.
-
|
Corey, agreed. We are logged in using AD and are configured as local admins on our machines. We can install everything else - VS, VS Code, DBeaver, SQL Server, etc. One other thing to note - I can install versions of NVM prior to 1.2.0 - which is totally fine for our needs - I just wanted to post this on here in case there was something we were missing. |
Beta Was this translation helpful? Give feedback.
-
|
Honestly, I'd stick with 1.1.12 for the time being anyway. I have a ton of updates queued for v1.2.3, which has been blocked by the arm64 build process. GitHub just announced arm64 Windows support a few minutes ago, so I will be putting out a new release after I incorporate that into the build process. I really don't know what could be causing this unless there is something specific configured in your AD environment preventing the install, like blocking access to a protected directory (like v1.2.0+ includes another binary that incorporates features from the upcoming Runtime platform (see https://opensource.author.io/nvm-for-windows-v120). I'll try to add more logging to these processes in anticipation of this issue. I'd appreciate if you could try installing 1.2.3 when it is released (if you can, no worries if not). |
Beta Was this translation helpful? Give feedback.
-
|
Yep can stick with 1.1.12 no problem at all. It fails immediately after trying to run the exe. I will try to remember to look for 1.2.3. Thanks Corey |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm helping a colleague install NVM on his machine and we're both unable to. When we try to install 1.2.0 or higher version, we get an error stating "You must be logged in as admin when installing this program". Not only are we both admins on our machines, but we also have tried installing by right clicking on the exe and running as admin.
Is there a step or something that we're missing that's causing this issue? As an FYI, we can install versions lower than 1.2.0.
Thank you
Beta Was this translation helpful? Give feedback.
All reactions