<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Edge on Aperture Zone</title>
    <link>https://aperturezone.com/tags/edge/</link>
    <description>Recent content in Edge on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/edge/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GPO - Neutralize Edge</title>
      <link>https://aperturezone.com/gpo/kill-edge/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/gpo/kill-edge/</guid>
      <description>&lt;p&gt;Let’s be honest: Edge isn’t terrible as a browser. What’s terrible is its &lt;em&gt;behavior&lt;/em&gt; in a managed environment.
It’s a browser we didn’t choose, one that imposes itself on every new user profile, and runs background services for no reason.
With every new user profile, Edge imposes itself as the default browser. Its &lt;code&gt;edgeupdate&lt;/code&gt; and &lt;code&gt;edgeupdatem&lt;/code&gt; services run constantly in the background, even on machines where no one has opened Edge. Its scheduled tasks restart after certain updates. And if you use Chrome, Opera, Firefox, or any other browser as your default, you have to reconfigure this on every new profile.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
