[Package Issue]: CPUID.HWMonitor
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- yaml
- Domain
- release
Research direction
Open manifests/c/CPUID/HWMonitor/1.68/CPUID.HWMonitor.installer.yaml and inspect the installer URL and SHA256 value. Compare the manifest hash with the downloaded installer, then validate the manifest by retrying installation; done means CPUID HWMonitor 1.68 installs without a hash mismatch.
Written by the indexing model from the issue text.
Description
Please confirm these before moving forward
- I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue
Installation issue.
Brief description of your issue
manifests/c/CPUID/HWMonitor/1.68/CPUID.HWMonitor.installer.yaml
wrong SHA256 hash.
should be FAE15460133A648CACA1A63FD809EF0B042CF82DAF73C239FA5AC7B062CB2B16
Steps to reproduce
try to install
Actual behavior
doesn't install (hash mismatch)
Expected behavior
install
Environment
Windows Package Manager v1.29.290
© 2026 Microsoft. All rights reserved.
Windows: Windows.Desktop v10.0.26200.9445
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.29.290.0
Screenshots and Logs
Found CPUID HWMonitor [CPUID.HWMonitor] Version 1.68
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.cpuid.com/hwmonitor/hwmonitor_1.68.exe
Installer hash does not match; this cannot be overridden when running as admin
End Time: "9/15/2026 12:07:22 PM"
Process return value: "-1978335215" (0x8A150011)
CPUID HWMonitor could not be updated
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 2h 36m
- Merged PRs (30d)
- 77
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/winget-pkgs
-
Help-Wanted Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-pkgs#438682 ·
-
Help-Wanted Needs-Triage Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-pkgs#438680 ·
-
Help-Wanted Needs-Triage Package-Update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/winget-pkgs#438662 ·
-
Error-Hash-Mismatch Help-Wanted Needs-Triage Package-Metadata
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/winget-pkgs#438650 ·
-
Help-Wanted Needs-Triage Package-Update
Difficulty 1/5 Under an hour Newbie friendliness 85/100
microsoft/winget-pkgs#438648 ·
All issues in microsoft/winget-pkgs
Similar issues
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
documentation pkg infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epiverse-trace/epiparameter#511 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100