Urgent.News

What's breaking now, across thousands of outlets.

Tech

Windows Developer Configurations fixes what Microsoft won't admit it broke

Microsoft published a list of everything wrong with its own defaults.

Windows Developer Configurations fixes what Microsoft won't admit it broke

Microsoft has released the Windows 11 26H2 update to the Windows Insider Release Preview Channel. This update shares the same servicing branch as previous versions 24H2 and 25H2. Users can expect familiar tweaks such as a movable taskbar, enhanced Start Menu customization, and the ability to remove web and Microsoft Store suggestions from local search results.

The update arrives in the form of an enablement package, a small piece of code that activates existing but dormant features. Microsoft emphasizes that this update is more compact than a full operating system replacement, requiring minimal downloads and reinstallation. The shared codebase and updates across all Windows 11 versions may raise questions about the necessity of the 26H2 release.

However, this reset of the support clock ensures 24 months of support for Home and Pro editions, and 36 months for Enterprise and Education editions. Enterprises are advised to validate compatibility with their apps, policies, and infrastructure before deployment. Microsoft has learned from past mistakes, such as the 2018 Windows 10 October update, and is exercising caution with the Release Preview phase.

The August Preview Update itself introduced improvements but was met with some user complaints regarding cursor and black desktop background issues. Microsoft has not reported any known problems with the current update.

Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at xda-developers.com →

More in Tech

Docker Says "Healthy" and the Pod Keeps Sending Broken Traffic

Run this on any Kubernetes cluster that has containers with HEALTHCHECK defined in their Dockerfile and no livenessProbe or readinessProbe configured in the manifest: kubectl get pods -o wide docker…

  • Docker's HEALTHCHECK runs inside Docker daemon, reports status to Docker inspect.
  • Kubernetes relies on its own health checks: livenessProbe, readinessProbe, startupProbe.
  • Pod may receive traffic despite Docker reporting it as healthy, causing potential issues.

More from Friday 28 August →