24

I also tried 2 solution. But It doesn't worked.

  1. Go to Tools > Options menu in Visual Studio.
  2. Go to Debugging > General menu item in left pane.
  3. In right view you will see and option Step over properties and operators (Managed only). Uncheck this option and then you are all set.

and

  1. Go to Tools > Options menu in Visual Studio.
  2. Go to Debugging > General menu item in left pane.
  3. In right view you will see and option Enable Just My Code (Managed only). Uncheck this option and then you are all set.
maycil
  • 754
  • 2
  • 8
  • 24

14 Answers14

46

CamStudio application was the issue in my case.
Somehow it reserved this key to itself and Visual Studio was not able to use it anymore (I've tested it MS Word (Alt+F10 - was working as expected, while CamStudio was on - when minimized it appears only in SysTray)).
I've closed CamStudio and it was fine:
F10 functionality "reappeared" in VS2008.

AdiKonstantin
  • 658
  • 1
  • 8
  • 8
  • Thanks for making sure your question was answered. – O. Jones Oct 24 '12 at 11:51
  • Awesome find. Noticed this right away. Just installed CamStudio so this answer caught my eye. – hylander0 May 18 '15 at 14:05
  • TechSmith's SnagIt had this same behavior for me. – solublefish Jul 07 '15 at 00:45
  • thanks for your answer this problem is still there on vs 2015 . – Khurram Ali Dec 22 '15 at 18:12
  • This is crazy... just spent 45min trying to figure out why F10 wasn't working, saw this and realized I had Camtasia Record opened, minimized. Really?!?! I guess I can plug my good keyboard back in again, seeing as how there's really nothing wrong with the F10 key... – jleach Aug 11 '16 at 10:39
  • Yes that is just what happened to me too. General key hook software can be an issue for that – Franck Nov 16 '16 at 19:00
19

Turns out my issue was simpler/more embarassing, but I figured I'd post it just in case it helps someone else.

I had the F Lock (function key lock) turned off, so my F10 keypress wasn't being sent as such. With these newer keyboards (mine is an MS wireless keyboard), there are several modifier keys that affect the keyboard behavior.

Once I enabled F Lock, everything worked as expected.

nalply
  • 26,770
  • 15
  • 78
  • 101
Joe H
  • 191
  • 1
  • 3
13

In the Options.Keyboard page, please select "Debug.StepOver" from the command listbox, and then put focus to the "Press shortcut keys" textbox and press F10, click Assign button to re-assign shortcut, does it work?

You can also try to run Visual Studio under safe mode, which will prevents all third-party VSPackages from loading when Visual Studio starts; if the issue disappear under safe mode, you may consider checking your installed add-ons or VSPackages.

Second, to log all activity of Visual Studio to a log file for further troubleshooting, please use the /Log switch, and post the log file content here, so we can do more investigation on it.

If this feature works well before, and suddenly behave abnormally, it usually indicate that some files or configurations of Visual Studio installation is corrupted or missed, you can:

  1. Restores Visual Studio default settings by using "Devenv.exe /ResetSettings" command. Please backup your settings before restore to default settings.

  2. Repair/reinstall Visual Studio;

To repair Visual Studio In the Add or Remove Programs dialog box, select Visual Studio then click Change/Remove.

Armaan
  • 190
  • 11
  • 2
    Just in case before anyone struggles with trying al sort of things. Check if you don't have any software running (look in the little icons near your system clock). I had "iFun Screen recorder" which was running and stealing the F10 keypress! – Keytrap Apr 19 '21 at 16:05
  • @Keytrap Thank you. It was exactly my case. – Petronius Feb 17 '22 at 18:30
10

Similar to the last post, I had another application that was open. So make sure all third party software is closed. In my situation I had installed CamStudio (screen recorder software). The moment I closed it I was able to start using F10 key again.

Shawn
  • 101
  • 1
  • 2
  • This was the problem in my case. I didn't realize that Camstudio had minimized to the tray, and then Windows 7 automatically hid the tray icon. – Chiara Coetzee Oct 09 '12 at 20:24
8

I also ran into this problem in Visual Studio 2012, and what fixed it for me was disabling .NET Reflector.

rockariotphobia
  • 186
  • 1
  • 3
3

I know this is an old issue, but it's one of the first search results for "Visual Studio F10 not working," so I wanted to post one possible solution here in case anyone else runs across this page with the same problem. My problem was caused by a very specific situation, so it might not work for everyone. The issue was the F10 shortcut simply was not working at all. Nothing happened when pressed. When I tried to reset the shortcut key for the Debug.StepOver, it wouldn't accept F10 as input.

SOLUTION: "Thaw" or uninstall Deep Freeze. I was using software called Deep Freeze to protect certain partitions on my hard drive. Unfortunately, Deep Freeze was protecting ALL of my hard drives, regardless of which drives I specified in the settings. When it was in "frozen" mode, it was causing crashes, hangs, and strange and erratic behavior in other programs including Visual Studio. When I rebooted in "thawed" mode, the problems went away and I regained the ability to F10 normally. Deep Freeze is commonly used on school and business computers, in which case you'd have to contact an administrator to deal with it, or alternately, set a different key combination for Debug.StepOver.

On a side note, also make sure that you're in DEBUG mode, not release mode, when trying to use F10 to step over.

Sphagnum Peat Moss
  • 31
  • 1
3

I had a similar problem on a Microsoft Ergonomic keyboard: F10 did not work as a step over for the debugger. Yet at the same time Fn-F10 worked on the Lenovo laptop. I found a resolution for the Microsoft Ergonomic keyboard: Press the Function lock key just to the right of F12. This is a toggle key that had the function keys turned off.

Roland Wales
  • 73
  • 1
  • 7
3

Tools - Options - Environment - Keyboard

Search with "Debug.StepOver", check is the shortcuts for selcted comman was set to F10(Global), if not then set it you should get it work. If the setting is correct, then you may running some other program that has registered the F10 key as a glabol hotkey and make this fail, try to open as few program as you can see if you find that program, or just change it to another key

Simon Wang
  • 2,843
  • 1
  • 16
  • 32
  • If u still have the issue, this worked for me. Even if you have Debug.StepOver shortkey on the F10, remove it, and assign it again. This did the trick to me. (Yeah, basically instead of assigning F10 to the Debug.StepOver, assign F10. :)))) ) – dezox Oct 07 '21 at 12:42
