Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Windows installer (MSI) is slow

Open
#257 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
perl, python
Domain
release

Research direction

Start by building the MSI and measuring it: run msiexec /i ECCE-windows-9.0.0-alpha.10.msi /l*v install.log and find which phase dominates (file costing, file copy, registry, or custom actions), then count files and components in the bundled Python, wxPython and Perl. Done means a clean install on NerdEgg has a stated time taken from the log and the CI MSI install/uninstall test still passes. Packaging changes need maintainer agreement on the approach first.

Written by the indexing model from the issue text.

Description

The per-user MSI (ECCE-windows-9.0.0-alpha.10.msi, ~180 MB, WiX v5) installs slowly on Windows 10; reported again on alpha.10, already listed as a known issue since alpha.8.

To find out first (measure, don't guess)

  • Time the phases from a verbose log: msiexec /i ECCE-windows-9.0.0-alpha.10.msi /l*v install.log. This shows file costing, file copy, registry and custom actions.
  • Number of files and components in the package. The bundled Python, wxPython and Perl add tens of thousands of small files, and MSI cost scales with the number of files and components more than with total size.
  • The effect of real-time antivirus (Windows Defender scans every file written): compare the install time with the zip unpacked to the same place.

Likely remedies, depending on the measurement

  • Fewer, larger components (one component per directory, or WiX harvesting with directory-level components), instead of one per file.
  • Ship the bundled runtimes as zip/archive files that are unpacked on first start, or put Python's standard library in its zip form (python3xx.zip).
  • Drop unused parts of the bundled runtimes: tests, documentation, __pycache__, unused Perl modules.
  • Check that no custom action runs a slow step (e.g. compiling .pyc files) at install time.

Done when: a clean install on NerdEgg takes a stated time (e.g. under 1 minute), measured from the log, and the CI MSI install/uninstall test still passes.

Dominant language
C
Stars
10
Forks
8
Avg merge
21m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FriendsofECCE/ECCE

All issues in FriendsofECCE/ECCE

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.