NexPhone Brings Windows 11 to a Pocket PC as Windows Stability Tests Persist

Microsoft’s ecosystem hit and curious pivot this week: a community-fueled revival of the Windows Phone concept via a third‑party device that can run Windows 11, while Microsoft’s flagship desktop OS continues to wrestle with a fresh wave of stability bugs affecting apps and core features. The juxtaposition — nostalgia and reinvention on one side, and a reminder of Windows’ complex update surface on the other — makes this installment of Microsoft Weekly a useful case study in where the platform stands in 2026.

Background​

Windows has been on a long arc since the mobile push of the early 2010s faded. Official Windows Phone work stopped years ago, but the idea of a true Pocket PC — a device that runs full Windows on a phone form factor — has persisted among enthusiasts. At the same time, Windows 11’s major updates (notably the 24H2 cycle and ongoing monthly updates) continue to introduce features while also exposing regressions that affect real users, from blue screens to app crashes and licensing/Store issues. The week’s coverage pulled together reports on both fronts: a hardware resurgence (the NexPhone family of devices) and new post‑update instability affecting Windows 11 users. Some of the claims come from investigative coverage and manufacturer announcements; others are confirmed by Microsoft’s own release‑health documentation and the evolving Insider channel rollouts.

---

The Windows Phone comeback — what’s actually happening​

A modern attempt at “Windows Phone” arrives in hardware form​

What’s being reported as “Windows Phone is back” is not Microsoft resurrecting the old platform, but rather an independent hardware effort to bring a full Windows experience to a smartphone‑style device. The most visible example is the NexPhone project, announced by Nex Computer/NexDock, which positions the device as a triple‑boot smartphone: Android, Linux, and Windows 11. Media coverage describes the device as a rugged, ARM‑based phone that can run Windows 11 in a mobile enclosure and also act as a pocketable PC when connected to external displays or lapdocks. This approach revives the spirit of Windows Phone — a touch‑first Windows experience on small screens — but relies on modern compatibility techniques and hybrid boot strategies rather than any legacy Windows Phone codebase.

Verified specifications and claims (what we can corroborate)​

Multiple outlets reporting on the NexPhone have published broadly consistent specifications and positioning details:

• Display: roughly a 6.5‑ to 6.6‑inch, 120 Hz panel on the flagship NexPhone models.
• SoC: Qualcomm QCM6490 (a chip used in modern ARM devices).
• Memory and storage: options around 12 GB RAM and 256 GB storage — expandable in some variants.
• Battery and ruggedization: large battery (reported ~5000 mAh), MIL‑STD‑810H claims, and IP68/IP69K water/dust resistance on certain SKUs.
• Boot/OS strategy: triple‑boot capability (Android 16, Debian‑style Linux, and Windows 11), plus a custom launcher/UX layer to make Windows feel more natural on a phone display.
• Pricing and availability claims: initial preorders reported with a $199 deposit and an MSRP example around $549, with expected shipping windows into 2026 in initial reporting. These price and shipping details originate from manufacturer announcements and early press briefings; they’re subject to change and should be treated as provisional until retail channels confirm them.

Because this is third‑party hardware attempting a complicated triple‑boot strategy on ARM silicon, several caveats apply: first‑party driver support for Windows on non‑standard phone hardware can vary, Windows on ARM still has gaps in driver and application parity, and the success of a desktop‑level experience in a phone will hinge on drivers, thermal constraints, and software adaptation.

---

Why this matters: the practical and symbolic significance​

• Symbolically, a device that runs Windows 11 on a phone form factor reopens a conversation about mobile productivity, continuity, and the portability of the Windows desktop. For enthusiasts and power users who want a true pocket PC, the concept is compelling.
• Practically, the NexPhone (and similar attempts) test whether Microsoft’s investments in Windows on ARM and the Windows Subsystem for Android can be leveraged by hardware partners to make a usable hybrid device.
• For enterprise and IT pros, the arrival of such devices raises questions about manageability, security updates, and corporate supportability — especially since these devices aren’t Microsoft‑branded and may not meet corporate procurement standards out of the box.

These implications make the NexPhone an important experiment: it’s not a return of Windows Phone in the brand/OS sense, but it revives the idea of a pocketable, full‑Windows device and tests the market’s appetite for it.

---

Windows 11: new bugs, acknowledged issues, and what’s changed​

The latest problem set: crashes, app errors and license validation headaches​

about Windows 11 focus on several emergent stability problems that are affecting users after recent updates. Coverage consolidated multiple, independently reported issues:

• A bug impacting a range of apps (including some built‑ins) that can lead to crashes or error code 0x803f8001, tied to Microsoft Store license validation or account/Store sync anomalies.
• Problems when apps access cloud‑backed storage (OneDrive, Dropbox) after certain updates, with Outlook’s PST handling singled out as particularly affected.
• Ongoing compatibility holds and blue‑screen scenarios previously tied to third‑party drivers (the Voicemeeter audio driver being a notable example), which Microsoft documented and addressed through safeguard holds and recommended driver updates.

Two points are crucial: Microsoft has publicly acknowledged several of the severe compatibility issues and applied safeguards to block the 24H2 feature update on affected devices; and some of the January 2026 problems are being investigated by Microsoft while provisional workarounds — such as resetting the Microsoft Store cache, reinstalling apps, or rolling back a specific update — are circulating among affected users and IT administrators.

Microsoft’s Voicemeeter safeguard: a useful blueprint​

The Voicemeeter case is instructive because Microsoft documented it on the Windows release‑health pages. Systems with Voicemeeter installed were blocked from rede due to a MEMORY_MANAGEMENT stop error tied to a Voicemeeter driver incompatibility. Microsoft’s guidance was straightforward:

• Update to the latest Voicemeeter version (which includes a fixed driver).
• If the device still shows the compatibility hold after updating drivers, contact the vendor (VB‑Audio) for more information.
• Do not manually bypass the safeguard unless you understand the risk and have tested in a non‑production environment.

This sequence — vendor driver fix, Microsoft safeguard, and gradual removal of the update hold once the vendor’s fix is in place — is the standard approach Microsoft has used for severe compatibility problems for several years. It’s slow and cautious by design, but that conservatism can be protective for enterprise fleets.

---

Cross‑checking the facts: what independent sources say​

• NexPhone / Windows‑on‑phone claims: Windows Central and Tom’s Hardware independently reported the NexPhone announcement and published largely consistent specs and pricing signals about the device’s triple‑boot approach and hardware choices. These independent reports corroborate the essential claim that hobbyist/third‑party devices are attempting to bring Windows 11 back to a phone form factor.
• Voicemeeter blue‑screen and safeguard hold: Microsoft’s own release health page documents the Voicemeeter memory management fault and the safeguard ID applied to affected devices; Neowin and other outlets picked up Microsoft’s owndvisory and relayed the same mitigation steps. That gives us both primary (Microsoft) and secondary (news) confirmation for this widely experienced issue.
• January 2026 app crash/Store license issues: TechRadar and other reporting outlets described a pair of newly surfaced bugs causing app crashes and cloud‑storage access freezes. Microsoft’s ongoing acknowledgement of related problems (and recommended mitigations for affected users) appears where relevant in the Windows support channels; however, a full root‑cause and patch schedule was not universally available at the time of reporting. That gap is reflected across outlets covering the story.

Where possible, the article material has been validated against at least two independent sources; primary documentation from Microsoft is used for confirmed issues and vendor/dev reporting is used to corroborate hardware claims.

---

Strengths and opportunities​

• Innovation from the ecosystem: Third‑party hardware like the NexPhone demonstrates creativity outside Microsoft’s captive device strategy. It shows there’s still interest in the concept of a pocket PC, and it can push Microsoft and partners to refine Windows on ARM and convergence scenarios.
• Improved transparency around safeguard holds: Microsoft’s use of documented safeguard IDs, KB notices, and public release‑health pages makes it easier for administrators to audit which devices and scenarios are blocked and why. This transparency is valuable for enterprise change management.
• Windows 11 feature depth: The ongoing development of Windows 11 continues to push functionality (improved File Explorer, Jump Lists refinements, Copilot+ features for eligible devices), which keep the platform competitive and adaptable to new workflows. These user‑facing improvements matter to productivity users who invest in the OS.

---

Risks, unknowns, and areas to watch​

• Driver and hardware fragility on non‑standard devices: Running Windows 11 on phone hardware will always risk driver gaps, thermal and battery management issues, and incompatible peripherals — especially for niche ARM device builds. Those risks can make the user experience uneven and pose support challenges for businesses.
• Update volatility: The continued surfacing of significant bugs following large updates underscores the tension between rapid feature delivery and robust QA. Enterprises and cautious consumers should assume that major updates can introduce regressions and plan deployments accordingly.
• Store and licensing fragility: License validation issues that manifest as app crashes (0x803f8001 and related errors) reveal how tightly interwoven the Microsoft Store, account sync, and OS updates are; a problem in one subsystem can cascade. That is a structural risk for users who rely on Store‑delivered apps for business workflows.
• Unverified commercial claims: Manufacturer MSRP, shipping dates, and deposit structures reported in early press coverage should be treated as provisional. Preorder terms often change between announcement and retail launch; until retail availability is confirmed, these are best‑effort indicators rather than fixed commitments.

---

Practical guidance for Windows users and IT teams​

• Before installing major feature updates (like 24H2 or new cumulative updates), create a full system restore point and validate backups.
• Check Microsoft’s release‑health pages and safeguard notices for known holds relevant to your hardware and installed software; these notices are the definitive guidance for high‑risk compatibility scenarios.
• If you run third‑party drivers (audio mixers like Voicemeeter, virtualization tools, or niche hardware), confirm vendor driver versions are certified or updated before attempting big OS upgrades.
• For unexpected app crashes after updates:
• Try Store cache reset and sign‑out/sign‑in of the Microsoft Store.
• Reinstall affected apps and verify license/account sync.
• If necessary, escalate to removing a specific update temporarily (with appropriate security considerations) while awaiting a fix.
• For organizations evaluating novel Windows‑on‑phone devices: treat them as pilot projects. Run dedicated testing workflows, confirm management tool compatibility, and avoid large‑scale rollouts until driver and MDM support are firmly in place.

---

What this means for Windows’ direction​

The dual narratives of the week — a hardware attempt to revive the pocket Windows concept, and renewed evidence that large platform updates can still produce disruptive regressions — are not contradictory. They highlight two truths about the Windows ecosystem:

• The platform remains fertile for experimentation. Interest in a Windows pocket PC proves that there’s still demand for converged device form factors and for Windows’ productivity model to be portable.
• The platform’s complexity is its own friction. As Windows stretches to support more hardware states, more cloud integrations, and more app distribution mechanisms, the surface area for regressions grows. Managing that complexity requires continued investment in testing, vendor coordination, and conservative rollout mechanisms.

If Microsoft and hardware partners can tighten driver certification, improve Store/account resilience, and keep a predictable cadence for fixes, the benefits of experimentation will outstrip the risks. Until then, cautious optimism — validated by staged pilots and careful update policies — is the prudent path.

---

Conclusion​

This week’s headlines are a reminder that Windows is a living platform: enthusiasts and hardware innovators are still pushing its boundaries, while enterprise and everyday users contend with the realities of an OS that must balance progress and stability. The NexPhone and similar devices reignite a familiar dream — Windows on the go — but their success depends on solid driver stacks and practical management strategies. Meanwhile, Microsoft’s public safety mechanisms (safeguard holds, published resolved‑issue guidance) and the community’s quick‑fix workarounds provide tools to survive rocky updates.
For users: back up, validate drivers, and treat major feature updates as planned events rather than automatic installs. For developers and hardware makers: prioritize driver testing and MDM compatibility. And for Microsoft: the challenge remains to deliver ambitious features while preserving the reliability that long‑time Windows users expect.
The next chapters will show whether pocket‑sized Windows devices become a useful niche or remain a hobbyist curiosity — and whether Microsoft’s update cadence can match the platform’s growing ambitions without putting stability at risk.

---

Source: Neowin https://www.neowin.net/news/microsoft-weekly-windows-phone-is-back-new-windows-11-bugs-and-more/

 

[ChatGPT]

Microsoft’s ecosystem produced one of those weeks that reads like a study in contrasts: an enthusiast‑led push to squeeze full Windows into a pocketable phone landed headlines, while Windows 11 itself continued to show brittle behavior after recent updates — including app crashes, cloud-storage freezes, and even cases where the rollback process fails entirely. The net effect is equal parts nostalgia and concern: a new “Windows Phone” concept arrives in hardware form, testing the limits of Windows on ARM, while administrators and everyday users wrestle with high‑impact regressions from the January cumulative changes. ]

---

Background​

For enthusiasts, the idea of a true pocket PC — a handheld that runs full Windows rather than a mobile‑first OS — never truly died. Official work on Windows Phone ended years ago, but the technical foundations Microsoft has built for Windows on ARM and cross‑platform compatibility (including the Windows Subsystem for Android) left room for third‑party experiments that attempt to revive the concept in new ways. At the same time, Microsoft’s update model — with monthly cumulative updates and larger feature releases such as 24H2 — has become a double‑edged sword: faster feature delivery due for regressions to appear in diverse real‑world configurations.
Two stories dominated coverage this week: the arrival of the NexPhone — a third‑party device marketed as a pocketable Windows 11 machine that can also run Android and Linux — and a spate of stability problems tied to the January 2026 cumulative update (KB5074109) and related release‑health items. Both stories are tightly coupled to long‑running themes for Windows users: the promise of portability and the need for robust, enterprise‑grade update telemetry and rollback mechanisms.

---

The NexPhone: “Windows Phone” Returns — But Not as You Remember​

What the NexPhone claims to be​

The NexPhone — publicized as a product from an enthusiast hardware house and covered widely by tech outlets — is positioned as a rugged, ARM‑based smartphone that offers a triple‑boot setup: Android (for mainstream mobile use), a Linux distribution (for hobbyist and server‑style tasks), and Windows 11 (for full‑desktop productivity when you need it). Reported flagship specs include a 6.5–6.6‑inch 120Hz display, Qualcomm QCM6490 SoC, up to 12 GB RAM, 256 GB storage, a ~5000 mAh battery, MIL‑STD ruggedization claims and IP68/IP69K ingress protection, plus a price target in the mid‑hundreds with preorder deposits. The vendor frames the device as both a standalone phone and a pocketable PC when docked to an external display or lapdock.
Those elements — on paper — are compelling: a single device that can switch between mobile and full Windows workflows is a vivid realization of the “pocket PC” dream. For fans of continuity and for certain classes of professionals (field engineers, journalists, or anyone who needs a full Windows toolchain on the go), the NexPhone’s promise resonates.

What’s verifiable today — and what isn’t​

Some details are straightforward to corroborate: multiple independent outlets reporting on the NexPhone published consistent specs and the vendor’s own marketing material matches those figures. That gives us reasonable confidence about the device’s headline specs and the triple‑boot concept.
However, several practical caveats must be emphasized as provisional:

• Driver completeness and stability for Windows on custom phone hardware are not guaranteed. Windows on ARM still depends on driver support for device‑specific radios, sensors, modem stacks, and camera pipelines; many of these components are deeply platform‑specific and historically challenging outside of supply‑chain partners. The claim that Windows 11 will deliver a smooth, phone‑style experience depends on vendor drivers and software adaptation.
• Battery life and thermals will be decisive. Delivering a desktop‑class experience on a phone requires careful throttling and battery sizes look promising, but real‑world Windows workloads (background services, emulation layers, and x86 translation on ARM) can significantly affect run times.
• App compatibility and performance: While Windows on ARM has improved, not every legacy desktop application runs identically; performance of emulated x86 apps, printing stacks, and certain kernel‑mode drivers remains variable.
• Availability and pricing: Early pricing and shipping windows reported in press briefings are frequently adjusted before retail launch. Preorder deposits and MSRP claims should be treated as manufacturer guidance, not final retail reality.

In short: the NexPhone revives the idea of Windows on a phone, but whether it delivers the experience most users expect will depend on driver maturity, software adaptation, and honest reporting from reviewers after extended, real‑world testing.

Why the NexPhone matters (even if it’s niche)​

• It tests whether Windows on ARM is mature enough to meaningfully expand beyond laptops and tablets.
• It pressures Microsoft and partners to continue investing in driver and subsystem parity.
• It shows an ongoing market for a pocketable Windows experience among enthusiasts and specialized workflows.
• Even if the NexPhone remains niche, successful engineering lessons could trickle up into mainstream ARM PCs and Surface devices.

---

Windows 11’s recent stability problems: symptoms, scope, and root causes​

The KB5074109 incident and rollback failures​

January’s cumulative update, KB5074109, became a lightning rod because it introduced several high‑impact regressions for some users: app crashes, issues with sleep/hibernate and shutdown, and application freezes when interacting with cloud‑backed storage. In many reported cases, Microsoft advised affected users to uninstall the update while it worked on fixes — but for a subset of machines, the uninstall itself failed with a servicing error (0x800f0905), leaving users in a difficult state where the buggy update could not be cleanly removed.
Why uninstall failed in some environments: the Windows servicing stack relies on multiple moving parts — servicing stack updates (SSU), the component store, and package manifests. When those plumbing components are inconsistent, corrupted, or when an SSU and LCU are packaged together in ways that the GUI uninstall path cannot handle, an attempt to roll back the LCU can produce a 0x800f0905 servicing error. Remedies suggested by experienced administrators include System Restore (if available), running the Windows Update repair / “Fix problems with Windows Update” flow, DISM‑based package removals and in‑place repair (repair install) — all of which carry trade‑offs and often require full backups before execution.

App crashes and the Store license validation error (0x803F8001)​

A parallel set of reports described multiple built‑in and Store‑dependent apps failing with error code 0x803f8001 or related messages indicating license validation failures. The behavior affected apps as varied as Notepad, Snipping Tool, and third‑party utilities that rely on Store entitlements or Store‑integrated services. Troubleshooting steps that helped some users included resetting the Microsoft Store cache (wsreset), signing out and back into the Store, or reinstalling affected apps; but the pattern suggested a broader licensing validation or Store backend glitch in addition to local cache corruption.
There were also reports of apps freezing when interacting with cloud storage backends (OneDrive, Dropbox), with Classic Outlook particularly impacted when PST files lived inside OneDrive folders. Microsoft’s guidance in several cases was pragmatic — move PST files out of cloud‑synced folders, apply vendor recommendations, and wait for a fixed cumulative update — but those are stopgaps rather than systemic fixes.

The Voicemeeter exemplar: how Microsoft uses safeguard holds​

A useful historical example of Microsoft’s cautious update posture is the Voicemeeter blue‑screen issue that surfaced during 24H2 testing. Microsoft applied a safeguard hold to devices running incompatible Voicemeeter drivers to prevent the feature update from being offered to those devices until a driver update arrived. That approach — vendor driver fix, Microsoft safeguardl of the hold — illustrates the way Microsoft balances rollout speed and stability, but it also highlights the limits of a binary rollout control when unpredictable interactions appear in the field. The Voicemeeter case is documented directly in Microsoft’s release‑health pages.

---

What Microsoft and vendors have done — and what they haven’t​

• Microsoft has acknowledged multiple regressions and applied targeted mitigations (including safeguard holds and out‑of‑band fixes in some cases). For KB5074109, the guidance has oscillated between advising uninstall where possible and issuing targeted patches.
• Vendors with driver faults (Voicemeeter, Easy Anti‑Cheat, etc.) have supplied driver updates in many instances, enabling Microsoft to lift safeguard holds for updated devices. But driver rollout relies on vendors and publisher cooperation — and that time lag is where users get exposed to risk.
• For the 0x803f8001 Store license issue, Microsoft’s immediate mitigations were standard support actions: Store cache reset, sign‑out/sign‑in, and reinstalling apps. These steps resolve local cache or identity synchronization issues in many cases, but they are not a substitute for backend fixes when a service outage or server‑side validation bug is involved.

---

Risks, implications, and what this means for users and organizations​

Consumer and enthusiast risks​

• Pausing updates or delaying major feature upgrades reduces exposure to regressions, but it also leaves systems vulnerable to security issues fixed in those updates.
• For enthusiasts chasing bleeding‑edge hardware like the NexPhone, device longevity hinges on vendor support for drivers and thermal firmware — elements that are often thin at launch for niche products.

Enterprise and IT risks​

• The KB5074109 uninstall failures underline a critical operational risk: when an LCU rollback is blocked by servicing errors, organizations may be forced into disruptive repair sequences (in‑place repair, image restores, or system reimaging).
• Managed fleets should expand pilot testing to include cloud‑sync scenarios, legacy productivity apps (Outlook with PSTs in OneDrive), and less common driver combinations (audio tools, virtualization, and anti‑cheat drivers). This broad testing matrix is often the difference between a smooth rollout and a cascade of help‑desk incidents.

Platform and vendor implications​

• Microsoft’s update model is structurally sound but operationally complex; the company must continue refining telemetry and real‑world telemetry ingestion to detect regressions earlier and to target safeguards more precisely.
• Third‑party hardware ventures like the NexPhone signal continued interest in Windows on ARM, which could accelerate OEM investment — but only if the driver and app ecosystems deliver predictable behavior. Early hardware successes can catalyze broader adoption; repeated high‑impact regressions can stall momentum.

---

Practical guidance: what to do right now​

For home users (step‑by‑step)​

1. Create a full image backup before attempting any uninstall or major repair. Always assume rollback can fail.
2. If you see error 0x803f8001 for multiple apps, try:
   • Reset the Microsoft Store cache with wsreset.exe.
   • Sign out of the Microsoft Store and sign back in.
   • Reinstall the affected Store apps.
3. For Outlook issues tied to PST storage, move PST files out of OneDrive or other cloud‑synced folders and use local storage or supported Archive configurations until a patch is available.
4. If KB5074109 is causing major system-level issues and the Settings → Update rollback fails with 0x800f0905:
   • Check for a System Restore point and consider restoring to a point before the update.
   • If System Restore is unavailable, consider the Windows “Fix problems with Windows Update” repair flow or an in‑place repair install that preserves apps and data. Prepare for downtime and backups.

For IT administrators and operators​

• Expand pilot testing matrices to include:
  • Cloud‑synced data workflows (OneDrive, Dropbox) and legacy applications (Outlook PSTs).
  • Niche audio and anti‑cheat drivers (Voicemeeter, Easy Anti‑Cheat).
  • Printing stacks and device‑specific drivers on ARM platforms.
• Maintain an up‑to‑date inventory of devices that may be subject to safeguard holds and use Windows Update for Business reporting to identify blocked devices.
• If a rollback is required but 0x800f0905 blocks it, collect CBS and DISM logs, engage Microsoft Support early, and consider DISM /Remove‑Package only after careful analysis and backups.

---

Strengths, weaknesses, and how to read the signals​

Notable strengths​

• Microsoft’s use of safeguard holds, while conservative, prevents many bad upgrades from being broadly distributed — the Voicemeeter case is a clear example of this approach working as intended.
• The NexPhone effort showcases the modularity of the modern PC stack: with Windows on ARM, vendor initiative can produce novel form factors and hybrid experiences that were impossible a decade ago.

Principal weaknesses and risks​

• Servicing complexity: when an update includes combined components (SSU + LCU), the uninstall path can be fragile, and servicing stack errors such as 0x800f0905 reveal operational fragility in real‑world contexts.
• Cross‑component regressions: the interplay between cloud storage sync, application logic (Outlook), and cumulative updates creates non‑obvious failure modes that are hard to catch in lab environments.
• Third‑party driver dependency: projects like NexPhone heighten reliance on vendor drivers — a risk when vendors are small teams or community projects without enterprise‑grade testing pipelines.

What to watch next​

• Microsoft’s official release‑health updates and any out‑of‑band patches addressing KB5074109 and the 0x803f8001 licensing issues. Expect clarifications from Microsoft as they roll fixes and remove or update safeguard holds.
• Independent long‑term reviews of any NexPhone shipping units that detail driver parity, thermals, and day‑to‑day Windows on ARM performance under mixed workloads. Those reviews will determine whether the NexPhone is a novelty or a practical pocket PC.

---

Conclusion​

This week’s headlines are an instructive microcosm of the Windows world in 2026: inventive hardware experiments push the ecosystem forward, but platform complexity and a sprawling update surface continue to produce sharp trade‑offs between speed and stability. The NexPhone’s promise to put Windows 11 into a pocketable handset is a vivid reminder that the platform’s architectural flexibility unlocks new device categories — but it also depends on mature drivers and software adaptation that are rarely instant.
Meanwhile, the KB5074109 and Store‑license incidents reinforce a perennial operational truth: updates are only as good as the rollback and mitigation paths available when they misbehave. For users and IT teams the immediate priorities are concrete and pragmatic: back up system images, expand pilot testing to include cloud‑backed workflows and niche drivers, and apply vendor guidance conservatively. For Microsoft and hardware vendors, the path forward is clear as well: invest in richer, earlier field telemetry and deeper vendor partnerships so the next big innovation — whether a pocket‑sized Windows PC or a broadly adopted ARM laptop — arrives with fewer regressions and safer update paths.

---

Source: Neowin https://www.neowin.net/amp/microsoft-weekly-windows-phone-is-back-new-windows-11-bugs-and-more/