Save the date: Windows office hours - October 15, 2026
Need answers from the people behind the products you manage every day? Join us for Windows Office Hours on October 15th from 8:00–9:00 AM PT, where experts from Windows, Microsoft Intune, Configuration Manager, Windows 365, Windows Autopilot, security, public sector, FastTrack, and more will be available to answer your questions. This is a live, chat-based event with no video and no meeting link. Simply join the discussion, ask your questions, and participate in conversations with Microsoft engineers and specialists. If you can't attend live, post your questions on the event page in advance and we'll address them during the session.
Windows 11 is really F annoying, it could actually cost someone their life.
Earlier today, a family member suddenly fell ill and required emergency care. After rushing them to the hospital and ensuring their condition had stabilized, I returned home intending to look up information about his illness. I had just installed Windows 11 26H2 a few hours prior. When I tried to go online to search for info, I needed to install the built-in Windows language input method, it took a full 20 minutes to finish, as long as installing the monthly security patches, whereas on Windows 10, it takes less than 2 minutes. Then there are the constant, junk notifications, things like "We'd like your feedback on Windows 11" or "Do you want to enable Onedrive syncing?" (and the only option is to snooze the reminder for a week). Not to mention the right-click menu, which suffers from extreme latency (over 0.4 seconds). F—CAN YOU IMAGINE HOW I FELT AT THAT MOMENT? Fortunately, it wasn't a critical emergency this time. And then there are the various basic functions that stop working at any moment, it’s basically a MALFUNCTIONING operating system. I’ve switched back to Windows 10 now.
Don't show windows 11 update notifications after the update has been viewed.
It used to be that we'd get a notification and the Windows Update taskbar icon would show on the taskbar ONLY when there was a new notification AND we had not yet viewed it. After that it would be silent. But now I see the taskbar icon ALL THE TIME until I install every available update. Since some updates are NOT SAFE to install immediately (let's face it, both Microsoft and NVidia are infamous for rolling out updates that are not yet fully mature, but they eventually fix them), but it is ideal to let them simmer for a few weeks and only then install them. The problem is a "Boy who cried wolf" syndrome. If installing an update is best to be delayed, the taskbar icon stays on, not just when a NEW product update shows up. So, we end up ignoring them all. Not good. I can't find a way to silence the new taskbar behavior so that I can choose when to install product updates and still have a visible sign that a new update that I have not yet inspected just showed up. So... how do I get the taskbar icon to go back to the old behavior? ONLY show the update icon if a new update for a product is available and I have not yet opened the Windows Update app since it became available... regardless of whether I installed it or not? Or has windows 11 been crippled and this is no longer possible?
Microsoft Emailed Me: KB5124010 File History Log Bug Is Under Investigation
Hi everyone, on September 23rd, I contacted Microsoft Support to report a minor issue with the file history log caused by the KB5124010 update. Several other users have also reported this problem. Microsoft Support sent an email yesterday confirming they are aware of the issue and are currently investigating. This is the content of the letter :Windows 11 Lock Screen Spotlight Not Updating (Error 0x80004002)
Hello everyone, I'm dealing with a persistent issue where Windows Spotlight on the Lock Screen refuses to update or fetch new images, getting permanently stuck on a default image. What makes this unique is that Windows Spotlight on the Desktop background works completely fine, meaning internet connectivity, backend content servers, and general user settings are functioning. The failure is strictly isolated to the lock screen integration. What is Already Tested & Ruled Out: Network & Policies: Internet connection is active, and no Group Policies or registry blocks are interfering. New User Account Test: Tested on a freshly created local account—the issue persists identically. System Files: Ran SFC /scannow and a full DISM /Online /Cleanup-Image /RestoreHealth repair. Corrupted files were successfully repaired, but the lock screen issue remained. Packages Verified: Checked via PowerShell; Microsoft.LockApp, Microsoft.Windows.ShellExperienceHost, and MicrosoftWindows.Client.WebExperience are all installed and registered properly. Assets Folders: The local Spotlight asset folders remain empty because background fetch tasks fail to download content. The Critical Diagnostic Clue: When investigating the underlying background tasks via Task Scheduler and PowerShell, I found that the Content Delivery Manager tasks are failing consistently: Task Path: \Microsoft\Windows\ContentDeliveryManager\UpdateContent (and SubscriptionContentChanged) Last Result Code: -2147467262 (0x80004002) Error Meaning: E_NOINTERFACE ("No such interface supported"). This indicates that a Windows component, registered COM interface, or background handler thatthe Content Delivery Manager task expects to talk to for the lock screen/shell interaction is missing,broken, or failing to bind. Attempts to manually re-register the Web Experience and Content Delivery Manager packages in an elevated PowerShell session are met with file-lock restrictions(0x80073D02) or core-package removal blocks (0x80070032). Has anyone encountered this specific 0x80004002 COM interface error affecting Lock Screen Spotlight on newer Windows 11 builds (version 26100+), and is there a way to safely repair or re-register the broken component interface without doing a full in-place upgrade? Any guidance would be greatly appreciated!Microsoft support KB5124010, KB5124008: Known issues in this update, Highlights: semantic ambiguity
Hello, I have a question regarding Microsoft is announcement. Hi everyone,I was reviewing the Microsoft support pages for the September 2026 Windows updates and got quite confused by the wording regarding the File History bug fix. Furthermore, my actual experience after updating doesn't seem to align with the official description. I'd like to hear your thoughts on this. Question 1: Does the word after in KB5124008 imply a phased/partial fix? https://support.microsoft.com/en-us/servicing/os/windows-11/2026/09/kb5124008-windows-11-24h2-25h2-security-update In the Known issues section of KB5124008, Microsoft lists a few specific symptoms: Incorrectly displaying a Reconnect your drive message. The Last Backup timestamp might not update, and previously backed-up files might show No previous version available. Application crash events referencing FileHistory.exe. However, in the Resolution section, Microsoft states: This issue is resolved in Windows updates released on and after September 22, 2026 such as KB5124010. What exactly does after mean in this context? Does it imply that KB5124010 did not completely fix all symptoms, and the remaining issues (like the timestamp bug) will not be fully resolved until the October 13th Patch Tuesday? Question 2: Why did the KB5124010 release notes omit the timestamp issue? https://support.microsoft.com/en-us/servicing/os/windows-11/2026/09/kb5124010-windows-11-24h2-25h2-update I then checked the Highlights section for KB5124010, which states: File History Fixed: This update addresses an issue where File History might fail to back up or restore files... Affected devices might incorrectly display a Reconnect your drive message... Noticeably, it completely omits any mention of fixing the Last Backup timestamp might not update symptom. Does this omission mean that this specific part of the bug has not been fixed yet? My Actual Experience: My suspicions seem to be confirmed in my actual usage. After installing the latest KB5124010 update, my File History can now successfully find the backup drive, run properly, and back up new files (Symptom 1 is resolved). However, the Last Backup date/timestamp still has not changed at all (Symptom 2 remains). To summarize my questions: Based on Microsoft is wording, is KB5124010 only a partial fix? For the lingering issues regarding the timestamp not updating and no previous version available, do I just have to wait for the October update? Has anyone else experienced this exact situation?File History timestamp sync bug still broken in KB5124010 - Anyone else?
To the Microsoft technical team Hi everyone,Quick post to see if anyone else is still running into File History timestamp sync issues on the latest builds. Test Environments: Laptop: Windows 11 25H2 (OS Build 26200.8973) Desktop: Windows 10 22H2 (OS Build 19045.7725) Home version The Issue:This problem started back in July (KB5101684 / KB5120249). While KB5124010 fixed the scheduled backup failure and Reconnect drive prompt from KB5124008, the timestamp and version sync bugs remain unfixed: Triggering Run now manually in Control Panel does not update the Last backed up timestamp to the current time. For newly created files (such as Word files), File Properties > Previous Versions displays: No previous versions are available. Changes to the contents of older files will not display the latest timestamp version; only the date and time of the previous version will be shown. A new entity version of the file has been created without any modifications. Other users (including community members in Japan and previous discussion threads) have confirmed identical behavior. File History is essential for daily backups, so getting this sorted out is critical.I'm really on the verge of a breakdown... Hopefully, the security patch will be completed in October. If you are experiencing this issue, please upvote and comment on my Feedback Hub report so the Windows engineering team prioritizes a fix: Feedback Hub Link: https://aka.ms/AA13n22w
(KB5124010) Niepowodzenie instalacji dnia 1.10.2026 — Ox800f0922
Mam problem z instalacją aktualizacji (Aktualizacja dla systemu Windows (KB5124010) Niepowodzenie instalacji dnia 1.10.2026 — Ox800f0922). Próbowałem też ponownie zainstalować system (Windows Update - Opcje zaawansowane - Odzyskiwanie - Rozwiązywanie problemów za pomocą usługi Windows Update Ta opcja jest teraz niedostępna) instalowanie zakończone niepowodzeniem, nie mogę zainstalować ponownie systemy za pomocą Windows Update. Próbowałem też zainstalować ponownie poprzez utworzenie bootowalnego pendrive za pomocą "Media creation tool" ale też nie mogłem zainstalować, a nawet naprawić systemu. Pobrałem plik obrazu systemu Windows kliknąłem na niego następnie został zamontowany on w napędzie, po wejściu do napędu i klikmięciu "setup.exe" również nie miałem możliwości instalacji systemu. W jaki sposób naprawić system aby zainstalować najnowszą aktualizację i mieć sprawny system? P.S jeżeli to zły dział to proszę o przeniesienie tematu.
Win11 update problem, PC hang after update
It has been happening since last 2 months. When updating window 11, the PC requested for a reboot but hung up in the bios screen. I have to switch off using the power button twice and the PC rollback to previous state. I have updated to the latest BIOS firmware. The motherboard is gigabyte B560M DS3H V2. How to solve?