1

Hey I also encountered this problem. I was debugging a c++ project.

For people who still suffer from this problem, try changing the properties of "Devenv.exe" under the "Compatibility" tab to "Run as Administrator".

This solved it for me, I hope it works for you too.

Prateek Malhotra
  • 11
  • 2
1

Issue Description:

Same issue as OP , but a little bit worse:

When I tried click any key in "Press shortcut Keys" here: VS2013 Keyboard options

I couldn't use F10, but I could use Alt+F10

Resolve:

Turns out I had few shortcut on my desktop with shortcut set to F10.

Application shortcut using F10 shortcut key

all of the shortcuts added (probably) by some bloatware I've installed by mistake.

I have deleted these shortcuts. and had to restart Explorer.exe process.

itsho
  • 4,640
  • 3
  • 46
  • 68
  • Similar issue but how can I find out what is using F10? – AbstractDissonance Feb 05 '16 at 06:41
  • @AbstractDissonance just click F10 on your desktop, have a look what's opening. I'd also use **Process Monitor** just to be sure that it's not a hidden exe. – itsho Feb 06 '16 at 21:52
  • Nothing. I don't have it assigned. I noticed it sorta highlights the line. It's not assigned anywhere in VS though nor to the desktop. I think I assigned it once to some app(swapscreen or camtasia)... It seems like it is "disabled" in windows. I think I once edited the registry for the keys for some reason and that might have messed it up(something VS related though). – AbstractDissonance Feb 07 '16 at 22:20
  • @AbstractDissonance see [this](http://superuser.com/questions/661961/what-other-tool-is-using-my-hotkey) and [this](http://superuser.com/questions/11308/how-can-i-determine-which-process-owns-a-hotkey-in-windows) – itsho Feb 08 '16 at 08:27
  • Thanks itsho, I had an recording app that was (globally) listening to F10. I have removed it `:-)` – Tahir Hassan Jun 30 '16 at 10:35
1

I just unplugged and plugged the keyboard, and it worked perfectly fine :) I'm using an external keyboard on my notebook.

Mehmet Recep Yildiz
  • 1,359
  • 17
  • 14
0

Another very specific situation that could cause stepping to not work: I have been using VS for many years with no problem. All of a suddden, in one particular (new) file, I could not step using the debugger. Using the Step Over command on the menu or by pressing F10 was causing it to step out of the method. The culprit? The [DebuggerStepThrough] attribute! I had copied a simple class used to represent an object that was serializable to XML. It had the DebuggerStepThrough attribute on it, and I wondered about it for a moment, but then forgot about and coded away, making several copies of it to set up the classes that would provide the required XML structure. Then in one of those classes I added a method that had some actual meaty logic. That's when I discovered I couldn't step through it. I could set breakpoints on individual lines and the debugger would stop, but that was getting to be a nuisance. As I read through all the above solutions and didn't find anything helpful, I suddenly remembered seeing the [DebuggerStepThrough] attribute. Hope this helps someone else.

Tom Bogle
  • 464
  • 4
  • 18
  • Please take a moment to read through the [editing help](/editing-help) in the [help]. Formatting on Stack Overflow is different than other sites. – double-beep Jun 17 '19 at 11:50
  • The square brackets are not a failed attempt at markup. Attributes in C# are indicated by square brackets, and I thought it best to include them here. I could've wrapped them as __code__, but that didn't feel particularly useful or necessary. – Tom Bogle Jun 18 '19 at 12:30
0

I had this problem also and I thought that my keyboard has a problem but ultimately I figure out that I use another program(camtesia)and that program use F10 shortcut. once I closed it ,the problem solved

0

In my case, clicking the clicking the F10 button after clicking the fn button on my keyboard works.

I'm using Visual Studio 2022

Stephen Melben Corral
  • 170
  • 1
  • 2
  • 11