Repository navigation
windows_without_admin
Both Windows installers need administrator rights: the .exe installer asks for them outright and installs into Program Files, and the .msi installs for every user of the machine. On a company PC where you are a standard user, neither will run.
You don't need them. Every release also comes as a portable archive: a folder you extract anywhere you're allowed to write, and start from a launcher script inside it. It is the same program as the installed one.
| Version | Where | File |
|---|---|---|
| 0.100.0 (latest stable) | Release 0.100 | qelectrotech-0.100.0+git8590-x86-win64-readytouse.7z |
| 0.200.1 (development, Qt 6) | Nightly build | qelectrotech-0.200.1-qt6+git<number>-x86-win64-readytouse.zip |
Take the name ending in -readytouse, not Installer_β¦exe or β¦.msi.
On the nightly page, files with -qt6 in the name are the current build. Files without it are the last Qt 5 build, kept frozen and no longer updated.
The stable .7z opens in Explorer on recent Windows 11 (23H2 and later). On Windows 10 you need 7-Zip; if you can't install that either, use the nightly .zip, which Windows opens natively.
0.200.1 is a development version. It is what most new work goes into, but it is not tagged as a stable release yet (see issue #1112). If your company only allows released software, use 0.100.0.
-
Unblock the download. Right-click the downloaded file β Properties β tick Unblock at the bottom of the General tab β OK. Without this, Windows marks every extracted file as "from the internet" and SmartScreen warns about each one.
-
Extract it to a folder you own, for example:
%LOCALAPPDATA%\QElectroTech(paste that into Explorer's address bar; it expands to
C:\Users\<you>\AppData\Local\QElectroTech).Documents\QElectroTechor a USB stick work too. AvoidProgram Files, which you can't write to. -
Start QElectroTech with the launcher in the top folder:
Version Launcher 0.100.0 Lancer QET.bat0.200.1 Lancer QET_qt6.bat("Lancer" is French for "launch".)
-
Optional: right-click the launcher β Send to β Desktop (create shortcut). That needs no special rights either.
If SmartScreen shows "Windows protected your PC", click More info β Run anyway. The builds are not code-signed, so this warning is expected.
The launcher tells QElectroTech where everything in the folder is. Run the .exe directly and it can start without its symbol collection, title blocks or translations.
What the launcher does:
| Step | Effect |
|---|---|
cd to its own folder |
The paths below work wherever you extracted it |
attrib +r elements/* /S /D |
Makes the shipped symbol collection read-only, so it can't be edited by accident |
--common-elements-dir=elements/ |
Shipped symbol collection |
--common-tbt-dir=titleblocks/ |
Shipped title block templates |
--lang-dir=lang/ |
Interface translations |
--config-dir=conf/ --data-dir=conf/ |
Your own symbols, title blocks, logs and config files stay in conf\ inside the folder |
Anything you add after the launcher's name is passed on to QElectroTech. So a project file dragged onto the launcher opens in QElectroTech.
| What | Where | Needs admin? |
|---|---|---|
| The program, shipped symbols and title blocks | The folder you extracted | No, it's your folder |
| Your own symbols, title blocks, logs |
conf\ inside that folder |
No |
| Preferences (the Settings dialog) | Registry, HKEY_CURRENT_USER\Software\QElectroTech\QElectroTech
|
No, it's your own part of the registry |
Your projects (.qet) |
Wherever you save them | No |
Nothing goes into Program Files or the machine-wide part of the registry.
The archive includes register_filetypes.bat, which makes Windows open .qet projects, .elmt symbols and .titleblock templates in this copy of QElectroTech when you double-click them.
It registers them for your account only, which needs no admin rights. This works in builds newer than the git10275 nightly (PR #1149, merged 29 September 2026). In 0.100.0 and in nightlies up to git10275 the script is broken; see Older downloads below.
- Run
register_filetypes.batfrom the top folder. - It should say "Les associations de fichier ont bien ete crees." ("the file associations were created"). Press a key to close it.
The associations point at this folder. If you move or rename it, run register_filetypes.bat again.
Older downloads: in 0.100.0 and nightlies up to git10275, the script doesn't work for a standard user. In the 0.200.1 nightlies it stops at once; in 0.100.0 it tries to write to the machine-wide part of the registry. With those, open a project like this instead:
- use File β Open inside QElectroTech, or
- drag the
.qetfile onto the launcher (Lancer QET_qt6.batorLancer QET.bat).
Don't use Open with β Choose another app β bin\QElectroTech.exe: that starts the program without the launcher, so it can come up without its collection (see above).
- Extract the new version to a new folder, next to the old one.
- Copy the old folder's
conf\into the new one, so your own symbols and title blocks come with you. Preferences are in the registry, so they carry over by themselves. - If you registered file associations, run
register_filetypes.batin the new folder. - Delete the old folder when you're happy.
Moving to a different computer? The preferences stay behind in the old computer's registry. Save them first with Settings β Save settings as..., and load the file on the new one with Load settings... β see Saving and loading settings.
- If you registered file associations, double-click
qet_uninstall_file_associations.regin the folder and confirm. (In builds newer than git10275 this also removes the per-user entries.) - Delete the folder.
- Optional: remove your preferences. Run
regeditand deleteHKEY_CURRENT_USER\Software\QElectroTech. If your company blocksregedit, you can leave the key: it's only settings.
| Symptom | Cause | What to do |
|---|---|---|
| "Windows protected your PC" | The build isn't code-signed | More info β Run anyway, or unblock the download before extracting |
| "This app has been blocked by your system administrator", or nothing happens | The company allows only approved programs (AppLocker or similar) | Only your IT department can allow it. Point them at the release page. |
| The symbol collection is empty | QElectroTech was started as bin\QElectroTech.exe
|
Start it with the launcher |
register_filetypes.bat says "β¦Lancer QET.bat n'a pas Γ©tΓ© trouvΓ©"
|
Bug in nightlies up to git10275 | Use a newer nightly, or open files as described above |
| Symbols in deeply nested folders show no name or thumbnail, or a script reports a symbol "would collide with a different element" | The full path to the symbol file is 260 characters or longer | Use a build from 2 October 2026 or later; see Long folder paths below |
Windows traditionally limits a file's full path to 260 characters, and a symbol
collection several folders deep, inside an already long folder such as
C:\Users\<you>\AppData\Local\QElectroTech\β¦, can pass that. Older builds then
found the symbol file but could not read it: it appeared without its name or
thumbnail, and a script adding it was told it would collide with another
element.
Builds from 2 October 2026 onwards read symbol files in a way that has no such limit (PR #1243). A symbol that still cannot be read is now reported as unreadable, with its full path and its length, rather than as a collision.
The same builds also tell Windows that QElectroTech handles long paths
(PR #1244).
That only matters on computers where Windows' own long-path support is switched
on (LongPathsEnabled in the registry, a machine-wide setting that needs an
administrator); there, other files with long paths open too. Without it, keep the
path of the extracted folder short, for example C:\QET.
- Downloads β every platform and package
- FAQ β general questions
- Preferences reference β what the settings stored in the registry control
- CLI Reference β the command-line options the launcher uses
Getting Started
π Languages β English Β· FranΓ§ais Β· Deutsch
Windows without admin rights β the portable archive, no installer
Guides
Conductors β wire properties, what feeds which export, cables, and hops where wires cross
Wires per terminal β limit the wires on a terminal, chain wiring instead of stars
Printing and exporting β paper, PDF, images, and what each path does differently
Linking elements β master, slave, terminal
PLC modules β I/O tables and linking a wire to a specific point
Using the element editor β drawing tools, saving, checks
Generic devices β a quick box symbol with terminals on any side, made by a wizard (pending)
Grid size and element size β why symbols aren't all the same scale, and scaling one without leaving the grid
Preferences reference β what each settings page does
Saving and loading settings β your whole setup in one file, to copy or keep
Keyboard-only control β mouseless QET, and what still needs a mouse
Mouse modifiers β what Shift, Ctrl and Alt change while you drag
3D mouse β SpaceMouse pan, zoom and buttons
Aligning items β snap symbols back to the grid, or line them up
Pictures on a sheet β labels, crop, transparency, what they cost in the file
Arcs and curved wires β the Arc tool, pulling an arc in or out, rounding a corner with a fillet, dashed arcs for lighting layouts
Grouping items β select, move and copy several items as one
Finding your place on a sheet β go to a cell like B13 or 4-B7, keep the headers in sight, show the cell limits, zoom and pan
Showing and hiding kinds of items β hide texts, wire numbers, shapes, pictures, tables or cross-references on every sheet
Drawing faster β place without dragging, the S shortcut bar, command search, gestures
Customising QElectroTech β keys, toolbar size and contents, the gesture ring (partly pending)
Managing collections β folders, writability, building your own shortlist
Templates β reusable multi-element blocks, placed by double-click or drag
Search & Replace β bulk property changes
Building a nomenclature query β the BOM/summary table builder
Linking wires across pages β sheet reports
Variables & formulas β %f, %{label}, sequences
Auto-numbering β schemes, sequences, freezing
Terminal strips β strips, levels, bridges
Title block templates β the .titleblock format
Importing EPLAN parts (.edz) β EPLAN Data Portal
DXF import & export β two unrelated features, one format; command-line export and layers
The project database β the in-memory SQLite cache
Development
Automating QET β CLI, XML formats, external tools
CLI Reference β command line usage
JavaScript Scripting β --run, geometry editing, undo
MCP server β let an AI assistant read, verify and edit projects
Connecting an AI assistant β setup for Claude, Copilot, Gemini, Codex, Cursor, LM Studio
Script buttons β stored scripts with an icon, by hand or by an assistant
Live mode β an assistant working in the open project while you watch
Macro recorder β record a task by hand, for an assistant to script
Vision β proposal, under discussion
