android, bug, address, bar, bottom
1 TopicEdge 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.27Views0likes0CommentsCritical 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.98Views0likes5CommentsUI overflow in extension permission dialog on Linux (Gnome)
When installing an extension, the permission dialog renders incorrectly and overflows its container. The dialog content appears clipped and does not scale properly within the window. This affects usability because parts of the UI (text/buttons) may be partially hidden depending on window size and display scaling. MS Edge version: Version 149.0.3993.0 (Official build) dev (64-bit) To reproduce: Open Microsoft Edge on any Linux distro using Gnome Navigate to the extension store Attempt to install an extension (e.g. AdGuard AdBlocker) Observe the permission popup dialog75Views0likes1CommentBookmarks are being forced into the active Tab Group (New behavior)
Hi there, I’ve noticed a very frustrating change in the latest Edge update. When I open a bookmark from the Favorites bar, it is now automatically forced into the currently active Tab Group. This behavior is counter-intuitive. For example, if I am browsing in a "Social" group and click a bookmark for "Gmail," I want it to open as a standalone tab, not as a part of the "Social" group. Currently, I have to manually drag every new tab out of the group, which is a major workflow killer. Disabling experimental flags doesn't fix this anymore. Please provide a toggle in the Settings menu to disable "Tab Group Inheritance" for bookmarks or revert this change. It should be the user's choice whether to add a new tab to a group or not.64Views0likes0CommentsMS Edge - Sidebar and copilot not working on Linux Ubuntu v24 LTS
Sidebar not syncing or accepting new app additions (+). Copilot button is dead/inactive. Sidebar settings are well configured. Using the latest version of the Ubuntu OS and MS Edge. Functionality appears to be absent as product was released without full functionality....Lame!27KViews45likes59CommentsMedia Player theme bugged
Noticed that the past couple of Dev builds have a broken media player where the theme is all black and it also looks like the layout is bugged, see screenshot below. I've also submitted feedback with a screen recording but wanted to see if anyone else was experiencing this.70Views0likes1CommentAzure Tiles Not loading with MS Edge Beta v147.0.3912.16
In the latest version of MS Edge, we cannot view or access the SAML Certificate data for Enterprise Applications hosted in Entra ID. Before: (v146.0.3856.62) After updating to v147.0.3912.16: As can be seen, the certificates cannot be displayed or accessed from this tile. This is affecting our test users who cannot rotate their SAML certificates but may have other impact for other Azure resources being accessed with MS Edge Beta.Solved97Views0likes2Comments