SSMS wont give up file associations











up vote
2
down vote

favorite












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 HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.sql, .sql files show a VSCode icon:



No FileExts entry - 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):



Auto-created entry



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:



Sublime B-entry



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:



Manually removed ssms.exeSSMS auto-entry










share|improve this question
























  • What are the contents of the registry key HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.sqlOpenWithList? Do they change when you associate the files with Sublime or are they somehow locked? If they seem locked, right-click the key, choose Permissions and add a screenshot. Note this.
    – harrymc
    Nov 9 at 9:16










  • Deleting that key from registry, .sql files show VSCode icon. Double-clicking file opens it in SSMS and creates new .sql registry entry with ssms.exe. Open with -> anything adds new key "b", "c" etc in the OpenWithList.
    – Alex McMillan
    Nov 10 at 4:58










  • If you are running Windows 10 1803 or 1809 this is a known confirmed bug. It’s also going to be fixed by the end of November. There really isn’t a work around at this time. All you can do is wait for the cumulative patch that fixes it.
    – Ramhound
    Nov 10 at 5:32












  • @Ramhound yeah I'm running 1803. Do you have any links you could share in an answer for me to accept?
    – Alex McMillan
    Nov 10 at 5:38






  • 1




    @AlexMcMillan There are about 12 duplicates here at SuperUser. Granted all with commentary from myself indicating it’s a bug.
    – Ramhound
    Nov 10 at 5:56

















up vote
2
down vote

favorite












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 HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.sql, .sql files show a VSCode icon:



No FileExts entry - 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):



Auto-created entry



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:



Sublime B-entry



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:



Manually removed ssms.exeSSMS auto-entry










share|improve this question
























  • What are the contents of the registry key HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.sqlOpenWithList? Do they change when you associate the files with Sublime or are they somehow locked? If they seem locked, right-click the key, choose Permissions and add a screenshot. Note this.
    – harrymc
    Nov 9 at 9:16










  • Deleting that key from registry, .sql files show VSCode icon. Double-clicking file opens it in SSMS and creates new .sql registry entry with ssms.exe. Open with -> anything adds new key "b", "c" etc in the OpenWithList.
    – Alex McMillan
    Nov 10 at 4:58










  • If you are running Windows 10 1803 or 1809 this is a known confirmed bug. It’s also going to be fixed by the end of November. There really isn’t a work around at this time. All you can do is wait for the cumulative patch that fixes it.
    – Ramhound
    Nov 10 at 5:32












  • @Ramhound yeah I'm running 1803. Do you have any links you could share in an answer for me to accept?
    – Alex McMillan
    Nov 10 at 5:38






  • 1




    @AlexMcMillan There are about 12 duplicates here at SuperUser. Granted all with commentary from myself indicating it’s a bug.
    – Ramhound
    Nov 10 at 5:56















up vote
2
down vote

favorite









up vote
2
down vote

favorite











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 HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.sql, .sql files show a VSCode icon:



No FileExts entry - 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):



Auto-created entry



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:



Sublime B-entry



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:



Manually removed ssms.exeSSMS auto-entry










share|improve this question















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 HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.sql, .sql files show a VSCode icon:



No FileExts entry - 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):



Auto-created entry



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:



Sublime B-entry



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:



Manually removed ssms.exeSSMS auto-entry







windows-10 file-association ssms






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 10 at 5:46

























asked Nov 7 at 0:56









Alex McMillan

637




637












  • What are the contents of the registry key HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.sqlOpenWithList? Do they change when you associate the files with Sublime or are they somehow locked? If they seem locked, right-click the key, choose Permissions and add a screenshot. Note this.
    – harrymc
    Nov 9 at 9:16










  • Deleting that key from registry, .sql files show VSCode icon. Double-clicking file opens it in SSMS and creates new .sql registry entry with ssms.exe. Open with -> anything adds new key "b", "c" etc in the OpenWithList.
    – Alex McMillan
    Nov 10 at 4:58










  • If you are running Windows 10 1803 or 1809 this is a known confirmed bug. It’s also going to be fixed by the end of November. There really isn’t a work around at this time. All you can do is wait for the cumulative patch that fixes it.
    – Ramhound
    Nov 10 at 5:32












  • @Ramhound yeah I'm running 1803. Do you have any links you could share in an answer for me to accept?
    – Alex McMillan
    Nov 10 at 5:38






  • 1




    @AlexMcMillan There are about 12 duplicates here at SuperUser. Granted all with commentary from myself indicating it’s a bug.
    – Ramhound
    Nov 10 at 5:56




















  • What are the contents of the registry key HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.sqlOpenWithList? Do they change when you associate the files with Sublime or are they somehow locked? If they seem locked, right-click the key, choose Permissions and add a screenshot. Note this.
    – harrymc
    Nov 9 at 9:16










  • Deleting that key from registry, .sql files show VSCode icon. Double-clicking file opens it in SSMS and creates new .sql registry entry with ssms.exe. Open with -> anything adds new key "b", "c" etc in the OpenWithList.
    – Alex McMillan
    Nov 10 at 4:58










  • If you are running Windows 10 1803 or 1809 this is a known confirmed bug. It’s also going to be fixed by the end of November. There really isn’t a work around at this time. All you can do is wait for the cumulative patch that fixes it.
    – Ramhound
    Nov 10 at 5:32












  • @Ramhound yeah I'm running 1803. Do you have any links you could share in an answer for me to accept?
    – Alex McMillan
    Nov 10 at 5:38






  • 1




    @AlexMcMillan There are about 12 duplicates here at SuperUser. Granted all with commentary from myself indicating it’s a bug.
    – Ramhound
    Nov 10 at 5:56


















