The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Microsoft released Edge 139 to the Stable Channel on August 7, 2025, starting with build 139.0.3405.86. The 139 branch later received several maintenance updates; Microsoft’s archived Stable notes list 139.0.3405.125, released August 28, 2025, as its final 139.x Stable build. Edge 139 is now a historical release, not the current version: Microsoft said Edge 152 was scheduled for Stable on August 27, 2026.
Edge 139 release dates and build numbers
The August 7 date is the Stable Channel release date, not a promise that every device received the update that day. Microsoft identifies 139.0.3405.86 as the first Stable build. Its archived notes list these subsequent 139.x releases:
| Stable build | Release date |
|---|---|
| 139.0.3405.86 | August 7, 2025 (initial Stable release) |
| 139.0.3405.102 | August 15, 2025 |
| 139.0.3405.111 | August 21, 2025 |
| 139.0.3405.119 | August 26, 2025 |
| 139.0.3405.125 | August 28, 2025 (final 139.x Stable build listed) |
These dates and builds are from Microsoft’s archived Stable Channel release notes. Microsoft’s Edge 139 web-platform notes also give August 7, 2025, as the release date.
What changed in the Stable release?
Browser fixes and updates
Microsoft’s Stable notes describe the release in broad categories: bug fixes, performance improvements, feature updates, policy updates, security updates, and web-platform changes. They do not describe a wholesale interface redesign. The listed categories do not mean every change is visible in the browser UI; some affect reliability, management, or websites and apps built for the web.
#1 Best Overall
Security updates
Microsoft says the August 28, 2025 build, 139.0.3405.125, incorporated the latest applicable Chromium security updates. That statement is specific to that build and date; it is not a vulnerability count or a current security recommendation. See Microsoft’s Edge security-update notes for the security-update record.
What Edge 139 means for web developers
Edge 139’s web-platform notes document changes across CSS, Web APIs, DevTools, and WebView2. Among the named additions and updates are CSS custom functions, the CSS font-width and corner-shape properties, transitions to an initial transition value, the request-close invoker command, audio-level information for WebRTC encoded frames, and a way to specify a crash-reporting endpoint. The notes also describe changed error reporting for workers blocked by Content Security Policy.
These are platform capabilities, not necessarily features an ordinary browser user will notice. Developers should consult the Edge 139 web-platform notes for implementation details and distinguish generally available support from experimental origin trials.
Origin trials are not general availability
The Edge 139 documentation lists experiments including the Prompt API, WebGPU Compatibility Mode, full-frame-rate render blocking, scope_extensions, and AriaNotify. Their presence in the release notes does not mean they were enabled for every user or production-ready by default. Access may depend on trial enrollment, flags, hardware, policy, or rollout. Availability can also differ among desktop Edge, mobile Edge, and WebView2.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsRank #3
- Used Book in Good Condition
What IT administrators should know
Edge 139 security baseline
Microsoft published its Edge 139 security baseline on August 7, 2025. It added the EnableUnsafeSwiftShader policy, which controls whether SwiftShader can serve as a software fallback for WebGL when hardware GPU acceleration is unavailable or disabled. This is an administrative setting, particularly relevant to managed or virtualized systems; it is not a consumer-facing feature announcement. Details are in Microsoft’s Edge 139 security-baseline post.
Stable and Extended Stable
Stable follows Microsoft’s ordinary feature-update cadence. Extended Stable is an organizational deployment option with a slower feature-update rhythm for environments that need more time to test changes; it is not simply a more secure edition. Microsoft’s 2026 release-cycle announcement says Extended Stable remains on an eight-week rhythm as regular Stable moves to a faster schedule. Administrators should check their channel, update policy, and deployment tooling before comparing a managed installation with a consumer Stable build.
For deployment and policy guidance, use Microsoft’s Edge deployment documentation or Edge for Business. Build numbers and available features can vary by operating system, channel, device capability, policy, and product surface.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to check your Edge version and update
- Open Microsoft Edge and select Settings and more (the three-dot menu).
- Select Help and feedback, then About Microsoft Edge.
- Read the full version and build number. An Edge 139 installation begins with
139.0; the remaining numbers identify the specific maintenance build. - Edge checks for updates on the About page. If an update is available, let it download and select Restart if prompted.
The update offered depends on your operating system, channel, device, and update policy. A managed device may be pinned to a version or receive updates through organizational tools. Administrators can also verify deployments through software inventory or endpoint-management systems; the About page is not their only option. On a managed Windows device, edge://policy can show policies applied to the browser.
Free tools Windows power users keep installed
One-click scans. No signup required.
Do not expect a current device to offer Edge 139 now. For a fresh installation, use Microsoft’s official Edge download page. If a managed installation is not updating, check with the organization’s administrator rather than installing a consumer package over its deployment.
Should you install Edge 139 now?
At its 2025 release, the sensible choice was to let Stable update normally and use the newest available 139.x build, rather than stopping at the initial 139.0.3405.86. Organizations could test policies, extensions, authentication, WebView2 apps, and business-critical sites before a broad rollout.
As of August 18, 2026, do not seek out Edge 139 as an update target. Use the current supported Stable version offered for your device. Microsoft’s 2026 release-cycle announcement said Edge 152 was scheduled to enter Stable on August 27, 2026; that was a scheduled date, not confirmation in itself that the release had already happened.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
