You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/debugger/debug-64-bit-applications.md
+30-20Lines changed: 30 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
-
title: Debug and troubleshoot 64-Bit applications
3
-
description: Learn how to debug a 64-bit application with Visual Studio. There are tips for troubleshooting unexpected debugging delays.
4
-
ms.date: 04/16/2025
2
+
title: A 64-bit debugger operation is taking longer than expected
3
+
description: Learn tips for troubleshooting unexpected debugging delays.
4
+
ms.date: 05/30/2025
5
5
ms.topic: how-to
6
6
dev_langs:
7
7
- CSharp
@@ -15,40 +15,50 @@ author: mikejo5000
15
15
ms.author: mikejo
16
16
manager: mijacobs
17
17
ms.subservice: debug-diagnostics
18
-
monikerRange: "<=vs-2019"
19
18
---
20
19
21
-
# Debug 64-Bit Applications
20
+
# Error: A 64-bit debugger operation is taking longer than expected
22
21
23
-
You can debug a 64-bit application that is running on the local computer or on a remote computer.
22
+
You might see one of the following errors:
24
23
25
-
To debug a 64-bit application that is running on a remote computer, see [Remote Debugging](../debugger/remote-debugging.md).
24
+
- "A 64-bit debugging operation is taking longer than expected." or
25
+
- "A debugger operation is taking longer than expected."
26
26
27
-
To debug 64-bit applications locally, Visual Studio uses a 64-bit worker process (msvsmon.exe) to perform the low-level operations that can't be done inside of the 32-bit Visual Studio process.
27
+
In these scenarios, Visual Studio sent a request to msvsmon.exe, and it's taken a long time for the result of that request to come back.
28
28
29
-
Mixed-mode debugging isn't supported for 64-bit processes that use .NET Framework version 3.5 or earlier.
29
+
The most common causes for this error are:
30
30
31
-
## Debug a 64-bit Application
31
+
- You have networking security software installed on your computer that has caused the networking stack to be unreliable, and it's dropped packets going over `localhost`. Try disabling all network security software and see whether this resolves it. If so, report to your network security software vendor that the software is interfering with `localhost` traffic. This shouldn't occur with Visual Studio 2019 and later, because those versions don't use sockets for this communication.
32
32
33
-
To try debugging a 64-bit application:
33
+
- You're running into an issue where Visual Studio becomes unresponsive, or other performance problem. If the problem happens regularly, you can [collect dumps](../debugger/using-dump-files.md) of Visual Studio (devenv.exe) and the worker process (msvsmon.exe) and send them to Microsoft. For information about reporting a problem, see [How to Report a Problem with Visual Studio](../ide/how-to-report-a-problem-with-visual-studio.md).
34
34
35
-
1. Create a Visual Studio solution, for example a C# console application.
35
+
::: moniker range=">= vs-2022"
36
+
- If you're using a version of Visual Studio prior to Visual Studio 2022, you may be trying to debug a 64-bit application while running in the 32-bit Visual Studio process. To resolve, follow instructions to [debug a 64-bit application](/previous-versions/visualstudio/visual-studio-2017/debugger/debug-64-bit-applications?view=vs-2017&preserve-view=true).
37
+
::: moniker-end
36
38
37
-
2. Set the configuration to 64-bit using the Configuration Manager. For more information, see [How to: Configure Projects to Target Platforms](../ide/how-to-configure-projects-to-target-platforms.md).
39
+
::: moniker range="<= vs-2019"
40
+
- In Visual Studio 2019 and earlier versions, you may be trying to debug a 64-bit application while running in the 32-bit Visual Studio process. To resolve, follow instructions in this article to debug a 64-bit application.
38
41
39
-
3. At this point the 64-bit version of the remote debugger (msvsmon.exe) starts. It runs as long as the solution with the 64-bit configuration is open.
42
+
## Debug a 64-bit Application
40
43
41
-
4. Start debugging. You should have the same experience as with a 32-bit configuration. If you get errors, see the Troubleshooting section below.
44
+
You can debug a 64-bit application that is running on the local computer or on a remote computer.
42
45
43
-
## Troubleshooting 64-bit debugging
46
+
- To debug a 64-bit application that is running on a remote computer, see [Remote Debugging](../debugger/remote-debugging.md).
44
47
45
-
You might see an error: "A 64-bit debugging operation is taking longer than expected." or "A debugger operation is taking longer than expected." In this case, Visual Studio has sent a request to msvsmon.exe, and it has taken a long time for the result of that request to come back.
48
+
- To debug 64-bit applications locally, Visual Studio uses a 64-bit worker process (msvsmon.exe) to perform the low-level operations that can't be done inside of the 32-bit Visual Studio process.
46
49
47
-
There are two main causes for this error:
50
+
Mixed-mode debugging isn't supported for 64-bit processes that use .NET Framework version 3.5 or earlier.
51
+
52
+
To try debugging a 64-bit application locally:
53
+
54
+
1. Create a Visual Studio solution, for example a C# console application.
48
55
49
-
- You have networking security software installed on your computer that has caused the networking stack to be unreliable, and it has dropped packets going over `localhost`. Try disabling all network security software and see whether this resolves it. If so, report to your network security software vendor that the software is interfering with `localhost` traffic. This shouldn't occur with Visual Studio 2019 and later, because those versions don't use sockets for this communication.
56
+
2. Set the configuration to 64-bit using the Configuration Manager. For more information, see [How to: Configure Projects to Target Platforms](../ide/how-to-configure-projects-to-target-platforms.md).
57
+
58
+
3. At this point the 64-bit version of the remote debugger (msvsmon.exe) starts. It runs as long as the solution with the 64-bit configuration is open.
50
59
51
-
- You're running into an issue where Visual Studio becomes unresponsive, or other performance problem. If the problem happens regularly, you can collect dumps of Visual Studio (devenv.exe) and the worker process (msvsmon.exe) and send them to Microsoft. For information about reporting a problem, see [How to Report a Problem with Visual Studio](../ide/how-to-report-a-problem-with-visual-studio.md).
60
+
4. Start debugging. You should have the same experience as with a 32-bit configuration. If you still get the same error, see the beginning of this article for other suggestions.
0 commit comments