edits

Author: Mikejo5000

docs/debugger/debug-multithreaded-applications-in-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: "Debug multithreaded applications"
 description: Debug multithreaded applications in Visual Studio and review tools and other articles about debugging multithreaded apps.
-ms.date: "05/06/2024"
+ms.date: "8/5/2025"
 ms.topic: "conceptual"
 f1_keywords:
   - "vs.debug.gputthreads"

docs/debugger/get-started-debugging-multithreaded-apps.md

@@ -1,7 +1,7 @@
 ---
 title: Learn to debug multithreaded applications
 description: Debug multithreaded applications by using the Parallel Stacks and Parallel Watch windows in the Visual Studio integrated development environment (IDE).
-ms.date: 04/16/2025
+ms.date: 8/5/2025
 ms.topic: how-to
 dev_langs: 
   - CSharp

docs/debugger/how-to-use-the-threads-window.md

@@ -11,6 +11,8 @@ dev_langs:
 helpviewer_keywords: 
   - multithreaded debugging, tutorial
   - tutorials, multithreaded debugging
+  - deadlock, debugging
+  - debugging, deadlock
 author: mikejo5000
 ms.author: mikejo
 manager: mijacobs

docs/debugger/using-the-parallel-stacks-window.md

@@ -1,7 +1,7 @@
 ---
 title: "View threads in the Parallel Stacks window"
 description: Use Parallel Stacks to help debug multithreaded applications. You can view stack information for all threads, and task-centered call stack information.
-ms.date: "01/22/2025"
+ms.date: "8/5/2025"
 ms.topic: "conceptual"
 f1_keywords:
   - "vs.debug.parallelstacks"
