Edge Sync stuck in Initializing with Backend Uninitialized
Hello, I am hoping to get feedback from people familiar with Edge Sync internals, synchronization failures, or similar cases. OVERVIEW Around October 13, 2026, I discovered that my Favorites and saved Passwords were no longer visible in Microsoft Edge. The issue is present on both my desktop PC and my laptop using the same personal Microsoft account. Approximately two weeks later, the issue remains unchanged. What makes this case unusual is that authentication appears to work correctly, Edge Sync servers respond successfully, and encryption keys download successfully, yet the sync engine never completes initialization. ENVIRONMENT Microsoft Edge Windows 11 Personal Microsoft account Desktop PC Laptop The same symptoms occur on both devices. SYNC INTERNALS edge://sync-internals consistently reports: Transport State = Initializing Sync Engine State = Stopped Backend Status = Uninitialized Sync Feature Enabled = True Bookmarks = 0 Passwords = 0 Additional values: Download Key Result = Fail Set Key Result = Fail SIGN-IN STATUS edge://signin-internals reports: Successful authentication Successful token retrieval No authentication errors There is no indication of a Microsoft account sign-in problem. SYNC DIAGNOSTICS sync_diagnostic.log repeatedly shows: SyncState after authenticated = FeatureCanStart Try to start sync engine Load and connect Nigori controller Update key data credentials Reset engine The sync engine repeatedly attempts initialization but never reaches a running state. SERVER COMMUNICATION cv_debug.log reports: SYNC_SERVER_OK EncryptionKeysFetcher.DownloadKeys = Success Key count = 10 SetEncryptionKeys = Success This confirms that sync servers respond and encryption keys can be downloaded successfully. One unusual observation is that Sync Internals reports: Download Key Result = Fail Set Key Result = Fail while the logs simultaneously report successful key download and processing. PROFILE VERIFICATION Active profile: ...\Microsoft\Edge\User Data\Default During troubleshooting, a file named "Bookmarks" could not be located within the active profile. The following sync-related components remain present: Sync Data LevelDB Nigori.bin Logs MULTI-DEVICE IMPACT The same behavior is present on both desktop and laptop using the same Microsoft account. This makes a single-device profile corruption scenario seem less likely. NEW OBSERVATION After the initial failure, I created a new Favorites folder named: After Edge Sync Failure 20261013 The folder appeared correctly in the Favorites Bar. After Microsoft Edge and Windows were closed and restarted, the folder was no longer present. This suggests the issue may still be actively affecting local Favorites persistence and is not limited to historical sync data. ACTIONS NOT PERFORMED Based on recommendations received in Microsoft Q&A, I have intentionally avoided: Reset Sync Deleting the Edge profile Clearing all Edge data Reinstalling Edge The goal has been to avoid overwriting potentially recoverable sync data. PRIMARY QUESTION My main question is not whether synchronization currently works. My main question is whether the original Favorites and Password records may still exist within the Edge Sync service and whether there is any supported way to determine that before attempting potentially destructive recovery actions. QUESTIONS Has anyone seen this exact combination of Transport State = Initializing, Sync Engine State = Stopped, and Backend Status = Uninitialized persisting for weeks? Can a corrupted Nigori or encryption-key state cause Favorites and Passwords to report zero items despite successful authentication and successful key download? Has anyone recovered Favorites or Passwords after a similar state? Is there any supported method to determine whether the original sync data still exists on the sync backend before attempting Reset Sync? Does this pattern suggest an account-level sync corruption, backend corruption, or another known Edge Sync failure mode? Any technical insight would be greatly appreciated. Thank you.Autosave steals focus when typing in Outcome pane
When typing in the "new Outcome" pane, the focus is stolen every few keystrokes. This appears to correlate with the autosave triggering. Discovery version: 0.15.20 OS: Windows 11 To replicate: - Define a purpose. - Create a new outcome. - Type into the "Statement" field.
File History problems after installing KB5124008, KB5126052,KB5126146, KB5122878, and KB890830
This morning, I ran Windows Update on two Windows 10/11 computers, but the file history feature stopped working completely after the update. Previously, after updating KB5120249 and KB5101684, files could still be backed up to the D: drive normally. The "Last Backup" time in "File History" is not updating correctly. Newly created or saved Word documents, pictures, videos, etc., still show "No previous version available" in "Content → Previous Versions". No folders were corrected; their dates are automatically updated. After running Windows Update again today, the file history feature stopped working on both computers. The File History panel pops up but cannot be used, prompting for a hard drive connection. (The hard drive is connected and I've confirmed it can read and write.) resulting in an "InconsistentState" entry in C:\Users\User\AppData\Local\Microsoft\Windows\FileHistory\Configuration. I'm very angry. If Microsoft doesn't address this, I'll keep complaining. If anyone else has encountered the same situation, please leave a comment below. You can also check Microsoft Q&A or the Microsoft Community Hub. The five updates installed are: September 8, 2026—KB5122878 (OS Builds 19045.7725 and 19044.7725) September 8, 2026-KB5126146 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 2026-09 Security Update (KB5124008) (26200.9445) 2026-09 .NET Framework Security Update (KB5126052) Windows Malicious Software Removal Tool x64 - v5.145 (KB890830) Deleting the %LocalAppData%\Microsoft\Windows\FileHistory folder also failed. Furthermore, "File History" itself is not listed in Microsoft's "Deprecated Features List." While other backup features suggest that Microsoft has no plans to discontinue it. Microsoft is going to pretend it doesn't exist. These worked normally before the update but stopped working afterward. This is to inform other users experiencing the same problem.
RDCMan v3.21 crashing
Getting the following error System.NullReferenceException: Object reference not set to an instance of an object. at RDCMan.Nodes.Server.Dock() at RdcMan.ServerForm.OnClosed(EventArgs e) at System.Windows.Forms.Form.WmClose(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at RdcMan.RdcBaseForm.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(HWND hWnd, UInt32 msg, WPARAM wparam, LPARAM lparam) The error seems to happen when I have an undocked session, I restart the remote machine on the the undocked window, and it stays open, when I try to reconnect, on the same undocked window, it opens another docked session, I can login to the new session, and undock it, so now I have two undocked windows, the old one (disconnected) and the new one. I try to close the old one and I get the error shown below, (details above). If I click Continue, nothing happens, if I hit Quit, it closes RDCMan, as stated in the window.To Do: scrolling bug
You can’t scroll all the way down in longer notes anymore in the Android app. The keyboard covers part of the note. I already tried to update it an reinstall it. Many users have this problem. This makes the app almost unusable. I'm on OneUi 7. I attached a screenshot with a transparent keyboard.
Microsoft Edge PDF Reader - signature validation warning for official signatures
Since the last edge update we are running into the following issue, which triggers support tickets on our side. It seems that the edge internal PDF Reader now supports validation of digital PDF signatures. This new feature however is incomplete and causes a lot of confusion for edge users. "Official" signatures are labeled as "Unknown Signature" and "The validity of the signature is still unknown": "Official signatures" means qualified signatures from members of the EUTL - the European trust list as defined in ETSI TS 119 612 („Trusted Lists“): [...] the European Commission publishes a central list with links to the locations where the national trusted lists are published as notified by Member States. This central list, called the List Of Trusted Lists (LOTL), is available in both a human readable format and in a format suitable for automated (machine) processing XML. Parts of the edge PDF reader seems to come from *dobe itself which adds additional confusion since in their products (*dobe reader, acrobat etc) the signatures are correctly verified. They support this list for several years now (next to their own AATL list). I tried to find out whether this feature is 'work-in-progress' or it is a bug however the last published roadmap is quite old and doesn't give helpful information regarding this aspect. So my question is: Is full support of PDF signature validation including support of the EUTL planned and if so when?sigcheck64 2.92 output in UNICODE instead ANSI
Hi I Upgrade sigcheck64 from 2.90 to 2.92. Now lot of scripts can't evaluate the version of an exe. I redirect the output from sigcheck64.exe -AcceptEULA -nobanner -n excel.exe to a file and see that the file is unicode. with 2.90 it works fine. FOR /F %i IN ('sigcheck64.exe excel.exe') DO ECHO %i results in 1 instead 16.0..... Can you fix this soon?
