Share via

Why is VS2026 slow on Windows 11?

Kenneth Kirrane 20 Reputation points
2026-03-06T12:35:09.1566667+00:00

When debugging our Backend application on Windows 10, VS was fast and responsive, as was the performance of the application. However, since upgrading to Windows 11, performance of the application when debugging is very slow and sluggish. Are they any performance tweaks or configuration changes that will optimise VS for Windows 11?

Developer technologies | Visual Studio | Debugging
0 comments
Answer accepted by question author
  1. Susmitha T (INFOSYS LIMITED) 2,690 Reputation points Microsoft External Staff
    2026-03-09T09:43:26.53+00:00

    Thank you for reaching out!

    Slow debugging after upgrading to windows 11 is usually related to debugger overhead or visual studio configuration rather that the OS itself.

    Please try the following:

    • Compare performance with start without debugging (Ctrl+F5).
    • Enable Just My Code and restrict symbol loading.
    • Disable diagnostic tools while debugging and code lens.
    • Temporarily disable extensions to rule out extension impact.
    • Ensure Visual Studio is updated to the latest build, and the solution is running from an SSD.

     

    If the issue still persists, you can raise a ticket through the official support channels:

    • Submit the issue directly from Microsoft Visual Studio: Open Visual Studio Go to help-> Send feedback -> Report a problem. or else 
    • You can also submit the issue on the developer community website: Developer Community

    If you find this helpful, Kindly mark the provided solution as "Accept Answer", so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-03-06T12:35:37.0033333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Several configuration and tuning steps can help improve Visual Studio 2026 debugging performance on Windows 11, both in Visual Studio itself and at the OS level.

    1. Optimize Visual Studio configuration
    • Upgrade to the latest Visual Studio 2026 build
      • Newer versions include targeted performance improvements, especially for F5/debugger startup and general responsiveness.
      • Visual Studio 2026 with .NET 10 provides up to ~30% faster F5 startup compared to Visual Studio 2022 with .NET 9 when debugging.
      • Make sure the latest update (for example, November Update 18.0.0 or later) is installed.
    • Review extensions and tool windows
      • Extensions can significantly slow Visual Studio, especially during debugging.
      • Disable non-essential extensions:
        • Go to Extensions > Manage Extensions and disable extensions one by one, re-checking performance.
      • Close or disable heavy tool windows that are not needed during debugging.
    • Disable CodeLens if working with large solutions
      • CodeLens runs background analysis (similar to continuous Find All References) and can cause high CPU and memory usage on large codebases.
      • To disable:
        • Tools > Options > All Settings > Text Editor > CodeLens and clear Enable CodeLens.
    • Disable map mode on the scrollbar
      • Map mode renders a miniature view of the file and can add overhead.
      • To switch to a lighter mode:
        • Tools > Options > All Settings > Languages > Defaults > General > Scroll Bars and set Vertical scroll bar mode to Bar mode.
    1. Tune debugging options for better performance

    If the slowdown is most noticeable while debugging (stepping, inspecting variables, long-running sessions), adjust these options:

    • Enable Just My Code (managed/.NET debugging)
      • Reduces symbol loading and memory usage by only loading symbols for the project’s own code.
      • To enable:
        • Tools > Options > All Settings > Debugging > General and select Enable Just My Code.
    • Restrict symbol loading (native or mixed debugging)
      • Loading many external PDBs is expensive.
      • Configure symbols so only project modules load:
        • Tools > Options > All Settings > Debugging > Symbols > Search and Load.
        • Use + Add under Included modules to specify only the modules that should load symbols.
    • Disable Diagnostic Tools when not needed
      • CPU profiling and diagnostic tools can consume large resources and remain enabled across sessions.
      • To turn them off:
        • Tools > Options > All Settings > Debugging > General and clear Enable Diagnostic Tools while debugging.
      • Re-enable only when actively profiling.
    1. Hardware and storage considerations
    • Prefer an SSD for Visual Studio and the solution
      • An SSD has more impact on Visual Studio performance than extra RAM or a faster CPU.
      • For best results, install Windows on the SSD; solution location is less critical but avoid running from USB drives.
    1. Windows 11 system-level optimizations

    Because the slowdown appeared after moving to Windows 11, also tune the OS to reduce overhead while debugging:

    • Set Windows visual effects to best performance
      • Reduces UI animations and effects that consume resources:
        • Select Start, type Adjust the appearance and performance of Windows, open it.
        • On Visual Effects, choose Adjust for best performance.
    • Set Power mode to Best performance (when plugged in)
      • Ensures the CPU can boost more aggressively during debugging:
        • Start > Settings > System > Power & battery.
        • In Power mode, select Best performance.
      • On some builds, you may also see System > Power & sleep > Additional power settings and can choose a High performance plan.
    • Monitor and close heavy background processes
      • Use Task Manager to ensure other apps are not competing for CPU/disk while debugging:
        • Press Ctrl+Shift+Esc.
        • On Processes, close apps and background processes not needed during debugging.
        • Check Performance and Startup apps tabs for components using high resources.
    • Optimize drives
      • If using an HDD, run Defragment and Optimize Drives periodically:
        • Start, type Defragment and Optimize Drives, open it.
        • Select the drive and choose Optimize.
    • Reduce unnecessary notifications and background interruptions
      • Start > Settings > System > Notifications and turn off notifications for apps that are not needed.
    1. General OS health
    • Keep Windows 11 fully updated
      • Install all Windows Updates and optional driver updates, as they can contain performance and reliability fixes:
        • Start > Settings > Windows Update > Check for updates.
        • Then Advanced options > Optional updates and install relevant drivers.
    • Scan for malware
      • Malware can cause high CPU/disk usage and make Visual Studio appear slow:
        • Start > Settings > Privacy & security > Windows Security > Virus & threat protection > Quick scan.
    1. Provide traces to Microsoft if the issue persists
    • If Visual Studio remains unusually slow on Windows 11 after these changes, capture a trace and send it via Help > Send Feedback > Report a Problem so the product team can analyze the specific performance issue on the environment.

    References:

    0 comments

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.