Apparently this is a known Win10 bug and should hopefully be fixed in an upcoming update.
I have installed SQL Server Management Studio v17.9 on a clean Windows 10 installation. This associated all .sql
files with SSMS.
I want to associate .sql
files with a plain text editor (eg: Sublime) but I am unable to change the default application. I have tried:
- Right click
.sql
file -> Open With -> Sublime + "Always use this program". - Settings -> Default Applications by File Type -> Find
.sql
-> Change to Sublime - Right click
.sql
file -> Properties -> "Change" button -> Sublime. - Using
ftype
via elevated command prompt as seen here
In all 3 cases, my selection is not reflected in any way, anywhere. The icon remains SSMS, and the file opens with SSMS.
Is there some kind of "File Association retention" setting within SSMS I am unaware of?
Edit: I can change the default application for non-SSMS-associated extensions without issue.
Edit: after deleting registry key HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.sql
, .sql
files show a VSCode icon:
If I then double-click New Users.sql
, it opens with SSMS and a refresh of regedit shows the .sql
entry recreated with ssms.exe associated (the icon remains VSCode):
If I then right-click -> open with -> Choose Another App -> Select Sublime and hit "Always use this to open .sql files", it opens with Sublime and a refresh of regedit shows a new "b" entry created for Sublime. The icon remains VSCode, and double-clicking opens it in SSMS:
If I then delete the a
entry for ssms.exe
and rename b
-> a
such that only sublime exists, then double-click the .sql file, it opens with SSMS and generates a new b
entry for itself:
Answer
I have installed SQL Server Management Studio v17.9 on a clean Windows 10 installation. This associated all .sql files with SSMS. I want to associate .sql files with a plain text editor (eg: Sublime) but I am unable to change the default application.
If you are running Windows 10 1803 or 1809 this is a known confirmed bug. The bug first appeared on PCs running Windows 10 April 2018 Update Build 17134.320 (KB4458469) which was issued on October 9. It also appears on PCs running Windows 10 October 2018 Update Build 17763.55 (KB4464330) which was also issued on October 9th, 2018.
For those machines running the April 2018 Update, Microsoft issued a patch KB4467682, in order to address this issue on November 27th, 2018. For those machines running the October 2018 Update, Microsoft issued a patch KB4469342, in order to address this issue on December 5th, 2018.
Addresses an issue that prevents some users from setting Win32 program defaults for certain app and file type combinations using the Open with… command or Settings > Apps > Default apps.
No comments:
Post a Comment