Why is Debugger in VS 2026 requiring double-click for F10 step into?

Corey Fleig 555 Reputation points
2026-10-07T20:30:49.5233333+00:00

I read several online queries about VS 2026 doing a double-click for F10. I went through several pages in

VS/Tools/Options, and no matter what I try to change in various settings, I have to hit F10 twice for each line of code. This wasn't the case a week ago.

I can make it work with Web apps, but this is a problem with Windows Desktop solutions.

I don't use hotkeys at all, my keyboard is a cheap 101 HP keyboard. Num lock ON, all others OFF.

Any thoughts?

Developer technologies | Visual Studio | Debugging
Answer accepted by question author
Brian Pham (WICLOUD CORPORATION) 410 Reputation points Microsoft External Staff Moderator
2026-10-08T02:46:54.8+00:00

Hi @Corey Fleig ,

Thank you for the detailed description. From what you've described, needing to press F10 twice for every step is not expected debugger behavior if it was previously advancing normally.

A few points worth checking:

  1. Verify the exact stepping behavior
    • When you press F10 the first time, does the yellow execution arrow remain on the same source line?
    • Or does it move to generated/framework code and then return after the second press?
  2. Check Debugging settings
    • Go to Tools > Options > Debugging > General.
    • Review:
    • Enable Just My Code
    • Step over properties and operators (Managed only)
    • If either setting was recently changed, restoring the previous value may return the earlier stepping behavior.
  3. Determine whether the issue is solution-specific
    • Try the same debugging workflow in a newly created Windows Desktop test project.
    • If the behavior only occurs in one solution, project settings or generated code may be involved.
  4. Check for recent updates
    • Since the issue started about a week ago, please let me know whether Visual Studio, extensions, workloads, or Windows itself were updated shortly before the behavior appeared.

Could you provide:

  • Your exact Visual Studio version (Help > About Microsoft Visual Studio)
  • Project type (WinForms, WPF, C++, etc.)
  • A screenshot or short example showing a line where F10 must be pressed twice

That information will help determine whether this is expected stepping behavior, a debugger setting change, or potentially a product issue.

If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation. Thank you.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-10-07T20:31:01.4266667+00:00

    F10 is Step Over, not Step Into. In Visual Studio, F10 runs the current line and then pauses at the next line after any called function returns. F11 is Step Into.

    If it feels like F10 needs to be pressed twice, the most likely explanation from the documented behavior is that the debugger steps by statements, not by physical lines. A single source line can contain more than one statement, so the debugger can appear to pause on the same line more than once before moving on.

    Also check whether the current line contains a function or method call:

    • F10 executes that call without entering it.
    • F11 enters the called function.
    • Shift+F11 runs until the current function returns.

    For Windows Desktop code, another factor is Just My Code. By default, the debugger skips non-user code. If stepping behavior changed recently, review:

    1. Open Tools or Debug > Options.
    2. Go to All Settings > Debugging > General.
    3. Verify Enable Just My Code is set the way expected.
    4. For managed code, also check Step over properties and operators (Managed only), because properties and operators are stepped over by default.

    If the goal is to enter framework or external code while debugging, clear Enable Just My Code.

    If a single line calls multiple methods and the goal is to enter only one of them, right-click the line and use Step Into Specific.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.