To deploy Microsoft Edge patches through Configuration Manager (SCCM/MECM), synchronize the Microsoft Edge product through the Software Update Point (SUP), then manage the resulting updates through the normal software-update workflow. This is separate from installing Edge: the Edge application wizard deploys the browser, while All Microsoft Edge Updates manages updates for channels already installed on clients. The steps below follow current-branch guidance; older examples such as Edge 79 are historical, not current patch recommendations.
What this workflow does—and what it does not
Configuration Manager must synchronize update metadata before Edge updates can appear in its console. Selecting the Edge product and relevant classifications at the SUP makes eligible metadata available; it does not automatically install Edge, distribute update content, or guarantee that ConfigMgr is the only system controlling Edge’s update behavior. A working SUP is required for software-update compliance assessment and deployment. Microsoft’s software-update preparation guidance describes that foundation.
Keep these tasks distinct:
- Install Edge: Use the built-in Create Microsoft Edge Application wizard to deploy a selected channel and version.
- Patch Edge: Synchronize updates and manage them from the Edge updates node or other software-update views.
- Control update behavior: Decide whether Edge Update, ConfigMgr, policy, Intune, or a combination governs rollout. Creating an Edge application does not by itself settle every device’s update authority.
Microsoft documents the Edge application and update-management experience for Configuration Manager current branch and Edge version 77 and later. The exact UI may vary by ConfigMgr release. See Microsoft’s Edge deployment documentation.
Check prerequisites before synchronizing
- A supported Configuration Manager current-branch site with a functioning SUP integrated with WSUS.
- A successful baseline software-update synchronization and the ability to synchronize the selected products and classifications.
- Healthy ConfigMgr clients with software updates enabled, plus target collections for pilot and production deployment.
- Distribution points with adequate storage and healthy content distribution.
- Network access appropriate to the architecture. The built-in Edge application experience uses endpoints including
https://aka.ms/cmedgeapi,https://edgeupdates.microsoft.com/api/products?view=enterprise, andhttp://dl.delivery.mp.microsoft.comfor release information and release content. These are relevant to the application deployment experience; they are not a complete network checklist for every WSUS/SUP design. Consult Microsoft’s endpoint and deployment guidance.
Enable the Microsoft Edge product at the Software Update Point
Configure products and classifications at the central administration site or a stand-alone primary site, rather than assuming that changing a child site’s settings will enable synchronization for the hierarchy.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
- In the Configuration Manager console, go to Administration > Site Configuration > Sites.
- Select the central administration site or stand-alone primary site.
- Choose Configure Site Components > Software Update Point.
- Open Products and find and select Microsoft Edge. Product grouping and labels can vary by WSUS generation and console language, so search the list for the product name rather than relying on an old screenshot.
- Open Classifications, select the categories your organization needs, and save the settings.
- Run Synchronize Software Updates and verify that the synchronization completes.
If Microsoft Edge is missing from Products, the product catalog may not yet have refreshed. Microsoft notes that a synchronization can be required before newly available products become selectable. See Configure classifications and products.
Choose classifications deliberately
Classifications describe update types; they are not interchangeable checkboxes that should all be enabled by default. Microsoft defines Updates as non-critical, non-security fixes; Security Updates as product-specific security fixes; and Critical Updates as critical non-security fixes. For Edge, a practical starting point is Updates and, where the synchronized Edge metadata uses it, Security Updates. Inspect the actual update properties in your environment rather than assuming every release is always assigned to the same classification. Microsoft’s classification definitions provide the fuller descriptions.
Synchronize and confirm that Edge updates arrived
The setup commonly takes two synchronization passes: first to refresh available product metadata, then—after selecting Microsoft Edge—to import Edge update metadata. In the console, use Synchronize Software Updates; wording and synchronization behavior can differ by release, so verify completion instead of relying on an assumed “full WSUS sync” label.
- Review
WsyncMgr.logon the site server for synchronization activity and errors. - In the console, open Software Library > Microsoft Edge Management > All Microsoft Edge Updates. The hierarchy may look slightly different across console versions.
- Open update properties and check product, classification, revision, supersedence, and applicability details.
- Use software-update monitoring or compliance views after deployment; metadata appearing in the node confirms synchronization, not client installation.
The Edge updates node is the current Microsoft-documented location for Edge updates. Microsoft describes the node and its tasks here. A historical HTMD procedure also uses WsyncMgr.log to verify synchronization: Deploy Microsoft Edge Patches with SCCM Software Updates.
Rank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
Review updates before deployment
Do not select an update solely because it is the newest-looking entry. Confirm that it matches the channels and devices you manage, and that its applicability and supersedence make sense for the rollout.
- Check the Edge channel present on target devices, such as Stable, Beta, or Dev where those channels are intentionally managed.
- Review architecture and applicability for the endpoint population.
- Check supersedence so the deployment does not unnecessarily target an older update when a later applicable update replaces it.
- Consider installed Edge version, operating-system support, and whether a fresh client software-update scan has run.
“Not applicable” is not by itself evidence of a failed deployment; the update may not apply to that device’s channel, version, architecture, or OS.
Deploy updates manually or through an update group
Manual deployment for a pilot or urgent update
- Open All Microsoft Edge Updates and select the intended update.
- Download the update if its content is not already available, then distribute it using the applicable ConfigMgr content workflow.
- Add it to a software update group or start a manual deployment.
- Target a pilot device collection and configure availability, deadline, user notifications, restart behavior, and download behavior to match your change policy.
- Monitor content distribution, client installation, and compliance before expanding the rollout.
Manual deployment is useful for a small pilot, an urgent security release, or investigating one specific update. Microsoft lists downloading and manual deployment among the tasks available from the Edge updates node. Edge updates in Configuration Manager.
Use a Software Update Group for recurring cycles
An Edge-specific software update group keeps browser servicing distinct from Windows update cycles and provides a place to promote tested updates. Add updates manually for a controlled cycle or let an ADR add matching updates. ConfigMgr can deploy an update group and subsequently deploy newly added updates according to its deployment configuration. Microsoft’s update-group guidance explains the relationship.
Recommended Free Tools
Rank #3
- Full HD Portable Monitor - MNN 15.6inch portable laptop monitor with 1920*1080 resolution, advanced IPS glossy screen support 178° full viewing angle, it renders accurate and bright color, draws you into the video or game with lifelike colors and amazing detail.It can effectively reduce blue light radiation damage, no flickering, eye-care, and make it easier to watch for a long time.A second monitor for working from home.
- Double Type-C Port -For Plug & Play, the MNN monitor provides 2 Full Feature Type-C ports. Only One USB Type-C Cable is required to connect to the power supply & display signal transmission. NOTE: Your device should support thunderbolt 3.0 or USB 3.1 Type C DP ALT-MODE.which supports multiple connect ways to your laptops, PC, Phones, Macbooks, PS5/PS4, Xbox, and Switch.
- Lightweight Ultra Slim for Travel - As a portable external monitor,MNN portable laptop monitor easily accommodate to every suitcase and backpack and stress-free when you are holding it for a long time. They are truly portable computer monitors for travelers, students, gamers,engineers, and everyone.
- Give consideration to work and games - through multiple display modes [Copy Mode/Extended Mode/Second Screen Mode/Portrait Mode], we can bring you a clear second screen in the meeting, and expand the screen anytime and anywhere to improve work efficiency and improve the quality of life. Adjusting to HDR mode can upgrade the image to a new level, providing you with brighter highlights,deeper and more realistic colors, more realistic images, and amazing viewing/gaming experience.
- Powerful Smart Cover - MNN portable external monitor can work in both landscape and portrait mode, can be used as a gaming monitor, screen extender for laptop or phone. Comes with a scratch-proof smart cover made of durable PU leather exterior, doubles as a stand, provides comprehensive protection for this portable computer monitor.
Use a narrowly scoped ADR for recurring Edge patching
An Automatic Deployment Rule (ADR) can reduce repetitive selection work, but constrain it to the Edge updates you intend to service. Common filters include product Microsoft Edge, only the required classifications, release date or age, and supersedence state. Separate rules may be appropriate where channels, architecture, or rollout requirements differ. Avoid broad product filters that can pull in unrelated updates. Review each ADR’s results and deployment target before relying on automation.
Roll out in stages and validate the browser
- IT test devices: Confirm installation and basic browser operation.
- Representative pilot: Include users, devices, and key applications that reflect production use.
- Early adopters or low-risk groups: Expand after reviewing pilot results.
- Broad production: Use phased deployments or successive collections where appropriate.
- Exception collection: Track devices held back for a documented compatibility or operational reason.
Before broad rollout, check that Edge launches, required extensions load, browser-based line-of-business applications work, WebView2-dependent applications continue working, browser policies remain applied, and the deployment has not caused an unwanted restart or disruption. After the client’s scan and inventory cycles, compare software-update compliance with the installed browser version. A deployment status can be healthy while inventory is still waiting to refresh.
Diagnose failures by layer
Microsoft Edge does not appear in Products
- Confirm an initial synchronization completed and the product catalog refreshed.
- Reopen SUP properties and search the Products list for Microsoft Edge.
- Check that configuration is being made at the central administration site or stand-alone primary site.
- Review
WsyncMgr.logand WSUS/SUP health. If synchronization is failing, resolve that before troubleshooting client deployment.
Synchronization completes, but the Edge node is empty
Confirm Microsoft Edge is selected as a product, relevant classifications are enabled, and a subsequent synchronization completed. Check the synchronization log for errors and allow the console to reflect imported metadata. Missing metadata is different from metadata that exists but has no distributed content.
Updates are visible but not applicable
Check channel, installed version, architecture, OS support, supersedence, and whether the client completed a fresh software-update scan. Also verify that another management system is not controlling the device’s update behavior. Do not force an inapplicable update just to change its compliance state.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
Content will not download
Check distribution-point availability, boundary-group assignment, content distribution status, firewall or proxy restrictions, and the relevant site-server access to Microsoft endpoints for the workflow being used. For Edge application-content download problems, Microsoft identifies PatchDownloader.log as a useful diagnostic. See the documented log mappings.
Installation fails or the browser stays on an older version
Separate download, applicability, and installation failures rather than treating them as one problem. Check whether the targeted update is superseded, the device is using another channel, Edge was open during servicing, or a restart or browser restart is pending. Confirm whether Edge Update or policy controls the final version, and allow inventory to refresh before concluding that the installed version is unchanged. For the built-in Edge application workflow, Microsoft maps SMSProv.log to provider/application creation issues, PatchDownloader.log to content downloads, and client AppEnforce.log to application installation. These are not substitutes for the standard software-update client logs when troubleshooting update deployments.
Compliance or policy looks stale
Check client activity, policy retrieval, scan timing, SUP connectivity, and ConfigMgr client health. If the browser’s behavior contradicts the deployment plan, inspect edge://policy for applied settings. Administrative templates include msedge.admx for browser policies and msedgeupdate.admx for Edge Update policies; mandatory policy overrides user preferences. Microsoft documents policy configuration, template use, and the registry policy path HKLMSOFTWAREPoliciesMicrosoftEdge at Configure Microsoft Edge with policy settings. To refresh Active Directory policy on a test device, run gpupdate /force.
Choose one update authority—or define the hybrid clearly
Edge self-updates
Edge Update handles browser servicing. This is a good fit when rapid security updates and lower ConfigMgr administration matter more than scheduling every release into a specific ConfigMgr window. ConfigMgr may still provide inventory, but exact rollout timing is less controlled.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
- VIVID COLORS: Experience stunning colors across the entire display with the IPS panel. Colors remain bright and clear across the screen, even when you change angles. Tones and shades are represented consistently and beautifully with less color washing.
- SMOOTH PERFORMANCE: Stay in the action when playing games, watching videos, or working on creative projects. The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments.¹
- MORE GAMING POWER: Gain a competitive edge with optimizable game settings. Color and image contrast can be instantly adjusted to see scenes more clearly, while Game Mode adjusts any game to fill your screen with every detail in view.
- EASY ON THE EYES: Protect your vision and stay comfortable, even during long sessions. Stay focused on your work with reduced blue light and screen flicker.²
- A MODERN AESTHETIC: Featuring a super-slim design with ultra-thin border bezels, this monitor enhances any setup with a sleek, modern look. Enjoy a lightweight and stylish addition to any environment.
ConfigMgr-managed updates
ConfigMgr provides approval, deployment rings, scheduling, and software-update reporting within an existing on-premises management estate. It depends on SUP/WSUS synchronization, content distribution, client health, and policy settings that do not undermine the intended update process.
Intune or a hybrid model
Intune can configure Edge policies for cloud-managed or co-managed devices, but moving the management plane does not by itself determine whether Edge self-updates or follows a controlled deployment workflow. A hybrid can leave native Edge updating enabled for most devices while using ConfigMgr or another process for selected groups; document which authority governs each group to avoid conflicting policies.
For organizations with a mature ConfigMgr deployment, native software updates are a reasonable fit for controlled Edge rollouts. Cloud-managed environments may prefer Intune policy and an explicitly chosen update model. Third-party patch-management platforms are most defensible when the need extends to broad third-party application catalogs, packaging, or remediation—not merely because Edge needs patches. Ensure overlapping ADRs, Edge Update policies, Intune assignments, and any external patch tool have a clear precedence.
Why older SCCM Edge guides need a date check
The HTMD article associated with this topic was published July 18, 2024, and its examples show Edge 79 builds, including 79.0.309.65. Those are historical examples, not current patch targets. Its title also labels it Part 1 and points toward a separate client-side deployment discussion; the workflow above includes the rollout and validation steps needed to take synchronized metadata through deployment. Read the original HTMD article. ConfigMgr 1910 references in older Edge installation material describe historical feature context, not a current-branch prerequisite: HTMD’s Edge installation article.
Do not use legacy operating-system examples as a current support recommendation. Microsoft notes that products beyond their support lifecycle are not supported for use with ConfigMgr, even though the latest current branch may still deploy certain ESU updates. Check the applicable product support lifecycle and current ConfigMgr documentation before including legacy devices. Microsoft’s product and classification guidance.
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.
