What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Microsoft Edge 135 reached the Stable Channel on April 3, 2025, starting with build 135.0.3179.54. It was not a major consumer redesign: the release focused on Chromium web-platform capabilities, enterprise administration, Microsoft 365 work features, certificate handling and security fixes. Edge 135 is now a historical, superseded version, so ordinary users should remain on the currently supported Stable Channel rather than seek out this build.
Edge 135 at a glance
| Change | Who it affects | What it does | Availability notes |
|---|---|---|---|
| Feature Usage sync | Users signed in to Edge | Synchronizes a separate category describing use of Edge features | Depends on account, sync settings, policy, platform and rollout |
| Bing trending suggestions | Some consumer users | Shows trending suggestions when the New Tab Page address bar is opened | Controlled by AddressBarTrendingSuggestEnabled; region and policy can affect visibility |
| Work Feed/My Feed redesign | Eligible commercial Microsoft 365 users | Emphasizes documents, SharePoint sites, Outlook events, apps and To Do tasks | Controlled rollout began in April 2025 |
| Work-search transition | Edge for Business deployments | Moves address-bar work searches toward Microsoft 365 results on M365.cloud.microsoft |
Primarily a commercial Microsoft 365 scenario |
| Intune policy management | Edge and Intune administrators | Allows Intune policies to be configured through the Edge management service | Requires suitable tenant configuration, permissions and availability |
| Purview authorized groups | Organizations using Microsoft Purview | Enforces authorized printer, USB-device and network-share groups | Compliance control, not a consumer privacy switch |
| Web-platform additions | Web developers and WebView2 applications | Adds CSS, HTML, JavaScript, WebRTC and service-worker capabilities | Browser compatibility and standards status vary |
| Entrust trust change | Enterprise certificate administrators | Restricts trust for certificates chaining to specified Entrust roots under a date condition | Not a blanket block of all Entrust certificates |
Microsoft’s release schedule lists the dates and builds in the Edge release schedule. The Stable release archive contains the product, policy and enterprise details.
When Edge 135 was released
Stable Edge 135 became generally available on April 3, 2025, with build 135.0.3179.54. The major version followed Edge 134 and preceded Edge 136. Microsoft subsequently published several Stable builds:
| Build | Date | Documented significance |
|---|---|---|
| 135.0.3179.54 | April 3, 2025 | Initial Stable release |
| 135.0.3179.66 | April 9, 2025 | Included a fix for a possible Google-results crash under a group-policy search configuration |
| 135.0.3179.73 | April 11, 2025 | Additional bug, performance and security maintenance |
| 135.0.3179.85 | April 17, 2025 | Fixed a first-run edge://welcome-new-device issue and a conditional Copilot toolbar-icon problem |
| 135.0.3179.98 | April 24, 2025 | Additional bug, performance and security maintenance |
Those patch numbers matter: “Edge 135” does not identify one identical binary. Security and reliability fixes differed between builds.
#1 Best Overall
What changed for everyday users?
Feature Usage can sync separately
Edge added a Feature Usage synchronization category. It describes how Edge features are used across devices; it is separate from synchronizing favorites, history, passwords or open tabs. Whether it appears depends on the signed-in account, synchronization choices, organization policy, platform and rollout status. It should not be interpreted as synchronization of every Edge preference.
Trending suggestions on the New Tab Page
On the Microsoft Edge New Tab Page, selecting the address bar could show Bing trending suggestions in the dropdown. This was specifically tied to that New Tab Page experience, not necessarily to every address-bar suggestion surface. Administrators can control it with AddressBarTrendingSuggestEnabled, and users may not see it because of region, account, policy or staged deployment differences.
What did not change
Edge 135 did not deliver a universal visual overhaul, a new tab-management system or a new Copilot product. Copilot already existed in Edge; the release archive records a later fix for a Copilot toolbar icon that could disappear when HubsSidebarEnabled was enabled.
Edge for Business and Microsoft 365 changes
Work Feed/My Feed redesign
For eligible commercial users with Microsoft 365 subscriptions, the enterprise New Tab Page Work Feed was reworked into a My Feed focused on:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →- Recently used Microsoft 365 documents.
- Recent SharePoint sites.
- Upcoming Outlook events.
- Microsoft 365 applications.
- To Do tasks.
The earlier network-content and activity emphasis was reduced or removed. Microsoft described flighting beginning in early April 2025, with updated feeds appearing from mid-April. This was a controlled enterprise rollout, not a change every consumer account was guaranteed to receive. New Tab Page policies continued to apply.
Work search moved toward Microsoft 365 results
After March 31, 2025, Edge for Business address-bar searches for work content were directed toward work results on M365.cloud.microsoft rather than the former Microsoft Search in Bing experience. Users could search documents, people and bookmarks by typing work, pressing Tab and entering a query. Microsoft noted that the relevant transition required Edge 134.0.3134.51 or later. This did not change the ordinary consumer web-search experience into a Microsoft 365 search.
Intune policies in the Edge management service
Administrators could configure Intune policies through the Edge management service alongside existing cloud browser policies. The policy-creation wizard was intended to provide a single management view. This is an administrative capability for organizations already using Microsoft Intune and Edge for Business; tenant permissions, licensing, configuration and rollout status determine what is available.
Purview authorized-group enforcement
Edge 135 added enforcement for Microsoft Purview authorized groups covering printers, removable USB devices and network shares. The goal was to prevent users from bypassing Data Loss Prevention controls through Edge. It is a compliance feature managed by an organization, not a setting that improves privacy for an individual consumer.
Policies added, changed or retired
| Policy | Status in Edge 135 | Purpose or implication |
|---|---|---|
AddressBarTrendingSuggestEnabled |
Introduced | Controls trending suggestions in the New Tab Page address bar |
NewTabPageCompanyLogoBackplateColor |
Introduced | Controls a company-logo backplate color on managed New Tab Pages |
PartitionedBlobUrlUsage |
Introduced | Controls partitioned Blob URL behavior |
WebContentFilteringBlockedCategories |
Introduced | Specifies blocked web-content categories |
WebRtcIPHandlingUrl |
Introduced | Controls WebRTC IP-handling behavior for specified URLs |
AddressBarMicrosoftSearchInBingProviderEnabled |
Deprecated | Signals the transition away from the former Microsoft Search in Bing provider |
RelatedMatchesCloudServiceEnabled |
Obsoleted | Should not be used for new deployments |
Administrators should use the Stable Channel release archive and current policy documentation when planning a deployment; policy behavior can change after the major version.
Developer features in Edge 135
Most of the technically significant work in Edge 135 was in the Chromium engine. These are web-platform capabilities, not new Edge-only interface controls. Feature detection and compatibility testing remain necessary before removing fallbacks.
CSS additions
- Carousel and scroll controls through
::column,::scroll-marker,::scroll-marker-groupsand::scroll-button(). - Nested pseudo-element styling such as
::before::marker. - The
interactivityproperty and logical overflow propertiesoverflow-inlineandoverflow-block. - Mathematical functions including
abs()andsign(). - Remembered scroll offsets for CSS anchor positioning.
- The
shape()function andprogress(),media-progress()andcontainer-progress(). safe-area-max-inset-*environment variables for layouts that account for device cutouts and safe areas.
Together, these primitives support more capable carousels, responsive shapes, logical writing-mode layouts, anchor-positioned interfaces and progress-driven effects. Support in Edge 135 does not imply support in every browser or older release.
Declarative HTML commands
Buttons can invoke built-in behavior with command and commandfor, reducing JavaScript for common dialog and popover interactions:
<button commandfor="dialog" command="show-modal">
Open dialog
</button>The attributes are web-platform features, not Edge-exclusive inventions. Use the appropriate fallback when targeting browsers without the same implementation.
Other HTML changes included rel="facilitated-payment" for push-payment integration and rel/relList support on SVG <a> elements.
JavaScript and Web APIs
- MediaStreamTrack in the Web Speech API: speech recognition or captioning can use an external audio track instead of only the default microphone.
- Float16Array: stores IEEE 16-bit floating-point values. It can reduce memory use and help graphics or machine-learning interoperability, but it has less precision than 32-bit floating point.
- NavigateEvent.sourceElement: exposes the source element for navigation events.
- Observable: adds a reactive event/data abstraction to the platform.
- fetchLater(): supports deferred network requests, useful for telemetry or cleanup when browser scheduling and page lifecycle permit.
- highlightsFromPoint(): lets editors and annotation tools respond to interactions with CSS Custom Highlights.
- Service-worker updates cover
srcdociframes andClient.url. - WebRTC encoded-frame capture and receive timestamps help conferencing applications measure media latency.
Removed or deprecated web features
Edge 135 removed navigator.xr.supportsSession; WebXR code should use navigator.xr.isSessionSupported(). It also removed the WebGPU maxInterStageShaderComponents limit, which was considered redundant with maxInterStageShaderVariables.
WebView2 Runtime and SDK
The corresponding WebView2 release notes list Runtime 135.0.3179.45 and SDK 1.0.3179.45, both dated April 7, 2025. An embedded WebView2 application receives the Chromium engine and runtime changes it supports, but it does not automatically expose Edge browser UI such as the sidebar, profile menu or New Tab Page.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsSee Microsoft’s Edge 135 web-platform release notes for the complete API list and implementation qualifications.
Security and certificate changes
Chromium and Edge security fixes
The initial Stable build incorporated Chromium security updates and Edge-specific fixes. Microsoft’s Stable security release notes identify fixes by exact build, including Edge-specific CVEs such as CVE-2025-29796, CVE-2025-25000 and, in a later April update, CVE-2025-29834. Do not assume every 135 build contained the same patch set; check the build-specific entry.
Entrust root-certificate constraint
Microsoft announced a Trusted Root Program change affecting listed Entrust roots. Certificates chaining to those roots would no longer be trusted by default when their earliest Signed Certificate Timestamp was later than April 16, 2025, at 7:00 a.m. UTC. This applied only to the specified roots and validation condition, not to every Entrust certificate.
Enterprise certificate teams should replace affected certificates. Microsoft also described installing the relevant root certificate as locally trusted as a possible mitigation, but that changes trust behavior and requires careful risk assessment; it is not a casual workaround.
Recommended Free Tools
Fixes in later Edge 135 builds
- .54 — April 3: initial Stable release.
- .66 — April 9: addressed a possible crash while displaying Google search results when Google was configured as the default search engine through group policy.
- .73 — April 11: supplied additional bug, performance and security maintenance.
- .85 — April 17: fixed a first-run problem involving
edge://welcome-new-deviceand a case where the Copilot toolbar icon could disappear withHubsSidebarEnabledenabled. - .98 — April 24: supplied further bug, performance and security updates.
These fixes do not establish that the whole major version was unstable; they show why updating within a major-version branch mattered.
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.
- Select the three-dot menu in the upper-right corner.
- Choose Help and feedback.
- Select About Microsoft Edge.
- Allow Edge to check for and install an update.
- Select Restart if prompted.
The About page displays the complete version and build. Compare all four components, not just “135,” when diagnosing a security or reliability issue.
If checking fails, restart Edge, restart Windows or macOS, and try again. On a managed device, ask the administrator whether update policies or an Extended Stable deployment controls the browser. Do not obtain Edge installers from unofficial mirror sites.
Is Edge 135 worth installing now?
No, not for ordinary users. Edge 135 has been superseded. Stay on the supported Stable Channel unless you have a specific compatibility, WebView2 testing, enterprise-validation or archival reason to reproduce the April 2025 environment. The release is worth understanding when you maintain a site using its APIs, administer Microsoft 365 or Purview controls, manage affected certificates, or troubleshoot one of its documented patch issues.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Its trade-offs are straightforward: newer platform primitives can reduce custom JavaScript but require cross-browser fallbacks; enterprise controls improve governance but add tenant and licensing complexity; certificate enforcement can improve trust decisions but may break an unremediated enterprise service; and staged rollouts can make two correctly updated users see different interface features.
Frequently asked questions
Frequently Asked Questions
When was Microsoft Edge 135 released?
The Stable Channel release became generally available on April 3, 2025.
What was the first Edge 135 build?
The initial Stable build was 135.0.3179.54.
Did Edge 135 introduce a new Copilot feature?
No major new Copilot feature was documented. A later 135 patch fixed a condition in which the Copilot toolbar icon could disappear when HubsSidebarEnabled was enabled.
Why might the redesigned Work Feed be missing?
The redesign targeted eligible commercial Microsoft 365 users and was flighted gradually. Account eligibility, New Tab Page policies and rollout timing all affected visibility.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhat is Feature Usage Data Sync?
It is a separate Edge Sync category describing feature use across devices; it is not the same as synchronizing history, favorites, passwords or open tabs.
Did Edge 135 block all Entrust certificates?
No. The change concerned specified Entrust roots and certificates whose earliest Signed Certificate Timestamp was later than April 16, 2025, at 7:00 a.m. UTC.
Which notable APIs arrived in Edge 135?
Examples include fetchLater(), Float16Array, Observable, external MediaStreamTrack support for Web Speech, highlightsFromPoint() and WebRTC encoded-frame timestamps.
Is Edge 135 still supported?
It is a historical, superseded major version. Use the currently supported Stable Channel unless you need version-specific testing.
Free tools Windows power users keep installed
One-click scans. No signup required.
How do I find my exact Edge build?
Open the three-dot menu, choose Help and feedback, then About Microsoft Edge. The full build number appears on that page.
How does WebView2 Runtime 135 differ from desktop Edge 135?
WebView2 Runtime 135.0.3179.45 and SDK 1.0.3179.45 provide the embedded Chromium runtime and APIs. They do not automatically include desktop Edge UI such as the sidebar or New Tab Page.
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.
