Let’s cut through the hype, verify what actually shipped versus what is still experimental, and break down what all of it means for PC enthusiasts, IT pros, and everyday users.
Windows 11 on an "iPhone Duo": Brilliant Engineering Demo, Not a Pocket PC Replacement
If you saw clips circulating on X showing desktop Windows 11 24H2 running locally on a half-folded Apple phone with a virtual keyboard and trackpad on the lower half, your first instinct was probably to ask whether it was remote desktop trickery. According to the open-source WindowsiOS repository published on GitHub by Ammaar Reshi, Google AI Studio’s product and design lead, it is running locally—though with major caveats that separate a remarkable developer proof of concept from something you should expect to install on Monday morning.
Reshi’s repository claims an end-to-end demonstration of unmodified retail Windows 11 24H2 ARM64 (Build 26100) booting and running Microsoft Edge, Electron-based developer tools, and Microsoft’s Prism x86-64 translation layer (xtajit64.dll) without jailbreaking, on hardware the project identifies as the foldable iPhone Duo (iPhone19,4) powered by an Apple A20 Pro chip and iOS 27 TXM. Notably, those hardware and "near-native" JIT performance claims come from Reshi’s own repository and demonstration; neither Microsoft nor Apple endorses or supports running Windows on iOS.
Why Running Windows 11 on Stock iOS Is Normally a Brick Wall
Since iOS 16.4, Apple locked third-party apps out of Hypervisor.framework, cutting off hardware EL2 virtualization on non-jailbroken iPhones and iPads. Traditional interpreter-based emulators like UTM SE fall back to QEMU’s threaded interpreter, which is 5× to 10× too slow for Windows 11 24H2—taking tens of minutes just to reach the desktop and choking on multi-process Chromium apps.
Building on upstream open-source projects—including Leviidev/Henge, Leviidev/Husk, StikDebug/StikJIT, TianoCore EDK2 ArmVirtQemu, and Red Hat’s virtio-win drivers—Reshi says he used Google’s Gemini 4 Carbon model to engineer a custom ARM64-to-ARM64 dynamic binary translator (JIT) paired with a 4 KB software MMU and a complete virtual PC hardware platform.
The Four Windows NT Hurdles WindowsiOS Claims to Solve
What makes WindowsiOS genuinely interesting to Windows systems engineers isn’t the novelty of a phone showing a Start menu—it’s the specific Windows NT kernel quirks documented in the codebase:
- 4 KB Page Granules and the
TCR_EL1.A1 = 1ASID Trap: Darwin runs on 16 KB host pages, whereasntoskrnl.exedemands 4 KB stage-1 translation granules. Worse, unlike Linux or macOS, Windows 11 ARM64 setsTCR_EL1.A1 = 1, storing the active process Address Space Identifier (ASID) inTTBR1_EL1rather thanTTBR0_EL1. During Windows context switches (KiSwapProcess), the ASID transiently passes through0.WindowsiOSimplements a canonical ASID-keyed software TLB stash (HvTlbStash) so context switches don't constantly thrash or leak stale user memory mappings. - Inline ARMv8.1 LSE Atomics and Clang’s
LDXR XZRGotcha: Windows NT’s dispatcher and heap hammer 128-bit lock-freeSLISToperations millions of times per second. Exiting the JIT to C on every atomic pair kills boot speed, soWindowsiOSlowers them to inline Apple SiliconLDPandCASPALinstructions. It also handles a subtle AArch64 encoding edge case (rt == 31) emitted by Clang in Chromium and Electron—where register 31 means zero-registerXZRinLDXRbut stack pointerSPinMOV/ADD—preventing renderer deadlocks. - Surviving Windows Prism (
xtajit64.dll) Unaligned Memory Accesses: Windows 11’s x86-64 translator expects unalignedFEAT_LRCPC2(LDAPUR/STLUR) loads and stores to work (SCTLR_EL1.nAA = 1). On Apple Silicon under Darwin, user-spacenAA = 0immediately kills the process withSIGBUSon an unaligned access. The translator emits inline alignment checks that let aligned instructions fly natively while routing unaligned ones to software helpers. - No DeviceTree Allowed—Full UEFI, ACPI 6.3, and Scratch-Built Audio: Windows 11 refuses FDT boot and expects PC-class firmware. The project implements dual 64 MB flash banks (including persistent NVRAM so
bcdbootentries survive reboots), ACPI 6.3 tables with GICv3 ITS MSI-X, NVMe 1.4, USB 3.0 xHCI compliant withUSBXHCI.SYS, WHQLvirtio-netover rootlesslibslirpNAT, and even a custom Intel ICH6 High Definition Audio PCIe controller (8086:2668) becausevirtio-sndlacks an inbox Windows driver. It even includesWinIOSBrowser.exeto relay OAuth sign-ins to iOS’s native Safari sheet for Passkeys and Face ID.
Practical takeaway: Don’t throw out your Surface or ThinkPad just yet. WindowsiOS ships as source code only, with no prebuilt IPA or OS images. Compiling and running it requires an Apple Silicon Mac, Xcode, on-device debugger attachment to bless JIT memory pages, and your own Windows 11 24H2 ARM64 image. As a technical showcase of ARM64 binary translation and AI-assisted systems coding, however, it is wildly impressive.
Android’s Native App Lock Returns in Beta—And Samsung Gets a Head Start
Over in the mobile world, Google finally addressed a privacy gap that Xiaomi and Apple (with iOS 18 back in 2024) solved years ago: a native, system-level App Lock in stock Android that doesn’t force you to duplicate apps inside Private Space or Samsung’s Secure Folder.
As reported by 9to5Google on November 18, 2026, App Lock originally popped up in an August Android 17 QPR2 beta build before vanishing in later updates. In a Reddit post explaining the yo-yo act, Google’s Community Engagement Manager stated the team temporarily pulled the feature from QPR2 Beta "to allow for additional polish, thorough testing, and robust integration across all system surfaces". It quietly resurfaced in Android 17 QPR3 Beta 3 on October 29, 2026, and Google officially invited Pixel beta testers to put it through its paces on November 18.
What App Lock Actually Locks Down
Unlike sketchy third-party Play Store "app lockers" that demand invasive Accessibility permissions, Android 17’s native implementation hooks straight into the OS:
- Quick Trigger: Long-press an app icon on the home screen (or manage apps via system settings) to add it to the lock list.
- Authentication Gate: Opening a locked app requires biometrics or your device PIN, pattern, or password—even if the phone itself is already unlocked.
- Surface Redaction: Beyond blocking launches, App Lock hides notification content, strips home-screen widgets and shortcuts, blurs or redacts previews in the Recents switcher, hides direct-share targets, and blocks locked app data from AI services.
The Catch: Timing, Platform Limits, and Feature Requests
| Platform / Channel | Current Status (Nov 2026) | Expected Stable Window | Notable Caveats |
|---|---|---|---|
| Google Pixel (Android 17 QPR3 Beta 3) | Available for Beta testers | Q1 2027 (likely March) | Pulled from QPR2; Pixel users wait until QPR3 |
| Samsung Galaxy (One UI 9.5 Beta) | Rolling out in Beta (Nov 18) | Galaxy S27 launch; ~May 2027 (est.) for older models | Based on Android 17 QPR2; Galaxy S26 Ultra adds Privacy Display integration |
| Android 16 and Earlier | Not supported | Not planned | Cannot be backported via Play System updates |
Notice the irony spotted by 9to5Google: because App Lock lives inside Android 17 QPR2’s platform code, Samsung’s One UI 9.5 beta (which launched November 18 for the Galaxy S26 lineup) picked it up right alongside Pixel’s QPR3 Beta 3. That means Samsung’s next flagship series could ship with stable native App Lock before Pixel owners get it in Q1 2027. Worse for anyone holding onto an older device, Google’s Mishaal Rahman confirmed on Reddit that App Lock relies on new core Android platform APIs and cannot be backported through Google Play System updates—if you don’t get an Android 17 OS upgrade, you’re out of luck. Meanwhile, early beta testers are already asking Google for one obvious upgrade: the ability to set a separate PIN or password for App Lock rather than relying on the main lock-screen credential.
Practical takeaway: If you hand an unlocked phone to friends, coworkers, or kids, native App Lock is one of Android 17’s most useful privacy upgrades—just verify your device is slated for Android 17 QPR2/QPR3 (or One UI 9.5), and remember it’s still beta software on Pixel and Galaxy devices today.
"I’d Be Honored to Return"—And NVIDIA’s Board Says "No Thanks"
For Windows gamers, workstation builders, and enterprise AI architects, leadership stability at NVIDIA isn’t mere Silicon Valley gossip; it sets the tone for GPU supply, driver quality, and multi-year compute roadmaps. And right now, Santa Clara is in the middle of the biggest corporate governance drama in semiconductor history.
To recap the verified timeline: on November 12, 2026, NVIDIA’s board of directors announced that founder Jensen Huang had resigned effective immediately as president, CEO, and board member. Longtime CFO Colette Kress stepped in as interim CEO while retaining her CFO duties, and former Synopsys CEO Harvey C. Jones was named NVIDIA’s first-ever Chair of the Board as the company launched a formal search covering internal and external candidates.
According to reporting from the Associated Press, Reuters, and TechCrunch, Huang’s abrupt departure followed disclosures of extramarital affairs, including a long-running relationship with former Megaspeed executive Alice Huang, whom U.S. intelligence officials suspect of working for China’s Ministry of State Security. Those revelations triggered both an independent board investigation and an SEC probe, alongside heightened scrutiny in Washington over whether export-restricted AI chips slipped past controls.
The Tuesday Turnaround That Wasn’t
Over the ensuing days, a vocal "Stand With Jensen" campaign gained steam among allies, employees, investors, and even President Donald Trump. On Tuesday, November 17, 2026, hours before NVIDIA’s quarterly earnings call, Huang broke his silence on X. Acknowledging "serious mistakes" in his personal life, Huang wrote that he had seen an outpouring of calls from employees, investors, partners, and customers, adding that if the board decided his return served shareholders, employees, the company, and America, he "would be honored" to return as CEO.
Did the board blink? Not even close.
At the top of NVIDIA’s Q3 fiscal 2027 earnings call later that day, Chair Harvey C. Jones delivered an unmistakable rebuttal. Explaining that Huang had voluntarily resigned after disclosing "personal behavior inconsistent with the company's code of conduct, standards, and cultural norms," Jones stated flatly: "The Nvidia board unanimously accepted his resignation and does not intend to reinstate Jensen as CEO".
Follow the Numbers—and the Bylaws
If the board was trying to prove NVIDIA can execute without its iconic leather-jacketed founder, the quarterly balance sheet handed them a massive shield:
- Blockbuster Q3 FY2027 Results: NVIDIA posted $115.8 billion in quarterly revenue (up 103% year-over-year), including $107.6 billion from data centers alone, and projected roughly $130 billion for Q4.
- New Governance Guardrails: NVIDIA formed a dedicated board committee on national security and export controls chaired by director Suzanne Nora Johnson.
- Why the Drama Isn’t Over: As Reuters noted, Huang still holds roughly 3.58% of NVIDIA shares (about 870.6 million shares as of March 2026)—enough under NVIDIA’s proxy-access bylaws to nominate up to two directors if he decides to press the issue with shareholders.
Practical takeaway: In the near term, NVIDIA’s product cadence and financial engine are humming under Colette Kress, and the board has drawn a clear governance boundary. Still, until a permanent CEO is named and federal and board investigations conclude, expect continued boardroom and policy turbulence around one of the PC industry’s most critical suppliers.
Windows & PC Rapid-Fire: SSD-Eating Drivers, Boot-Stick Saves, and a Browser Hotline
Beyond the three headline stories, several Windows-centric developments from the same week deserve a spot on your radar—especially if you maintain PCs or manage Windows 11 endpoints:
- NVIDIA GeForce SSD Write Bug Fixed in Hotfix 621.35: Users on GeForce drivers 621.14 and 621.24 discovered that
NVDisplay.Container.exe(the NVIDIA Display Container LS service) was continuously rewriting a binary log file (C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg) at rates between 3 GB and 30 GB per hour while idle—mirroring a recent AMD driver scare. On November 20, 2026, NVIDIA released Hotfix Driver 621.35 (tracking bug7116722) to halt the runaway writes. Remember that hotfix drivers skip WHQL certification and won’t appear in the NVIDIA App, so affected users must download 621.35 manually from NVIDIA’s support site—or check Windows Resource Monitor’s Disk tab to confirmNVDisplay.Container.exeisn’t hammering their NVMe drive. - Rufus 4.16 Rescues Millions of PCs from AMI’s NTFS Bug: Released November 17, 2026, Rufus 4.16 ships a workaround for a long-standing bug in AMI’s UEFI NTFS driver that broke runtime UEFI boot-media validation across millions of motherboards. Pete Batard’s utility also adds a Windows User Experience toggle to restore Windows 11’s classic full right-click context menu during setup, accurately labels USB 3.2 (20 Gbps), USB 4.0 (40 Gbps), and USB 4.1 (80 Gbps) drives, updates embedded GRUB to 2.16 and Microsoft’s UEFI DBX URLs, and closes multiple local/MITM security vulnerabilities.
- Mozilla’s
1-855-25-FIREFOXHotline Crashes Microsoft Ignite: While Microsoft hosted Ignite 2026 in San Francisco, Mozilla stationed its fox mascot Kit and personal-injury-lawyer-style billboards outside Moscone Center, inviting frustrated Windows users to call 1-855-25-FIREFOX. Citing its Over The Edge 2.0 research, Mozilla points out that outside the European Economic Area—where the Digital Markets Act forced cleaner behavior—Windows Search, Widgets, PDF defaults, Windows Backup, and Copilot still steer users back toward Microsoft Edge regardless of their chosen default browser. - Impossible OS Wants Native Win32 Without Linux—by 2028: Solo South African developer Derick Payne (Rizonesoft) unveiled Impossible OS, an open-source, from-scratch 64-bit x86-64 operating system written in C and assembly. Currently in pre-alpha (over 1.44 million lines of code), it aims for a Windows 11-inspired desktop, native Win32 API execution without traditional emulation, and Linux ELF support, with an ambitious first public alpha target of August 8, 2028. Treat it as a fascinating long-term kernel experiment rather than an imminent Windows replacement.
The Bottom Line for WindowsForum Readers
Whether it’s a developer coaxing Windows 11 ARM64 onto an un-jailbroken foldable phone through sheer JIT wizardry, Android 17 finally baking system-wide App Lock into core APIs, or NVIDIA’s board drawing a hard governance line while shipping a GeForce storage hotfix, this week proved one constant across consumer and enterprise tech: the boundaries between hardware, OS defaults, and corporate leadership are shifting fast. Keep your GeForce drivers updated to 621.35 if you were hit by the idle write bug, grab Rufus 4.16 for your troubleshooting toolkit, and take every dazzling social-media OS port—and boardroom comeback rumor—with a healthy dose of technical skepticism.
Correction (November 21, 2026): The GeForce Hotfix Driver 621.35 release date was corrected from November 21 to November 20, 2026. NVIDIA released the hotfix on November 20, as confirmed by NVIDIA Customer Care and multiple outlets reporting that day.
References
- 7 Days: Native Android app lock, Windows 11 on iPhone Duo, Huang wants to return Neowin · 2026-11-21T20:44:01+00:00
- 9to5google.com 9to5google.com
- Nvidia says it doesn't plan to reappoint Jensen Huang as CEO | TechCrunch techcrunch.com