Microsoft.sysinternals.processmonitor issues

Silencious · Friday at 6:56 PM

According to winget. I have version 4.04, and 4.05 is ready to upgrade. But when I try to update it, it fails. Can anyone help or explain what I'm doing wrong?

Hughbris · Friday at 10:31 PM

I use the command line winget - I'm very pleased to find out that Sysinternals can be installed that way, and I'm very much guessing this might be the issue;

Found Sysinternals Suite [Microsoft.Sysinternals.Suite] Version 2026-07-09
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://download.sysinternals.com/files/SysinternalsSuite.zip
██████████████████████████████ 192 MB / 192 MB
Installer hash does not match; this cannot be overridden when running as admin

Some kind of server-side problem someone needs to fix.

garlin · Friday at 11:45 PM

The winget package repository lists Process Monitor as bumped from version 4.0.5 to version 4.1 today.

You might want to restart WMT.

Hughbris · Saturday at 12:09 AM

What is WMT?
Rebooted, ran winget install --id=Microsoft.Sysinternals.Suite -e
Same error - I'm not fussed, it would be nice to have sysinternals installed natively

garlin · Saturday at 12:57 AM

We have two separate problems.

1. The original poster is using a 3rd-party utility (Windows Maintenance Tool), and not the winget command.

2. MS pushed out a different version of the full Sysinternals Suite for download, but forgot to update the current SHA256 hash on the winget repo:

Code:

  InstallerUrl: https://download.sysinternals.com/files/SysinternalsSuite.zip
  InstallerSha256: 9012AA4D47692054CCCA7D03A4375F4AD8C48A2941085F9435CE375A47986C80

But the current ZIP file has a different SHA256 hash:

Code:

PS C:\Users\GARLIN\Downloads> Get-FileHash .\SysinternalsSuite.zip
                                                          
SHA256          EC1C22581518E5A8661EC26886BC2EAEFE9E59CF2AD7FBA41926C19D356DE169       C:\Users\GARLIN\Downloads\SysinternalsSuite.zip

Which means someone at MS forgot to update the installer config on GitHub. And you'll have to wait.

FreeBooter · Saturday at 1:09 AM

In this guide, you will learn the steps to download and install updates for apps on Windows 11 and Windows 10 without the Microsoft Store using the Windows Package Manager (winget) command-line tool.

Hughbris · Saturday at 1:11 AM

Thanks for the explanation Garlin

Silencious · Saturday at 5:15 AM

garlin said:
We have two separate problems.

1. The original poster is using a 3rd-party utility (Windows Maintenance Tool), and not the winget command.

2. MS pushed out a different version of the full Sysinternals Suite for download, but forgot to update the current SHA256 hash on the winget repo:

Code:

InstallerUrl: https://download.sysinternals.com/files/SysinternalsSuite.zip InstallerSha256: 9012AA4D47692054CCCA7D03A4375F4AD8C48A2941085F9435CE375A47986C80

But the current ZIP file has a different SHA256 hash:

Code:

PS C:\Users\GARLIN\Downloads> Get-FileHash .\SysinternalsSuite.zip SHA256 EC1C22581518E5A8661EC26886BC2EAEFE9E59CF2AD7FBA41926C19D356DE169 C:\Users\GARLIN\Downloads\SysinternalsSuite.zip

Which means someone at MS forgot to update the installer config on GitHub. And you'll have to wait.

Thank you all for your inputs and thoughts. I posted my issue, but I forgot to say I did use PowerShell as admin and used the Winget commands, but it reported my same issue. Today, when I reviewed the replies, I followed the person who posted the YouTube video and now. All I have to report is that Windows Edge was the only app that needed upgrading, and the issue I had is no longer there. I wonder if MS has corrected their problem? Once again, thank you for your input.

FreeBooter · Saturday at 5:22 AM

The video belongs to me, you can use winget upgradecommand to update all installed apps with available updates.

I myself use Sysinternal utility but i download it from Microsoft website.

Sysinternals Suite - Sysinternals

The Windows Sysinternals troubleshooting Utilities have been rolled up into a single suite of tools.

learn.microsoft.com

garlin · Saturday at 10:19 AM

Silencious said:
Thank you all for your inputs and thoughts. I posted my issue, but I forgot to say I did use PowerShell as admin and used the Winget commands, but it reported my same issue. Today, when I reviewed the replies, I followed the person who posted the YouTube video and now. All I have to report is that Windows Edge was the only app that needed upgrading, and the issue I had is no longer there. I wonder if MS has corrected their problem? Once again, thank you for your input.

Sysinternals is provided in 3 different formats: winget package, Store app, and direct download.

The actual tools are the same inside all 3 files. But if you download the ZIP directly from MS, winget has no idea you have a newer copy of the package. It keeps a separate database of previously installed packages, and can't see your download. While you have a newer Sysinternals to use, winget still thinks it's behind in package versions.

The SHA256 hash is a mechanism to help protect against attackers tampering with the ZIP contents. winget and the Store will do the comparison for you. When you download the ZIP from MS, there's no published checksum for you to use. The risk is low since you're getting the file from MS, but it's not a trivial risk since most of the Sysinternals tools must be run as the Admin.

Silencious · Saturday at 10:44 AM

I downloaded the above, but it looks complicated, and with them being execution files, I'm reluctant to click in case I ... muck it up. Thanks anyway. I'll keep the file anyway when I become more confident in Windows tech. I'll rely on you guys

garlin · Saturday at 10:56 AM

The ZIP file expects you to extract the files into a target folder. The winget and Store versions will always install them into the same "Program Files" folder for you.

While they constantly improve Sysinternals with bug fixes, you're not missing much if you don't have the newest version. Your current suite is fine for daily use. And someone at MS will eventually figure out the problem on their end.

TairikuOkami · Saturday at 11:38 AM

Hughbris said:
Same error - I'm not fussed, it would be nice to have sysinternals installed natively

A lot of malware uses lolbins like psexec, so not a good idea, just install tools you need. Then again, I use Nirsoft suite, so ...

garlin said:
1. The original poster is using a 3rd-party utility (Windows Maintenance Tool), and not the winget command.

It looks that WMT uses it's own update database, since process monitor was updated to 4.05 weeks ago.
I use PortableApps for simple apps, it seems to be updated promptly, I use winget script for the rest.

Code:

winget upgrade --all -h -u --accept-package-agreements --accept-source-agreements

FreeBooter · Saturday at 11:40 AM

The Sysinternal utilities portable no installation needed.

Microsoft.sysinternals.processmonitor issues

Well-known member

Attachments

My Computer My Computer

At a glance

.

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

.

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

.

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Microsoft 365 Basic

Attachments

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer