এটিই সর্বশেষ সংস্করণ। · প্রকাশ:
ইনস্টলার ফাইল 1.136.177
| আর্কিটেকচার | ধরন | কার জন্য | ফাইল সাইজ | ডাউনলোড | SHA256 |
|---|---|---|---|---|---|
| ৬৪-বিট | পোর্টেবল | — | — | github.com | VirusTotal |
লিংক ও SHA256 নেওয়া হয়েছে Windows Package Manager-এর কমিউনিটি ম্যানিফেস্ট থেকে। ফাইল চালানোর আগে তার হ্যাশ মিলিয়ে দেখুন।
রিলিজ নোট
[1.136.177] - 2026-11-12
Process Manager, its safety chip and Why is it slow? now call a program part of Windows only when it runs from a
folder Windows keeps its own programs in, not from any folder inside Windows.
Fixed
- A program named like a part of Windows was trusted when it ran from any folder inside the Windows folder, including
ones such as Windows\Temp that any program can write to. Process Manager then refused to end it with a blue-screen
warning, and its chip, tooltip and description called it part of Windows. Only the System folder now counts for the
processes Process Manager refuses to end, and only the folders Windows keeps its programs in count for the Windows
label; a copy anywhere else is "Not recognised", as one in your profile already was. The whole Windows folder had
counted since the path check came in 1.131.11.
- WSL as the Microsoft Store installs it, in Program Files\WSL, is called part of Windows instead of "Not
recognised".
- Why is it slow? could miss a copy of a part of Windows that was busier than Windows' own processes of that name. Its
second look at the processor did not read again where each program it had already seen runs from, so it counted
the copy with the real ones and found nothing unusual. Since a copy is counted on its own (1.136.117), each program
keeps its folder from the first look.
- SysManager starts the Windows tools it uses only from the System folder or the Windows folder. One found in
neither used to be started by its bare name, which Windows looks for in other folders first, SysManager's own
among them; now it is not started at all, and the tab says it could not be. Notepad, which Windows 11 can install
from the Microsoft Store instead, is started from your own Store copy when SysManager runs without administrator
rights.
Changed
- A 32-bit copy of svchost, ctfmon or userinit, in SysWOW64, now gets the part-of-Windows question when you end it,
instead of a refusal.
- Microsoft Defender's engine in its platform folder under ProgramData now gets the security warning when you end it,
instead of the general one.
Verify the download
Get-FileHash .\SysManager-v1.136.177.exe -Algorithm SHA256
Expected SHA256: 99CC73F90CEC7B3792ECB519C094C7E150CB4428F8F3A4119277EBFE03B6792D
This build is not code-signed, so Windows will warn on first launch. That is
expected for a small independent app: see what the warning says and what to
click.
Code signing is planned through the SignPath Foundation,
which provides free certificates to open-source projects, with signing performed by
SignPath.io. Until then, the SHA256 above and the build
attestation below are what establish that a download is the genuine build.
Code signing policy
This release is not code-signed. The team roles, release-approval process and
privacy policy required by the SignPath Foundation programme
are documented in advance under Code signing
policy. That
documentation is a prerequisite for applying, not evidence of a certificate. The
attribution line naming SignPath as the signing provider will appear here once a
certificate is actually issued.
This program will not transfer any information to other networked systems unless
specifically requested by the user or the person installing or operating it. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use it. Full
privacy policy.
Verify where this binary came from
This exe was built by GitHub Actions from this public source, and the build is
recorded in the Sigstore public transparency log. With the
GitHub CLI:
gh attestation verify .\SysManager-v1.136.177.exe --repo laurentiu021/SystemManager
That proves which commit and workflow produced this exact binary, something the
SHA256 file cannot show, since it is published alongside the exe it describes.
Each release also ships SysManager-v1.136.177.sbom.json, a CycloneDX inventory of
every dependency resolved for this build, and THIRD-PARTY-NOTICES.txt, the
licenses and notices of the open-source components the exe carries, which About
also opens from the exe itself.https://github.com/laurentiu021/SystemManager/releases/tag/v1.136.177