New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Context Menu\Folder shortcut problem after installing PS Core 6.1 on Windows #7815

Closed
PGomersall opened this Issue Sep 18, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@PGomersall

PGomersall commented Sep 18, 2018

Steps to reproduce

Install PowerShell Core 6.1 on Windows choosing to add context menu "Open PowerShell from here". Once installed, just clicking any Windows shortcut for a folder opens a PowerShell 6.1 window not the Windows Explorer window at the folder.
This only seems to happen with Directory\Folder shortcuts in Quick Launch (%APPDATA%\Microsoft\Internet Explorer\Quick Launch) that are then exposed on Quick Launch toolbar on W10 taskbar as they respond to single click to open. The single click open PowerShell. Uninstall returns behavior to normal.

Expected behavior

Clicking a folder shortcut opens the folder in Windows Explorer.


Actual behavior
---------------

Clicking any Windows shortcut when on Quick Launch toolbar on W10 taskbar for a folder opens a PowerShell 6.1 window not the folder in a Windows Explorer window at the folder.

Environment data

PS D:\Downloads> $PSVersiontable

Name Value


PSVersion 6.1.0
PSEdition Core
GitCommitId 6.1.0
OS Microsoft Windows 10.0.17134
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0

This system is a fully patched W10 Education x64 version in domain environment.

@iSazonov

This comment has been minimized.

Collaborator

iSazonov commented Sep 19, 2018

@bergmeister Could you please comment the Issue?

@bergmeister

This comment has been minimized.

Contributor

bergmeister commented Sep 19, 2018

@PGomersall Please fill in the complete issue template. You have not given sufficient details about your environment. Please provide the output of $PSVersiontable and the OS version. Does the issue go away when you uninstall PowerShell Core (which it should if it was caused by PowerShell Core)
I got a new Windows 10 laptop today and cannot reproduce the issue here, I suspect your reported happens maybe only on an old or special OS version.
When I implemented the feature, I did not manually test this on old Desktop Windows versions like e.g. Windows 7 or 8.1 (but I think I tested it on WinServer 2008R2)
@iSazonov The feature purely works by setting registry keys.

@PGomersall

This comment has been minimized.

PGomersall commented Sep 19, 2018

@bergmeister

This comment has been minimized.

Contributor

bergmeister commented Oct 2, 2018

Just an update that I can reproduce now and will start to look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment