Windows 10 Ends Mainstream Support as Windows 11 Expands Copilot AI

Microsoft’s mid‑October push makes the moment unmistakable: as free mainstream security support for Windows 10 ends, Microsoft is simultaneously widening Windows 11’s lead with a major set of AI features built around Copilot — voice activation (“Hey, Copilot”), expanded on‑screen intelligence (Copilot Vision), experimental agentic workflows (Copilot Actions) and a new Copilot+ hardware tier that ties the highest‑performance experiences to neural processing units (NPUs).

Background / Overview​

Microsoft set a hard calendar date for Windows 10’s lifecycle: October 14, 2025 is the end of mainstream support for consumer editions. After that date Microsoft no longer issues free security updates, quality fixes, or routine technical assistance for most Windows 10 Home and Pro devices — though the machines will continue to boot and operate. Microsoft’s lifecycle and support pages make this explicit and explain the remediation routes: upgrade to Windows 11 where possible, enroll in the consumer Extended Security Updates (ESU) program for a short bridge, or replace the hardware.
Microsoft’s consumer ESU program is time‑boxed: ESU enrollment for eligible Windows 10 devices provides security‑only patches through October 13, 2026. Enrollment paths include signing in with a Microsoft account (a free route for many users), or a one‑time paid option for devices that remain local‑accounted. The ESU is presented as a temporary bridge, not a long‑term policy.
At the same moment Microsoft is accelerating Windows 11’s AI integration. The company positions this not as a small feature update but as a shift in how people will interact with PCs: voice becomes a first‑class input, the OS can “see” selected screen content to offer context, and limited agentic actions can carry out multi‑step tasks with user authorization. That commercial and product timing creates a migration pressure point: upgrade, pay for temporary ESU, or keep running an unsupported OS — each with tangible costs.

---

What Microsoft announced (feature rundown)​

Hey, Copilot — voice as a core input​

Microsoft has rolled out an opt‑in wake‑word capability that lets users summon Copilot by saying “Hey, Copilot” when a PC is unlocked. Wake‑word detection uses a small on‑device model (an on‑device audio buffer) to spot the phrase; full transcription and reasoning occur in the cloud after the wake is confirmed. Microsoft emphasizes the feature is off by default and requires explicit enabling in Copilot settings. The rollout started in Insiders and is expanding to general channels.
Key points:

• Wake‑word detection is local; a short audio buffer exists only temporarily in memory.
• Copilot sessions send audio to the cloud for processing after wake detection.
• The feature requires the PC to be powered and unlocked to respond.

Copilot Vision — permissioned on‑screen intelligence​

Copilot Vision lets the assistant analyze selected windows or app content when users grant permission. The capability performs OCR, extracts tables or text, identifies UI elements, and can provide contextual help — for example, explaining a dialog box, summarizing a document section or helping with a web form. Microsoft positions Vision as session‑bound and permissioned, not as continuous surveillance.

Copilot Actions — constrained agents​

Microsoft introduced an experimental agent layer — Copilot Actions — which can carry out multi‑step, real‑world tasks with explicit user authorization. Demonstrations show Actions orchestrating things like reservations or form filling via controlled connectors. Microsoft says Actions are off by default, operate with least privilege and require visible approvals for critical steps. Reporters and Microsoft both stress that guardrails are central to the feature’s design while the company refines permissions.

App‑level and system integrations​

Windows built‑in apps such as Notepad, Paint and Photos are receiving AI enhancements (quick drafting, object selection, relight and erase tools). File Explorer and right‑click menus (Click‑to‑Do) are surfacing conversational helpers and AI actions for files, while gaming is getting a dedicated Gaming Copilot for in‑game assistance. Some capabilities are tied to Microsoft 365/Copilot entitlements.

Copilot+ PCs and on‑device acceleration​

Microsoft and OEMs are promoting a Copilot+ device class: laptops and desktops with neural acceleration (NPUs) able to run latency‑sensitive AI workloads locally. Microsoft argues this improves responsiveness and privacy for on‑device features, while also creating a hardware differentiation that may limit advanced experiences to newer machines. The hardware/entitlement gating is strategic — it improves performance but raises concerns about fragmentation and upgrade costs.

---

Security, migration and the ESU trade‑offs​

Windows 10 end of mainstream support changes the threat calculus. Without vendor patches, new kernel and platform vulnerabilities can remain unpatched, increasing the risk that attackers will exploit aging endpoints. Microsoft’s recommended options are straightforward: upgrade to Windows 11, enroll in ESU while you plan a migration, or move to an alternative OS such as Linux or ChromeOS Flex for older hardware.
Consumer ESU mechanics matter:

• Free ESU routes exist if eligible devices remain signed in with a Microsoft account and meet enrollment conditions.
• A paid one‑time ESU purchase is available for local account users who need a temporary lifeline.
• ESU delivers security‑critical updates only; it does not include feature updates or regular product support.

For many users, the decision will hinge on hardware compatibility. Windows 11’s minimum requirements remain stricter (TPM 2.0, Secure Boot, supported CPU list), which leaves a substantial installed base of older PCs unable to take the free upgrade path. That reality is why Microsoft and independent vendors emphasize trade‑in, recycling and alternative OS options.

---

Privacy, data residency and the “always‑listening” debate​

Microsoft’s documentation makes a technical claim meant to reassure users: wake‑word detection runs locally and the 10‑second audio buffer used for detection is not stored persistently. Nevertheless, once Copilot is active the audio and context are processed in the cloud to produce responses, which raises legitimate privacy questions — especially in shared, sensitive or regulated environments. Copilot Vision and Actions similarly require permission but surface new vectors where screen content, app context and uploaded snippets may be transmitted to cloud models for analysis.
Privacy and governance considerations:

• Auditability: enterprises must log Copilot activity and agent approvals to maintain accountability.
• Consent and visibility: in shared spaces, audible responses from Copilot could expose private queries to bystanders.
• Data retention: conversation histories and transcripts can persist unless users or admins delete them; retention settings must be explicit.
• Regulatory risk: organizations handling sensitive data must evaluate Copilot features against local compliance regimes and data residency rules.

Put bluntly: Microsoft documents precautions, but the real test will come from independent audits, enterprise policy controls and concrete administrative tooling that enforces least privilege at scale.

---

Environmental and consumer‑protection concerns​

The end of Windows 10 support surfaces a durability vs. disposal dilemma. Consumer advocates and right‑to‑repair groups warned that many users will either continue using unsupported devices (accepting risk) or replace them prematurely, which drives e‑waste and creates environmental harm. Groups such as PIRG have publicly argued that the choices facing tens or hundreds of millions of Windows 10 device owners are stark: run insecure systems, pay for temporary ESU, or discard working hardware. That tension has been widely reported and discussed.
Practical mitigation steps that consumer groups and Microsoft both promote include:

• Use trade‑in and manufacturer recycling programs rather than landfilling old PCs.
• Consider alternative OSes (e.g., Linux distributions or ChromeOS Flex) to extend device life where security policies allow.
• Explore certified refurbished devices if replacement is necessary.

Still, environmental advocates note that a large, rapid refresh cycle has a real carbon and toxic‑waste footprint. The policy implications intersect with right‑to‑repair debates, regulatory scrutiny and procurement choices for public institutions.

---

Enterprise impact and procurement risks​

For IT leaders the October 2025 milestones create several simultaneous project pressures: patch and inventory unmanaged Windows 10 endpoints, decide ESU enrollment for holdouts, pilot Windows 11 upgrades, and evaluate whether Copilot features are appropriate for managed fleets. At the same time, Microsoft’s Copilot+ hardware tier and licensing models complicate procurement.
Key enterprise questions:

• Which endpoints qualify for a safe, supported Windows 11 upgrade path?
• Do organizational policies permit Copilot voice/vision or agentic automation in production environments?
• Are the benefits of on‑device NPUs worth the capital expense and re‑procurement cycle?
• How will management tooling (MDM, logging, SIEM) incorporate Copilot actions and their approval flows?

Microsoft and partners will supply migration tools and device inventories, but large fleets should treat Copilot features as controlled pilots. The recommended approach is to inventory, pilot, measure and then scale — not to flip wide permissions on day one.

---

Technical verification and reality check​

Marketing claims about “on‑device” privacy or seamless local inference deserve independent validation. Two technical realities matter:

• Many advanced Copilot features still depend on cloud LLMs for reasoning even when a local wake‑word or NPU‑accelerated preprocessing is used.
• On‑device acceleration reduces latency but does not eliminate data flows to the cloud when large models are required or for features that call external connectors.

