Package fails to install with the error that 'Test-ProcessAdminRights' is not recognized as the name of a cmdlet

[luigilink]

Checklist

• I confirm there are no unresolved issues reported on the Chocolatey Status page.
• I have verified this is the correct repository for opening this issue.
• I have verified no other issues exist related to my problem.
• I have verified this is not an issue for a specific package.
• I have verified this issue is not security related.
• I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

I try to install packages with powershell:
I run this cmdlet: choco install notepadplusplus.install

What is Expected?

I expect to have this package installed.

How Did You Get This To Happen?

I run this cmdlet: choco install notepadplusplus.install

System Details

• Operating System: 10.0.14393.0
• Windows PowerShell version: 5.1.14393.8330
• Chocolatey CLI Version: 2.5.0
• Chocolatey Licensed Extension version: Chocolatey v2.5.0 | 0 packages installed.
• Chocolatey License type:
• Terminal/Emulator: Windows PowerShell

Installed Packages

Chocolatey v2.5.0
chocolatey-compatibility.extension 1.0.0
chocolatey-core.extension 1.4.0
chocolatey-dotnetfx.extension 1.0.1
chocolatey-visualstudio.extension 1.11.1
dotnetfx 4.8.0.20220524
KB2919355 1.0.20160915
KB2919442 1.0.20160915
microsoft-edge 139.0.3405.86
sql-server-management-studio 21.4.8
ulsviewer 16.0.3129.1000
10 packages installed.

Output Log

Chocolatey v2.5.0
Installing the following packages:
notepadplusplus.install
By installing, you accept licenses for the packages.
Downloading package from source 'https://community.chocolatey.org/api/v2/'
Progress: Downloading notepadplusplus.install 8.8.3... 100%

notepadplusplus.install v8.8.3 [Approved]
notepadplusplus.install package files install completed. Performing other installation steps.
The package notepadplusplus.install wants to run 'chocolateyInstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[A]ll scripts/[N]o/[P]rint): y

Installing 64-bit notepadplusplus.install...
ERROR: The term 'Test-ProcessAdminRights' 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.
The install of notepadplusplus.install was NOT successful.
Error while running 'C:\chocolatey\lib\notepadplusplus.install\tools\chocolateyInstall.ps1'.
 See log for details.

Chocolatey installed 0/1 packages. 1 packages failed.
 See the log for details (C:\chocolatey\logs\chocolatey.log).

Failures
 - notepadplusplus.install (exited -1) - Error while running 'C:\chocolatey\lib\notepadplusplus.install\tools\chocolatey
Install.ps1'.
 See log for details.

Enjoy using Chocolatey? Explore more amazing features to take your
experience to the next level at
 https://chocolatey.org/compare

Additional Context

chocolatey.log

[github-actions]

To vote for this issue, please add a 👍 emoji to the issue description. Votes in comments are not recorded.

[pauby]

I've just installed it here and there is no issue. I would suggest this is a local environment issue. It feels to me like Chocolatey CLI is not installed properly.

[luigilink]

I still have the issue. I think it's related to the OS version. I also tried using PowerShell Core, but the problem persists :(

[luigilink]

Where does this Cmdlet Test-ProcessAdminRights come from ?

[supersnellehenk]

I just had the same issue, this was due to a remnant of UniGetUI with my two Windows accounts.

I have a separate non-admin and admin user, and my admin user had the "ChocolateyInstall" environment variable set to a path in my admin user's AppData folder. I realised this after reinstalling chocolatey and it mentioning a non-default install path.

Deleting that so it installs in C:\ProgramData\chocolatey successfully made that error go away. (I had the same issue installing maven)

[corbob]

@luigilink I think @supersnellehenk might be onto something there. To answer your question of where the Cmdlet comes from, it is a compiled cmdlet that comes from Chocolatey.PowerShell.dll. From your log file, it looks like it's installed things to C:\chocolatey instead of the regular C:\ProgramData\Chocolatey. This raises a few questions:

• If you look in C:\chocolatey\helpers, do you have Chocolatey.PowerShell.dll and chocolateyInstaller.psm1?
• Do you also have a C:\ProgramData\Chocolatey directory?
• What do you get when you run get-command choco.exe -All?

[luigilink]

I found another solution instead of using the package notepadplusplus.install — I used notepadplusplus instead.
Now everything works great.
Unfortunately, I can't confirm whether those directories exist because I deleted the Azure VM and started from scratch.
We can close this issue if you prefer, and I’ll reopen it if I manage to reproduce the problem. Sounds good?

[gep13]

@supersnellehenk said...
I just had the same issue, this was due to a remnant of UniGetUI with my two Windows accounts.

This could definitely be part of the issue 😢

When using UniGetUI, Chocolatey is installed to a non-standard location, and if you switch away from UniGetUI to Chocolatey proper, you are left with Chocolatey running in a non-standard location, and any attempt to re-install Chocolatey will still use the non-standard location, due to the $env:ChocolateyInstall being set to that value. To fix this, you would need to delete this environment variable, and re-install Chocolatey to install into the default location.

[corbob]

I found another solution instead of using the package notepadplusplus.install — I used notepadplusplus instead. Now everything works great. Unfortunately, I can't confirm whether those directories exist because I deleted the Azure VM and started from scratch. We can close this issue if you prefer, and I’ll reopen it if I manage to reproduce the problem. Sounds good?

I'm not sure that the use of notepadplusplus would be what fixed it, but that's neither here nor there as you're no longer having the issue. I'll close this issue and we can reopen it if you manage to reproduce it 😄