Source note: LemonLoader is independent. Project-specific facts below are limited to information published by the LemonLoader repository, releases, or wiki; general troubleshooting advice is identified by context.
Documented expectation
The installation wiki says first boot can take from about one minute to twenty minutes or more depending on the size of the app.
Why patience matters
A slow first boot should not automatically be classified as a hang. Give the documented initialization process a reasonable window before force-closing the app.
When slow becomes suspicious
If the app never progresses or crashes repeatedly, capture Latest.log, remove optional mods, and compare the target environment with the documented runtime/architecture scope.
Later launches
The project release history mentions pre-generated proxy assemblies improving initial loading for apps that use them, but support is app-specific. Do not assume the same acceleration applies universally.
Measure before calling it a performance problem
The project documentation explicitly allows for a slow first boot, so compare first-run behavior with later launches. Record how long initialization takes and whether the app is actually progressing, producing logs, or crashing.
Reduce avoidable variables
Test the clean patched app before adding multiple mods. A heavy mod set can change startup behavior, so it should not be used as the baseline for judging LemonLoader initialization. If startup becomes worse after one change, reverse that single change and compare again.
Do not turn app-specific acceleration notes into a universal performance claim. A release feature that improves one supported app path may not apply to other titles.
Recommended next step
For a clean path through the project, use the verified download page, follow the installation guide, and keep the logging guide available for troubleshooting.