Independent benchmarking of NPU throughput (TOPS), energy usage, inference latency and real‑world user scenarios will be crucial to separate marketing from measurable utility. Enterprises should insist on third‑party benchmarks before committing to widespread Copilot+ refresh programs.

---

What users should do now — practical checklist​

• Inventory: Identify which machines are still running Windows 10 and classify by role (user, kiosk, lab, server) and hardware compatibility with Windows 11.
• Patch and protect: If remaining on Windows 10 temporarily, enroll in ESU where appropriate and maintain layered defenses (EPP, network segmentation, vulnerability scanning).
• Evaluate alternatives: For incompatible hardware, test Linux distributions or ChromeOS Flex as cost‑effective, security‑minded alternatives.
• Pilot Copilot: Trial Copilot features in controlled environments to measure productivity gain and privacy impact before broad enablement.
• Recycle responsibly: Use manufacturer or certified recyclers for decommissioned devices to reduce e‑waste.
• Policy and logging: For enterprises, create clear governance for Copilot voice/vision and Actions; require approval workflows and full logging.

---

Strengths: what Microsoft gets right​

• Accessibility and convenience: Making voice a robust, opt‑in input and allowing on‑screen context can materially speed workflows for many users, including those with mobility impairments.
• Product continuity: Integrating Copilot across apps and the OS reduces friction for users already invested in Microsoft 365 and Edge.
• Hardware acceleration: NPUs genuinely reduce latency for local models, improving perceived responsiveness for many AI features on modern devices.

---

Risks and open issues​

• Privacy and data flows: Local wake‑word spotting is only part of the story; full processing often happens in the cloud. Organizations must evaluate whether that transmission fits their compliance model.
• Fragmentation and equity: Hardware and licensing gates create a two‑tier Windows experience: Copilot+ users enjoy faster, private on‑device AI while others get reduced capabilities. That can exacerbate digital inequities.
• Environmental impact: A surge in premature hardware replacement risks increased e‑waste; consumer and policy responses will shape whether the migration is sustainable.
• Vendor lock‑in: Deeper Copilot integrations tie workflow value to Microsoft services and entitlements, raising questions about future switching costs.
• Security of agentic features: Copilot Actions introduce new attack surfaces; least‑privilege design and transparent auditing are essential before broad deployment.

---

Verdict: pragmatic optimism with guardrails​

Microsoft’s AI investments for Windows 11 are ambitious and will produce real, immediate utility for users on modern hardware. Voice activation, contextual on‑screen help and constrained agents can improve accessibility and reduce friction for common tasks. But the timing — coincident with Windows 10’s end of mainstream support — amplifies nontechnical costs: financial pressure to replace or repair hardware, environmental consequences, and a governance burden for privacy and security.
The sensible path is pragmatic: treat ESU as a temporary bridge, pilot Copilot features with robust logging and consent controls, demand independent NPU and privacy audits, and prioritize recycling or alternative OS strategies for devices that cannot upgrade. Organizations and consumers that follow those steps will capture genuine productivity benefits while limiting the downsides.

---

Final takeaway​

October’s twin headlines — Windows 10 end of mainstream support and Windows 11’s Copilot expansion — are linked by strategy and consequence. Microsoft is concentrating its innovation on Windows 11 and making AI a foundational interaction model. That shift brings useful capabilities but also hard trade‑offs: security timelines, privacy engineering, hardware economics and environmental cost. The next year will be decisive: how quickly organizations pilot, govern and validate Copilot features will determine whether the move to an AI‑first Windows is a genuine productivity upgrade or a costly fragmentation that favors the newest, most expensive devices.

---

Source: Qatar Tribune Microsoft pushes AI updates in Windows 11 as it ends support for Windows 10

 

[ChatGPT]

Microsoft’s mid‑October moves changed the Windows landscape in one week: Windows 10’s free mainstream support ended, Microsoft opened a one‑year consumer Extended Security Updates (ESU) bridge while simultaneously accelerating Windows 11’s Copilot‑first vision — including the public awaken‑word “Hey, Copilot” and Copilot Vision — even as October cumulative updates introduced a serious WinRE regression that can leave recovery menus inaccessible on affected machines.

Background​

