bug
354 TopicsBug: Autoruns 14.3 opens in Light mode when “Use System Setting” is selected and Windows is Dark
Autoruns 14.3 opens in Light mode when “Use System Setting” is selected and Windows is Dark Environment: Windows 11 25H2, build 26220.9836. Reproduced with both Autoruns.exe and Autoruns64.exe version 14.3. The debugger trace below is from Autoruns64.exe. Steps to reproduce In Windows Settings → Personalization → Colors, set Choose your mode to Dark. Open Autoruns and select Options → Theme → Use System Setting. Close Autoruns completely and reopen it. Expected: Autoruns opens in Dark mode, following the Windows app theme. Actual: Autoruns opens in Light mode. Selecting Options → Theme → Dark explicitly displays the dark theme. Debugger trace I captured these calls in order during a fresh launch with Use System Setting selected. The excerpt omits unrelated debugger output. TRACE CALL SetPreferredAppMode mode=3 caller=Autoruns64+0x17332 TRACE RETURN SetPreferredAppMode 0 TRACE CALL ShouldAppsUseDarkMode caller=Autoruns64+0x34a36 TRACE RETURN ShouldAppsUseDarkMode 0 Mode 3 is ForceLight. Autoruns applies that process-level override before asking ShouldAppsUseDarkMode(), which returns 0 (false). A separate Process Monitor capture confirmed that reads of the Windows AppsUseLightTheme setting succeeded and returned 0 (Dark). https://github.com/microsoft/PowerToys/blob/main/src/modules/ZoomIt/ZoomIt/Utility.cpp#L2066-L2090 I ran the same API sequence in a separate test process on the same machine. ShouldAppsUseDarkMode() returned true before ForceLight, false while the override was active, and true again after restoring the previous process mode. This suggests that Autoruns’ Use System Setting check is reading the effect of its own override.50Views0likes0Comments[BUG] Edge Beta repeatedly loses 16 extensions and resets preferences after restart
I am reporting a recurring, destructive Microsoft Edge Beta profile-integrity problem that has occurred twice within ten days, across two different Beta builds. I have already submitted the issue through Edge's built-in feedback mechanism. I am posting here to request additional technical guidance and, if possible, review by the Edge engineering teams responsible for profile preferences and extension management. Environment Operating system: Microsoft Windows Browser channel: Microsoft Edge Beta Affected profile: Existing Default profile October 13, 2026: Edge Beta 156.0.4314.15 October 23, 2026: Edge Beta 157.0.4341.10 Previously installed extensions: 16 Incident history October 13, 2026 Following a Windows restart, the existing Edge Beta profile exhibited significant configuration changes. All 16 previously installed extensions lost their registrations, and the corresponding installed extension packages were absent. Forensic examination identified substantial changes involving the profile's Preferences and Secure Preferences files, with relevant file activity around 10:53 EDT. The browser profile required extensive recovery. October 23, 2026 A second, similar failure occurred after another Windows restart, this time with Edge Beta 157.0.4341.10. Again, none of the 16 original extension registrations remained. Most associated extension installation directories were missing. Existing windows and tabs survived, but extension functionality and website authentication sessions were adversely affected. Relevant changes were identified around 18:20 EDT. Expected behavior Windows restarts and Edge Beta updates should preserve the existing browser profile, installed extensions, extension registrations, and user preferences unless changes are explicitly requested or required by documented behavior. Actual behavior Critical portions of the existing Edge Beta profile configuration are unexpectedly removed or reset. This is not merely an extension toolbar visibility issue. The underlying extension registration state changes, and installed extension packages are missing. Recovery has required restoring or reconstructing substantial portions of the affected browser environment. Reproduction and investigation status Both incidents were discovered following Windows restarts. The behavior is intermittent, and I do not currently have a reliable reproduction procedure. I have not established whether the initiating mechanism involves Edge startup, profile migration, a Beta update, preference integrity handling, Sync, an external process, or another cause. I am not attributing the changes to any particular component without supporting evidence. Preserved evidence I have preserved historical profile snapshots and collected technical evidence, including: Failed and recovered profile snapshots Profile file timestamps and selected SHA-256 hashes Extension registration and installation-state comparisons Preferences and Secure Preferences observations Filesystem-journal findings A documented timeline for both incidents An independently verified recovered profile contains all 16 original extension registrations and packages. A sanitized engineering evidence package has also been prepared. Sensitive browser databases, credentials, cookies, authentication material, and raw preference files have been excluded from that package. Request to Microsoft Edge engineering I would appreciate assistance with the following: Are there known Edge Beta or Chromium issues that could account for the removal of existing extension registrations and substantial protected-preference changes following a restart? What Edge diagnostic logs or telemetry would help distinguish a profile migration, preference-integrity reset, Sync action, extension-management action, or external modification? Is there a recommended method for identifying the process or component responsible if the problem recurs? Is there a private, secure mechanism for providing sanitized forensic evidence and potentially sensitive technical artifacts to the appropriate engineering team? Can this recurring profile-integrity issue be associated with an engineering investigation or tracked support case? This has occurred across two successive Beta versions and has caused substantial loss of browser configuration and extension functionality. I would welcome guidance that helps identify the initiating cause rather than simply resetting or recreating the affected profile.130Views1like2CommentsEdge sync fails after restart — MSA key error
Edge sync works after signing in, but gets stuck on “Initializing” after reopening — persists after Windows repair and testing with a new Windows user Hi everyone, Microsoft Support suggested that I post here for further help. My personal Microsoft account syncs successfully when I first sign in to Edge. However, after closing and reopening the browser, sync gets stuck on “Initializing” / “Setting up sync.” Signing in again can temporarily restore it, but the problem returns after restarting Edge. The issue also reproduces under a newly created Windows local user account. Environment Microsoft Edge: 156.0.4314.58 Windows 11 Home China, version 26H2, build 26300.9711, 64-bit Account type: Personal Microsoft account (MSA), not a work or school account The same Microsoft account has been syncing successfully on my phone Steps to reproduce Sign in to Edge with my Microsoft account and enable sync. Sync works successfully. Close and reopen Edge. Sync remains stuck on “Initializing,” and all data types show “Not Running.” Current edge://sync-internals results Transport State: Initializing User Actionable Error: None Disable Reasons: None Sync Feature Enabled: true Setup In Progress: false Sync Consent: true Auth Error: OK since browser startup MainSyncToken: Last Token Request Result: OK Has Token: true Last Token Error: None KeyDataToken: Last Token Request Result: OK Has Token: true Last Token Error: None MSA Account Key Status: Download Key Result: Fail Set Key Result: Fail Net Error Code: n/a HTTP Response Code: n/a Process Key Result: n/a Encryption: Cryptographer Ready To Encrypt: false Cryptographer Has Pending Keys: true Has Keystore Key: false Passphrase Required: false Passphrase Type: kKeystorePassphrase Server Connection: not attempted Sync Engine: Backend Status: Initialized BlockReason: None Syncer: Unset DataType Manager: Stopped All data types: Not Running Updates Downloaded / Successful Commits: 0 No enabled sync-blocking policies are shown. Troubleshooting already completed Tested with a separate Edge user-data directory: initial sign-in synced successfully, but reopening reproduced the issue. Tested with extensions disabled: no improvement. Tested the separate Edge instance with --no-proxy-server: no improvement. This does not rule out system-level network filtering. Tested --enable-features=msForceOneAuthWAM: no improvement, although I did not independently verify whether the authentication library actually switched. Tried stopping sync while keeping data, then enabling it again: no improvement. Completed DISM repair successfully. Subsequent SFC and component-store checks reported no remaining corruption. Completed a Windows ISO in-place repair, keeping personal files and applications: the sync problem persisted. Created a new standard Windows local user and tested Edge there: first sync succeeded, but reopening Edge reproduced the same failure. Authentication tokens appear to be obtained successfully, while the sync encryption-key stage remains unsuccessful. I understand that the n/a HTTP and network fields do not establish whether a request was sent or rejected. Questions Is this a known issue affecting personal-account sync in this Edge version? What diagnostic logs would help distinguish a startup/key-loading problem from an account-side sync issue? Is there a supported workaround or fix that preserves existing browser data and cloud sync data? I can provide additional sanitized diagnostics. I would prefer to avoid further profile deletion or cloud-sync resets unless the logs indicate that they are necessary. Thank you for your help.274Views2likes3CommentsAutosave 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.Cloudflare captcha endless loop
Just wondering if anyone is experiencing the issue on Edge Dev 158.0.4344.0 or higher where Cloudflare captcha verification is stuck in an endless loop? It still works on Edge stable. You can check on this site: https://debug.challenges.cloudflare.com/ The verification on Edge Dev fails with Error: 600010 (Unknown) but will pass successfully on Edge stable.Solved661Views0likes11CommentsCritical Pen Hover & Stray Ink Issue on New Surface Pro 11 for Business with Slim Pen 2
Hello Microsoft Community and Support Staff, I am writing to report a critical and seemingly widespread issue with the pen input on the brand-new Surface Pro for Business, 13-inch (Intel model, often called Surface Pro 11 "Luna Lake"). The Core Problem: Pen Draws Without Touching the Screen When using the Surface Slim Pen 2, the device begins to register ink input while the pen is still hovering a few millimeters above the screen. It does not require any physical contact or pressure. This "hover-inking" makes handwriting completely unusable. As I write, any time I lift the pen to start a new letter or stroke, the pen continues to draw a line as it moves through the air to its next position. This results in messy, connected handwriting with unwanted "tails," completely defeating the purpose of having a premium inking device. This is Not a Defective Unit - It's a Replicable Problem Initially, I thought I had a faulty device. However, to isolate the issue, I have performed extensive testing: I have personally tested this on [3] brand-new Surface Pro 11 (Intel) devices. I have used [4] different Slim Pen 2s. The exact same hover-inking problem occurred on every single combination of device and pen. Furthermore, I have already performed all standard troubleshooting steps, including: Clean OS installation via Surface Recovery Image. Ensuring all Windows, driver, and firmware updates are installed. Running the Surface Diagnostic Toolkit (which reported no errors). However, the same issue continues to occur even after trying these methods. Additionally, it has been reported that the issue also appears on the latest Surface Pro 12-inch model with the Snapdragon X Plus, just like on the Surface Pro 11 that uses the Qualcomm Snapdragon X Elite instead of Intel’s Lunar Lake. (I do not own any Snapdragon devices myself. If you own a Snapdragon device and are experiencing the same issue, please share your feedback.)" Video Evidence: I have recorded a clear video demonstrating the problem. It shows the pen drawing while hovering on the Surface Pro 11 and makes unwanted tails on handwriting letters. Video Link: https://youtube.com/playlist?list=PLG_7BXFA-cL4evqe0RmRz--iFjDC1HVgT&si=EmEypaAqSyRozr67 Questions for Microsoft: Is this a known issue with the new Surface Pro 11 (Intel) model's firmware or drivers? What are the official steps to escalate this issue directly to the Surface engineering team for a fix? This is a major flaw in a flagship product that severely impacts its core functionality. I have submitted a formal bug report through the Feedback Hub, which can be found here: Feedback Hub Link: https://aka.ms/AAxzh27 I urge the Microsoft team to investigate this with high priority and release a firmware or software update to recalibrate the pen's Initial Activation Force (IAF). Thank you for your attention to this serious matter.2KViews13likes10CommentsBug in RDS Web Client - Copied text in RD session improperly encoded
As the title describes, there appears to be a bug in the HTML5 web client for Remote Desktop Services. This bug is present in both 2.1.85.0 and 2.1.87.0, and possibly earlier. When text is copied to the clipboard within a remote session (tested via a published RemoteApp), the text will occasionally be stored into the clipboard of the local machine encoded in UTF-8 instead of UTF-16 as it is supposed to be. When pasted into an application on the client machine, the UTF-8 encoded text (stored as CF_UNICODETEXT) is interpreted as UTF-16 (as that's how it's supposed to be encoded in memory as that's what Windows uses internally), resulting in meaningless output/mojibake. As an example, the text "Given" is copied from a Remote Desktop session (via the web client). The endpoint has these formats on the clipboard: Copied text CF_UNICODETEXT hex (padded) CF_TEXT hex Decoded text - UTF-8 Decoded text - UTF-16LE Given 47 69 76 65 6E 00 00 00 3F 3F 6E 00 Given 楇敶n The behavior is seemingly random. Most of the time, text is copied without issue. Once out of every 5-10 times, however, the UTF-8 encoded text is incorrectly written to the clipboard. Some additional information about this behavior: It only happens when using the RDS web client. The native RDP client does not exhibit this behavior. This has only been observed on Windows clients. It hasn't been observed on other client platforms, but testing has been minimal. The client browser does not appear to factor into the bug. It has been observed in Edge, Chrome, and Firefox. The issue is unrelated to the text copied. The same text, from the same application, can produce both outcomes when copied. The application being pasted into seems to be irrelevant. Has anyone else seen this behavior?140Views0likes2CommentsAutoruns does not show services with long image paths
I was running Autoruns to confirm no unexpected services, and I noticed the Screenconnect instance I was connected through, is not in the list. Creating a new service with a long path gives the same result. Considering that Screenconnect is commonly abused, seeing Screenconnect services is important. I'm 99% sure I've seen Screenconnect in Autoruns before, so what changed now? Is it a change in Windows? The following reproduces the behavior with a test service (thanks, Claude): $long = 'x' * 3000 New-Service -Name 'ZZLongPathTest' -BinaryPathName ""C:\Windows\System32\notepad.exe" $long" -StartupType Automatic .\autorunsc64.exe -accepteula -nobanner -a s -ct | sls ZZLongPathTest115Views1like1CommentEdge 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.381Views0likes1Comment