"Open with" context menu has changed

How do I restore "Always" to the "Open with" context menu? Currently my only choice is "Just once". I know how to do it for individual apps but I want the choice for all apps.

Thanks, Team.

Create and Save AS a regfile (.reg). Remember, the default is to save as txt; save then view extensions and rename.



To revert to default, create and save as:


; How to remove registry keys using REGEDIT
; SOURCE: How to add, modify, or delete registry subkeys and values by using a .reg file - Microsoft Support
; To delete a registry KEY with a .reg file, put a hyphen (-) in front of the RegistryPath in the .reg file.

; For example, to delete the Test subkey from the following registry key: HKEY_LOCAL_MACHINE\Software
; put a hyphen in front of the following registry key in the .reg file:
; [-HKEY_LOCAL_MACHINE\Software\Test]

;To delete a registry VALUE with a .reg file, put a hyphen (-) after the equals sign following the DataItemName in the .reg file.
; For example, to delete the TestValue registry value from the following registry key: HKEY_LOCAL_MACHINE\Software\Test
; put a hyphen after the "TestValue"= in the .reg file.
; HKEY_LOCAL_MACHINE\Software\Test
; "TestValue"=-

siddav said:

How do I restore "Always" to the "Open with" context menu? Currently my only choice is "Just once". I know how to do it for individual apps but I want the choice for all apps.

Thanks, Team.

Click to expand...

Welcome to ElevenForum.

In the Taskbar search box, just type: Defaults

That will take you to the Default File Associations page.
There you can permanently select a program to open a file type.






Also, I gave you ten points just for filling out your computer specs.

IgnorantOne said:

Create and Save AS a regfile (.reg). Remember, the default is to save as txt; save then view extensions and rename.

https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies#externalprotocoldialogshowalwaysopencheckbox

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]
"ExternalProtocolDialogShowAlwaysOpenCheckbox"=dword:00000001

Click to expand...

Hi @IgnorantOne
I do not think the OP wants to modify his Edge policies.
What gave you that idea?

@siddav
Hi, what type of file are you referring to?

Even if you can change the context menu, I'm not sure why you would want to when the entries you already have will do what you want.
When you right click a file , choose "open with" and select your preferred application from the list, this selection by default becomes Your "always" preferred application for that particular file type and is reflected in settings>apps>default apps>file types. . Not all file types give you the option of "just once" when you select "open with"

If you want a particular application to handle ALL the file types the application is capable of handling, you can do that in that same section of settings. IMO this is a big improvement over when we had to manually find and change every single file type an app could open to set file type defaults.

glasskuter said:

Even if you can change the context menu, I'm not sure why you would want to when the entries you already have will do what you want.
When you right click a file , choose "open with" and select your preferred application from the list, this selection by default becomes Your "always" preferred application for that particular file type and is reflected in settings>apps>default apps>file types. . Not all file types give you the option of "just once" when you select "open with"

Click to expand...

I just wish it'd remember the hosts file editing setting.
It only gives the option 'Just Once'.

OAT said:

I just wish it'd remember the hosts file editing setting.
It only gives the option 'Just Once'.

Click to expand...

I thought about that, too as well as .reg and .bat files. But I think for once MS makes sense in handling those particular file types in that way if you really consider how those particular types affect the system.

glasskuter said:

I thought about that, too as well as .reg and .bat files. But I think for once MS makes sense in handling those particular file types in that way if you really consider how those particular types affect the system.

Click to expand...

Yes, you are right as it can indeed be seen as an added layer of protection.

Thought of something else that sets HOSTS apart @OAT
Hosts defined as "file" which is not a valid file type handled in file associations.

glasskuter said:

Thought of something else that sets HOSTS apart @OAT
Hosts defined as "file" which is not a valid file type handled in file associations.

Click to expand...

Yeah, I am aware of that, since there isn't even a '.' .