Exercise 1: Why Store Apps Uninstall Cleanly and EXE Installers Don't — Possible Solution ==================================================================== WHAT MAKES A MICROSOFT STORE APP DIFFERENT WHILE RUNNING ------------------------------ Per this chapter, Store apps are "packaged as MSIX... each app runs with its own isolated storage and a specific, declared set of permissions." Everything the app writes - its files, its settings, its data - lives inside that isolated sandbox boundary, not scattered across shared system locations like the general Windows registry or common program-data folders. WHY THAT SAME BOUNDARY MAKES UNINSTALL CLEAN ------------------------------ Per this chapter, Store apps "uninstall cleanly by design: no leftover registry entries or orphaned files, since the sandbox boundary that limited the app's reach while running also bounds exactly what has to be removed." Because the app was never allowed to write outside its own isolated storage in the first place, removing that one contained storage area removes everything the app ever created - there's no scattered, hard-to-track leftover data anywhere else to miss. WHY A TRADITIONAL EXE INSTALLER HAS NO SUCH GUARANTEE ------------------------------ Per this chapter, EXE installers are "just ordinary programs that happen to install something - there's no format-level guarantee of a clean rollback or a standard, predictable uninstall behavior; whatever the installer's own author built in is all there is." An EXE-installed program isn't sandboxed at all - it can write to shared registry locations, shared program-data folders, and anywhere else a regular program has access to. Removing it cleanly depends entirely on the uninstaller the original author wrote correctly tracking and removing every one of those locations - there's no structural boundary forcing completeness the way MSIX's sandbox does. WHY THIS IS A FORMAT-LEVEL DIFFERENCE, NOT A QUALITY DIFFERENCE ------------------------------ This isn't about one uninstaller being written more carefully than another - it's that MSIX's sandboxing architecturally guarantees containment regardless of the app's own uninstall logic, while an EXE installer's completeness depends entirely on its author having tracked every location it ever wrote to, with no structural safety net if they didn't. WHY THIS WORKS AS AN ANSWER ------------------------------ It explains the sandboxing mechanism this chapter describes for MSIX apps, connects that same mechanism directly to why uninstall is clean by design, and contrasts it with the EXE installer's lack of any structural boundary - correctly framing the difference as architectural rather than a matter of one installer being better-written than another.