Modernize your Win32 application for security and privacy Q&A
summary
Win32 app isolation ships as a public preview that packages Win32 apps into App Containers and Helium silos using MSIX app identity, adds file-system virtualization and registry virtualization, and enforces brokered file access via a mini‑filter so APIs like file dialogs, drag‑and‑drop, named pipes and systray icons keep working. A capability profiler records run‑time calls and auto‑edits the manifest, usually requiring no code changes. It limits lateral access (reduces ransomware scope) and is in Windows Insider builds ahead of a future GA.
AI-written summary · about
chapters (9)
- 0:00Win32 app isolation intro
- 3:10Why isolate Win32 apps
- 8:08Developer experience goals
- 11:02How isolation works
- 18:53Minimal code changes
- 23:48Centennial vs partial trust
- 29:51Public preview & next steps
- 33:04Customer testimonials
- 36:36Q&A
related talks
45mThe Windows Sandbox Paradox
18mThe Latest in Windows Security for Developers
46mSecuring Applications and Pipelines on a Container Platform
44mWindows Phone App Security For Builders And Breakers
22mAchieving Pragmatic Parity for Windows Containers
44mUnleash Windows App Security & Reputation with Trusted Signing
31mYour Containers Aren’t Alone: Demystifying Container Isolation
21mBattle of Windows Service: A Silver Bullet to Discover File Privilege Escalation Bugs Automatically