Login at Kodi Home

nogginthenog · 2017-03-23, 18:16

Hoopy, pala66, and any others who are completely stuck: open a command prompt, type 'path' (without the quotation marks), press Enter, and let us see the output.

pala66 · 2017-03-23, 18:28

(2017-03-23, 18:16)nogginthenog Wrote: Hoopy, pala66, and any others who are completely stuck: open a command prompt, type 'path' (without the quotation marks), press Enter, and let us see the output.

C:\Users\Kodi>Path
PATH=C:\Windows\System32\WindowsPowerShell\v1.0\

Thank you

nogginthenog · 2017-03-23, 18:33

(2017-03-23, 18:28)pala66 Wrote: C:\Users\Kodi>Path
PATH=C:\Windows\System32\WindowsPowerShell\v1.0\

Now use Windows Explorer and check whether the folder C:\Windows\System32\WindowsPowerShell\v1.0\ actually exists on your computer and whether it contains the program powershell.exe.

**Rechi** · 2017-03-23, 18:38

(2017-03-23, 18:28)pala66 Wrote: C:\Users\Kodi>Path
PATH=C:\Windows\System32\WindowsPowerShell\v1.0\

Have you changed your PATH variable?
At least %SystemRoot%;%SystemRoot%\System32\Wbem should be in it. If you want to also add powershell it must be %SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0

pala66 · 2017-03-23, 18:38

(2017-03-23, 18:33)nogginthenog Wrote:
(2017-03-23, 18:28)pala66 Wrote: C:\Users\Kodi>Path
PATH=C:\Windows\System32\WindowsPowerShell\v1.0\

Now use Windows Explorer and check whether the folder C:\Windows\System32\WindowsPowerShell\v1.0\ actually exists on your computer and whether it contains the program powershell.exe.

Verified, yes the powershell.exe, and powershell_ise.exe both are there FYI.

C:\Windows\System32\WindowsPowerShell\v1.0

Thank you

pala66 · 2017-03-23, 18:42

(2017-03-23, 18:38)Rechi Wrote:
(2017-03-23, 18:28)pala66 Wrote: C:\Users\Kodi>Path
PATH=C:\Windows\System32\WindowsPowerShell\v1.0\

Have you changed your PATH variable?
At least %SystemRoot%;%SystemRoot%\System32\Wbem should be in it. If you want to also add powershell it must be %SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0

Hi Rechi, I did but no luck. I just tried your path "%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0"

Still no luck. Do I need to reboot the machine for the path update to take effect?

**Rechi** · 2017-03-23, 18:45

Execute Path again in a cmd and check if it is equal to %SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0.
If not equal, you may need to reboot.

nogginthenog · (This post was last modified: 2017-03-23, 18:56 by nogginthenog.)

I think %SystemRoot%\System32 needs to be in there too.

pala66 · 2017-03-23, 18:53

(2017-03-23, 18:45)Rechi Wrote: Execute Path again in a cmd and check if it is equal to %SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0.
If not equal, you may need to reboot.

It has changed and does indeed match. Still no luck launching the installer same error. Tried rebooting anyway and the installer still fails. .

nogginthenog · 2017-03-23, 18:55

(2017-03-23, 18:53)pala66 Wrote: It has changed and does indeed match. Still no luck launching the installer same error. Tried rebooting anyway and the installer still fails. .

See #53.

pala66 · 2017-03-23, 18:57

(2017-03-23, 18:55)nogginthenog Wrote:
(2017-03-23, 18:53)pala66 Wrote: It has changed and does indeed match. Still no luck launching the installer same error. Tried rebooting anyway and the installer still fails. .

See #53.

Does it matter where that gets inserted into the string?

Thank you

**Rechi** · 2017-03-23, 18:58

(2017-03-23, 18:53)pala66 Wrote: It has changed and does indeed match. Still no luck launching the installer same error. Tried rebooting anyway and the installer still fails. .

Please also tell me which versions you have tested.
Test 17.1 and the test builds I've linked to in this thread.

nogginthenog · 2017-03-23, 18:58

(2017-03-23, 18:57)pala66 Wrote:
(2017-03-23, 18:55)nogginthenog Wrote:
(2017-03-23, 18:53)pala66 Wrote: It has changed and does indeed match. Still no luck launching the installer same error. Tried rebooting anyway and the installer still fails. .

See #53.

Does it matter where that gets inserted into the string?

Thank you

No, but to be tidy, put it second. Remember to use one semi-colon between each entry.

pala66 · 2017-03-23, 19:01

(2017-03-23, 18:57)pala66 Wrote:
(2017-03-23, 18:55)nogginthenog Wrote:
(2017-03-23, 18:53)pala66 Wrote: It has changed and does indeed match. Still no luck launching the installer same error. Tried rebooting anyway and the installer still fails. .

See #53.

Does it matter where that gets inserted into the string?

Thank you

I added that in like this:

Running Path in CMD gets me this FYI

C:\Users\Kodi>path
PATH=C:\Windows;C:\Windows\System32;C:\Windows\System32\Wbem;C:\Windows\System32
\WindowsPowerShell\?v1.0

C:\Users\Kodi>

Still no luck.

nogginthenog · 2017-03-23, 19:02

There should be no question mark near the end there - that is not a valid character in a pathname.