How to check the digital signature of the Simplebim installer and installed application

Gio Siradze
Gio Siradze
  • Updated

Any EXE or DLL from Datacubist can be checked in under a minute: open the file's Properties in Windows and confirm that the Digital Signatures tab names Datacubist Oy as the signer and reports the signature as OK. No file hashes are needed.

Every program file that Datacubist publishes is digitally signed with a code-signing certificate issued to Datacubist Oy by DigiCert. The signature proves two things at once: the file was published by Datacubist, and it has not been changed since it was signed. A single changed byte makes Windows report the signature as invalid.

Method 1: Windows File Explorer

This works on any Windows PC and needs no extra tools.

  1. In File Explorer, right-click the file (for example Simplebim12.exe) and choose Properties.
  2. Open the Digital Signatures tab. If the tab is missing, the file carries no signature at all. See If the Check Fails.
  3. In the Signature list, the Name of signer must read Datacubist Oy.
  4. Select that row and click Details. The dialog must say This digital signature is OK.
  5. Optional: click View Certificate. Issued to must be Datacubist Oy and Issued by must be a DigiCert code signing CA.

Any other signer name, a missing tab, or a dialog that reports the signature as not valid means the file is not a genuine, unmodified Datacubist file.

Method 2: PowerShell

Use this when you want the result as text, for example for a support ticket or an internal record. No administrator rights are needed.

  1. Press the Windows key, type PowerShell and press Enter.
  2. Run the command below with the path of the file you want to check:
Get-AuthenticodeSignature "C:\Program Files\Datacubist\Simplebim 12\Simplebim12.exe" | Format-List Status, StatusMessage, @{n='Signer';e={$_.SignerCertificate.Subject}}, @{n='Issuer';e={$_.SignerCertificate.Issuer}}

A genuine, unmodified file prints this:

Status        : Valid
StatusMessage : Signature verified.
Signer        : CN=Datacubist Oy, O=Datacubist Oy, L=Tampere, C=FI
Issuer        : CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1, O="DigiCert, Inc.", C=US

Status must be Valid and Signer must begin with CN=Datacubist Oy. Any other result means the check failed:

Status Meaning
NotSigned The file carries no signature at all.
HashMismatch The file was signed but has been changed since.
NotTrusted or UnknownError Windows cannot verify the certificate chain. Usually the PC has no internet access or an outdated root certificate store.

Method 3: For IT Administrators

Check a whole installation at once. The command below lists every Datacubist program file under the Simplebim 12 installation folder whose signature is missing, broken or from another signer. An empty result means every file passed.

Get-ChildItem "C:\Program Files\Datacubist\Simplebim 12" -Recurse -Include Simplebim*.exe, Simplebim*.dll, AppInterface.dll -Exclude *.resources.dll |
  Get-AuthenticodeSignature |
  Where-Object { $_.Status -ne 'Valid' -or $_.SignerCertificate.Subject -notlike 'CN=Datacubist Oy,*' } |
  Select-Object Status, Path

Language resource files (*.resources.dll in the language subfolders) hold only translated texts, no program code, ship unsigned by design, and are excluded from the check.

Inventory of all signers. To see who signed each file in the folder, including third-party components:

Get-ChildItem "C:\Program Files\Datacubist\Simplebim 12" -Recurse -Include *.exe, *.dll |
  Get-AuthenticodeSignature |
  Select-Object Status, @{n='Signer';e={$_.SignerCertificate.Subject}}, Path |
  Sort-Object Signer, Path | Format-Table -AutoSize

signtool. If the Windows SDK is installed, signtool prints the full certificate chain and the timestamp:

signtool verify /pa /v "C:\Program Files\Datacubist\Simplebim 12\Simplebim12.exe"

The output must end with Successfully verified, and the last link of the signing chain must read Issued to: Datacubist Oy, Issued by: DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1. The /pa switch selects the standard Authenticode policy. Without it, signtool applies the Windows driver policy and reports a false error.

Pinning the certificate. For a stricter check, compare the thumbprint of the signing certificate as well. The current certificate has the SHA-1 thumbprint B16C6079CF2C76B47890754F038D8E4CAC91775D and is valid until 6 March 2027. The thumbprint changes when Datacubist renews the certificate; the signer name does not. Files signed with an earlier certificate stay valid after its expiry, because every signature is timestamped.

(Get-AuthenticodeSignature "C:\Program Files\Datacubist\Simplebim 12\Simplebim12.exe").SignerCertificate.Thumbprint

What a Valid Result Looks Like

Whichever method you use, a genuine Datacubist file shows these values.

Item Expected value
Name of signer / Issued to Datacubist Oy (Tampere, Finland)
Issued by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Signature status "This digital signature is OK" in File Explorer, Valid in PowerShell
Timestamp Present, countersigned by DigiCert
Digest algorithm SHA-256

The installer is signed the same way. When you start it, the Windows User Account Control prompt shows Verified publisher: Datacubist Oy. An installer that shows Unknown publisher instead has not come from Datacubist unchanged.

Third-party components. The installation folder also contains components from other publishers. These are signed by their own publisher or not at all, and the check in this guide does not apply to them.

Files Publisher Signed by
Infragistics.*.dll Infragistics (user interface controls) Not signed by the vendor
CadFasterEngine4DirectX.dll, WebStep*.dll CadFaster (3D viewer) Not signed by the vendor
Microsoft.*.dll, System.*.dll, WebView2Loader.dll Microsoft Microsoft Corporation or Microsoft Windows
BCF*.dll, BIMcollab*.dll KUBUS (BIMcollab) Kubus
Newtonsoft.Json.dll Json.NET Json.NET (.NET Foundation)
MySql.Data.dll Oracle Oracle America, Inc.
QlmLicenseLib.dll Soraco Technologies (license library) Soraco Technologies Inc. Windows may report this signature as outside its validity period, because the vendor signed the file without a timestamp. This is expected.

If the Check Fails

  1. Do not run or install the file.
  2. For a downloaded installer: download it again from our official download page or from the link in your license email, and repeat the check. A download that was interrupted or altered on the way fails with HashMismatch or "not valid".
  3. For a file inside an existing installation: something on the PC changed the file after installation, for example an antivirus repair, a disk error or malware. Run a full antivirus scan, then uninstall Simplebim and reinstall it from a freshly downloaded and verified installer.
  4. For NotTrusted or UnknownError on a PC without internet access: Windows could not fetch the DigiCert root certificates or check for revocation. Copy the file to a PC that is online and repeat the check there.
  5. If the check still fails, or you are unsure, send the file name, the status and the signer name you see to support@simplebim.com. Do not attach the file itself.

Related to

Was this article helpful?

1 out of 1 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.