Software de empaquetado MSIX para Windows 11, Intune y AVD, sin medios de instalación.

No. Forge captures directly from running Windows systems, so packages can be produced even when the original installer media is missing, incomplete, or no longer usable. This is one of the most common reasons teams start with Forge rather than traditional packaging tools.

Yes. Signing, manifest fix-ups, and modification packages are handled inside the Forge workflow, with certificate management supported for both customer-managed and Microsoft-trusted chains. Teams do not need to switch to external signing tools for the MSIX delivery path.

Yes. The same capture produces AppAttach-ready MSIX packages for Azure Virtual Desktop, alongside IntuneWin, MSIX, and MSI outputs. Windows 365 does not currently support AppAttach, so Cloud PC delivery uses MSIX or IntuneWin from the same capture.

Forge stages the Package Support Framework as part of packaging. File and registry redirection and working-directory fix-ups are applied so the captured application behaves correctly inside the container, without changing the application source code. That covers the common failures where an app writes next to its own executable or expects a fixed install path.

Yes. forge_msix is a drop-in replacement for Microsoft's makeappx.exe, so a build folder becomes a signed, validated MSIX using the switches an existing pipeline already passes. Developers and ISVs can scaffold a manifest from the built executable, create and sign in one step, then validate and smoke-test the package as a stage in the release pipeline.

Yes. Forge captures from running systems, which means you can package applications even when the original installer media is lost or unavailable. This is one of its most commonly used capabilities for legacy estate work.

Forge supports capture from Windows XP through Windows 11, covering the full range of environments typically encountered in legacy migration programmes.

Forge produces MSI, MSIX, App-V, IntuneWin, and MSIX AppAttach packages from a single capture. MSIX and IntuneWin cover Intune and Windows 365 delivery; MSIX AppAttach is the delivery format for Azure Virtual Desktop (Windows 365 does not currently support AppAttach). One capture, multiple modern delivery targets without re-running the capture process.

EtherAssist is embedded within the Forge platform and provides AI-guided routing at each packaging stage, including dependency resolution, compatibility assessments, and MSIX fix-up recommendations. It reduces the manual investigation needed when applications fail to package cleanly, and closes the MSIX skills gap for teams without dedicated packagers.

Yes. EtherApps Forge is available through EfficientEther's channel partners and distributors including Northamber in the UK and ARJ Distribution across the Nordic region. Full pricing, a free trial, and an ROI calculator are available at www.etherapps.ai.

A typical release stage calls forge_msix pack with the same flags an existing makeappx.exe invocation already uses, pointing at the build output folder, then forge_msix sign against the pipeline's certificate, and forge_msix validate to smoke-test the result before it is published as a build artifact. Because forge_msix accepts the same switches as makeappx.exe, teams usually swap the binary in an existing GitHub Actions or Azure DevOps YAML step rather than writing new pipeline logic.