Skip to content
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

Add .CPL back to $env:PathExt #9797

Closed
brwilkinson opened this issue Jun 1, 2019 · 5 comments · Fixed by #9828
Closed

Add .CPL back to $env:PathExt #9797

brwilkinson opened this issue Jun 1, 2019 · 5 comments · Fixed by #9828
Assignees
Labels
Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a Resolution-Fixed The issue is fixed.

Comments

@brwilkinson
Copy link

brwilkinson commented Jun 1, 2019

Is it possible to add in the .CPL pathext ?

I use this frequently for launching control panel items.

e.g.
appwiz
sysdm

Windows PowerShell

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.18908.1000

ls env:pathext

Name                           Value
----                           -----
PATHEXT                        .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.CPL

Actual behavior

 $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.0.0-preview.1

ls env:pathext

Name                           Value
----                           -----
PATHEXT                        .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

The ENV:Pathext was already removed on linux, so I hope Windows should still have .CPL.

@brwilkinson brwilkinson added the Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a label Jun 1, 2019
@iSazonov
Copy link
Collaborator

iSazonov commented Jun 3, 2019

You could directly add new value to PATHEXT environment variable. Why must pwsh do this internally?

@brwilkinson
Copy link
Author

brwilkinson commented Jun 3, 2019 via email

@iSazonov
Copy link
Collaborator

iSazonov commented Jun 3, 2019

I don't know history why it was removed.
/cc @SteveL-MSFT

@SteveL-MSFT
Copy link
Member

This was inadvertently removed as part of #4942. Since this is a break from WinPS, we should put it back.

@SteveL-MSFT SteveL-MSFT self-assigned this Jun 5, 2019
@iSazonov iSazonov added the Resolution-Fixed The issue is fixed. label Aug 23, 2019
@ghost
Copy link

ghost commented Sep 19, 2019

🎉This issue was addressed in #9828, which has now been successfully released as v7.0.0-preview.4.:tada:

Handy links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Question ideally support can be provided via other mechanisms, but sometimes folks do open an issue to get a Resolution-Fixed The issue is fixed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants