TWiT's listing gives the episode a second subtitle, "The Patch Parade Continues & FilmCraft vs. Clipchamp." It dates the episode November 11, 2026. Thurrott.com dated its post November 12. The difference is probably just separate publishing records or time zones. Windows Weekly records on Wednesdays, and TWiT's date matches that day.
The episode notes are mostly headlines. This guide checks the Windows items against Microsoft's own announcements and explains what they mean for Windows 11 users and IT admins.
What the episode covered
Here is how both show listings group the topics:
- Windows: Patch Tuesday, described as "minor improvements across 25H2/26H2 and 26H1," and five Insider builds released on a Friday with "just one notable feature change"
- Software: Clipchamp compared with FilmCraft, a new Discover feed in Microsoft Edge and Windows 11 Widgets, Opera passing 100 million desktop users, and Vivaldi's rebuilt tracker and ad blocker
- Hardware: Qualcomm's earnings and Thurrott's HP OmniBook Ultra 16 review, billed as "RTX Spark is here"
- AI and dev: Nvidia CEO Jensen Huang, productivity uses for Google Antigravity, Adobe's wider AI partnerships with Microsoft and Google, an AI-focused Linux distribution, .NET 11's release at .NET Conf 2026, and Discord rewriting its app in Rust
- Xbox and gaming: the Xbox Nano Controller, a faster Xbox app for Windows 11, mobile and cloud, AutoSR on AMD-based Copilot+ PCs and the ROG Xbox Ally handhelds, GTA VI preloading, EA's Ultima and Wing Commander remasters, and console sales
- Tips and picks: free ways to transfer music playlists between services and upscale old photo scans, plus "AI" as the app pick of the week, which Thurrott admits is not really an app
TWiT's promotional text mentions "1000+ vulnerabilities" in Patch Tuesday. That figure comes from the show's own blurb. The Microsoft sources available for this guide do not confirm it, so treat it as the show's description rather than an official count.
Section summary: This was a typical Windows Weekly episode, with servicing news first and then browsers, hardware, AI and Xbox. The parts most useful to Windows readers are the Insider builds and the Patch Tuesday version spread, covered below.
Five Insider builds, one notable feature
The notes say "five new builds on Friday, just one notable feature change." Both parts check out, but "five builds" needs some explaining.
Microsoft's Windows Insider blog post for November 6, 2026 lists these builds:
| Channel | Build | Version line |
|---|---|---|
| Beta | 26320.9876 (later 26320.9877) | 26H2 |
| Experimental | 26340.9882 | 26H2 |
| Beta (26H1) | 28020.3445 | 26H1 |
| Experimental (26H1) | 28120.3454 | 26H1 |
| Experimental (Future Platforms) | 29704.1000 | Future Platforms |
Beta gets build 26320.9876 and Experimental gets build 26340.9882, with additional builds for Beta 26H1 (28020.3445), Experimental 26H1 (28120.3454), and Experimental Future Platforms (29704.1000). On November 9, Microsoft updated the post to say the Beta build had moved to 26320.9877, with no extra payload for Insiders.
So these are not five big feature drops. They are the same week's updates spread across two channels and three version lines. As Winaero put it, the Beta build moves the Beta channel to Windows 11 version 26H2 through an enablement package, so the build-number increase alone brings no major changes.
The Future Platforms channel is also changing its schedule. The Experimental (Future Platforms) channel will start getting weekly synthetic cumulative update builds with no new features, used to test backend flighting and updating services. Microsoft says it will not publish release notes for these test builds and will list them in Flight Hub instead. If your Future Platforms machine starts updating more often, that is expected, and you are not missing new features.
The notable feature: type your PIN while Windows Hello scans
The headline change is in the Experimental channel. You no longer have to wait for Windows Hello to finish trying your face or fingerprint before you type your PIN.
According to ITdaily, signing in and unlocking behave more consistently in the new build, and the screen gives clearer instructions. Windows Latest tested it on a Lenovo laptop with an IR camera. After installing Build 26340.9882, its testers saw the lock screen says "Look at the camera or enter your PIN," and the PIN field is ready while the camera is still scanning.
There is one exception. After certain events, such as a restart, the PIN is required first, and biometrics work as usual afterward. Many Windows Hello setups already ask for the PIN after a reboot, so this does not weaken that check.
Eleven Forum's copy of the release notes also mentions an addition for IT admins. In Event Viewer > Windows Logs > Security, event 4628 records the Windows Hello methods a user has set up and which method they used to sign in (PIN, face, fingerprint, or no Windows Hello). If you want to know whether staff actually use the face-unlock cameras you paid for, this event will tell you.
To try it (test machines only):
- Open Settings > Windows Update > Windows Insider Program.
- Link your Microsoft account.
- Choose the Experimental channel.
- Check for updates and install Build 26340.9882 or later.
Windows Latest describes the same steps: go to Settings > Windows Update > Windows Insider Program, link your Microsoft account, choose the Experimental channel, and check for updates.
Getting the build does not guarantee the feature. Microsoft is rolling out the new sign-in gradually, so not every Insider in the Experimental channel gets it immediately. Microsoft has not yet announced when the feature will arrive in the regular version of Windows 11. If your lock screen hasn't changed after updating, you are most likely still waiting for the gradual rollout.
Section summary: The five-build headline is accurate but counts updates across channels and versions. The one feature that matters is the Windows Hello PIN change, which is Experimental-only, rolling out gradually and has no release date for regular Windows 11.
Why Patch Tuesday covered three Windows versions
The Patch Tuesday headline lists "25H2/26H2 and 26H1." That reflects how many versions Microsoft is currently servicing.
Microsoft announced the Windows 11 2026 Update, version 26H2, on September 29, 2026. It ships as an enablement package for eligible devices on versions 24H2 and 25H2. All three versions share a servicing branch, so moving to 26H2 is a small download and one restart, much like a monthly update. Version 26H1 is a separate build line, which is why it has its own Insider builds and gets its own mention in the notes.
Things to know if you manage Windows machines:
- Gradual rollout: Microsoft is releasing 26H2 in controlled stages and may block devices with known compatibility problems. Not seeing the update yet doesn't mean something is wrong.
- Enterprise deployment: 26H2 is available through Windows Autopatch and the Microsoft 365 admin center. Microsoft recommends deploying to a test group first to check apps and key workflows before going wider.
- Support clock resets: Installing 26H2 gives Home and Pro editions 24 months of support and Enterprise and Education editions 36 months.
- Early opt-in: Home users who want it sooner can turn on Get the latest updates as soon as they're available in Settings > Windows Update.
.NET 11: check your support dates
The episode's ".NET 11 arrives" item matters most to developers. Microsoft's .NET lifecycle page shows .NET 11 support starting November 10, 2026. The same page shows support for both .NET 8 and .NET 9 ending in November 2026, while .NET 10 is supported until November 2028.
If your apps still target .NET 8 or 9, plan the move now. The safest target is probably .NET 10 or .NET 11, depending on how often your team wants to upgrade. This is our reading of Microsoft's published dates, not something stated on the show.
Xbox, AutoSR and console sales
For PC gamers, two items stand out: the redesigned Xbox app for Windows 11, mobile and cloud, and AutoSR coming to AMD-based Copilot+ PCs and ROG Xbox Ally handhelds. TWiT's linked coverage says the new Xbox app for PC launches up to 60% faster.
The episode notes don't give rollout dates, supported models or setup steps for AutoSR, so we won't guess at them. What we can say is that AutoSR is Microsoft's automatic upscaling feature, and it is now listed for AMD-based Copilot+ PCs and the ROG Xbox Ally handhelds.
On sales, both listings report 2.6 million PS5 units for Sony, now past 100 million in total. They also report 6.49 million units for Nintendo. TWiT's linked headline says those are Switch 2 units, while the episode notes just say "Switch."
Analysis: a busy week with little change for most users
Most of what Microsoft shipped this week is incremental. The Insider builds bring one feature, and Microsoft's own label for Patch Tuesday is "minor improvements." Even the 26H2 release is designed to install with little disruption. For most people, that is good news.
The episode's AI items push the other way. The notes link to Thurrott's RTX Spark review, titled "The Little Engine That Couldn't," and a post saying local AI does not rise to the challenge. They also point to an AI-focused Linux distribution pitching itself as a Windows replacement. Those are the hosts' opinions and are worth hearing as such. They are not benchmarks we have checked.
For Windows readers, the most practical items from this episode are:
- Patch your machines.
- Plan your 26H2 rollout with a test group first.
- Move .NET 8 and 9 apps before support ends.
- If you run an Insider test PC, try typing your PIN while Windows Hello is still scanning.
Related reading on WindowsForum.com
Readers who want more detail can browse the forum's coverage of Windows Hello and sign-in troubleshooting, the Windows 11 26H2 enablement package, Windows Autopatch, Insider channel changes after Microsoft's April 2026 overhaul, and .NET lifecycle planning.
Correction (November 12, 2026): An earlier version of this article said .NET 11 support started on November 9, 2026. Microsoft's .NET lifecycle page lists November 10, 2026 as the start of .NET 11 support, with .NET 8 and .NET 9 support ending the same day.