Solution
An assessment-first route for legacy apps where the installation media is lost, the vendor portal is gated or gone, or nobody is sure whether the app still works on Windows 11 or a Cloud PC. We find what is actually installed, recover the app without the original installer, repackage it for modern Windows delivery, and validate legacy app compatibility before the migration wave.
No installer
rescue legacy apps when the installation media is lost or the vendor portal is gated
4 outputs
MSIX, MSI, IntuneWin, and AppAttach from one capture
Win 11 + Cloud PC
legacy app compatibility validated before the migration wave
The problem
Plain version: the business still depends on apps that were installed years ago, but the original install disc, the download link, or the vendor portal is no longer there. IT version: legacy line-of-business software with missing installation media, gated installer portals, undocumented dependencies, and unknown Windows 11 and Cloud PC compatibility is blocking the next migration wave. Both versions need the same answer: find what is actually installed, rescue it without the original installer, and prove whether it can move to Windows 11, Intune, AVD, or Windows 365 Cloud PC.
ISO, EXE, and MSI files have been deleted off old shares. CDs are in a cupboard nobody can find. The person who originally installed it left years ago. A workflow that only works with clean installer media does not survive contact with a real legacy estate.
The vendor has retired the product, moved behind a partner portal, or only ships a subscription replacement. The contract is still valid, the app still runs, but nobody can re-download the original installer without a long, uncertain support ticket.
Nobody can say whether the app will run on Windows 11, in a Cloud PC, or under Azure Virtual Desktop. Teams default to leaving the legacy device alone and the migration slips. Without a real compatibility check, the risk feels bigger than it usually is.
Even when the app can be rescued, turning it into a signed MSIX, MSI, IntuneWin, or AppAttach package needs experienced packagers, and they are busy. Without an assessment-first route, every legacy app looks like a custom project.
What changes
We capture the application footprint from a working machine: files, registry, services, dependencies, and configuration. You get a clear list of what runs, where it runs, and what it depends on, without needing the original installer.
EtherApps Forge produces signed MSIX, MSI, IntuneWin, or AppAttach from the same capture. One rescue covers Intune deployment, Azure Virtual Desktop AppAttach, and Windows 365 Cloud PC delivery (Windows 365 uses MSIX or IntuneWin).
Each legacy app comes back with a clear verdict: ships as-is, ships with fix-ups, needs a remediation step, or genuinely cannot move yet. That turns legacy app compatibility from a gut feeling into a documented decision the migration board can sign off.
Once the legacy app is recovered and assessed, the same record routes into MSIX packaging and deployment, agentic app packaging, or application modernisation and migration. You don't restart the work to move from rescue into rollout.
What the rescue looks like
We start where the legacy app is still running. EfficientEther captures the installed footprint directly, even when the original installer is lost or the vendor portal is closed, then routes it into MSIX, MSI, IntuneWin, or AppAttach so the same app can ship to Intune, Azure Virtual Desktop, and Windows 365 Cloud PC. Each app comes back with a clear compatibility verdict for Windows 11.
Walkthrough
A short walkthrough of legacy app capture from a working machine, package output, and a Windows 11 compatibility verdict — no original installer required.
How we deliver it
EtherApps Forge leads. Forge captures running legacy apps directly from a working machine when installation media is lost or gated, produces signed MSIX, MSI, IntuneWin, and AppAttach outputs from the same capture, and applies AI-guided routing so the right output format is picked per app. EtherInsights joins where the same programme also needs Windows 365 cohort planning, Intune readiness, or migration baselines from Azure Virtual Desktop or legacy VDI alongside the legacy app rescue work.
EtherApps Forge captures installed Windows applications from running systems, analyses the real application footprint, supports AI-guided packaging decisions, and produces deployment-ready outputs for modern environments.
EtherInsights started as the cost management platform for Microsoft 365 and Azure. It shows where spend is going, which owners need to act, and how to turn waste into savings. It now extends that operating view into full Windows 365 lifecycle support, plus tenant, user, security, device, and Intune reporting.
Where this fits
FAQ
Plain answers for IT leads and the people who actually rely on the app. No installer? No vendor portal? Windows 11 compatibility unknown? Here's how each is handled.
Yes. EtherApps Forge captures the application directly from a machine where it is already installed and running. We pick up the files, registry entries, services, and dependencies, then build a signed MSIX, MSI, IntuneWin, or AppAttach package from that capture. No installer media is required to start.
Usually not. If the app is licensed and installed somewhere in the business, the rescue works from the installed footprint. We don't depend on re-downloading the installer from the vendor. We do still recommend checking the licence terms before you redistribute the repackaged app internally.
Each app comes back with a compatibility verdict: ships as-is on Windows 11, ships with manifest fix-ups, needs a remediation step (for example a runtime or a kernel-mode dependency that is no longer supported), or genuinely cannot move yet. That verdict feeds straight into the migration plan so legacy app compatibility stops being a guess.
The capture is read-only against the source machine. We typically capture from a representative reference machine or a controlled VM rather than a live user device, so day-to-day work isn't disrupted. The output is reviewed and signed before anyone deploys it.
Some apps genuinely can't move to MSIX (drivers and kernel-mode components are a common reason). For those, the assessment is still useful: you get a clear documented reason, an MSI or IntuneWin path where possible, and a shortlist of apps that need a modernisation conversation rather than a packaging one.
No. The assessment closes the upstream gap (no installer, no clarity, no compatibility data) so the packaging team isn't stuck on detective work. A human reviewer still signs off each package before release.
Start here
Book a legacy app review and we'll walk through a real app: missing installer, gated vendor portal, or unknown Windows 11 compatibility. You leave the call knowing what can be rescued, what can be repackaged, and what genuinely needs a different conversation.
