Windows 10 end-of-support has compressed the timeline
Migration programmes that used to have three years now have months. Packaging work that was scheduled across multiple waves now lands on a single wave with little slack.
Solution
Package, sign, and deploy MSIX across Intune, Azure Virtual Desktop AppAttach, and Cloud PC delivery.
EtherApps Forge captures applications directly from running systems, supports App-V to MSIX migration and MSIX app conversion, handles signing and manifest fix-ups, and produces Intune-ready and AppAttach-ready packages. Built for MSPs, migration partners, and internal IT teams.
Oct 2025
Windows 10 end-of-support, migration window is months, not years
4 formats
MSIX, MSI, IntuneWin, AppAttach from one capture
Installer-less
capture-first workflow when the original media is lost
App-V to MSIX
App-V to MSIX migration: choosing the right method
App-V to MSIX migration means assessing the App-V estate, converting suitable packages, fixing runtime gaps, then signing, testing, and deploying through Intune. App-V is no longer being developed and App-V server support ended in April 2026, so most estates are planning the move. Compare the main methods below.
| Method | Best for | Watch-outs |
|---|---|---|
| Manual repackaging | Small estates and one-off packages that need full control | Slow at scale; every package repeats the same hand-built steps |
| MSIX Packaging Tool conversion | App-V 5.1 packages with healthy sources; free Microsoft tooling | App-V 4.x is not supported directly; scripts and runtime fixes still need PSF work |
| Scripted batch conversion | Large App-V 5.1 estates run through command-line template conversions | Needs clean conversion environments and per-package review of failures |
| Capture-first repackaging (EtherApps Forge) | App-V 4.x packages, lost installers, and complex apps that resist direct conversion | Capture runs need a controlled VM and human review before release |
The problem
MSIX stays hard because the blockers sit upstream of the format itself.
MSIX is the modern Microsoft deployment format, but the path from a legacy Windows application to a signed, deployed MSIX is narrow. Teams run into four blockers: installer media that has been lost for years, in-house MSIX skills that are scarce and expensive, manifest and signing pitfalls that do not surface until deployment, and diverse targets that seem to need different packaging runs. Intune uses MSIX or IntuneWin, Azure Virtual Desktop uses AppAttach, and Windows 365 uses MSIX or IntuneWin (Windows 365 does not currently support AppAttach).
MSIX packaging skills are in short supply
Experienced packagers are rare and in demand. Training a team from scratch extends timelines past the Windows 10 end-of-support cliff, which is why AI-guided routes and capture-first workflows matter.
Source material is incomplete
Legacy applications often have no installer, no documentation, and undocumented dependencies. Any MSIX workflow that depends on clean installer media does not survive contact with a real legacy estate.
Signing and certificate management add MSIX-specific friction
Signing, manifest fix-ups, and modification packages are MSIX-specific problems that teams do not hit until late in the process. A pipeline that handles them inline is materially faster than one that punts to external signing tools.
What changes
Outcome blocks
MSIX ready for every modern target
One capture produces signed MSIX for Intune, IntuneWin for legacy-path Intune deployment, MSIX AppAttach for Azure Virtual Desktop, and MSI for legacy targets. Windows 365 delivery uses MSIX or IntuneWin output.
Signing and certificate handling inline
Signing, manifest fix-ups, and modification packages are handled inside the workflow with customer-managed or Microsoft-trusted certificate chains, so no separate signing toolchain is required.
AI-guided route selection
AI-guided routing picks MSI, MSIX, AppAttach, or IntuneWin per application and suggests dependency resolution and compatibility fixes, so packaging teams without deep MSIX skills keep moving.
Lower programme risk
Fewer packages stuck in manual rework at the end of the migration wave, with one capture covering multiple modern delivery targets rather than running separate pipelines per output.
The packaging view
From live application to signed MSIX in one pipeline.
Capture, sign, and apply manifest fix-ups inside EtherApps Forge, then route through a reviewer checkpoint into MSIX for Windows 11 and Intune, AppAttach for Azure Virtual Desktop, IntuneWin for endpoint deployment, or MSI for legacy targets - all from the same capture.
How we deliver it
Product mapping
This route is led by EtherApps Forge for capture-first MSIX, MSI, IntuneWin, and AppAttach outputs with signing and AI-guided routing handled inline. Windows 365 does not currently support AppAttach, so Cloud PC delivery uses MSIX or IntuneWin. Bring in EtherInsights where the programme also needs Windows 365 cohort design, licensing planning, or migration baselines from Azure Virtual Desktop or legacy VDI alongside the packaging workstream.
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
- Windows 10 end-of-support driven Windows 11 migration: package the existing application estate into MSIX before cutover.
- Azure Virtual Desktop AppAttach rollout: produce AppAttach packages without re-capturing each app. Windows 365 delivery uses MSIX or IntuneWin from the same capture (no AppAttach support today).
- Intune migration off ConfigMgr: convert existing MSI or App-V packages to MSIX for modern Intune deployment, or land via IntuneWin where it fits the estate.
- Sovereign and regulated sector MSIX adoption: UK public sector, EU defence, finance teams moving to signed, modern-delivery app estates.
- MSP packaging-factory operations: repeatable MSIX packaging across multiple customer tenants with consistent signing and AI-guided routing.
FAQ
Questions buyers usually ask before an MSIX packaging trial.
Keep the evaluation grounded in installer-less capture, signing, target-format routing, and how EtherApps Forge sits alongside existing packaging teams.
Why MSIX now, not later?
Windows 10 support ends October 2025, Intune defaults to modern deployment paths, and Azure Virtual Desktop AppAttach requires MSIX. The migration window has compressed from years into months for most teams, and MSIX is the format that lands across Intune, AVD AppAttach, and modern Cloud PC delivery alongside IntuneWin.
We do not have the original installers. Can EtherApps Forge still produce MSIX?
Yes. Capture-first means no installer media dependency. EtherApps Forge captures the installed application footprint from a live system (files, registry, AppData, services, and dependencies) and produces signed MSIX, MSI, IntuneWin, and AppAttach outputs from one capture. This is the main reason teams pick EtherApps Forge over traditional packaging toolchains for legacy estates.
Can we produce AppAttach and Intune MSIX from one capture?
Yes. One capture produces signed MSIX for Intune, IntuneWin for legacy-path Intune deployment, and MSIX AppAttach for Azure Virtual Desktop. Windows 365 delivery uses MSIX or IntuneWin from the same capture. Windows 365 does not currently support AppAttach, so Cloud PC delivery goes via the MSIX or IntuneWin path.
Does this replace our existing packaging team?
No. AI-guided routing augments the team by closing the MSIX skills gap and suggesting the right path per application, but a human reviewer still signs off on each package. EtherApps Forge works alongside existing packaging workflows rather than replacing packager judgement.
Can App-V packages be converted directly to MSIX?
App-V 5.1 packages can be converted directly with the Microsoft MSIX Packaging Tool, through the interface or the command line for batch runs. App-V 4.x packages are not supported directly; Microsoft recommends converting from the source installer, and where the installer is lost a capture-first repackage from a live installation is the practical route. EtherApps Forge covers that capture-first path with human review before release.
What breaks during App-V to MSIX conversion?
The usual blockers are launch and logoff scripts, runtime behaviours that assumed the App-V client, middleware dependencies, and packages whose source media no longer exists. The Package Support Framework fixes many runtime gaps after conversion, and packages that resist direct conversion can be repackaged capture-first instead. A short assessment pass before migration finds these blockers early.
Do migrated MSIX packages need signing?
Yes. Every MSIX package must be signed with a certificate the estate trusts before Windows will install it, so plan certificate handling as part of the migration workflow rather than an afterthought. EtherApps Forge builds signing into the packaging pipeline, and the same certificate discipline applies to packages converted with Microsoft tooling.
How do I deploy migrated MSIX apps with Intune?
Assign the signed MSIX packages through Intune like any modern Windows app, starting with a pilot ring on representative Windows 11 devices before broad assignment. Keep the App-V package available until the pilot proves the converted app behaves correctly, then retire the old delivery path as each wave completes.
What happened to App-V support?
Microsoft moved the App-V client and sequencer to fixed extended support, so they still ship with Windows but receive fixes only, and support for the App-V server components ended in April 2026. Teams already using App-V packages on Azure Virtual Desktop can use App-V app attach without an App-V server, and most estates are using this window to plan a controlled App-V to MSIX migration.
Start here
Move the MSIX pipeline from narrow and risky to signed, tested, and delivered.
Start with a 7-day EtherApps Forge trial on a real application, or book a demo to walk through capture-first MSIX, signing, and AppAttach routing before Windows 10 end-of-support compresses the timeline further.
- One capture produces MSIX, IntuneWin, AppAttach for AVD, and MSI outputs in one workflow, rather than separate runs per target format.
- Signing, manifest fix-ups, and modification packages are handled inline, so the MSIX pipeline does not hand off to an external signing toolchain mid-process.
- AI-guided routing closes the MSIX skills gap without removing the human reviewer, so packaging teams retain control and evidence of each decision.