What are the contents of the registry key HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.sqlOpenWithList? Do they change when you associate the files with Sublime or are they somehow locked? If they seem locked, right-click the key, choose Permissions and add a screenshot. Note this.
– harrymc
Nov 9 at 9:16




What are the contents of the registry key HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.sqlOpenWithList? Do they change when you associate the files with Sublime or are they somehow locked? If they seem locked, right-click the key, choose Permissions and add a screenshot. Note this.
– harrymc
Nov 9 at 9:16












Deleting that key from registry, .sql files show VSCode icon. Double-clicking file opens it in SSMS and creates new .sql registry entry with ssms.exe. Open with -> anything adds new key "b", "c" etc in the OpenWithList.
– Alex McMillan
Nov 10 at 4:58




Deleting that key from registry, .sql files show VSCode icon. Double-clicking file opens it in SSMS and creates new .sql registry entry with ssms.exe. Open with -> anything adds new key "b", "c" etc in the OpenWithList.
– Alex McMillan
Nov 10 at 4:58












If you are running Windows 10 1803 or 1809 this is a known confirmed bug. It’s also going to be fixed by the end of November. There really isn’t a work around at this time. All you can do is wait for the cumulative patch that fixes it.
– Ramhound
Nov 10 at 5:32






If you are running Windows 10 1803 or 1809 this is a known confirmed bug. It’s also going to be fixed by the end of November. There really isn’t a work around at this time. All you can do is wait for the cumulative patch that fixes it.
– Ramhound
Nov 10 at 5:32














@Ramhound yeah I'm running 1803. Do you have any links you could share in an answer for me to accept?
– Alex McMillan
Nov 10 at 5:38




@Ramhound yeah I'm running 1803. Do you have any links you could share in an answer for me to accept?
– Alex McMillan
Nov 10 at 5:38




1




1




@AlexMcMillan There are about 12 duplicates here at SuperUser. Granted all with commentary from myself indicating it’s a bug.
– Ramhound
Nov 10 at 5:56






@AlexMcMillan There are about 12 duplicates here at SuperUser. Granted all with commentary from myself indicating it’s a bug.
– Ramhound
Nov 10 at 5:56












1 Answer
1






active

oldest

votes

















up vote
2
down vote



accepted
+50











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 appears on PCs running Windows 10 April 2018 Update Build 17134.345 (KB4462919) which was issued on October 9.




Source 1




As reported earlier, the issue appeared with the release of KB4462919 (Build 17134.345) for version 1803 and KB4464330 (Build 17763.55) for version 1809, which were pushed out on October 9 as Patch Tuesday cumulative updates.




Source 2



Microsoft Response:




Microsoft is working on a resolution and estimates a solution will be available in late November 2018.




Source 3






share|improve this answer





















  • Worth pointing out that this issue existed before KB4462933 was released and this bug was confirmed to exist. The bug was first a known issue, with KB4458469, but likely exists at the very least the patch before it. It is unknown what cumulative patch introduced this issue. Microsoft has not made that known. However, due to the numerous issues that have been solved, one should just wait until it’s fixed.
    – Ramhound
    Nov 10 at 5:52












  • This information took my thinking in a completely different direction; thanks.
    – Alex McMillan
    Nov 10 at 5:53








  • 1




    I will update this answer when the issue is patched, and flag previous questions, as duplicates (because this will have a proper answer and reasons)
    – Ramhound
    Nov 10 at 6:00











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1373310%2fssms-wont-give-up-file-associations%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
2
down vote



accepted
+50











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 appears on PCs running Windows 10 April 2018 Update Build 17134.345 (KB4462919) which was issued on October 9.




Source 1




As reported earlier, the issue appeared with the release of KB4462919 (Build 17134.345) for version 1803 and KB4464330 (Build 17763.55) for version 1809, which were pushed out on October 9 as Patch Tuesday cumulative updates.




Source 2



Microsoft Response:




Microsoft is working on a resolution and estimates a solution will be available in late November 2018.




Source 3






share|improve this answer





















  • Worth pointing out that this issue existed before KB4462933 was released and this bug was confirmed to exist. The bug was first a known issue, with KB4458469, but likely exists at the very least the patch before it. It is unknown what cumulative patch introduced this issue. Microsoft has not made that known. However, due to the numerous issues that have been solved, one should just wait until it’s fixed.
    – Ramhound
    Nov 10 at 5:52












  • This information took my thinking in a completely different direction; thanks.
    – Alex McMillan
    Nov 10 at 5:53








  • 1




    I will update this answer when the issue is patched, and flag previous questions, as duplicates (because this will have a proper answer and reasons)
    – Ramhound
    Nov 10 at 6:00















