Microsoft Sysinternals: Process Explorer 17.1, SDelete 2.06, and Sysmon 1.5.1 for Linux
Microsoft Sysinternals: Process Explorer 17.1, SDelete 2.06, and Sysmon 1.5.1 for Linux
Publish Date: 2026-03-08 00:00:00
Source Domain: www.igorslab.de
Microsoft has updated three key tools from the Sysinternals suite. What initially appears to be a minor maintenance update reveals a typical Microsoft strategy upon closer inspection: ensuring stability in the Windows ecosystem while simultaneously integrating Linux more closely as an infrastructure platform. With Process Explorer 17.1, SDelete 2.06, and Sysmon 1.5.1 for Linux, administrators, security analysts, and forensic experts receive minor but significant improvements.
Process Explorer 17.1: Stability fix for long process names
Process Explorer has been a standard tool for administrators for years. The tool basically replaces the Windows Task Manager, but with significantly more depth. In addition to running processes, the program also displays DLL dependencies, open handles, and thread details. This is precisely why it is often the first tool to be launched in incident response environments or malware analysis. With version 17.1, Microsoft has fixed a bug that could cause a crash when process names were unusually long. It sounds trivial, but it’s not. Especially in modern container or build environments, processes with extremely long path names or generated names often occur. A crash of the analysis tool in precisely such scenarios is the digital equivalent of a fire hose with a hole in it.
In short: not a new feature, but an important stability fix.
SDelete 2.06: Secure deletion with extended file paths
SDelete is one of those tools that hardly gets any public attention, but is enormously important in practice. The command line program deletes files in such a way that they can no longer be recovered. It does this by overwriting the data areas on the hard disk several times.
Version 2.06 brings two changes:
- Support for long file paths
- Optimization of MFT cleanup exclusively on NTFS partitions
The first change in particular is long overdue. For several years now, Windows has supported long paths beyond the classic 260-character limit….
