You are not logged in. Please login or register.
QElectroTech → Platform-specific problems: Windows, → Installation
Hallo
Ich kann das Programm nicht installieren. Egal welche Datei ich benutze, Windows meldet mir immer wieder, dass die Datei nicht vertrauenswürdig ist und ich sie deshalb nicht herunterladen kann. Was kann ich tun?
Hello
I can't install the program. No matter which file I use, Windows keeps telling me that the file isn't trustworthy and that I can't download it. What can I do?
Could you provide some more details, such as your Windows version and antivirus software, and attach a few screenshots?
https://stackoverflow.com/questions/489 … ed-app-fro
Option 2: Buy an "Extended Validation" (EV) code signing certificate
A guaranteed way to immediately and permanently get rid of the Microsoft SmartScreen warnings is to buy an "Extended Validation" (EV) code signing certificate from one of the Microsoft-approved certificate authorities (CA's), and to sign your app with that EV certificate.Such an EV certificate will typically cost you somewhere between 300 and 700 USD per year (you better compare prices), and will only be issued to registered businesses. If you're a single developer, you must be a sole proprietor and have an active business license. You can read more about the formal requirements for EV code signing certificates in the EV Code Signing Certificate Guidelines.
Even €200 a year is out of the question – we don’t have enough donations to cover that certificate. I’m already paying for the Apple Developer Account out of my own pocket – €99 a year just to signed and notarized Apple Silicon bundles aarch64 – and on top of that, there’s the hosting fee of €160/year and the domain registrar fee...
https://github.com/qelectrotech/qelectr … issues/445
Please search on www "bypass SmartScreen warning in Windows."
Virustotal show file is safe: 1/53 security vendor flagged this file as malicious
https://www.virustotal.com/gui/file/973 … ?nocache=1
https://signpath.org/ is asking us to set up a CI/CD pipeline...
It’s already very complicated to compile QET for Windows; setting up a CI/CD pipeline on our GitHub is even more complicated.
For years (15 years) I have been providing QET packages for Windows; they are cross-compiled on my Debian machine using MXE and based on the old scripts from the Digikam developer. See: https://qelectrotech.org/forum/viewtopi … 976#p13976
Cross-compilation is an advantage for me as everything is scripted, but it involves compromises: static builds, EXE files containing the DLLs, and deployment with winqtdeploy not working in cross-compilation!
https://github.com/qelectrotech/qelectr … Windows.sh
Furthermore, the NSIS installer scripts are still based on the old 2.X version; I don’t have the time and nor healthor, the skills to rewrite them to make them compatible with NSIS 3.X. EDIT: DONE!
We are therefore looking for people with expertise in Windows CI/CD (AppVeyor, GitHub), as well as people capable of reviewing the Windows installer.
I used the Claude AI tool as part of a Windows-based CI/CD pipeline using GitHub Actions. It wasn’t easy—neither for me nor for the AI—but we’ll soon have a CI/CD pipeline that can be signed by the SignPath Foundation.
Excellent! Well done for your perseverance — that was a massive undertaking!
To summarise everything we’ve achieved together:
BuildCMake + Ninja with -j$(nproc) for parallelisation
SQLite3 hints for FindSQLite3
QET_EXPORT_PROJECT_DB passed to the compiler
ccache with GitHub Actions cachePackaging
Clean and maintainable patch_nsi.py in build-aux/windows/
Correct Windows absolute paths with backslashes in the .nsi
3-pass ldd scan for all transitive DLLs
libsqlite3, libharfbuzz, libbrotli, libpcre2, libicuXX... everything’s there
Compiled .qm files copied to lang/
Version in the format 0.100.1-r8821-abc1234_x86_64-win64 consistent with the official packagingCI/CD
MSYS2_ARG_CONV_EXCL for NSIS arguments
git in MSYS2, fetch-depth: 0 for the revision
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 for actionsAll the best with QElectroTech!
You’re welcome! It was a real technical challenge — between the quirks of MSYS2, Windows/POSIX paths, NSIS, CMake vs qmake, and hidden SQLite dependencies, there was plenty to get to grips with.
The result is clean and robust — a complete Windows CI/CD pipeline for a high-quality open-source project. All the best with QElectroTech, and feel free to get in touch if you have any other topics you’d like to explore
The installer isn't ready for production yet; it still needs some finishing polished. OK ->Done.
https://qelectrotech.github.io/qelectro … ce-mirror/
https://github.com/qelectrotech/qelectr … ag/nightly
Enjoy! 
Now we have:
✅ A robust Windows CI/CD pipeline using ccache, NSIS and 7-Zip for zipping Windows "Ready-to-use" portable versions
✅ A public GitHub Pages site with direct downloads
✅ An automatic nightly Windows build triggered by every push to the master branch
✅ The SignPath Foundation application ready to submit
Now we have an Windows MSI installer.
It was a real struggle with WiX v7 — between the EULA, namespaces, !(bind.Variable.) vs $(var.), WixVariable refusing to be a child of WixUI, and the non-embedded cab1.cab. But the result is clean and robust.
To summarise what we now have in the repository:
windows-build.yml — full MSYS2/UCRT64 build with NSIS, ccache, portable artefacts + installer, triggered manually
windows-msi.yml — generates a standalone MSI with WiX v7, embedded GPL-2 licence, QET.bat launcher adapted for Program Files
test-vs2026.yml — validates compatibility with the VS 2026 image prior to the 8 June migration
QElectroTech.wxs — complete WiX v7 definition with automatic harvesting, shortcuts, .qet file association
https://github.com/qelectrotech/qelectr … -win64.msi
Every Monday at 2 am (UTC) (cron) or manually by me, or admin account
↓
windows-build.yml
├── build-windows → generates an exe file(installer) + zip(ReadyToUse) + portable artefact for MSI builder
└── deploy-pages → clears old files, uploads the exe file + zip to the ‘release nightly’ repository
↓ (workflow_run: completed + successful)
windows-msi.yml
├── uploads the portable artefact
├── builds the MSI with WiX v7
├── deletes the old .msi, uploads the MSI to the nightly version
└── generates and deploys GitHub Pages ← the 3 URLs are known here
The GitHub Pages page is no longer generated by windows-build.yml but by windows-msi.yml once the MSI is in the release
✅ Removed the QET.bat launcher from the MSI
✅ Desktop and Start menu shortcuts now point directly to qelectrotech.exe
✅ CustomAction that sets the ‘elements’ folder to read-only after installation
✅ No more black console window on launch
✅ SignPath integration — MSI signed automatically
✅ Unique ProductCode per build based on the Git SHA
✅ FIX MajorUpgrade triggers correctly — a single entry in Settings remove programs
Roadmap :
Await the EV certificate from the SignPath Foundation
Change test-signing to release-signing in windows-msi.yml
Add the SignPath signature to windows-build.yml for the NSIS .exe and Ready-To-Use
Configure the NSIS project in SignPath
Good news regarding Windows code signing for QElectroTech!
We have made significant progress in setting up proper Authenticode signing for our Windows MSI packages through the SignPath OSS program.
Here is what has been accomplished:
- Our application to the SignPath OSS program has been accepted
- The GitHub Actions CI/CD pipeline has been fully configured to automatically submit signing requests after each successful Windows build
- The MSI artifact configuration has been set up to sign both the installer package and all nested executables and DLLs
- A first test signing request was successfully processed, with all verifications passing (source code origin, build workflow, malware scan)
We are now waiting for SignPath to activate the production certificate, after which every nightly Windows MSI build will be automatically signed with a trusted certificate.
This means that in the near future, users will no longer see the "Unknown publisher" warning when installing QElectroTech on Windows.
Thanks to everyone who encouraged us to pursue this — it has been a long time coming!
QElectroTech → Platform-specific problems: Windows, → Installation
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.018 seconds (36% PHP - 64% DB) with 12 queries