up vote
2
down vote



accepted
+50











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 appears on PCs running Windows 10 April 2018 Update Build 17134.345 (KB4462919) which was issued on October 9.




Source 1




As reported earlier, the issue appeared with the release of KB4462919 (Build 17134.345) for version 1803 and KB4464330 (Build 17763.55) for version 1809, which were pushed out on October 9 as Patch Tuesday cumulative updates.




Source 2



Microsoft Response:




Microsoft is working on a resolution and estimates a solution will be available in late November 2018.




Source 3






share|improve this answer





















  • Worth pointing out that this issue existed before KB4462933 was released and this bug was confirmed to exist. The bug was first a known issue, with KB4458469, but likely exists at the very least the patch before it. It is unknown what cumulative patch introduced this issue. Microsoft has not made that known. However, due to the numerous issues that have been solved, one should just wait until it’s fixed.
    – Ramhound
    Nov 10 at 5:52












  • This information took my thinking in a completely different direction; thanks.
    – Alex McMillan
    Nov 10 at 5:53








  • 1




    I will update this answer when the issue is patched, and flag previous questions, as duplicates (because this will have a proper answer and reasons)
    – Ramhound
    Nov 10 at 6:00













up vote
2
down vote



accepted
+50







up vote
2
down vote



accepted
+50




+50





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 appears on PCs running Windows 10 April 2018 Update Build 17134.345 (KB4462919) which was issued on October 9.




Source 1




As reported earlier, the issue appeared with the release of KB4462919 (Build 17134.345) for version 1803 and KB4464330 (Build 17763.55) for version 1809, which were pushed out on October 9 as Patch Tuesday cumulative updates.




Source 2



Microsoft Response:




Microsoft is working on a resolution and estimates a solution will be available in late November 2018.




Source 3






share|improve this 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 appears on PCs running Windows 10 April 2018 Update Build 17134.345 (KB4462919) which was issued on October 9.




Source 1




As reported earlier, the issue appeared with the release of KB4462919 (Build 17134.345) for version 1803 and KB4464330 (Build 17763.55) for version 1809, which were pushed out on October 9 as Patch Tuesday cumulative updates.




Source 2



Microsoft Response:




Microsoft is working on a resolution and estimates a solution will be available in late November 2018.




Source 3







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 10 at 5:51









Ramhound

19.1k156083




19.1k156083












  • Worth pointing out that this issue existed before KB4462933 was released and this bug was confirmed to exist. The bug was first a known issue, with KB4458469, but likely exists at the very least the patch before it. It is unknown what cumulative patch introduced this issue. Microsoft has not made that known. However, due to the numerous issues that have been solved, one should just wait until it’s fixed.
    – Ramhound
    Nov 10 at 5:52












  • This information took my thinking in a completely different direction; thanks.
    – Alex McMillan
    Nov 10 at 5:53








  • 1




    I will update this answer when the issue is patched, and flag previous questions, as duplicates (because this will have a proper answer and reasons)
    – Ramhound
    Nov 10 at 6:00


















  • Worth pointing out that this issue existed before KB4462933 was released and this bug was confirmed to exist. The bug was first a known issue, with KB4458469, but likely exists at the very least the patch before it. It is unknown what cumulative patch introduced this issue. Microsoft has not made that known. However, due to the numerous issues that have been solved, one should just wait until it’s fixed.
    – Ramhound
    Nov 10 at 5:52












  • This information took my thinking in a completely different direction; thanks.
    – Alex McMillan
    Nov 10 at 5:53








  • 1




    I will update this answer when the issue is patched, and flag previous questions, as duplicates (because this will have a proper answer and reasons)
    – Ramhound
    Nov 10 at 6:00
















Worth pointing out that this issue existed before KB4462933 was released and this bug was confirmed to exist. The bug was first a known issue, with KB4458469, but likely exists at the very least the patch before it. It is unknown what cumulative patch introduced this issue. Microsoft has not made that known. However, due to the numerous issues that have been solved, one should just wait until it’s fixed.
– Ramhound
Nov 10 at 5:52






Worth pointing out that this issue existed before KB4462933 was released and this bug was confirmed to exist. The bug was first a known issue, with KB4458469, but likely exists at the very least the patch before it. It is unknown what cumulative patch introduced this issue. Microsoft has not made that known. However, due to the numerous issues that have been solved, one should just wait until it’s fixed.
– Ramhound
Nov 10 at 5:52














This information took my thinking in a completely different direction; thanks.
– Alex McMillan
Nov 10 at 5:53






This information took my thinking in a completely different direction; thanks.
– Alex McMillan
Nov 10 at 5:53






1




1




I will update this answer when the issue is patched, and flag previous questions, as duplicates (because this will have a proper answer and reasons)
– Ramhound
Nov 10 at 6:00




I will update this answer when the issue is patched, and flag previous questions, as duplicates (because this will have a proper answer and reasons)
– Ramhound
Nov 10 at 6:00


















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1373310%2fssms-wont-give-up-file-associations%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Index of /

Tribalistas

Listed building