Microsoft’s lifecycle calendar reached a hard milestone on October 14, 2025: mainstream servicing for the consumer and most commercial SKUs of Windows 10 officially ended. That means routine security rollups, feature updates, and standard technical assistance for those editions are no longer delivered unless a device is enrolled in an extension program. Microsoft published a consumer Extended Security Updates (ESU) option that provides security‑only updates through October 13, 2026 for eligible Windows 10 systems running version 22H2; ESU is explicitly limited to Critical and Important security fixes and does not restore feature updates or standard Microsoft support.
At the same time Microsoft is pushing Windows 11 as an AI PC platform: Copilot features that were once experimental are being folded into the OS at system level. The most visible new capabilities are the hands‑free wake‑word experience (“Hey, Copilot”), Copilot Vision (screen‑aware, permissioned multimodal assistance), and an early set of agentic automation features called Copilot Actions. Microsoft’s messaging ties some premium, low‑latency experiences to a new Copilot+ device class that pairs Windows 11 with on‑device neural hardware. Those product positioning and hardware claims are presented as vendor guidance and should be treated as such while administrators validate the details for their environments.
Across the same fortnight Microsoft shipped October cumulative updates for Windows 11 — and those updates carried some problematic side‑effects. A security rollup released on October 14, 2025 (commonly referenced as KB5066835 with build variants 26100.6899 and 26200.6899) and accompanying SafeOS/WinRE dynamic updates produced reports of a regression: USB keyboards and mice may not function inside the Windows Recovery Environment (WinRE), leaving users unable to navigate recovery tools. Microsoft has acknowledged the behavior on its Release Health dashboard and is investigating.

---

What ended, what remains: Windows 10 lifecycle and ESU​

The facts, precisely stated​

• Windows 10 mainstream support ended October 14, 2025. After that date, Microsoft no longer issues routine cumulative updates or general technical assistance for the affected SKUs.
• Microsoft offered a one‑year Consumer Extended Security Updates (ESU) path that covers security‑only patches through October 13, 2026 for qualifying Windows 10 (22H2) devices. ESU is time‑boxed and does not include feature updates.
• Microsoft will continue some ancillary protections (for example, some Defender components and intelligence updates may persist under different release cadences), but OS servicing and support are materially curtailed for unenrolled systems.

Practical, short‑term implications​

For home users the immediate risk is increased exposure if the machine remains internet‑connected and unpatched past the ESU window. For organizations, the decision is governance: upgrade, accept paid extended support, or isolate and harden the endpoint fleet. The consumer ESU is a short bridge and not a long‑term compliance solution for enterprise IT.

---

Windows 11’s AI push: Hey, Copilot, Vision, Actions​

What Microsoft shipped and how it works​

Microsoft announced that the voice wake‑word “Hey, Copilot” is publicly available, letting users invoke Copilot by voice and engage in a conversational session with the assistant. The implementation is designed as an opt‑in local wake‑word spotter that keeps only a short transient audio buffer until the user explicitly invokes the session; after invocation, richer speech processing and generative reasoning may happen in the cloud or locally when hardware supports on‑device inference. Visual and audible indicators show when Copilot is listening to reduce ambiguity.
Copilot Vision expands Copilot’s remit beyond text: it can analyze user‑selected windows or screen regions — with explicit user permission — to extract text (OCR), identify interface elements, summarize content, and provide contextual guidance. These interactions are session‑bound and require consent each time a new screen or region is shared.
Copilot Actions are experimental agent‑style capabilities that allow Copilot to carry out delegated, multi‑step tasks on behalf of the user (for example, triaging email and filing attachments, or orchestrating multi‑app workflows) while the user focuses elsewhere. Those workflows are permissioned and instrumented, but they raise governance questions about scope and auditability.

Hardware claims and the Copilot+ device class​

Microsoft and partner messaging identify Copilot+ PCs as systems equipped with dedicated Neural Processing Units (NPUs) able to accelerate on‑device models and lower latency for AI features; promotional guidance has referenced NPU throughput in the tens of TOPS as a differentiator for the “best” experience. These numbers describe vendor positioning and performance targets; IT teams should treat them as marketing guidance until validated against independent device benchmarks and Microsoft’s formal product documentation.

Strengths: why this is compelling​

• Natural interaction: Voice + vision moves Windows toward more natural, accessible input modes for complex tasks. The potential productivity gains are real when the assistant is accurate and responsive.
• Contextual help: Copilot Vision’s ability to understand current screen state can reduce friction for troubleshooting and content extraction.
• Local-first design: A local wake‑word spotter and on‑device processing (where available) reduce latency and can improve privacy posture compared with cloud‑only systems — if implemented correctly.

Risks and open questions​

• Privacy and telemetry: Even with opt‑in wake words and visual indicators, the workflows involve audio capture and, in some cases, screen imagery; organizations must validate what telemetry is retained, for how long, and where processing occurs. Independent audits and clear admin controls are essential.
• Security and access control: Agentic actions that can modify files, send messages, or access networked resources need robust permission surfaces and audit logs. IT must map those capabilities to least‑privilege controls.
• Hardware churn and environmental costs: Positioning Copilot as a tiered experience tied to NPU hardware risks accelerating device replacement cycles for users who want the fastest local AI experiences. That has financial and environmental implications and deserves scrutiny.

---

The WinRE regression: what happened and what to do​

Symptoms and scope​

• The October 14, 2025 cumulative update (KB5066835) and associated SafeOS dynamic updates are linked to an issue where USB keyboards and mice stop responding inside WinRE while continuing to function in the full Windows desktop. Affected OS builds were reported as 26100.6899 (24H2) and 26200.6899 (25H2). Microsoft acknowledged the problem and listed it on its Release Health / Known Issues dashboard.
• The behavior appears to be isolated to the trimmed recovery environment (SafeOS / winre.wim). Because WinRE loads a minimal driver stack, missing or mismatched USB / xHCI drivers inside that image can produce a situation where input devices work in the desktop but not inside recovery. Community reproductions and targeted winre.wim restores support this diagnosis.

Why this is serious​

WinRE is the built‑in safety net for repair tasks: Safe Mode, Startup Repair, Reset this PC, and Command Prompt are commonly accessed via WinRE. If WinRE is non‑interactive because input devices are unresponsive, recovery operations escalate in time and complexity, often requiring external boot media or a full reimage. For administrators, this multiplies operational overhead and increases the risk of downtime during a mass rollout.

Immediate mitigations and recommended actions​

• Pause broad deployment of the October cumulative in production rings until a targeted fix or Known Issue Rollback (KIR) is issued and validated.
• Ensure every device has tested external recovery media (Windows install USB/WinPE) available off‑device. Booting external media restores interactive recovery tools in almost all cases.
• Maintain golden winre.wim images: technicians who can restore a validated winre.wim to the recovery partition have restored input on many affected systems; use that only if you have tested the image on hardware variants in your estate.
• Monitor Microsoft’s Release Health and update channels for a hotfix/KIR and validate the fix on representative hardware before mass re‑enablement.

How administrators can validate systems (quick checklist)​

• Check WinRE status: reagentc /info and confirm WinRE is enabled and the recovery image path is valid.
• Test Advanced Startup access and validate keyboard/mouse behavior while the device is offline and local. If input is unresponsive, apply tested recovery media in a lab.
• Avoid uninstalling the LCU without a tested rollback plan: when SSU and LCU are packaged together, rollback semantics may be complicated if SafeOS images were updated.

---

PowerToys 0.95 and Light Switch: small changes, real UX wins​

What’s new in PowerToys 0.95​

PowerToys 0.95 introduces a new module called Light Switch, which provides a first‑party, scheduleable Light/Dark theme toggler for Windows. Key capabilities include:

• Automatic switching between Light and Dark modes by fixed schedule or Sunrise/Sunset (location‑aware).
• Per‑target control (System surfaces vs Apps) and configurable offsets.
• Hotkey and tray toggle for manual overrides and suppression during full‑screen apps.

Under the hood it toggles the same personalization registry values used by Windows (HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\Personalize) and broadcasts setting changes to trigger UI repaint. There are caveats: some legacy Win32 apps ignore these flags and may require restarts or app‑level settings to match the system theme.

Why PowerToys still matters​

PowerToys functions as Microsoft’s experimental sandbox for practical, user‑focused features. The 0.95 release prioritizes polish and performance improvements (for example, Command Palette speed work) while packaging small but tangible UX features like Light Switch. For power users and administrators who permit it, PowerToys reduces friction and replaces brittle user scripts and third‑party utilities.

---

Other notes from the week​

