Why does Visual Studio run in “Always on top” mode?
up vote
30
down vote
favorite
My copy of Visual Studio seems to be set in "Always On Top" Mode. It runs this way by default; there seems to be no way of changing it.
Visual Studio runs as Administrator/Elevated, but that really shouldn't affect whether or not Visual Studio runs as "Always On Top."
Any idea why this may be occurring, and how to prevent it from happening?
visual-studio always-on-top
edited Apr 4 '16 at 10:56
DavidPostill♦
103k25220255
asked Jun 12 '11 at 6:31
SomeUser
151124
add a comment |
up vote
30
down vote
favorite
My copy of Visual Studio seems to be set in "Always On Top" Mode. It runs this way by default; there seems to be no way of changing it.
Visual Studio runs as Administrator/Elevated, but that really shouldn't affect whether or not Visual Studio runs as "Always On Top."
Any idea why this may be occurring, and how to prevent it from happening?
visual-studio always-on-top
edited Apr 4 '16 at 10:56
DavidPostill♦
103k25220255
asked Jun 12 '11 at 6:31
SomeUser
151124
4
I saw a glimpse of this problem with Visual Studio 2010 starting to run "Always On Top" in Windows7, but it only happened straight upon a ReSharper update, and got resolved as soon as Visual Studio was restarted.
– user157214
Sep 9 '12 at 9:43
1
Which version of Visual Studio do you refer to?
– Marcel
Dec 10 '13 at 10:18
Do you have ReSharper installed also? It seems to have a history of causing this type of issue on various versions.
– panhandel
Dec 31 '13 at 22:48
I was able to fix the problem with this: stackoverflow.com/a/27411034/2667554
– enn
Apr 27 '15 at 9:54
Simple restart of visual studio 2010 helped me also.
– FrenkyB
Nov 19 '15 at 11:18
add a comment |
up vote
30
down vote
favorite
up vote
30
down vote
favorite
My copy of Visual Studio seems to be set in "Always On Top" Mode. It runs this way by default; there seems to be no way of changing it.
Visual Studio runs as Administrator/Elevated, but that really shouldn't affect whether or not Visual Studio runs as "Always On Top."
Any idea why this may be occurring, and how to prevent it from happening?
visual-studio always-on-top
edited Apr 4 '16 at 10:56
DavidPostill♦
103k25220255
asked Jun 12 '11 at 6:31
SomeUser
151124
My copy of Visual Studio seems to be set in "Always On Top" Mode. It runs this way by default; there seems to be no way of changing it.
Visual Studio runs as Administrator/Elevated, but that really shouldn't affect whether or not Visual Studio runs as "Always On Top."
Any idea why this may be occurring, and how to prevent it from happening?
visual-studio always-on-top
visual-studio always-on-top
edited Apr 4 '16 at 10:56
DavidPostill♦
103k25220255
asked Jun 12 '11 at 6:31
SomeUser
151124
edited Apr 4 '16 at 10:56
DavidPostill♦
103k25220255
asked Jun 12 '11 at 6:31
SomeUser
151124
edited Apr 4 '16 at 10:56
DavidPostill♦
103k25220255
edited Apr 4 '16 at 10:56
DavidPostill♦
103k25220255
edited Apr 4 '16 at 10:56
DavidPostill♦
103k25220255
103k25220255
asked Jun 12 '11 at 6:31
SomeUser
151124
asked Jun 12 '11 at 6:31
SomeUser
151124
asked Jun 12 '11 at 6:31
SomeUser
151124
151124
4
I saw a glimpse of this problem with Visual Studio 2010 starting to run "Always On Top" in Windows7, but it only happened straight upon a ReSharper update, and got resolved as soon as Visual Studio was restarted.
– user157214
Sep 9 '12 at 9:43
1
Which version of Visual Studio do you refer to?
– Marcel
Dec 10 '13 at 10:18
Do you have ReSharper installed also? It seems to have a history of causing this type of issue on various versions.
– panhandel
Dec 31 '13 at 22:48
I was able to fix the problem with this: stackoverflow.com/a/27411034/2667554
– enn
Apr 27 '15 at 9:54
Simple restart of visual studio 2010 helped me also.
– FrenkyB
Nov 19 '15 at 11:18
add a comment |
4
I saw a glimpse of this problem with Visual Studio 2010 starting to run "Always On Top" in Windows7, but it only happened straight upon a ReSharper update, and got resolved as soon as Visual Studio was restarted.
– user157214
Sep 9 '12 at 9:43
1
Which version of Visual Studio do you refer to?
– Marcel
Dec 10 '13 at 10:18
Do you have ReSharper installed also? It seems to have a history of causing this type of issue on various versions.
– panhandel
Dec 31 '13 at 22:48
I was able to fix the problem with this: stackoverflow.com/a/27411034/2667554
– enn
Apr 27 '15 at 9:54
Simple restart of visual studio 2010 helped me also.
– FrenkyB
Nov 19 '15 at 11:18
4
4
I saw a glimpse of this problem with Visual Studio 2010 starting to run "Always On Top" in Windows7, but it only happened straight upon a ReSharper update, and got resolved as soon as Visual Studio was restarted.
– user157214
Sep 9 '12 at 9:43
I saw a glimpse of this problem with Visual Studio 2010 starting to run "Always On Top" in Windows7, but it only happened straight upon a ReSharper update, and got resolved as soon as Visual Studio was restarted.
– user157214
Sep 9 '12 at 9:43
1
1
Which version of Visual Studio do you refer to?
– Marcel
Dec 10 '13 at 10:18
Which version of Visual Studio do you refer to?
– Marcel
Dec 10 '13 at 10:18
Do you have ReSharper installed also? It seems to have a history of causing this type of issue on various versions.
– panhandel
Dec 31 '13 at 22:48
Do you have ReSharper installed also? It seems to have a history of causing this type of issue on various versions.
– panhandel
Dec 31 '13 at 22:48
I was able to fix the problem with this: stackoverflow.com/a/27411034/2667554
– enn
Apr 27 '15 at 9:54
I was able to fix the problem with this: stackoverflow.com/a/27411034/2667554
– enn
Apr 27 '15 at 9:54
Simple restart of visual studio 2010 helped me also.
– FrenkyB
Nov 19 '15 at 11:18
Simple restart of visual studio 2010 helped me also.
– FrenkyB
Nov 19 '15 at 11:18
add a comment |
8 Answers
8
active
oldest
votes
up vote
11
down vote
I had a similar thing happen with Visual Studio being stuck as always on top. It started happening after I hit the Windows key followed by a bunch of arrow/home/end/pageup/pagedn keystrokes by accident (I had meant to use the control key).
What seemed to clear the always-on-top behavior was to select a different application (eg: Chrome), then press Windows-Home (which minimized everything other than Chrome), then press Window-Alt-Home. Then I could un-minimize Visual Studio, and it would no longer be always on top.
This worked with VS2010, VS2012 and VS2013 when they got into this weird always on top mode.
edited Mar 10 '15 at 18:40
user147426
154
answered Jan 21 '14 at 1:56
user281806
21124
3
This work around didn't work for me. Windows-Alt-Home seems to just tell Chrome to go to the home page. Focusing on the desktop and Windows-Alt-Home didn't seem to work either. - I run VS2010 in Admin mode - Resharper - Windows 7 I don't have a solution, just giving feedback
– David Chiew
Feb 5 '15 at 22:35
5
This almost worked for me; I had to press Windows+Home (I didn't know about that one) and then simply pressed Windows+Home again. Windows+Alt+Home just sent my chrome to it's homepage. So: Windows+Home -> wait for the windows to come down -> Windows+Home -> Fixed!
– Nebula
Dec 10 '15 at 7:26
As @Nebula pointed out, the ALT modifier should not be used. Confirmed fix for VS 2017 as well! :)
– Johny Skovdal
Jul 4 '17 at 9:17
add a comment |
up vote
2
down vote
Perhaps an addin is causing it? Try disabling addins in Tools/Add-in manager then run Visual Studio in safe mode by executing
devenv.exe /safemode
answered Jan 8 '14 at 7:44
frodeborli
1443
this is the definitive answer imho.
– nocarrier
May 14 '14 at 1:46
works like a charm with after installing Resharper 8.2 !
– Guy
Apr 29 '15 at 6:02
add a comment |
up vote
2
down vote
Save your work, close Visual Studio, reopen it. Hit start, or debug, or hit F5.
This worked for me.
Very strange though, for months I didn't have this problem, and earlier when I started debugging, my window was behind Visual Studio's window... Thought it strange as it never happened before. Closed Visual Studio, reopened it, and viola.
answered May 26 '16 at 13:38
James Heffer
311
add a comment |
up vote
1
down vote
Use windowdetective to check if it's actually set to always ontop
Work from there to determine the cause.
answered Jan 26 '14 at 0:41
Elitism
412
add a comment |
up vote
0
down vote
Maybe for some reason, the always-on-top property of your Visual Studio (VS) is being saved somewhere and then reloaded on run.
Depending on your VS version, you may be able to use FileBox eXtender(FBX) to change its always-on-top property for each run or permanently. It is probably better to use the version matching your Windows' architecture; 64-bit for x64 and 32-bit for x86. Also, FBX can probably be only used for elevated-mode programs if itself is run in elevated mode (e.g. "Run as Administrator").
Always-on-top status can be switched by clicking the pushpin on the program title bar when FileBox eXtender is running.
answered Dec 11 '13 at 18:11
Mohammad Amin Bandekhoda
15814
add a comment |
up vote
0
down vote
When I got this problem I found a solution to the reverse problem over at How-To Geek. Luckily it involved a TOGGLE which I could use to disable the always on top mode that Visual Studio's window had gotten into. As per the above link, I added this to my AutoHotkey script
^SPACE:: Winset, Alwaysontop, , A
and then I selected Visual Studio's window and used ctrl-space to toggle always on top. It worked like a charm.
answered Jun 28 '16 at 8:49
Sebastian Ärleryd
11616
add a comment |
up vote
0
down vote
Restarting Visual Studio 2015 fixed the problem.
In my case, VS switched in "Always On Top" mode while I was using intellisense from ReSharper.
answered Aug 1 '17 at 16:03
swabber
1
add a comment |
up vote
0
down vote
Fixed the issue with VS2017 on Windows 10 by giving focus to another application and pressing Windows+Home (to minimize all windows apart from the one which got focus) and then Windows+Home again to restore all other windows (including VS) and this time VS wasn't always on top anymore.
answered Nov 26 at 16:29
Bruno Douglas
1
add a comment |
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
});
}
});
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%2f296019%2fwhy-does-visual-studio-run-in-always-on-top-mode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
8 Answers
8
active
oldest
votes
8 Answers
8
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
11
down vote
I had a similar thing happen with Visual Studio being stuck as always on top. It started happening after I hit the Windows key followed by a bunch of arrow/home/end/pageup/pagedn keystrokes by accident (I had meant to use the control key).
What seemed to clear the always-on-top behavior was to select a different application (eg: Chrome), then press Windows-Home (which minimized everything other than Chrome), then press Window-Alt-Home. Then I could un-minimize Visual Studio, and it would no longer be always on top.
This worked with VS2010, VS2012 and VS2013 when they got into this weird always on top mode.
edited Mar 10 '15 at 18:40
user147426
154
answered Jan 21 '14 at 1:56
user281806
21124
3
This work around didn't work for me. Windows-Alt-Home seems to just tell Chrome to go to the home page. Focusing on the desktop and Windows-Alt-Home didn't seem to work either. - I run VS2010 in Admin mode - Resharper - Windows 7 I don't have a solution, just giving feedback
– David Chiew
Feb 5 '15 at 22:35
5
This almost worked for me; I had to press Windows+Home (I didn't know about that one) and then simply pressed Windows+Home again. Windows+Alt+Home just sent my chrome to it's homepage. So: Windows+Home -> wait for the windows to come down -> Windows+Home -> Fixed!
– Nebula
Dec 10 '15 at 7:26
As @Nebula pointed out, the ALT modifier should not be used. Confirmed fix for VS 2017 as well! :)
– Johny Skovdal
Jul 4 '17 at 9:17
add a comment |
up vote
11
down vote
I had a similar thing happen with Visual Studio being stuck as always on top. It started happening after I hit the Windows key followed by a bunch of arrow/home/end/pageup/pagedn keystrokes by accident (I had meant to use the control key).
What seemed to clear the always-on-top behavior was to select a different application (eg: Chrome), then press Windows-Home (which minimized everything other than Chrome), then press Window-Alt-Home. Then I could un-minimize Visual Studio, and it would no longer be always on top.
This worked with VS2010, VS2012 and VS2013 when they got into this weird always on top mode.
edited Mar 10 '15 at 18:40
user147426
154
answered Jan 21 '14 at 1:56
user281806
21124
3
This work around didn't work for me. Windows-Alt-Home seems to just tell Chrome to go to the home page. Focusing on the desktop and Windows-Alt-Home didn't seem to work either. - I run VS2010 in Admin mode - Resharper - Windows 7 I don't have a solution, just giving feedback
– David Chiew
Feb 5 '15 at 22:35
5
This almost worked for me; I had to press Windows+Home (I didn't know about that one) and then simply pressed Windows+Home again. Windows+Alt+Home just sent my chrome to it's homepage. So: Windows+Home -> wait for the windows to come down -> Windows+Home -> Fixed!
– Nebula
Dec 10 '15 at 7:26
As @Nebula pointed out, the ALT modifier should not be used. Confirmed fix for VS 2017 as well! :)
– Johny Skovdal
Jul 4 '17 at 9:17
add a comment |
up vote
11
down vote
up vote
11
down vote
I had a similar thing happen with Visual Studio being stuck as always on top. It started happening after I hit the Windows key followed by a bunch of arrow/home/end/pageup/pagedn keystrokes by accident (I had meant to use the control key).
What seemed to clear the always-on-top behavior was to select a different application (eg: Chrome), then press Windows-Home (which minimized everything other than Chrome), then press Window-Alt-Home. Then I could un-minimize Visual Studio, and it would no longer be always on top.
This worked with VS2010, VS2012 and VS2013 when they got into this weird always on top mode.
edited Mar 10 '15 at 18:40
user147426
154
answered Jan 21 '14 at 1:56
user281806
21124
I had a similar thing happen with Visual Studio being stuck as always on top. It started happening after I hit the Windows key followed by a bunch of arrow/home/end/pageup/pagedn keystrokes by accident (I had meant to use the control key).
What seemed to clear the always-on-top behavior was to select a different application (eg: Chrome), then press Windows-Home (which minimized everything other than Chrome), then press Window-Alt-Home. Then I could un-minimize Visual Studio, and it would no longer be always on top.
This worked with VS2010, VS2012 and VS2013 when they got into this weird always on top mode.
edited Mar 10 '15 at 18:40
user147426
154
answered Jan 21 '14 at 1:56
user281806
21124
edited Mar 10 '15 at 18:40
user147426
154
edited Mar 10 '15 at 18:40
user147426
154
edited Mar 10 '15 at 18:40
user147426
154
154
answered Jan 21 '14 at 1:56
user281806
21124
answered Jan 21 '14 at 1:56
user281806
21124
answered Jan 21 '14 at 1:56
user281806
21124
21124
3
This work around didn't work for me. Windows-Alt-Home seems to just tell Chrome to go to the home page. Focusing on the desktop and Windows-Alt-Home didn't seem to work either. - I run VS2010 in Admin mode - Resharper - Windows 7 I don't have a solution, just giving feedback
– David Chiew
Feb 5 '15 at 22:35
5
This almost worked for me; I had to press Windows+Home (I didn't know about that one) and then simply pressed Windows+Home again. Windows+Alt+Home just sent my chrome to it's homepage. So: Windows+Home -> wait for the windows to come down -> Windows+Home -> Fixed!
– Nebula
Dec 10 '15 at 7:26
As @Nebula pointed out, the ALT modifier should not be used. Confirmed fix for VS 2017 as well! :)
– Johny Skovdal
Jul 4 '17 at 9:17
add a comment |
3
This work around didn't work for me. Windows-Alt-Home seems to just tell Chrome to go to the home page. Focusing on the desktop and Windows-Alt-Home didn't seem to work either. - I run VS2010 in Admin mode - Resharper - Windows 7 I don't have a solution, just giving feedback
– David Chiew
Feb 5 '15 at 22:35
5
This almost worked for me; I had to press Windows+Home (I didn't know about that one) and then simply pressed Windows+Home again. Windows+Alt+Home just sent my chrome to it's homepage. So: Windows+Home -> wait for the windows to come down -> Windows+Home -> Fixed!
– Nebula
Dec 10 '15 at 7:26
As @Nebula pointed out, the ALT modifier should not be used. Confirmed fix for VS 2017 as well! :)
– Johny Skovdal
Jul 4 '17 at 9:17
3
3
This work around didn't work for me. Windows-Alt-Home seems to just tell Chrome to go to the home page. Focusing on the desktop and Windows-Alt-Home didn't seem to work either. - I run VS2010 in Admin mode - Resharper - Windows 7 I don't have a solution, just giving feedback
– David Chiew
Feb 5 '15 at 22:35
This work around didn't work for me. Windows-Alt-Home seems to just tell Chrome to go to the home page. Focusing on the desktop and Windows-Alt-Home didn't seem to work either. - I run VS2010 in Admin mode - Resharper - Windows 7 I don't have a solution, just giving feedback
– David Chiew
Feb 5 '15 at 22:35
5
5
This almost worked for me; I had to press Windows+Home (I didn't know about that one) and then simply pressed Windows+Home again. Windows+Alt+Home just sent my chrome to it's homepage. So: Windows+Home -> wait for the windows to come down -> Windows+Home -> Fixed!
– Nebula
Dec 10 '15 at 7:26
This almost worked for me; I had to press Windows+Home (I didn't know about that one) and then simply pressed Windows+Home again. Windows+Alt+Home just sent my chrome to it's homepage. So: Windows+Home -> wait for the windows to come down -> Windows+Home -> Fixed!
– Nebula
Dec 10 '15 at 7:26
As @Nebula pointed out, the ALT modifier should not be used. Confirmed fix for VS 2017 as well! :)
– Johny Skovdal
Jul 4 '17 at 9:17
As @Nebula pointed out, the ALT modifier should not be used. Confirmed fix for VS 2017 as well! :)
– Johny Skovdal
Jul 4 '17 at 9:17
add a comment |
up vote
2
down vote
Perhaps an addin is causing it? Try disabling addins in Tools/Add-in manager then run Visual Studio in safe mode by executing
devenv.exe /safemode
answered Jan 8 '14 at 7:44
frodeborli
1443
this is the definitive answer imho.
– nocarrier
May 14 '14 at 1:46
works like a charm with after installing Resharper 8.2 !
– Guy
Apr 29 '15 at 6:02
add a comment |
up vote
2
down vote
Perhaps an addin is causing it? Try disabling addins in Tools/Add-in manager then run Visual Studio in safe mode by executing
devenv.exe /safemode
answered Jan 8 '14 at 7:44
frodeborli
1443
this is the definitive answer imho.
– nocarrier
May 14 '14 at 1:46
works like a charm with after installing Resharper 8.2 !
– Guy
Apr 29 '15 at 6:02
add a comment |
up vote
2
down vote
up vote
2
down vote
Perhaps an addin is causing it? Try disabling addins in Tools/Add-in manager then run Visual Studio in safe mode by executing
devenv.exe /safemode
answered Jan 8 '14 at 7:44
frodeborli
1443
Perhaps an addin is causing it? Try disabling addins in Tools/Add-in manager then run Visual Studio in safe mode by executing
devenv.exe /safemode
answered Jan 8 '14 at 7:44
frodeborli
1443
answered Jan 8 '14 at 7:44
frodeborli
1443
answered Jan 8 '14 at 7:44
frodeborli
1443
answered Jan 8 '14 at 7:44
frodeborli
1443
1443
this is the definitive answer imho.
– nocarrier
May 14 '14 at 1:46
works like a charm with after installing Resharper 8.2 !
– Guy
Apr 29 '15 at 6:02
add a comment |
this is the definitive answer imho.
– nocarrier
May 14 '14 at 1:46
works like a charm with after installing Resharper 8.2 !
– Guy
Apr 29 '15 at 6:02
this is the definitive answer imho.
– nocarrier
May 14 '14 at 1:46
this is the definitive answer imho.
– nocarrier
May 14 '14 at 1:46
works like a charm with after installing Resharper 8.2 !
– Guy
Apr 29 '15 at 6:02
works like a charm with after installing Resharper 8.2 !
– Guy
Apr 29 '15 at 6:02
add a comment |
up vote
2
down vote
Save your work, close Visual Studio, reopen it. Hit start, or debug, or hit F5.
This worked for me.
Very strange though, for months I didn't have this problem, and earlier when I started debugging, my window was behind Visual Studio's window... Thought it strange as it never happened before. Closed Visual Studio, reopened it, and viola.
answered May 26 '16 at 13:38
James Heffer
311
add a comment |
up vote
2
down vote
Save your work, close Visual Studio, reopen it. Hit start, or debug, or hit F5.
This worked for me.
Very strange though, for months I didn't have this problem, and earlier when I started debugging, my window was behind Visual Studio's window... Thought it strange as it never happened before. Closed Visual Studio, reopened it, and viola.
answered May 26 '16 at 13:38
James Heffer
311
add a comment |
up vote
2
down vote
up vote
2
down vote
Save your work, close Visual Studio, reopen it. Hit start, or debug, or hit F5.
This worked for me.
Very strange though, for months I didn't have this problem, and earlier when I started debugging, my window was behind Visual Studio's window... Thought it strange as it never happened before. Closed Visual Studio, reopened it, and viola.
answered May 26 '16 at 13:38
James Heffer
311
Save your work, close Visual Studio, reopen it. Hit start, or debug, or hit F5.
This worked for me.
Very strange though, for months I didn't have this problem, and earlier when I started debugging, my window was behind Visual Studio's window... Thought it strange as it never happened before. Closed Visual Studio, reopened it, and viola.
answered May 26 '16 at 13:38
James Heffer
311
answered May 26 '16 at 13:38
James Heffer
311
answered May 26 '16 at 13:38
James Heffer
311
answered May 26 '16 at 13:38
James Heffer
311
311
add a comment |
add a comment |
up vote
1
down vote
Use windowdetective to check if it's actually set to always ontop
Work from there to determine the cause.
answered Jan 26 '14 at 0:41
Elitism
412
add a comment |
up vote
1
down vote
Use windowdetective to check if it's actually set to always ontop
Work from there to determine the cause.
answered Jan 26 '14 at 0:41
Elitism
412
add a comment |
up vote
1
down vote
up vote
1
down vote
Use windowdetective to check if it's actually set to always ontop
Work from there to determine the cause.
answered Jan 26 '14 at 0:41
Elitism
412
Use windowdetective to check if it's actually set to always ontop
Work from there to determine the cause.
answered Jan 26 '14 at 0:41
Elitism
412
answered Jan 26 '14 at 0:41
Elitism
412
answered Jan 26 '14 at 0:41
Elitism
412
answered Jan 26 '14 at 0:41
Elitism
412
412
add a comment |
add a comment |
up vote
0
down vote
Maybe for some reason, the always-on-top property of your Visual Studio (VS) is being saved somewhere and then reloaded on run.
Depending on your VS version, you may be able to use FileBox eXtender(FBX) to change its always-on-top property for each run or permanently. It is probably better to use the version matching your Windows' architecture; 64-bit for x64 and 32-bit for x86. Also, FBX can probably be only used for elevated-mode programs if itself is run in elevated mode (e.g. "Run as Administrator").
Always-on-top status can be switched by clicking the pushpin on the program title bar when FileBox eXtender is running.
answered Dec 11 '13 at 18:11
Mohammad Amin Bandekhoda
15814
add a comment |
up vote
0
down vote
Maybe for some reason, the always-on-top property of your Visual Studio (VS) is being saved somewhere and then reloaded on run.
Depending on your VS version, you may be able to use FileBox eXtender(FBX) to change its always-on-top property for each run or permanently. It is probably better to use the version matching your Windows' architecture; 64-bit for x64 and 32-bit for x86. Also, FBX can probably be only used for elevated-mode programs if itself is run in elevated mode (e.g. "Run as Administrator").
Always-on-top status can be switched by clicking the pushpin on the program title bar when FileBox eXtender is running.
answered Dec 11 '13 at 18:11
Mohammad Amin Bandekhoda
15814
add a comment |
up vote
0
down vote
up vote
0
down vote
Maybe for some reason, the always-on-top property of your Visual Studio (VS) is being saved somewhere and then reloaded on run.
Depending on your VS version, you may be able to use FileBox eXtender(FBX) to change its always-on-top property for each run or permanently. It is probably better to use the version matching your Windows' architecture; 64-bit for x64 and 32-bit for x86. Also, FBX can probably be only used for elevated-mode programs if itself is run in elevated mode (e.g. "Run as Administrator").
Always-on-top status can be switched by clicking the pushpin on the program title bar when FileBox eXtender is running.
answered Dec 11 '13 at 18:11
Mohammad Amin Bandekhoda
15814
Maybe for some reason, the always-on-top property of your Visual Studio (VS) is being saved somewhere and then reloaded on run.
Depending on your VS version, you may be able to use FileBox eXtender(FBX) to change its always-on-top property for each run or permanently. It is probably better to use the version matching your Windows' architecture; 64-bit for x64 and 32-bit for x86. Also, FBX can probably be only used for elevated-mode programs if itself is run in elevated mode (e.g. "Run as Administrator").
Always-on-top status can be switched by clicking the pushpin on the program title bar when FileBox eXtender is running.
answered Dec 11 '13 at 18:11
Mohammad Amin Bandekhoda
15814
answered Dec 11 '13 at 18:11
Mohammad Amin Bandekhoda
15814
answered Dec 11 '13 at 18:11
Mohammad Amin Bandekhoda
15814
answered Dec 11 '13 at 18:11
Mohammad Amin Bandekhoda
15814
15814
add a comment |
add a comment |
up vote
0
down vote
When I got this problem I found a solution to the reverse problem over at How-To Geek. Luckily it involved a TOGGLE which I could use to disable the always on top mode that Visual Studio's window had gotten into. As per the above link, I added this to my AutoHotkey script
^SPACE:: Winset, Alwaysontop, , A
and then I selected Visual Studio's window and used ctrl-space to toggle always on top. It worked like a charm.
answered Jun 28 '16 at 8:49
Sebastian Ärleryd
11616
add a comment |
up vote
0
down vote
When I got this problem I found a solution to the reverse problem over at How-To Geek. Luckily it involved a TOGGLE which I could use to disable the always on top mode that Visual Studio's window had gotten into. As per the above link, I added this to my AutoHotkey script
^SPACE:: Winset, Alwaysontop, , A
and then I selected Visual Studio's window and used ctrl-space to toggle always on top. It worked like a charm.
answered Jun 28 '16 at 8:49
Sebastian Ärleryd
11616
add a comment |
up vote
0
down vote
up vote
0
down vote
When I got this problem I found a solution to the reverse problem over at How-To Geek. Luckily it involved a TOGGLE which I could use to disable the always on top mode that Visual Studio's window had gotten into. As per the above link, I added this to my AutoHotkey script
^SPACE:: Winset, Alwaysontop, , A
and then I selected Visual Studio's window and used ctrl-space to toggle always on top. It worked like a charm.
answered Jun 28 '16 at 8:49
Sebastian Ärleryd
11616
When I got this problem I found a solution to the reverse problem over at How-To Geek. Luckily it involved a TOGGLE which I could use to disable the always on top mode that Visual Studio's window had gotten into. As per the above link, I added this to my AutoHotkey script
^SPACE:: Winset, Alwaysontop, , A
and then I selected Visual Studio's window and used ctrl-space to toggle always on top. It worked like a charm.
answered Jun 28 '16 at 8:49
Sebastian Ärleryd
11616
answered Jun 28 '16 at 8:49
Sebastian Ärleryd
11616
answered Jun 28 '16 at 8:49
Sebastian Ärleryd
11616
answered Jun 28 '16 at 8:49
Sebastian Ärleryd
11616
11616
add a comment |
add a comment |
up vote
0
down vote
Restarting Visual Studio 2015 fixed the problem.
In my case, VS switched in "Always On Top" mode while I was using intellisense from ReSharper.
answered Aug 1 '17 at 16:03
swabber
1
add a comment |
up vote
0
down vote
Restarting Visual Studio 2015 fixed the problem.
In my case, VS switched in "Always On Top" mode while I was using intellisense from ReSharper.
answered Aug 1 '17 at 16:03
swabber
1
add a comment |
up vote
0
down vote
up vote
0
down vote
Restarting Visual Studio 2015 fixed the problem.
In my case, VS switched in "Always On Top" mode while I was using intellisense from ReSharper.
answered Aug 1 '17 at 16:03
swabber
1
Restarting Visual Studio 2015 fixed the problem.
In my case, VS switched in "Always On Top" mode while I was using intellisense from ReSharper.
answered Aug 1 '17 at 16:03
swabber
1
answered Aug 1 '17 at 16:03
swabber
1
answered Aug 1 '17 at 16:03
swabber
1
answered Aug 1 '17 at 16:03
swabber
1
1
add a comment |
add a comment |
up vote
0
down vote
Fixed the issue with VS2017 on Windows 10 by giving focus to another application and pressing Windows+Home (to minimize all windows apart from the one which got focus) and then Windows+Home again to restore all other windows (including VS) and this time VS wasn't always on top anymore.
answered Nov 26 at 16:29
Bruno Douglas
1
add a comment |
up vote
0
down vote
Fixed the issue with VS2017 on Windows 10 by giving focus to another application and pressing Windows+Home (to minimize all windows apart from the one which got focus) and then Windows+Home again to restore all other windows (including VS) and this time VS wasn't always on top anymore.
answered Nov 26 at 16:29
Bruno Douglas
1
add a comment |
up vote
0
down vote
up vote
0
down vote
Fixed the issue with VS2017 on Windows 10 by giving focus to another application and pressing Windows+Home (to minimize all windows apart from the one which got focus) and then Windows+Home again to restore all other windows (including VS) and this time VS wasn't always on top anymore.
answered Nov 26 at 16:29
Bruno Douglas
1
Fixed the issue with VS2017 on Windows 10 by giving focus to another application and pressing Windows+Home (to minimize all windows apart from the one which got focus) and then Windows+Home again to restore all other windows (including VS) and this time VS wasn't always on top anymore.
answered Nov 26 at 16:29
Bruno Douglas
1
answered Nov 26 at 16:29
Bruno Douglas
1
answered Nov 26 at 16:29
Bruno Douglas
1
answered Nov 26 at 16:29
Bruno Douglas
1
1
add a comment |
add a comment |
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%2f296019%2fwhy-does-visual-studio-run-in-always-on-top-mode%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
4
I saw a glimpse of this problem with Visual Studio 2010 starting to run "Always On Top" in Windows7, but it only happened straight upon a ReSharper update, and got resolved as soon as Visual Studio was restarted.
– user157214
Sep 9 '12 at 9:43
1
Which version of Visual Studio do you refer to?
– Marcel
Dec 10 '13 at 10:18
Do you have ReSharper installed also? It seems to have a history of causing this type of issue on various versions.
– panhandel
Dec 31 '13 at 22:48
I was able to fix the problem with this: stackoverflow.com/a/27411034/2667554
– enn
Apr 27 '15 at 9:54
Simple restart of visual studio 2010 helped me also.
– FrenkyB
Nov 19 '15 at 11:18