Forum Widgets
Latest Discussions
PWA shortcuts don't keep asociated with window - Linux
I recently upgraded to version140.0.3485.14 (Official build) beta (64-bit) and noticed that my PWA, even if they open correctly in a independent window, don't show the "running window counter" on the taskbar. So, for example, if a open Outlook, the window open and loads the app, but if a I click the icon again, it opens another window, wich is a little annoying. I tried removing the PWA from Edge, rebooting, and installing again, but didn't work. Because the only change I made is updating Edge, I think is related to this build. (too lazy to go back or install the stable release)Light - Lite version of Edge
Is there a light-lite version of MS Edge? if not, could one be made as it takes some time/forever to load, with that annoying "wait/leave" notice that keeps popping up. Cut out most of the add ones like PDF reader etc., and let the user add his/her own choice. Keep it small and faster then at present. WinEdge Dev on Windows - Tab sync not working
Just wondering if anyone else is seeing a bug where on Windows and Edge Dev (latest version), tab sync just says "No tabs from other devices". But if you go to Edge Stable, it does show open tabs. It also shows my recent tabs with Edge Dev on Android, so I know the sync is working, just the desktop client is not showing them. I've sent feedback for this issue but since sync is still working correctly, I am wondering if this is a UI bug.
MS Edge use of file:// protocol in script and link tags
I'm trying to view an html file that exists on my hard drive. I have <SCRIPT> and<LINK> tags with relative addresses to files (stylesheets and scripts) in the folder (and subfolders) that contains the html file. OOTB Edge errors in the console attempting a GET for these files. Is there a way, perhaps via Internet Options, to override this behavior and access the additional files from my hard drive? I'm not interested in a webpage self-hosting solution. Thanks in advance for any insight you can provide.
Edge Password Manager keeps passwords cleartext at runtime — misaligned with Chromium (CWE-316)
Microsoft Edge is a strong Chromium‑based browser, and its Password Manager is promoted as a secure, integrated solution. However, its current runtime behavior prevents adoption: saved passwords remain available in cleartext during the entire Edge session, even when they are not actively used. This differs from the Chromium / Chrome model, where credentials are decrypted only on demand and cleared afterward. Importantly, the device does not need to be “fully compromised”: a standard user‑mode process, using common Windows APIs and tooling that often bypass traditional antivirus detection, can extract all stored credentials from the running Edge process. Chromium / Chrome already addresses this by combining DPAPI (user scope), App‑Bound Encryption, and process‑to‑process protections, ensuring passwords are decrypted only on demand and not kept continuously available at runtime. Request: please align Edge Password Manager runtime behavior with the Chromium model: decrypt passwords only when needed avoid keeping unused credentials available in cleartext This would close a significant gap with Chromium and remove an important blocker to real‑world adoption, without impacting user experience.
Export tool for Edge Collections before deprecation
Microsoft is deprecating the 'Collections' feature in Edge, but there is currently no export option available for personal Microsoft accounts. This creates a serious problem for users who rely heavily on Collections for research, organization, and long‑term workflows. In my case, I have 166 main Collections, each containing dozens of items. Migrating this manually is simply impossible/undoable. ‼️ Please Microsoft: provide an official export tool (HTML, JSON, or migration to Favorites/Bing Saves) before removing the feature. Without this, users risk losing years of structured work and saved content. This is essential for anyone who has used Collections as a core part of their workflow.
Critical Edge Sync issue after Win11Pro reinstall – incomplete rehydration
A - ENGLISH VERSION Critical Edge Sync issue after Windows 11 Pro reinstall – incomplete rehydration, Device Info = 5, modules stuck Hello, I am experiencing a major issue with Microsoft Edge synchronization after a full reinstall of Windows 11 Pro. Despite multiple reinstalls, several days of waiting, and all possible local troubleshooting steps, Edge Sync remains incomplete, and none of my historical data is rehydrated. Below is the full context, timeline, symptoms, technical observations, and questions. 1) Full chronological context 1.1 – Full PC reset Clean Windows 11 Pro reinstall Sign‑in with Microsoft personal account Windows Insider Program activated (Beta channel) 1.2 – Edge Beta installed automatically Edge Beta was installed automatically without warning. I suspected it might be the cause of the incomplete sync. 1.3 – Leaving the Insider Program I left Insider only to try restoring full Edge synchronization. 1.4 – New Windows 11 Pro 25H2v2 reinstall Clean install Edge Stable installed Sync enabled Several days of waiting 1.5 – Result: sync still incomplete Even on Edge Stable, historical data never returns. 2) Symptoms 2.1 – Missing data No previous tab groups restored Incomplete history “Other devices” sessions missing Passwords visible in settings but not rehydrated No data from my previous Windows 11 PC 2.2 – Sync modules stuck In edge://sync-internals: Saved Tab Group: frozen for days Passwords: “Running” but no data rehydrated Sessions: incomplete Typed URLs / History: partial 2.3 – Device Info = 5 The cloud still lists 5 devices, including my previous Windows 11 installation. This indicates that historical data should be available. 2.4 – Last Synced active Sync is active, but missing data is never returned. 3) Technical diagnosis Everything points to a “consistent but incomplete” cloud profile state: Client sync works Server reports sync as healthy Historical data is never rehydrated Critical modules remain stuck Issue reproduces across multiple devices (Win10, Win11) This suggests a server‑side Edge Sync profile corruption, or a metadata divergence after: Insider → Stable channel change Windows reinstall Local profile deletion Edge Beta auto‑installation Microsoft account reconnection 4) Key question: Is Edge Beta limited in synchronization? I would like an official clarification: → Does Edge Beta restrict any sync modules? → Are Saved Tab Group, Sessions, or Passwords limited in Edge Beta? → Are there backend differences between Edge Stable and Edge Beta? If Edge Beta is not the cause, I will gladly re‑enable my Insider profile. I left Insider only to attempt restoring full sync. 5) Request I kindly request: → A backend analysis of my Edge Sync profile, to check: metadata integrity module states device list consistency possible corruption ability to rehydrate historical data I can provide: sync‑internals screenshots logs additional details multi‑device testing Thank you very much for your help. B - VERSION FRANÇAISE Problème critique de synchronisation Edge après réinstallation Windows 11 Pro – réhydratation incomplète, Device Info = 5, modules bloqués Bonjour, Je rencontre un problème majeur avec la synchronisation Microsoft Edge, apparu après une réinitialisation complète de mon PC Windows 11 Pro. Malgré plusieurs réinstallations, plusieurs jours d’attente, et toutes les procédures locales possibles, la synchronisation reste incomplète, et mes données antérieures ne sont jamais réhydratées. Je détaille ci‑dessous l’ensemble du contexte, les étapes, les symptômes, les observations techniques et les questions. 1) Contexte chronologique complet 1.1 – Réinitialisation complète du PC Réinstallation Windows 11 Pro “vierge” Connexion au compte Microsoft personnel Activation du programme Windows Insider (canal Bêta) 1.2 – Edge Bêta installé automatiquement Sans avertissement ni information, Edge Bêta a été installé automatiquement sur mon système Insider. Pensant que Edge Bêta pouvait être la cause d’une synchronisation incomplète, j’ai tenté de revenir à Edge Stable. 1.3 – Sortie du programme Insider J’ai quitté le programme Insider uniquement pour tenter de retrouver une synchronisation Edge stable et complète. 1.4 – Nouvelle réinstallation Windows 11 Pro 25H2v2 Installation propre Edge Stable installé automatiquement Synchronisation activée Plusieurs jours d’attente pour réhydratation 1.5 – Résultat : synchronisation toujours incomplète Même après retour à Edge Stable, les données antérieures ne reviennent pas. 2) Symptômes observés 2.1 – Données manquantes Aucun groupe d’onglets antérieur n’est restauré Historique incomplet Sessions “Autres appareils” très partielles Mots de passe visibles dans les paramètres mais non réhydratés dans l’interface Données provenant de mon ancien PC Windows 11 absentes 2.2 – Modules Edge Sync bloqués Dans edge://sync-internals : Saved Tab Group : valeur figée depuis plusieurs jours Passwords : module “Running” mais aucune donnée réhydratée Sessions : incomplètes Typed URLs / History : partiels 2.3 – Device Info = 5 Le cloud conserve encore les identifiants de 5 appareils : PC Windows 10 Smartphone PC Windows 11 actuel PC Windows 11 avant réinstallation PC Windows 11 Insider (Edge Bêta) Cela prouve que les données de l’ancien appareil devraient être disponibles, mais ne sont pas renvoyées au client. 2.4 – Last Synced actif La synchronisation est active, mais ne renvoie pas les données manquantes. 3) Diagnostic technique Tout indique un état “cohérent mais incomplet” du profil cloud Edge : Le client synchronise correctement Le serveur considère la synchronisation comme valide Mais les données historiques ne sont jamais renvoyées Les modules critiques (Saved Tab Group, Passwords, Sessions) restent bloqués Le problème est identique sur plusieurs appareils (Win10, Win11) Cela suggère une corruption du profil Edge Sync côté serveur, ou une divergence entre métadonnées locales et cloud après : changement de canal (Insider → Stable) réinstallation Windows suppression du profil local Edge Bêta imposé réactivation du compte Microsoft 4) Question cruciale : Edge Bêta est‑il bridé dans la synchronisation ? Je souhaite obtenir une réponse officielle : → Edge Bêta limite‑t‑il certaines fonctions de synchronisation ? → Certains modules (Saved Tab Group, Sessions, Passwords) sont‑ils restreints dans Edge Bêta ? → Existe‑t‑il des différences de backend entre Edge Stable et Edge Bêta ? Si Edge Bêta n’est pas en cause, je serai heureux de réactiver mon profil Insider. J’ai quitté Insider uniquement dans l’espoir de retrouver une synchronisation complète. 5) Demande Je sollicite : → Une analyse backend de mon profil de synchronisation Edge pour vérifier : l’intégrité des métadonnées l’état des modules la cohérence des appareils la présence ou non d’une corruption la possibilité de réhydrater les données historiques Je suis prêt à fournir : captures edge://sync-internals journaux détails supplémentaires tests sur plusieurs appareils Merci d’avance pour votre aide.