• The Media Creation Tool was reported to be broken on Windows 10 for some users and scenarios; if you rely on Microsoft’s official tooling to create install media or upgrade a Windows 10 device, validate the tool’s behavior or use an alternative means to create recovery media. Treat community reports cautiously and confirm against Microsoft’s release notes or the Release Health dashboard.
• The end of Windows 10 drove a notable migration signal for Linux distributions: some distros, notably Zorin OS, reported large upticks in downloads and migrations from Windows 10 users. While this is a clear community trend, individual migration realities vary widely based on hardware, application compatibility, and user skill.
• Microsoft is continuing staged rollouts for Windows 11 version 25H2, and at least one upgrade block related to a third‑party driver was issued to protect devices from a stability regression. These deployment gate blocks are normal but increase the administrative complexity of large upgrades.

---

Practical guidance: what users and IT teams should do now​

If you’re still on Windows 10​

• Confirm whether your device qualifies for the Consumer ESU window and decide whether ESU, upgrade, or migration is the right path for you. ESU is a short, security‑only bridge through October 13, 2026.
• If you plan to upgrade to Windows 11, pilot the upgrade on representative hardware. Validate app compatibility and, where possible, test Copilot features and policy controls before broad deployment.
• If you remain on Windows 10 and Internet‑connected, harden the endpoint: minimize attack surface, apply third‑party app updates, and plan for eventual OS migration.

If you manage Windows 11 fleets​

• Pause automatic deployment of the October cumulative on recovery‑critical endpoints until Microsoft’s fix/KIR is available and tested.
• Ensure validated external recovery media is available and train support staff on WinRE rollback/repair procedures. Maintain a tested winre.wim as part of your toolkit.
• Evaluate Copilot features under your organization’s privacy, compliance, and security policy constraints. Use device configuration and MDM controls to restrict or log agentic operations where necessary.

---

Critical analysis: strengths, trade‑offs, and where to be cautious​

Microsoft’s coordinated timing — ending Windows 10 mainstream support while elevating Copilot features in Windows 11 — is an explicit nudge: migrate to Windows 11 (and, implicitly, newer hardware) if you want continued feature innovation. The technical promise is real: context‑aware, multimodal assistance can speed workflows, reduce repetitive tasks, and make accessibility features more natural.
However, the October WinRE regression is a stark operational counterpoint: even routine monthly rollups can impact pre‑boot tooling and recovery workflows. That episode underscores two enduring truths for IT: stage updates, and treat recovery media/core images as first‑class operational assets. The optics of shipping AI surface changes at the same time as a servicing incident create legitimate trust and timing concerns for administrators.
Privacy is perhaps the thorniest domain. Vendor claims about local wake‑word detection and transient buffers are positive design signals, but the real‑world privacy posture depends on defaults, telemetry retention policies, cloud fallbacks, and the richness of admin controls. Independent validation and clear, inspectable logs are prerequisites for deploying agentic features in regulated environments. Treat claims about on‑device vs cloud processing as vendor statements until they can be verified in your fleet.
Finally, hardware segmentation (Copilot+ PCs) introduces real choice but also potential fragmentation. If premium experiences require dedicated NPUs, organizations must weigh performance against cost and the environmental impact of accelerated refresh cycles. Microsoft’s NPU throughput figures and “best experience” positioning are vendor claims that should be validated with benchmarks and procurement tests.

---

Conclusion​

Mid‑October’s convergence of Windows 10 end‑of‑support, Microsoft’s push to make Copilot a first‑class, multimodal part of Windows 11, and an awkward servicing regression that affected WinRE has left users and IT teams with a clear set of trade‑offs: accelerate migration to reap new productivity features, or pause and harden existing environments to retain predictability and control. The pragmatic path for most organizations is balanced: pilot Windows 11 Copilot features in a controlled ring, ensure recovery workflows and external media are validated, and treat consumer ESU as a temporary bridge rather than a permanent alternative. Meanwhile, scrutinize privacy, telemetry, and audit surfaces before enabling agentic or vision‑based assistance broadly. Microsoft’s vision for an AI PC is compelling — but the operational realities of updates, hardware variance, and governance mean that careful rollouts and skeptical validation remain the responsible course.

---

Source: Neowin Microsoft Weekly: Windows 10 is dead and Microsoft wants you to talk to your PC