question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL" Does not work properly

See original GitHub issue

Steps to reproduce


adding ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=0 to msiexec options for 

Powershell 7.0.3
&
Powershell 7.1.0

does not work, as context menu options are still added regardless of the value set.


Expected behavior

Powershell installer should not add context menu option to registry if value is set to 0

Actual behavior


Powershell installer is still adding context menu for powershell in explorer window 

Environment data


Name                           Value
----                           -----
PSVersion                      7.0.3
PSEdition                      Core
GitCommitId                    7.0.3
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0


Name                           Value
----                           -----
PSVersion                      7.1.0-preview.7
PSEdition                      Core
GitCommitId                    7.1.0-preview.7
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0



Issue Analytics

  • State:open
  • Created 3 years ago
  • Comments:8 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
heathscommented, Sep 25, 2020

Property condition checks in Windows Installer are traditionally, is it set or not? 0 is not treated as false. This is true of Winodws Insatller standard properties as well. If you want to force a property to “off” (undefined), set it’s value to nothing:

msiexec /i powershell.msi /l*v "%TEMP%"\install.log" /qn ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=
0reactions
horst789githubcommented, Dec 19, 2022

same problem… with Powershell 7.3.0

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to enable "Open PowerShell Here" context menu in ...
Open regedit and go to path HKEY_CLASSES_ROOT\Directory\background\shell . Create new key powershellmenu . Change the Default value of the powershellmenu key to ...
Read more >
How to add "Open Powershell Here" to right click menu for ...
If you are trying to run a .ps from Windows Explorer right-click, then add this key. If for example for example PWSH, then...
Read more >
How to Add "Open PowerShell Here" to the Right-Click ...
To to that, right-click the powershellmenu key and choose New > String Value. Name the new value “Extended.” You don't need to make...
Read more >
Add Open PowerShell to Context Menu
Press Start button + R to open run command dialog box. · Navigate to the following path: · Right click on the right...
Read more >
Add Open PowerShell window here as administrator in ...
All my scripts work properly for me with all libraries it seems like. The only way that I have been able to get...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found