Forum Widgets
Latest Discussions
[Feature Request] Edge for Business-Extension Policy-blank minimum version breaks ExtensionSettings.
Hi, I have a Core Edge for Business policy, where I manage settings and extensions for majority of users in my company. I was adding an extension to it to Allow an extension being installed. By default when You choose extension from a store it is getting added to GUI with setting "Allow". After that when I edit entry for this addon and tried to add minimum version (8.6 in Edge store, while schema is #.#.#) I decided not to add it to not overcomplex settings. I have saved the settings. Few second later all my extensions were gone, some users reported same problems. Luckly I have quickly reverted the changes so policies did not update for everyone. Replication steps: Under Edge://policy I have identified that ExtensionSettings report Error: Error at ExtensionSettings.hfaciehifhdcgoolaejkoncjciicbemc.minimum_version_required: Schema validation error: Invalid value for string Json shows: "hfaciehifhdcgoolaejkoncjciicbemc": { "installation_mode": "allowed", "minimum_version_required": "", "override_update_url": false, "toolbar_state": "default_hidden" }, In GUI there is no clue about it, looks like not configured, when saving all goes "green". Extensions are getting uninstalled. Once reverted some extensions are back and require reconfiguration. I.e. Passsbolt asks for recovery key. Please if possible add a feature to validate such settings to not allow saving : "minimum_version_required": "" as in some cases in production it might be a nightmire ( Imagine reconfiguring ## addons times #### Users ).
Edge >=150 blocks ALL extensions on *.cloud.microsoft (regression from 149) - no policy override
Starting with Edge 150, a hardcoded extension blocklist applies to *.cloud.microsoft (M365 Copilot and Microsoft 365 app surfaces). Extensions no longer run on these pages. This is a regression - on Edge 149 and earlier it worked fine on the same pages. The block affects all extensions, not a specific category, and it is not overridable via ExtensionSettings (runtime_allowed_hosts), ExtensionInstallForcelist, or any other policy we have tested. It hits both regular user-installed extensions and admin-approved, force-installed extensions on managed devices - so admins have no way to re-enable trusted extensions on these surfaces either. Confirmed breakage so far: - Password managers - verified with Bitwarden (users end up copy/pasting credentials out of the manager on Copilot pages, a real security regression) - Corporate training / user-adoption extensions - Accessibility extensions relied on by employees Ask to the Edge team: restore the pre-150 behavior, or ship an override so extensions can run on *.cloud.microsoft pages (for example, honor runtime_allowed_hosts / the force-install list on these surfaces). If this is by design, please document it clearly so users and admins stop chasing a config that cannot work. Environment: Edge Stable >=150 (works on 149 and earlier), Windows, both unmanaged and MDM-managed (Intune/GPO). Reproducible on a clean profile with a single extension. Are other users / admins / extension vendors seeing the same thing after updating to 150? Please add your affected extension below so Microsoft can gauge the blast radius.
Edge Dev Version 149.0.3984.0 (Official build) dev (64-bit) Update
Got this update on Edge Dev today, immediately thereafter its locked up my pc after it applied and i went to open a new tab (had to ctrl+alt+del and end task it) its something specific here as edge stable and beta still work. unsure what's changed or if others have the same issue? diving into logs in just a sec...
BrowserCodeIntegritySetting vs. Memory integrity / HVCI
Hello all, we have set BrowserCodeIntegritySetting to '2' (Enabled: Enable code integrity guard enforcement in the browser process.) This causes the browser to crash once a user tries to logon to Citrix terminal servers with EntraID/Fido2. This is probably cased by an unsigned Citrix CtxFidoMuxdll, but from our understanding this should be properly handled and the browser should not just crash. While investigating the root cause, we found very few information about Code Integrity Guard. It seems it was shipped as part of Device Guard but nowadays is named Memory integrity or hypervisor-protected code integrity (HVCI) and independent from Device Guard. Is this understanding correct and can we expect that the feature name will be updated and a proper documentation will be added? BR, JoeWhat is EdgeSafeHostingExtensionEnabled about?
Hello, with v145 the EdgeSafeHostingExtensionEnabled policy was introduced. The description says, "Microsoft Edge Safe Hosting component extension is installed automatically when users visit supported Microsoft services, such as Microsoft 365 Copilot app." Is this a regular browser extension? If so, what is the related Extension ID? How does this combine with other extension management policies? Or is it a browser component, which should show up under edge://components? What would be its name? What is the exact purpose of "Microsoft Edge Safe Hosting component" extension? Thanks for any hints. BR JoeQuestion: Windows Enterprise / EDU Version - End of Life (EOL) Notification
Hello Microsoft Community - Enterprise, i have a general question about the Windows Enterprise / EDU Version and the End of Life (EOL) notification . I have a general question about End of Life (EOL) and the notification process. Could someone please explain and tell me exactly how is the notification process for Windows EOL in the Enterprise/EDU version? My understanding is this: For the Windows Home version, the notification is given 30 days in advance, see below. But what about the Enterprise/EDU version? Is it 36 months in advance? For products and services governed by the https://learn.microsoft.com/en-us/lifecycle/policies/modern, unless otherwise noted, Microsoft's policy is to provide a minimum 30 days' notification when customers are required to take action in order to avoid significant degradation to the normal use of the product or service. I would appreciate your help.
Edge browser crashes after file download / open
Hello, I am using Edge browser Version 142.0.3595.80 (Official build) (64-bit), on Linux. When downloading a file , and trying to open the downloaded file from wihin browser, it causes edge browser instances to close. I have been using other browsers to get around the problem. Is this a known problem, and are there a solution to this problem? Thanks, JayMy Work feed is missing on the Edge landig page with Beta 144.0.3719.18
Since introduction of Beta 144.0.3719.18 the Work / Discover is changed to Discover only on the landingpage. See below: This means that the handy Microsoft 365 information are missing (Latest documents, Sharepoint sites and comming up events). Stable version 143.0.3650.96 does not have this issue, next to MSN there is a toggle (Work Discover) to choose from. More people seen this behaviour? Regards, Henno
