Public website
Separate Dari and English pages provide product information, setup guidance and the download interface. They do not contain company credentials or private signing keys.
MURTAZA ONE
Understand what is checked. And what stays separate.
The website, desktop application and release distribution have distinct responsibilities. This page explains the download checks without presenting them as a guarantee of every aspect of software security.
Three roles. Clear boundaries.
The website reads public release data. It does not publish application updates.
Desktop application
The installed application handles its own activation, sign-in, company workspace and Update Center. Website files do not replace those application components.
Release distribution
The publisher’s release manifest identifies a stable Windows version and its versioned installer. Website downloads follow that published record rather than a manually selected old executable.
What happens when you click Download.
The browser repeats the check for each download request.
Read the current release information
A fresh request reads the existing public manifest through a website-only read-only link. No release file is edited and no version number is fixed into the download button.
Verify the metadata signature
The browser checks the RSA-PSS SHA-256 signature using the known public release key, then checks the stable channel, Windows x64 platform and allowed installer URL. An unknown key or invalid record stops the download.
Request the versioned installer
After verification, the browser requests the installer from the official update host. You choose whether to save and run it. This website does not execute the installer.
Metadata verification has a specific scope.
A digital signature is not a blanket security guarantee.
The browser verifies the signed release metadata before handing the installer download to the browser. It does not independently read and hash the completed executable saved on your computer. The SHA-256 value is shown for an optional file-integrity comparison.
This release signature is separate from Windows Authenticode or SmartScreen. Do not disable operating-system protection to proceed past an unexpected warning. Stop and ask your administrator when the source or file is uncertain.
A signing-key rotation, incompatible manifest format or intentionally older release can require a reviewed website trust update. The download interface fails visibly instead of silently accepting an unrecognized release.