Cannot install Javinizer GUI -

madmax2 commented 2 years ago

Expected Behavior

Install Javinizer GUI

Current Behavior

Error occurred when creating PowerShell Universal directories: Cannot bind argument to parameter 'Path' because it is null.

Steps to Reproduce (for bugs)

open powershell 7 administrator mode,

Install the python modules using pip. If running Unix/MacOS, use pip3/python3

pip install pillow pip install googletrans==4.0.0rc1 pip install google_trans_new

Install the module from PowerShell gallery

Install-Module Javinizer

Check that the module has been installed; if error, restart your console

Javinizer -v

Version : 2.5.10 Prerelease : alpha Project : https://github.com/jvlflame/Javinizer License : https://github.com/jvlflame/Javinizer/blob/master/LICENSE ReleaseNotes : https://github.com/jvlflame/Javinizer/blob/master/.github/CHANGELOG.md

Install GUI

Javinizer -InstallGUI Y

Get error Error occurred when creating PowerShell Universal directories: Cannot bind argument to parameter 'Path' because it is null.

Your Environment

Module version used: 2.5.10
Operating System and PowerShell version: Windows 10 , powershell 7

amakuramio commented 2 years ago

I have the same problem

chronotank79 commented 2 years ago

I also have the same issue.

nova168168 commented 2 years ago

I also have the same issue.

SetilaSilvios commented 2 years ago

Since I am not a developer nor a native English speaker, what I write can be inaccurate. This is just how I solved the problem.

It happens when PowerShell fails to load the file directory(=Path) of the 'Javinizer' module.

You might have installed a previous/different versions of Powershell, and they install modules in different directory. PowerShell 7 can partially load modules installed with those different versions, but cannot load its directory with command Get-InstalledModule, which is included in the process of installing GUI.

So before following what I write below, type Get-InstalledModule in your PowerShell and see if 'Javinizer' is in the list. If not, you have to install Javinizer in the directory that PowerShell 7 uses.

As I don't know any advanced methods, I just deleted Javinizer and reinstalled with PowerShell 7.

Normally deleting Javinizer can be done with command Uninstall-Module Javinizer, but since PowerShell 7 cannot even recognize it as 'Installed Module' you have to delete it with different version of PowerShell(=the one you have installed before), or just find the folder manually. In my case, it was in C:\Program Files\WindowsPowerShell\Modules.
Then install Javinizer again, with PowerShell 7. Install-Moudle Javinizer. After that, try Get-InstalledModule command to check if PowerShell can load it properly.

Done. Now install GUI.

New one might be in C:\Users\(Username)\Documents\PowerShell\Modules
There can be some easier ways, such as just moving module folder to proper directory and type some commands to import that. But it's out of my ability. If you want to try other ways, refer to this link.

PriestMarmore commented 1 year ago

One thing I did wrong was installing this with the Windows Powershell instead of Powershell 7, so when I moved to Powershell 7 and tried to install the GUI I couldn't even though I could see my version of javinizer (Javinizer -v). I ended up deleting my files from javinizer (just search on file explorer for Javinizer and open the location of the files and delete them) and doing the process with Powershell 7 from the beginning this time and it worked

javinizer / Javinizer