@@ -24,8 +24,8 @@ The **Parallel Stacks** window is useful for debugging multithreaded application
 - [Threads view](#threads-view) shows call stack information for all threads in the app. You can navigate between threads and stack frames on those threads.
 
 - [Tasks view](#tasks-view) shows task-centered call stack information.
-  - In managed code, **Tasks** view shows call stacks of <xref:System.Threading.Tasks.Task?displayProperty=fullName> objects.
-  - In native code, **Tasks** view shows call stacks of [task groups](/cpp/parallel/concrt/task-parallelism-concurrency-runtime), [parallel algorithms](/cpp/parallel/concrt/parallel-algorithms), [asynchronous agents](/cpp/parallel/concrt/asynchronous-agents), and [lightweight tasks](/cpp/parallel/concrt/task-scheduler-concurrency-runtime).
+  - For .NET apps using the async/await pattern, the Tasks view is the most helpful for debugging. For a step-by-step tutorial, see [Debug an async application](../debugger/walkthrough-debugging-a-parallel-application.md).
+  - For apps using the [Task Parallel Library (TPL)](/dotnet/standard/parallel-programming/task-parallel-library-tpl) but not the async/await pattern, or for C++ apps using the [Concurrency Runtime](/cpp/parallel/concrt/concurrency-runtime), the **Threads** view in the **Parallel Stacks** window is the most useful tool for debugging.
 
 - [Method View](#method-view) pivots the call stack on a selected method.
 

docs/debugger/using-the-tasks-window.md

@@ -1,7 +1,7 @@
 ---
 title: Use the Tasks Window to view concurrent operations
 description: Tasks are asynchronous operations that can run concurrently. Multiple tasks can run on the same thread. Use Tasks to view task and WinJS.Promise object information.
-ms.date: "02/25/2025"
+ms.date: "08/5/2025"
 ms.topic: "conceptual"
 f1_keywords:
   - "vs.debug.paralleltasks"
@@ -21,12 +21,10 @@ ms.subservice: debug-diagnostics
 
 The **Tasks** window resembles the **Threads** window, except that it shows information about <xref:System.Threading.Tasks.Task?displayProperty=fullName> or [task_handle](/cpp/parallel/concrt/reference/task-group-class) objects instead of each thread. Like threads, tasks represent asynchronous operations that can run concurrently; however, multiple tasks may run on the same thread.
 
-In managed code, you can use the **Tasks** window when you work with <xref:System.Threading.Tasks.Task?displayProperty=fullName> objects or with the **await** and **async** keywords (**Await** and **Async** in VisualBasic). However, the **Tasks** view in the **Parallel Stacks** window is often more helpful for debugging. For more information, see [Debug an async application](../debugger/walkthrough-debugging-a-parallel-application.md).
-
-For C/C++ code, you can use the **Tasks** window when you work with [task groups](/cpp/parallel/concrt/task-parallelism-concurrency-runtime), [parallel algorithms](/cpp/parallel/concrt/parallel-algorithms), [asynchronous agents](/cpp/parallel/concrt/asynchronous-agents), and [lightweight tasks](/cpp/parallel/concrt/task-scheduler-concurrency-runtime). For more information about tasks in native code, see [Concurrency Runtime](/cpp/parallel/concrt/concurrency-runtime).
+In .NET code, you can use the **Tasks** window when you work with apps using the async/await pattern (**Await** and **Async** in VisualBasic). However, the **Tasks** view in the **Parallel Stacks** window is often more helpful for debugging async applications. For more information, see [Debug an async application](../debugger/walkthrough-debugging-a-parallel-application.md).
 
 > [!TIP]
-> For C/C++ code, the **Threads** view in the **Parallel Stacks** window is typically the most helpful when you need to debug tasks. For more information, see [View threads and tasks in the Parallel Stacks window](../debugger/using-the-parallel-stacks-window.md).
+> For C/C++ code, the **Threads** view in the **Parallel Stacks** window is typically the most helpful when you need to debug [task groups](/cpp/parallel/concrt/task-parallelism-concurrency-runtime), [parallel algorithms](/cpp/parallel/concrt/parallel-algorithms), [asynchronous agents](/cpp/parallel/concrt/asynchronous-agents), and [lightweight tasks](/cpp/parallel/concrt/task-scheduler-concurrency-runtime). For more information, see [View threads and tasks in the Parallel Stacks window](../debugger/using-the-parallel-stacks-window.md).
 
 You can use the **Tasks** window whenever you break into the debugger. You can access it on the **Debug** menu by clicking **Windows** and then clicking **Tasks**. The following illustration shows the **Tasks** window in its default mode.
 
@@ -49,7 +47,7 @@ The columns in the **Tasks** window show the following information.
 |**Flags**|Shows which tasks are flagged and lets you flag or unflag a task.|
 |**Icons**|![Yellow arrow](media/icon-parallel-yellow-arrow.png) A yellow arrow indicates the current task. The current task is the top-most task on the current thread.<br /><br /> ![Green arrow](media/icon-parallel-green-arrow.png) A green arrow indicates the current debugger context (following a switch to task in the debugger).<br /><br />![White arrow](media/icon-white-arrow.png) A white arrow indicates the breaking task, that is, the one that was current when the debugger was invoked.<br /><br /> ![Pause icon](media/icon-paused.png) The pause icon indicates a task that has been frozen by the user. You can freeze and unfreeze a task by right-clicking it in the list.|
 |**ID**|A system-provided number for the task. In native code, this is the address of the task.|
-|**Status**|The current state (scheduled, active, blocked, deadlocked, awaiting, or completed) of the task. <br /><br />![Status Scheduled](media/icon-status-scheduled.png) Scheduled. A scheduled task is one that has not yet been run and, therefore, doesn't yet have a call stack, assigned thread, or related information.<br /><br /> ![Status Active](media/icon-status-running.png) Active. An active task is one that was executing code before breaking in the debugger.<br /><br /> ![Status Blocked](media/icon-status-block.png) Blocked. A blocked task is one that is blocked because it's waiting on an event to be signaled, a lock to be released, or another task to finish.<br /><br />  ![Status Awaiting](media/icon-status-awaiting.png) Awaiting. A non-blocking, waiting task that uses the async/await pattern.<br /><br /> ![Status Deadlocked](media/icon-status-excluded.png) Deadlocked. A deadlocked task is a waiting task whose thread is deadlocked with another thread.<br /><br /> Hover over the **Status** cell for a deadlocked or awaiting task to see more information about the block. **Warning:**  The **Tasks** window reports deadlock only for a blocked task that uses a synchronization primitive that is supported by Wait Chain Traversal (WCT). For example, for a deadlocked <xref:System.Threading.Tasks.Task> object, which uses WCT, the debugger reports **Awaiting-deadlocked**. For a deadlocked task that is managed by the Concurrency Runtime, which doesn't use WCT, the debugger reports **Waiting**. For more information about WCT, see [Wait Chain Traversal](/windows/desktop/Debug/wait-chain-traversal).|
+|**Status**|The current state (scheduled, active, blocked, deadlocked, awaiting, or completed) of the task. <br /><br />![Status Scheduled](media/icon-status-scheduled.png) Scheduled. A scheduled task is one that has not yet been run and, therefore, doesn't yet have a call stack, assigned thread, or related information.<br /><br /> ![Status Active](media/icon-status-running.png) Active. An active task is one that was executing code before breaking in the debugger.<br /><br /> ![Status Blocked](media/icon-status-block.png) Blocked. A blocked task is one that is blocked because it's waiting on an event to be signaled, a lock to be released, or another task to finish.<br /><br />  ![Status Awaiting](media/icon-status-awaiting.png) Awaiting. A non-blocking, waiting task that uses the async/await pattern.<br /><br /> ![Status Deadlocked](media/icon-status-excluded.png) Deadlocked. The deadlock symbol refers to a waiting task whose associated thread is deadlocked with another thread.<br /><br /> Hover over the **Status** cell to see more information about the block. **Warning:**  The **Tasks** window reports deadlock only for a blocked task that uses a synchronization primitive that is supported by Wait Chain Traversal (WCT). For example, for a deadlocked <xref:System.Threading.Tasks.Task> object, which uses WCT, the debugger reports **Awaiting-deadlocked**. For a deadlocked task that is managed by the Concurrency Runtime, which doesn't use WCT, the debugger reports **Waiting**. For more information about WCT, see [Wait Chain Traversal](/windows/desktop/Debug/wait-chain-traversal).|
 |**Start Time**|The time at which the task became active.|
 |**Duration**|The number of seconds that the task has been active.|
 |**Completion Time**|The time at which the task completed.|

docs/debugger/walkthrough-debugging-a-multithreaded-application.md

@@ -1,7 +1,7 @@
 ---
 title: View threads in the debugger
 description: Explore the Threads window in the Visual Studio debugger. Group, sort, flag, freeze, thaw, and search for threads. Display call stacks in C#, Visual Basic, and C++.
-ms.date: 12/17/2024
+ms.date: 8/5/2025
 ms.topic: concept-article
 f1_keywords:
   - "vs.debug.threads"
@@ -32,7 +32,7 @@ The **Threads** window in the Visual Studio debugger lets you examine and work w
 
 The **Threads** window is available only while the Visual Studio debugger is running. During a debugging session, you can open the window by selecting **Debug** > **Windows** > **Threads**.
 
-This article describes how to work with the **Threads** window for your C#, Visual Basic, or C++ programs. If you're looking for step-by-step guidance on how to debug multithreaded apps, see [Get started debugging multithreaded applications](./get-started-debugging-multithreaded-apps.md) and [Debug a deadlock using the Threads view](./how-to-use-the-threads-window.md).
+This article describes how to work with the **Threads** window for your C#, Visual Basic, or C++ programs. However, the **Threads** view in the Parallel Stacks window is often more helpful for debugging. For more information, see [Debug a deadlock using the Threads view](./how-to-use-the-threads-window.md) and [View threads and tasks in the Parallel Stacks window](../debugger/using-the-parallel-stacks-window.md).
 
 ## Explore the Threads window table
 

docs/debugger/walkthrough-debugging-a-parallel-application.md

@@ -72,9 +72,7 @@ Here are a few important points to remember when interpreting data in the Tasks
 
    If the start window isn't open, choose **File** > **Start Window**.
 
-   ::: moniker range=">=vs-2022"
    On the start window, choose **New project**.
-   ::: moniker-end
 
    On the **Create a new project** window, enter or type *console* in the search box. Next, choose **C#** from the Language list, and then choose **Windows** from the Platform list.