Skip to contentTalk to us
العربيةLog inStart free
The installer · Windows Studio

Create an EXE installer with AI, and know exactly what is in it

The .exe you download from Fanann is a real installer for your app: it installs it, names it and includes its uninstaller. This page explains what is inside, how to share it, and how to be sure the file in your hands is the one you built.

Start building freeSee the steps
One file, 64-bitNo admin rightsA SHA-256 checksum per build
The installer

Three facts about the file you download

1

One file with your app’s name

It is named <App>-Setup-<version>.exe. No folders, no companion files, nothing to unpack before installing.

2

It installs per user, with no admin

It installs into the current user’s account, so no administrator prompt appears and you do not need the IT department.

3

It carries its real status

The build card says whether the file was tested on Windows. We do not write “fully ready” on something that has not been tested.

1Contents

What is inside the installer

Inside is your whole app: the screens you reviewed, the logic that calculates, saves and prints, and the data-location setting. In Local mode the app carries its data rules and creates the database on the PC at first start. In Cloud mode it carries the address of your app in Fanann Cloud and no secret keys: each employee signs in with their own account.

  • The app’s name, icon and version number
  • An uninstaller
  • No custom system-level code is written for your app: abilities are fixed and off by default
2Sharing

Installing on more PCs, and what happens to the data

Downloading the installer is open to the members of your workspace. From there, copy it to the other PCs like any file. What happens to the data depends on your choice: in Local mode every PC starts with its own empty database. With Fanann Cloud each employee signs in and sees the same records.

  • Local: five PCs = five databases
  • Cloud: five PCs = one database
  • Removing an employee’s cloud access does not delete the program from their PC
3Verifying

Checksums and versions: make sure it is your file

Every build has a SHA-256 checksum: a string of letters and digits that changes if even one character of the file changes. Copy it from the build card and compare it with the checksum of the file on the PC. Every build also has a version number and release notes, so you know which file is on which machine. And a build stays “Built” until it is really installed and started on a Windows machine, when it becomes “Tested on Windows”.

  • A copy button for the checksum on the build card
  • A release history with notes for each version
  • The newest ready build of each app is always kept
Situations

Three moments you will meet with an installer

Installing on the shop PC

You download the file on your own PC, carry it on a USB stick to the shop PC and run it. It does not ask for an administrator password. In Local mode the app needs no internet after that.

Sending it to another branch

Send the file with the checksum in a separate message and ask the recipient to compare it before running.

Shipping version 1.1

Changed the app? Raise the number, write the release notes and build. Then the new file is installed over the old one on each PC. In Local mode, take a backup first.

The steps

How to install your app on another PC safely

Six steps that take minutes and spare you the question “is this file all right?”.

  1. 1

    Download the file from your workspace

    From the release history in Windows Studio. Do not rely on a copy that reached you through a third party.

  2. 2

    Copy the checksum from the build card

    Use the Copy button next to SHA-256. Keep it in a note, or send it alongside the file in a separate message.

  3. 3

    Move the file to the other PC

    By USB stick, shared folder or email. The PC must be 64-bit Windows 10 or 11.

  4. 4

    Compute the file’s checksum and compare

    Open a command prompt in the file’s folder and type: certutil -hashfile YourFile.exe SHA256 then compare the output with the checksum you copied. If they differ, do not run the file.

  5. 5

    Run the installer

    Once the checksum matched, double-click the file and follow the steps. The install completes without admin rights.

  6. 6

    Open the app and confirm

    In Local mode it starts with an empty database on this PC. In Cloud mode, sign in and confirm you can see the shared records.

Plainly: the installer’s limits today

.exe onlyNo MSI package, no build for ARM or 32-bit systems, none for Mac or Linux.
No automatic updateThe installed app does not update itself. A new version is downloaded and installed by hand.
Files are not kept foreverOlder installers are kept for a period set by your plan, then removed. The newest ready build of each app always stays.
FAQ

Questions people ask

Is the EXE I download safe?
The file is built on Fanann’s servers from your own app, and only members of your workspace can download it. The way to check for yourself: download it straight from your workspace and compare the SHA-256 checksum with the build card.
Does the install need administrator rights?
No. The app is installed into the current user’s account, so no administrator prompt appears.
What does a PC need to run the app?
64-bit Windows 10 or Windows 11. The app relies on a Windows component to draw its interface, which current versions already have. If it is missing, the installer adds it, and that one time it may need an internet connection.
Can I get an MSI package?
Not at the moment. What is available is one per-user .exe installer. If your organization deploys software through central tools that require MSI, that is not supported today.
Windows Studio

The rest of Windows Studio

AI Windows app builder

The main page: describe your business software in plain words, watch it take shape in a Windows window, choose where its data lives and download a real installer.

Meet Windows Studio

Build a Windows app with AI

The steps in plain language with a worked example: from one sentence about the job, to an interactive preview, to the data choice, to the installer.

See the details

AI desktop app builder

When desktop software beats a website: working offline, speed at the counter, printers and files, and data that is local or shared.

See the details

AI POS software builder

A point of sale for a restaurant or shop: orders, receipts, the printer, and how staff see the same orders on more than one PC.

See the details

AI inventory software builder

Inventory software on Windows: products, barcode input, stock movements and their history, reports, and when local data is enough.

See the details

Windows app templates

Eight starting points you can change: POS, inventory, invoicing, expenses, front desk, attendance, labels and a file organizer, each with a suggested data location.

See the details

Compare: local vs cloud data

The decision guide: where should your app’s data live? A comparison table, real scenarios, costs, and why five PCs do not share a local database.

See the details

Guide: Windows app from idea to EXE

A long-form guide for business owners: writing the brief, reviewing the preview, choosing the data location, building the installer, sharing and updating it.

Read the guide
Guide: Windows app from idea to EXETrust center: security and privacy at FanannPricing: how Windows Studio is charged
From the blog

What people ask about Windows programs

All Windows apps guides
Setup.exeHow to make a Windows app in 2026, even if you have never coded11 min readSetup.exeHow to make an employee attendance program9 min readSetup.exeHow to print barcode labels from your own program9 min read

A real installer, with its real status.

Build your app, download an .exe with its name, version and checksum, and roll it out to your work PCs. Signing up is free.