Edit Context Menu Entry for .VBS and .ICO files
up vote
1
down vote
favorite
If I want to change the "Edit" context menu entries of certain file extensions to open them with certain programs, I typically just have to find the corresponding registry key, go to the "Shell/Edit/Command" subkey, and then change the default value to be something like this:
"C:Program FilesMicrosoft VS CodeCode.exe" "%1"
However, it seems that it's not always very easy to find those keys. It seems like there is "precedence" happening somewhere. For example, If I want a .ps1 script to have its "edit" context menu entry open with .vs code, I don't go here (the way I would for, say for example, a .hpp file):
ComputerHKEY_CLASSES_ROOTSystemFileAssociations.ps1shellEditcommand
Instead, I have to go here:
ComputerHKEY_CLASSES_ROOTMicrosoft.PowerShellModule.1ShellEditCommand
If I try the former, then nothing ends up happening; the latter seems to have precedence over the former.
Naturally, this can make it very difficult to find the right keys when trying to change the context menu entries of other file types that Windows typically deals with, such as ".ico" and ".vbs" extensions.
Do you know of any resources that can help me find the right registry key to go to for any given extension? I've been trying to find the right keys so that I can modify the "edit" context menu entry for ".ico" and ".vbs" extensions, but to no avail so far. Which keys are they?
windows windows-10 windows-registry context-menu desktop-customization
add a comment |
up vote
1
down vote
favorite
If I want to change the "Edit" context menu entries of certain file extensions to open them with certain programs, I typically just have to find the corresponding registry key, go to the "Shell/Edit/Command" subkey, and then change the default value to be something like this:
"C:Program FilesMicrosoft VS CodeCode.exe" "%1"
However, it seems that it's not always very easy to find those keys. It seems like there is "precedence" happening somewhere. For example, If I want a .ps1 script to have its "edit" context menu entry open with .vs code, I don't go here (the way I would for, say for example, a .hpp file):
ComputerHKEY_CLASSES_ROOTSystemFileAssociations.ps1shellEditcommand
Instead, I have to go here:
ComputerHKEY_CLASSES_ROOTMicrosoft.PowerShellModule.1ShellEditCommand
If I try the former, then nothing ends up happening; the latter seems to have precedence over the former.
Naturally, this can make it very difficult to find the right keys when trying to change the context menu entries of other file types that Windows typically deals with, such as ".ico" and ".vbs" extensions.
Do you know of any resources that can help me find the right registry key to go to for any given extension? I've been trying to find the right keys so that I can modify the "edit" context menu entry for ".ico" and ".vbs" extensions, but to no avail so far. Which keys are they?
windows windows-10 windows-registry context-menu desktop-customization
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
If I want to change the "Edit" context menu entries of certain file extensions to open them with certain programs, I typically just have to find the corresponding registry key, go to the "Shell/Edit/Command" subkey, and then change the default value to be something like this:
"C:Program FilesMicrosoft VS CodeCode.exe" "%1"
However, it seems that it's not always very easy to find those keys. It seems like there is "precedence" happening somewhere. For example, If I want a .ps1 script to have its "edit" context menu entry open with .vs code, I don't go here (the way I would for, say for example, a .hpp file):
ComputerHKEY_CLASSES_ROOTSystemFileAssociations.ps1shellEditcommand
Instead, I have to go here:
ComputerHKEY_CLASSES_ROOTMicrosoft.PowerShellModule.1ShellEditCommand
If I try the former, then nothing ends up happening; the latter seems to have precedence over the former.
Naturally, this can make it very difficult to find the right keys when trying to change the context menu entries of other file types that Windows typically deals with, such as ".ico" and ".vbs" extensions.
Do you know of any resources that can help me find the right registry key to go to for any given extension? I've been trying to find the right keys so that I can modify the "edit" context menu entry for ".ico" and ".vbs" extensions, but to no avail so far. Which keys are they?
windows windows-10 windows-registry context-menu desktop-customization
If I want to change the "Edit" context menu entries of certain file extensions to open them with certain programs, I typically just have to find the corresponding registry key, go to the "Shell/Edit/Command" subkey, and then change the default value to be something like this:
"C:Program FilesMicrosoft VS CodeCode.exe" "%1"
However, it seems that it's not always very easy to find those keys. It seems like there is "precedence" happening somewhere. For example, If I want a .ps1 script to have its "edit" context menu entry open with .vs code, I don't go here (the way I would for, say for example, a .hpp file):
ComputerHKEY_CLASSES_ROOTSystemFileAssociations.ps1shellEditcommand
Instead, I have to go here:
ComputerHKEY_CLASSES_ROOTMicrosoft.PowerShellModule.1ShellEditCommand
If I try the former, then nothing ends up happening; the latter seems to have precedence over the former.
Naturally, this can make it very difficult to find the right keys when trying to change the context menu entries of other file types that Windows typically deals with, such as ".ico" and ".vbs" extensions.
Do you know of any resources that can help me find the right registry key to go to for any given extension? I've been trying to find the right keys so that I can modify the "edit" context menu entry for ".ico" and ".vbs" extensions, but to no avail so far. Which keys are they?
windows windows-10 windows-registry context-menu desktop-customization
windows windows-10 windows-registry context-menu desktop-customization
asked Nov 20 at 20:19
jippyjoe4
274110
274110
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377093%2fedit-context-menu-entry-for-vbs-and-ico-files%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown