Blog Post

Sysinternals Blog
1 MIN READ

NotMyFault, RDCMan, ZoomIt, CoreInfo, Process Explorer, Process Monitor, and PsPing

Alex_Mihaiuc's avatar
Alex_Mihaiuc
Icon for Microsoft rankMicrosoft
Aug 12, 2026

Learn about the latest updates to NotMyFault, RDCMan, ZoomIt, CoreInfo, Process Explorer, Process Monitor, and PsPing

NotMyFault v4.6

This update to NotMyFault, a tool that creates on-demand Windows crashes, hangs, and kernel memory leaks, is now in Rust and has a modern UI.
 

RDCMan v3.20

This update to RDCMan, a tool for managing and connecting to Remote Desktop sessions, adds Azure Virtual Desktop workspace feed, and Microsoft Dev Box support.
 

ZoomIt v12.2

This update to ZoomIt, a screen magnification and annotation tool, introduces DemoMirror for mirroring the screen, a screen region, or a window, onto a second monitor.
 

CoreInfo v4.02

This update to Coreinfo, a tool that reports processor, socket, NUMA memory, and cache topology of a system, as well as processor features supported, improves CPU vendor name detection, and adds Intel LP-E cores support.
 

Process Explorer v17.13

This update to Process Explorer, an advanced process, DLL, and handle viewing utility, adds core type information for Intel CPUs.
 

Process Monitor v4.05

This update to Process Monitor, a utility for observing real-time file system, Registry, and process or thread activity, adds a new Process Tree PID filtering capability for matching based on any ancestor process ID in the process tree.
 

PsPing v2.13

This update to PsPing, a tool implementing the standard ping functionality, alongside TCP/UDP latency and bandwidth measurements, fixes a series of bugs.
Updated Aug 12, 2026
Version 2.0

13 Comments

  • mdConfigMgr's avatar
    mdConfigMgr
    Copper Contributor

    Was the "VM Console Connect" removed from RDCMan 3.20?

    My VMs previously using this option don't work anymore and I don't see a way in the settings to re-enable this functionality.

    • Alex_Mihaiuc's avatar
      Alex_Mihaiuc
      Icon for Microsoft rankMicrosoft

      Start RDCMan with the old engine, -mstsc in the command line.

      • UrSv's avatar
        UrSv
        Copper Contributor

        That restores the Connection and Gateway Settings as well.

  • UrSv's avatar
    UrSv
    Copper Contributor

    As mentioned by others there seem to be problems with gateways and the Gateway Settings seems to be broken. The tab is not visible at all any more and the MFA functionality does not work anymore. This unfortunately renders 3.20 unusable for most people in my organisation. 

    Edit: Connection Settings is also gone. 

    Edit2: I restored to 3.12 and it is working as I suppose it should.

  • clatini's avatar
    clatini
    Copper Contributor

    Regarding RDCMan 3.20, the new RDG file format is incompatible with the previous version, making it impossible to go back to using RDCMan 3.12 unless you have a backup of the configuration file (mine has over 200 RDP hosts configured...). It would be useful if this behavior were flagged on the first launch of the new version. Additionally, the new version doesn't correctly handle multi-language keyboards on the client, forcing to use CTRL+SHIFT or ALT+SHIFT to switch layouts every session.

  • chrmaier's avatar
    chrmaier
    Copper Contributor

    Process Explorer dark theme is still not working on all server OS. Last working was 17.06.

    • chrmaier's avatar
      chrmaier
      Copper Contributor

      Okay, if I explicitly switch the theme to dark - that is, if I don't select “Use System Settings” - and restart Process Explorer, it works.  However, the checkmarks in the menus are then also dark and impossible to see.

  • biruleiubes's avatar
    biruleiubes
    Copper Contributor

    RD Gateway is **bleep**ed up on RDCMan. Also, esc exit full screen and doesn't work well like 3.12. 

  • NotMyFault.exe and NotMyFault64.exe are now broken. They don't launch, generating the following error message:

    ---------------------------
    notmyfault64.exe - Entry Point Not Found
    ---------------------------
    The procedure entry point TryCreatePackageDependency could not be located in the dynamic link library Z:\Downloads\NotMyFault\notmyfault64.exe.
    ---------------------------
    OK
    ---------------------------

    I assume this is because of a missing dependency, e.g., a version of the Windows App Runtime not found on my PC.

    • Alex_Mihaiuc's avatar
      Alex_Mihaiuc
      Icon for Microsoft rankMicrosoft

      What version of the operating system are you running?

      • The_Smart_One's avatar
        The_Smart_One
        Iron Contributor

        Latest version, updated last night.

        With respect, what kind of question is this? Can't this app crash my OS unless it is fully patched? 😂