Win 11 25H2

[netnet]

Major Update ekek awilla tiye , Ubala dammada guys,
podi ekak neda damma wulak naha

 

[olu bakka]

කවුද බන් මුන්ගෙ අප්ඩේට් සිස්ටම් එක හදන්නෙ. ඒ මගුල අප්ඩේට් වෙන්නෙ ඌට ආස වෙලාවට. අප්ඩේට් වෙයන් කිවුවම කැරකි කැරකි ඉඳල එරර් එකක් එනව. එක්කො ෆයිබර් ලයින් එකකට ගැහුවත් ගිගාබයිට් දෙක තුනේ අප්ඩේට් එක බෑවෙන්න දවසක් දෙකක් යනව. ඔය මොකක්වත් නැතුව වැදගත් වැඩක් කරන්න ගත්ත්ම ඒ අස්සෙ අරක ඩවුන්ලෝඩ් කරන්න අරන් බිල් ගේට්ස්ගෙ අම්ම අප්ප සිහි කරනව.

 

[netnet]

කවුද බන් මුන්ගෙ අප්ඩේට් සිස්ටම් එක හදන්නෙ. ඒ මගුල අප්ඩේට් වෙන්නෙ ඌට ආස වෙලාවට. අප්ඩේට් වෙයන් කිවුවම කැරකි කැරකි ඉඳල එරර් එකක් එනව. එක්කො ෆයිබර් ලයින් එකකට ගැහුවත් ගිගාබයිට් දෙක තුනේ අප්ඩේට් එක බෑවෙන්න දවසක් දෙකක් යනව. ඔය මොකක්වත් නැතුව වැදගත් වැඩක් කරන්න ගත්ත්ම ඒ අස්සෙ අරක ඩවුන්ලෝඩ් කරන්න අරන් බිල් ගේට්ස්ගෙ අම්ම අප්ප සිහි කරනව.

Original windows ?

 

[tha123]

ගැහුවා බන්.. කිසි දැනෙන වෙන්සක් නෑ.. මුන්ගේ update නම් අනේමන්දා

 

[olu bakka]

Original windows ?

Yes.

 

[HKavinda]

ආව දවස්වලම දැම්මා බන්

 

[Uchiha_Nimnora]

Perfect — that makes your question about localhost and Windows 25H2 even more relevant

Since you’re in SOC, here’s the security-focused summary of 25H2’s effect on local environments and tooling:

---

SOC & Security Tool Impacts in 25H2​

Good News​

• No localhost or loopback restrictions — tools like Burp Suite, Fiddler, Nessus, Wireshark, Splunk Forwarders, and local ELK stacks run normally.
• Windows Defender for Endpoint now logs more telemetry natively (including deeper AMSI integration).
• Sysmon, Event Viewer, and ETW sources remain unaffected.
• PowerShell 7.5 preview compatibility improved — better logging for script block tracing.

---

Potential SOC-Relevant Changes​

1. Loopback isolation tightening for UWP and Store apps — may interfere with traffic capture (you may need to re-allow loopback with:
   CheckNetIsolation LoopbackExempt -a -n=<PackageFullName>
   ```)
   
   
   
2. SMB hardening updates — legacy SMBv1 shares might break. This affects some internal forensic tools or old malware test environments.
3. LSASS protection defaults→ enabled by default on new installs (Credential Guard ON).
   • Great for security.
   • But you’ll need to disable it (via Group Policy or registry) if doing credential dumping analysis in isolated labs.
4. Enhanced driver blocklist (kernel) — can block custom packet capture drivers used by tools like Npcap or older Wiresharkbuilds.
   • Fix: install the latest Npcap signed version.
5. Firewall resetcan remove custom inbound rules (for test servers, honeypots, etc.).
   • Re-verify your inbound/outbound SOC lab rules after upgrade.

---

Notable Known Issues​

Here are the primary ones reported so far:

1. DRM / Protected Media Playback Problems
   Applications that use the “Enhanced Video Renderer” (EVR) with HDCP enforcement or other DRM-protected audio/video may see playback issues or failures (black screens, interruptions, errors) in 25H2. (Windows Central)
   • This especially affects older Blu-ray/DVD apps or live TV recorders that rely on legacy rendering paths. (Windows Central)
   • Microsoft acknowledges it and says a fix is “in progress”. (Windows Central)
   • If you use such media apps, this could matter to you.
2. Updates via Standalone Installer (WUSA) Might Fail
   If you install a .msu update file (especially from a network share with multiple .msu files) using the Windows Update Standalone Installer (WUSA), you may encounter error codes such as ERROR_BAD_PATHNAME. (Windows Central)
   • The workaround: copy the .msu file(s) to a local folder and run from there. (Windows Central)
   • Mostly affects enterprise/deployment scenarios; less likely to affect average home users.
3. SMB v1 File Sharing Broken / Impaired
   One of the issues listed is that file sharing over SMB v1 may not work correctly after 25H2. (Windows Latest)
   • If you have legacy network shares using SMB v1 (older NAS devices, older Windows versions), this could disrupt them.
   • Note: SMB v1 is generally deprecated, but some environments still use it.
4. Performance Gains Are Minimal / Non-existent
   Some benchmarking shows that 25H2 offers essentially the same performance as 24H2 — no significant improvements. (TechRadar)
   • If you were hoping for a big speed boost or major feature jump, this might be disappointing.
   • For many users with already good setups, the upgrade may feel more like a “maintenance” update rather than a big leap.
5. Installation / Compatibility Blocks for Certain Hardware
   Although many blocks have been lifted, some devices with incompatible drivers (e.g., older Intel Smart Sound Technology drivers, certain webcams) had upgrade compatibility holds. (Windows Latest)
   • If your hardware is older or using niche drivers, there’s a possibility of unexpected issues.
   • Also: installing on unsupported hardware (i.e., bypassing checks) carries higher risk of instability. (TECHCOMMUNITY.MICROSOFT.COM)
6. Increased Memory / Resource Usage (User Reports)
   There are user-forum reports (not always confirmed by Microsoft) suggesting that after upgrading to 25H2, RAM usage increased in some systems. (Microsoft Q&A)
   • Example: “What I immediately noticed was my RAM usage went up ~2 GB” after upgrading.
   • These are anecdotal, so treat them with caution, but worth noting.