chore: bundle evbunpack tool and add EVB control/launch fixes

- Add Enigma Virtual Box (EVB) engine support: detection, badge, unpack/restore UI
- Bundle evbunpack.exe under Engines/Evb/Tools/evbunpack (Apache-2.0, with LICENSE/README)
- Copy Engines\\**\\Tools\\** to build output via csproj (publish already covered by publish.ps1)
- Throttle evbunpack progress reporting and shorten timeout to stop UI freeze
- Rename original packed exe to .glbak and write a completion marker; make Restore reverse it
- Launch the unpacked exe from _evb_extracted so script mods apply
- Replace EVB MessageBox dialogs with readable log summaries
- Remove obsolete boxed/7zip extraction code (NwjsPackageUnpacker, TkoolPackagedExtractionService)
This commit is contained in:
armonica committed 2026-10-07 09:30:09 +09:00
1 parent 8cea2a147d
commit 05e7bdb3c0
23 files changed
+1542 -1288

No files matched your search

+62
View File
@@ -0,0 +1,62 @@
# evbunpack (bundled tool)
`evbunpack.exe` is a bundled, third-party unpacker used by the **Evb** engine module to
unpack applications protected with **Enigma Virtual Box**.
## Provenance
- Upstream project: https://github.com/mos9527/evbunpack
- Description: Enigma Virtual Box Unpacker / 解包・脱壳工具
- License: Apache-2.0 (see `LICENSE` in this folder for the full text)
- Repository status: **archived (read-only) by the owner on 2026-02-06**
- Version / release: bundled from the upstream Windows builds
(see the "For Windows Users: Builds are available here" link in the upstream README,
which points to the project's GitHub Releases page).
> **NOTE**: The binary in this folder is not committed as part of the normal source
> tree review flow. Place the upstream-release `evbunpack.exe` here before publishing.
> If the file is absent, the `Evb` engine module reports the tool as unavailable and
> skips unpacking instead of throwing (callers degrade gracefully).
## CLI usage
```
evbunpack [-h] [--log-level {DEBUG,INFO,WARNING,ERROR,CRITICAL}] [-l]
[--ignore-fs] [--ignore-pe] [--legacy-fs]
[-pe {10_70,9_70,7_80}] [--out-pe OUT_PE]
file output
```
- `file` : the packed `.exe` (input)
- `output` : the folder that receives the unpacked files (created if missing)
The tool restores **both** the virtual file system contents **and** the original PE
executable, in a single invocation.
### PE variant selection
| Packer version | Unpack with flags |
|----------------|------------------------------|
| 11.00 | `-pe 10_70` |
| 10.70 | `-pe 10_70` |
| 9.70 | `-pe 9_70` |
| 7.80 | `-pe 7_80 --legacy-fs` |
`EvbUnpackerToolProvider.BuildArguments` defaults to `-pe 9_70` and can be overridden
per call.
## Alternatives (when re-bundling is not possible)
- Install via PyPI: `pip install evbunpack` and run `python -m evbunpack ...`
(requires a Python runtime on the target machine).
- Build from source with `setup.py` / `pyinstaller` following the upstream README.
## Where it is used
- `Engines/Evb/EvbUnpackerToolProvider.cs` — resolves the executable and builds CLI arguments.
- `Engines/Evb/EvbUnpackService.cs` — orchestrates detection, unpacking and re-detection.
Resolution order (see `EvbUnpackerToolProvider.GetToolPath`):
1. `Engines/Evb/Tools/evbunpack/evbunpack.exe` (bundled layout, this folder)
2. `Engines/Evb/Tools/evbunpack.exe` (flat layout)
3. `AppPathHelper.ResolveEngineTool("Evb", "evbunpack/evbunpack.exe")` fallback probe.