Windows 11 File Explorer - User Profile Contacts directory
Description: Opening the Contacts folder causes the Windows 10 quick access buttons panel to appear Affected versions: 22000.51 -> 22000.194 Steps to recreate issue: Open File Explorer and navigate to %userprofile% (or go up a directory and double click the folder with your username) Open the 'Contacts' folder
KB5089573 forced install + Lenovo network stack degradation (HTTPS latency, build 26200.8524)
KB5089573 installed automatically on a Lenovo system despite updates being paused and no preview updates enabled. After installation, the system jumped to build 26200.8524 and the network stack degraded severely. Heavy HTTPS sites (LinkedIn, Google Finance, YouTube) take 20–60 seconds to load across all browsers. Speedtest is normal, other devices on the same network are unaffected, and both Edge and Chrome show identical latency. DISM shows no package for KB5089573 and the update cannot be uninstalled. Looking for correlation data from other Lenovo users.
Tab header font issue when the "new zoom" feature is enabled
We found a curious font display issue, which can only be reproduced if the "new zoom" feature flag is active: We can reproduce it with build 20026.20076 with the zoom slider visible (e.g. in the "Current Channel (Preview)"), but we cannot reproduce it on the same build with the zoom slider invisible (e.g. on a freshly updated system in the Current Channel, which has not received the staged rollout yet) or with older builds (e.g. the current Monthly Channel build). The problem itself is unrelated to zooming. Repro 1. Create a new Access database. 2. Create a new form in Design View. 3. Add a Tab Control. 4. Set the tab control's "Use Theme" property to "No". 5. Add a button with the following code: Private Sub Command3_Click() Dim start As Double ' Localize the page name, if you use a non-English version of Access Me.Page2.Visible = True ' Simulate long-running operation (3 seconds) start = Timer Do Until Timer > start + 3: Loop End Sub 6. Save and open the form in Form View. 7. Click the button. Expected result: Nothing happens for 3 seconds. Actual result: The tab header's font switches to some old raster system font (MS Sans Serif?). After 3 seconds, the form returns to the 21st century. This issue is easy to work around: just do the long-running operation before setting the Visibility property, this will reduce the font-change to a short flicker. Still, this appears to be an unintended side effect of the changes made for the "new zoom" feature, so I thought it might be helpful to report it while that feature is still being worked on.
Picture-in-Picture seek controls bypass MediaSession ad restrictions on YouTube
In Microsoft Edge, the Picture-in-Picture overlay exposes functional +10s/-10s seek controls during YouTube ad playback. The seek action advances the ad playhead even when YouTube has declared the seekforward action as unavailable via the Media Session API. Repro: InPrivate window, logged out of YouTube Play any video on youtube.com When pre-roll ad starts, click the in-player PiP icon Press +10s seek-forward on the PiP overlay Observed: a non-skippable NPCI ad followed by a Maggi ad were both bypassed in ~10 seconds of wall-clock time. The main <video> element briefly buffers during seek, consistent with HTMLMediaElement.currentTime being mutated directly rather than dispatched through the page's registered MediaSession action handlers. Cross-browser: verified the same flow in Google Chrome on the same Windows install. Seek-forward during ad playback does NOT advance the playhead, confirming YouTube's MediaSession setup is correct and isolating the issue to Edge's PiP implementation. Impact: affects any site using the Media Session API to restrict seek — live streams, DRM-protected content, ad-bound playback. Not YouTube-specific. Environment: Edge version: latest stable channel OS: Windows 11 - Chrome compared: latest stable channel
Critical 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.
Bug na bateria após atualização em 06/05/2026
Olá, pessoal. Tenho um notebook com processador Intel Core i5 de 11ª geração e faço parte do Programa Windows Insider. Na quarta-feira, 06/05/2026, por volta das 16h, ao desligar o notebook, apareceu a opção de atualização. Selecionei “Atualizar e desligar”. Aguardei o desligamento, fechei a tampa e deixei o equipamento conectado ao carregador, com aproximadamente 80% de bateria. Por volta das 18h, ao sair para dar aula, levei o notebook sem o carregador. Ao chegar à instituição e ligar o equipamento, ele permitiu apenas digitar a senha de login e desligou completamente, sem possibilidade de religar. Ao retornar para casa, conectei o carregador e o sistema indicava bateria em 0%. Aguardei cerca de 30 minutos, mas o nível de bateria não aumentou. Depois de alguns minutos conectado, consegui iniciar o notebook, porém a bateria continuava marcando 0%. Verifiquei o Windows Update e havia uma atualização não concluída. Tentei corrigir removendo a atualização e baixando novamente, mas ela não finalizava. Durante todo o dia 07/05/2026, tentei atualizar novamente, sem sucesso. O notebook ficou muito lento e a bateria continuava em 0%. Na sexta-feira pela manhã, 08/05/2026, após deixar o equipamento durante a madrugada baixando a atualização, ela chegou a 99%, mas não concluiu. Resolvi então restaurar o sistema, escolhendo a opção de manter aplicativos e arquivos. A restauração foi concluída com sucesso. O equipamento voltou ao normal em desempenho e, no primeiro reinício, a bateria voltou a aparecer com 100%. Realizei testes de carga e descarga durante a manhã de 08/05/2026 e utilizei o equipamento normalmente à tarde. Na manhã de 09/05/2026, notei algo estranho: a bateria ainda estava em 100%, mesmo após o notebook passar a noite hibernado. Continuei trabalhando e, de repente, o equipamento desligou sem qualquer aviso de bateria fraca. Ao conectar novamente o carregador e iniciar a máquina, a bateria voltou a ficar travada em 0%, mesmo após mais de 2 horas conectada. Ao verificar as atualizações, percebi que as mesmas atualizações estavam novamente disponíveis. Já removi a inscrição no Programa Windows Insider e desinstalei as atualizações recentes, mas isso não alterou a situação. Entrei em contato com o suporte da Microsoft e fui orientado a relatar o caso aqui, pois, por participar do Programa Insider, pode se tratar de um bug relacionado a alguma versão que esteja em conflito com o gerenciamento da bateria. Pretendo restaurar novamente a máquina para verificar se o funcionamento volta ao normal. As atualizações relacionadas são: * KB5073032 - 2025.11 * KB5082257 * KB5082417 Gostaria de saber se outros usuários do Programa Insider tiveram problema semelhante envolvendo atualização, bateria travada em 0% ou falha no gerenciamento de energia após atualização recente.Edge 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.
