When Visual Studio runs as administrator, Ctrl-C and Ctrl-V shortcut keys are not working...
But when running VS normally - not as administrator - those shortcut keys work fine.
I have some not the same issue, as an author, but i think maybe it is somehow related.
My case is : time to time i can't press CTRL+C in my microsoft visual studio 2022 (community edition) to interupt terminal execution (powershell). For separately opened terminal (outside of Visual Studio) works great, so something wrong with VS.
Only one fix i found is to disable in options->keyboard -> edit.copy hotkey and re-assign it from "Global" to "Text editor". So, it may affect other areas, but works fine in this case. What is the core issue here and how to fix it other way i did not found.
Maybe will be helpfull for anybody.
I have this behaviour for all text-editor that I use in "Run as Administrator" mode.
The problem comes from a third-party application that uses a global hook (listens to a global hotkey) on those keystrokes (e.g. "Ctrl+C"). In my case it was a personal AutoHotKey/AutoIt3 script that was acting like a copy-paste board. But it could be some other application, or a malware.
If you disable such an application, the keyboard shortcuts Ctrl+C etc. should work fine.
In Tools=> Options => Keyboard => Check that Edit.Cut and Edit.Copy is bound to Ctrl+X and Ctrl+C
Or you can reset your settings using Reset button.
I have the following AHK file running to remap the Caps Locks to control.
+Capslock::Capslock ; make shift+Caps-Lock the Caps Lock toggle
Capslock::Control ; make Caps Lock the control button
It works well on other applications like Atom, Chrome, Evernote, and ect. But only has problem with Visual Studio 2013. The Caps Locks still function as caps locks. Even worth, if I accidentally pressed Caps Locks in Visual Studio and close it, I have to reopen Visual Studio and press Caps Locks again to cancel.
Is there any way to solve this issue?
Problem solved. Run AHK as administrator, because I ran the Visual Studio 2013 in admin mode. Then if any application run as administrator, the AHK should run the same, otherwise will be malfunction.
Thanks for Paul Stelian and wOxxOm.
Visual Studio seems to install some kind of keyboard handler, but I've found that simply (re-)loading my AHK after starting VS brings back my mappings. Presumably, there is some table that VS and AHK are both writing to.
There is a Reload item on the AHK tray icon's context menu.
Also, as there are other situations that will cause CapsLock to be toggled against your wishes, you probably want to either add a mapping to toggle it back (the documentation uses +Capslock::Capslock as an example), or else add SetCapslockState, AlwaysOff if you never care about using it.
I have a minor annoyance with Visual Studio. In the bottom right hand corner of Visual Studio, there is a INS/OVR button to toggle Insert/Overwrite. I always have this button set to INS, and I always want it to be set to INS.
However, sometimes when I build the solution, Visual Studio changes this back to OVR. I have to click on the button to change it back to INS, which is slightly inconvenient.
I do not know why this setting sometimes changes.
Is there anyway I can permanently disable the overwrite mode in Visual Studio or prevent solution builds from changing this setting?
Visual Studio, Tools > Options > Environment > Keyboard, remove the shortcut binding for Edit.OvertypeMode
I don't think you can permanently turn insert/overwrite off. Are you accidentally pressing insert on your keyboard? You can press the insert key on your keyboard or Shift+0 on the numpad to toggle it back again.
Go to Visual Studio Code's settings and type "overtype" in the search bar, and set it to 'never'.
Hope this helped! :)
Sometimes visual studio wont disable overtype even if you hit insert with numlock on, If this happens just close script and open it again and it will work. This is a bug in visual studio.
I keep getting a very annoying problem in Visual Studio. When I try to delete some text by pressing backspace it doesn't work. Why is this? What is going on? Sometimes I have to close and open Visual Studio to make this problem go away but I just tried that right now and it didn't work. Backspace works in Notepad in case you are wondering.
In Visual Studio go to:
Tools
Options
Environment
Keyboard
Find "Edit.DeleteBackwards" command.
In "Use new shortcut in:" dropdown select "Text Editor".
In "Press shortcut keys:" click backspace so it would show "Bkspce"
Click "OK".
Backspace should start working for you again.
This seems to happen to me when I open a solution and there are files already open. I used to close the files, then close and re-open the solution to fix it, but now I just hit Alt + Enter.
Here is the blog where I found this trick.
I solved this issue resetting keyboard mapping scheme.
Tools -> Options -> Environment -> Keyboard -> Reset.
A quick fix for me is to simply open any menu from the menu bar. Once the menu is closed the non-character keys start to work again.
Except for the above methods.
You should also check the shortcut key settings:
File -> Preferences -> Keyboard Shortcuts -> 'Then check the item: deleteLeft'.
I get this from time to time in VS2010 as well and simply just using the mouse to change tabs/files seems to always fix it now. Nothing more.
This method is working at 100%.
Go to "File-> Preferences -> Keyboard Shortcuts" and search for deleteLeft and add keybinding "Backspace".
Odd that this is still an issue even in VS 2019. Both the backspace and delete keys didn't work. Quick fix, I just ran the project and it seemed to give it the kick it needed.
All I did was exit visual studio and restart it.None of the above options worked for me.
In my case the problem was the "When" Condition in "File-> Preferences -> Keyboard Shortcuts".
I removed "textInputFocus && !editorReadonly" and it works now as expected.
I'm looking forward to the side effects ;).
Try resetting your Visual Studio Settings
Go to :
All Program > Visual Studio 20xx > Visual Studio Tools
Run Developer Command Prompt for VS20xx as Administrator and this command:
devenv.exe /resetsettings
A quick work-around for me is locking the pc (Windows+L) and logging in again.
You can reset keyboard mapping scheme like this
Options => Environment => Keyboard then select (Default) in the comboBox and click Reset button and then Ok button to confirm
Visual studio 2019 : Keyboard mapping sheme
Tested in Visual Studio 2019
This problem happened for me when I used a different version of resharper at home and then took that project to my employment. Backspace works for me now after I deleted the bin and obj and resharper directories.
I have this problem after I install Vim, uninstall Vim Backspace works fine.
When this issue has happened to me, I've found that hitting delete or backspace is unresponsive only within a portion of my code. This portion happened to be some code that I've pasted in from the internet somewhere.
To fix this issue, I cut out the recently pasted problematic code and then pasted it into a text editor like Notepad++. Then copying and pasting that same code out of the text editor and back into Visual Studio fixed the problem.
Using Visual Studio Community 2019 (16.4.3)
I just searched this issue because I could click in my document, type, et cetera, but I could not use backspace, delete, ctrl+z, or the arrow keys.
Opening the "File" menu, I noticed the Save option referred to a different file. I checked that file and found that all of the keys that seemed not to work were actually editing that other file.
Switching between the file in half-focus and the file I intended to edit worked and, luckily, undo was able to fix the file I unknowingly butchered.
If you wound up here, check your "File" menu to make sure the correct file is referenced, since the fix is quick and easy to try.
Just had this exact issue (along with 'Enter', 'Ctrl+X', 'Ctrl+C', 'Ctrl+V', 'Ctrl+Z' keyboard mappings seemingly doing nothing) in the latest VS preview version below:
Microsoft Visual Studio Professional 2022 (64-bit) - Preview
Version 17.2.0 Preview 6.0
The fix for me was to move to another tab (I had multiple open) use the backspace key which worked fine, then move back to the original tab with which it wasn't working, save the file (as it had outstanding changes) and then I found backspace and all other shortcuts then worked!
I can only think that VS got in a locked (to keyboard mappings) state for that particular tab.
A few notes on this:
I knew it wasn't a keyboard issue as I was able to use those
keys/mappings fine in other apps.
I found closing and reopening VS didn't work.
Also resetting the keyboard mappings (through Options menu as others have described) didn't work.
I had multiple tabs open.
Resharper was disabled.
I just had this happen in one instance of Visual Studio 2022, caused by the debug settings editor window being open in another instance of Visual Studio 2022 in the background where I couldn't see it.
Closing that window resolved it.
I've had this issue for a long time. I'm not sure what causes it, but Alt + Enter works.
The extensions that I'm running include AnkhSVN, MySQL Tools, and Productivity Power Tools.
My install of Visual Studio 2008 does not support IE style back and forward navigation withe the mouse in the C# code editor.
Searches show that multiple people have run into this problem but I have yet to find a correct solution.
There's even a VS add-in hack just to work around the "bug".
Any idea why this functionality fails for some users and how to fix it?
You can mitigate the problem by AutoHotKey tool (free, open source).
Let's assume your Visual Studio 2008 has these editor commands and their respective shortcuts:
View.NavigateBackward = Ctrl+-
View.NavigateForward = Ctrl+Shift+-
You should be able to verify these shortcuts in keyboard options. Verified? Let's proceed.
So will you be just fine if your mouse will send these keyboard shortcuts if the Visual Studio's main window is active?
Then install the tool and add the following two mappings:
XButton1::^-
XButton2::^+-
These correspond to above keyboard shortcuts: ^ = Ctrl, + = Shift, - = -
Using AutoHotKey icon in notification area, reload definition file you just updated. Now your mouse buttons should produce the above shortcuts. Test them.
If they work for you in Visual Studio editor, you can limit them only to Visual Studio main window, otherwise they work across the entire desktop:
SetTitleMatchMode, RegEx
#IfWinActive, .*- Microsoft Visual Studio
XButton1::^-
XButton2::^+-
#IfWinActive
Feel free to adjust title-matching regex if needed.
Do not forget to reload definitions file to apply any changes you made.
Bonus:
And here are some other handy operations if you are holding Shift or Ctrl:
(You have those mouse buttons, let's use them... for commands across the entire desktop.)
+XButton1::^c
+XButton2::^v
^XButton1::^x
^XButton2::^z
(Letters must be lowercase, because uppercase means Shift+letter.)
(And always make sure you are running AHK elevated (as administrator.))
Enjoy!
Visual Studio 2008 is an editor and the apps built in it can also be built in any later version such as Visual Studio 2015. Not trying to be flippant, but the fix is to move to a later version of Studio. If money is a factor look into the Community version. (See Free Dev Tools - Visual Studio Community 2015)