Skip to content

Commit f516c88

Browse files
authored
Merge pull request #941 from MicrosoftDocs/main
Deploy updated DebugView documentation
2 parents e8ca21c + ee45a11 commit f516c88

3 files changed

Lines changed: 68 additions & 16 deletions

File tree

sysinternals/downloads/debugview.md

Lines changed: 67 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: DebugView
44
description: This program intercepts calls made to DbgPrint by device drivers and OutputDebugString made by Win32 programs.
55
ms:assetid: 'e20c3b02-fe03-4067-82e9-f5c01398b804'
66
ms:mtpsurl: 'https://technet.microsoft.com/Bb896647(v=MSDN.10)'
7-
ms.date: 03/26/2026
7+
ms.date: 03/27/2026
88
---
99

1010
# DebugView v5.0
@@ -25,23 +25,59 @@ output, so you don't need a debugger to catch the debug output your
2525
applications or device drivers generate, nor do you need to modify your
2626
applications or drivers to use non-standard debug output APIs.
2727

28+
> [!NOTE]
29+
> *DebugView* v5.0 requires Windows 10 version 1809 (build 17763) /
30+
> Windows Server 2019 or later.
31+
2832
## DebugView Capture
2933

3034
*DebugView* will capture:
3135

3236
- Win32 **OutputDebugString**
3337
- Kernel-mode **DbgPrint**
34-
- All kernel-mode variants of **DbgPrint** implemented in Windows and Windows Server
38+
- All kernel-mode variants of **DbgPrint**
3539

3640
*DebugView* also extracts kernel-mode debug output generated before a
37-
crash from Windows crash dump files if *DebugView* was
38-
capturing at the time of the crash.
41+
crash from Windows crash dump files if *DebugView* was capturing at the
42+
time of the crash.
3943

4044
## DebugView Capabilities
4145

4246
*DebugView* has a powerful array of features for controlling and
4347
managing debug output.
4448

49+
Features new to version 5.0:
50+
51+
- **Dark mode and modern UI:** *DebugView* now features a completely
52+
redesigned interface using Windows XAML Islands technology. The UI
53+
automatically follows the system-wide light or dark theme setting,
54+
with dark mode applied consistently to the title bar, menus, toolbar,
55+
dialogs, and the output list view. The modernized toolbar and menu bar
56+
provide a visual style consistent with other Sysinternals tools such
57+
as Process Monitor.
58+
- **Automatic crash recovery:** When *DebugView* detects that the
59+
previous session ended due to an ungraceful shutdown (such as a system
60+
crash), it automatically scans the Windows crash dump file, recovers
61+
pending kernel debug traces from the previous session, and displays
62+
them in the output window. This enables post-mortem analysis of
63+
kernel-mode debug output that was captured right up to the moment of a
64+
system failure, without any manual intervention.
65+
- **UI virtualization for large captures:** The output list view now
66+
uses owner-data virtualization, which means only the visible rows are
67+
rendered at any time. This allows *DebugView* to efficiently handle
68+
captures containing hundreds of thousands or millions of debug
69+
messages without excessive memory consumption or UI slowdown.
70+
- **Dedicated PID column:** A new Process ID column is displayed by
71+
default, making it easier to identify which process generated each
72+
debug output message. The PID column can be toggled on or off from
73+
the Options menu.
74+
- **On-demand UAC elevation:** *DebugView* no longer requires
75+
administrative privileges at launch. It starts as a standard user and
76+
requests elevation via a UAC prompt only when you enable kernel-mode
77+
capture or other operations that require elevated privileges.
78+
- **DPI-aware rendering:** Menu icons, toolbar buttons, dialogs, and
79+
the output list all scale correctly on high-DPI displays.
80+
4581
Features new to version 4.6:
4682

4783
- **Support for Windows Vista 32-bit and 64-bit**
@@ -119,8 +155,9 @@ Here is a list highlighting some of *DebugView*'s other features:
119155
- **Most-recent-filter lists:**<em>DebugView</em> remembers your most recent
120156
filter selections, with an interface that makes it easy to reselect
121157
them.
122-
- **Process ID option:** Toggle the display of process IDs for Win32
123-
debug output.
158+
- **Dedicated PID column:** A separate Process ID column shows which
159+
process generated each debug message, toggleable from the Options
160+
menu.
124161
- **Clipboard copy:** Select multiple lines in the output window and
125162
copy their contents to the clipboard.
126163
- **Log-to-file:** Write debug output to a file as its being captured.
@@ -130,25 +167,40 @@ Here is a list highlighting some of *DebugView*'s other features:
130167
- **Crash-Dump Support:**<em>DebugView</em> can recover its buffers from a
131168
crash dump and save the output to a log file so that users can send
132169
you the output your Windows driver generated right up to the time of
133-
a crash.
170+
a crash. In version 5.0, this recovery is performed automatically on
171+
startup when an ungraceful shutdown is detected.
134172

135173
The on-line help file describes all these features, and more, in
136174
detail.
137175

176+
## System Requirements
177+
178+
*DebugView* v5.0 requires Windows 10 version 1809 (build 17763) or
179+
Windows Server 2019 or later. The modern UI is built on Windows XAML
180+
Islands, which requires this minimum OS version. Users on older versions
181+
of Windows should use *DebugView* v4.90.
182+
138183
## Installation and Use
139184

140185
Simply execute the *DebugView* program file (dbgview.exe) and
141-
*DebugView* will immediately start capturing debug output. Note that if
142-
you run *DebugView* you must have administrative
143-
privilege to view kernel-mode debug output. Menus, hot-keys, or toolbar
144-
buttons can be used to clear the window, save the monitored data to a
145-
file, search output, change the window font, and more. The on-line help
146-
describes all of *DebugView*'s features.
186+
*DebugView* will immediately start capturing debug output.
187+
*DebugView* starts as a standard user; you will be prompted for
188+
elevation via UAC only when you enable kernel-mode capture or other
189+
operations that require administrative privileges. Menus, hot-keys, or
190+
toolbar buttons can be used to clear the window, save the monitored data
191+
to a file, search output, change the window font, and more. The on-line
192+
help describes all of *DebugView*'s features.
193+
194+
If a previous *DebugView* session was active during a system crash,
195+
*DebugView* will automatically detect the ungraceful shutdown on the
196+
next launch, scan the crash dump file, and display any recovered kernel
197+
debug traces from the prior session.
147198

148199
![DebugView screenshot](media/debugview/DebugView.gif)
149200

150-
This is a screenshot of *DebugView* capturing Win32 debug output from a
151-
remote system. Note the presence of a highlighting filter.
201+
This is a screenshot of *DebugView* capturing debug output. Note the
202+
modern dark mode interface with the dedicated PID column and highlighting
203+
filter.
152204

153205
[![Download](media/shared/Download_sm.png)](https://download.sysinternals.com/files/DebugView.zip) [**Download DebugView**](https://download.sysinternals.com/files/DebugView.zip) **(1012 KB)**
154206

61.3 KB
Loading

sysinternals/downloads/notmyfault.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms:mtpsurl: 'https://technet.microsoft.com/Mt742033(v=MSDN.10)'
77
ms.date: 03/26/2026
88
---
99

10-
# NotMyFault v4.40
10+
# NotMyFault v4.4
1111

1212
**By Mark Russinovich**
1313

0 commit comments

Comments
 (0)