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!
File History has stopped functioning
My file history program has stopped functioning. I tried searching the internet for some of these error messages and I have not found anything that has a solution that works. I tried deleting the backup on my backup drive, and also deleting the file history data/configuration folders so it would "start fresh" and I still keep getting errors. Here are some of the errors: Also have gotten a bunch of different errors for "reparse points". This is one example. I tried to exclude some of these folders from the backup but it didn't seem to help. But how do I find and eliminate a "reparse point" so it doesn't cause the file history to fail? And why doesn't file history just ignore those folders and go on and back up everything else?
802.1x wired network profiles missing after upgrade to Windows 11 24H2
Issue Description: During the upgrade of workstations to Windows 11 24H2, the IEEE 802.1X wired network security profiles are occasionally not restored after the upgrade process completes. As a result, affected devices fail to authenticate against Cisco ISE, leading to a loss of LAN connectivity. The issue appears to occur randomly and does not show any clear correlation with specific hardware models or workstation configurations. We are using Feature Updates to upgrade workstations to Windows 11 24H2, deployed through SUP in SCCM/MECM. This approach works best for us because it does not require any user interaction during the upgrade process. I developed a remediation script that is triggered by a scheduled task based on a specific event ID generated when Cisco ISE rejects authorization. The script successfully restores the locally stored 802.1X profiles and resolves the issue. However, I am wondering whether there is a better or more native way to handle this scenario. Has anyone experienced a similar issue with Windows 11 24H2 and 802.1X profiles? Any advice before we open a support case with Microsoft Support?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/AA13n22wMicrosoft 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?(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.Ethernet metric
I have my ethernet ports set to the following metric WWAN 10 WiFi 20 Ethernet 30 with no cable in the RJ45 port WWAN (SIM in laptop) works fine and I can accxess the internet When I plug in an Ethernet cable windows overrides my metrics and tries to connect that port to the internet and I lose connection to the internet Im working on long haul ethernet routers I need the cable port to connect and configure the router but not connect to the internet the WWAN port is there so I can give our tier 3 support remote access top my desktop via team viewer and the team chat When cconneted to WiFi connecting a cable doesnt effect the connection, only when using WWAN is it effected I need them in this priority WWAN 1, WiFi 2, RJ45 port 3. What do I need to set to force Windows 11 ver 26H2 to follow my metric settings and not override them
Unable to remove an inactive/old linked PC from Link to Windows Android app
Hi everyone, I currently have two PCs linked to the Link to Windows Android app. One of them is no longer active, but it still appears in the app, and I’m unable to remove it. I have already tried the usual troubleshooting steps, including resetting the Link to Windows app, but the inactive PC continues to be listed. Interestingly, when I check Devices under my Microsoft Account, only my currently active PC is shown. The inactive PC does not appear there. This issue has been ongoing for more than two years. I recently contacted Microsoft Support regarding this issue, and after further troubleshooting, I was advised to seek assistance from the Microsoft Community. Has anyone experienced a similar issue or knows how to remove an old/inactive PC that is still listed in the Link to Windows Android app? Any advice would be appreciated. Thank you.
Windows 11 Microsoft Account authentication fails system-wide – WAM/Sign-in issue
Hello, I am experiencing a system-wide Microsoft account authentication/sign-in problem on Windows 11 25H2. Microsoft Support has already assisted me with extensive troubleshooting and recommended that I report the issue here because the problem appears to be related to the Microsoft account authentication/sign-in process rather than to a specific Windows user profile. Main issue I am currently using a local Windows account. When I go to Settings > Accounts > Your info > Sign in with a Microsoft account instead, the process eventually asks me to authenticate my existing local Windows account. The password for my local account is definitely correct and works normally on the Windows sign-in screen. However, the same password is rejected during the Microsoft account linking/conversion process. The problem is not limited to my Windows user profile. To test this, I created a completely new local Windows test account. The exact same problem occurs there as well: the local password works for signing in to Windows, but is rejected when attempting to link/convert the local account to a Microsoft account. This strongly suggests that the issue is system-wide rather than caused by corruption of my individual Windows user profile. Additional Microsoft authentication issue I also tried to submit this problem through the Windows Feedback Hub. During the submission process, Windows Security asks me to verify my identity for my Microsoft account using my Windows Hello PIN. My correct Windows Hello PIN is rejected with the message that the PIN is incorrect. Therefore, I cannot submit the report through the Feedback Hub. At the same time, I can successfully sign in to my Microsoft account through a web browser. In fact, I was able to sign in to the Microsoft Tech Community through the browser in order to submit this report. Additional symptoms that have now appeared The problem is no longer limited to linking my Microsoft account to Windows: Outlook is no longer reliably receiving new emails. Microsoft Word can no longer save documents. Feedback Hub cannot authenticate my Microsoft account because the correct Windows Hello PIN is rejected. Microsoft account authentication through the web browser continues to work normally. These additional symptoms make me suspect that there may be a common problem with Microsoft account authentication, WAM (Web Account Manager), the account broker, or another Windows authentication component. Troubleshooting already performed Extensive troubleshooting has already been carried out: The problem was reproduced with a newly created local Windows test account. The local account password was verified and works correctly at the Windows sign-in screen. SFC was run and did not identify an unresolved system-file corruption problem. DISM was run and the component store was repaired/checked. A Windows 11 repair installation was already performed. The problem remained afterward. Relevant Microsoft account/authentication components and services were checked. Microsoft Account Sign-in Assistant, WAM-related components, Account Control/Credential Provider-related components and associated services were checked and appear to be present/running. Credential-related services, including Credential Manager/Vault-related components and TokenBroker, were checked. The issue persists across multiple local Windows accounts. Microsoft Support has therefore concluded that this does not appear to be a simple user-profile corruption issue and may instead involve the Microsoft account linking/authentication pipeline. Current situation Windows 11 25H2 is otherwise running, and my Microsoft account itself is accessible through the browser. However, Microsoft account authentication within Windows appears to fail in several places. I would therefore appreciate assistance in determining whether this is a WAM/account broker/Microsoft account authentication issue and how the affected Windows authentication components can be repaired or reset without reinstalling Windows from scratch. Please let me know if diagnostic logs, event logs, correlation IDs, or any other information would be useful. I can provide additional diagnostic information if required. Thank you.
Windows 11 25H2 Build 9457 lockscreen not changing picture
Hello to all, so, we have three laptops that have Windows 11 25H2 Build 9457, two of these have Enterprise whilst the third one has the Pro version installed, one of the Enterprise laptops is my work laptop, the other one I use for testing image installations etc and is freshly installed with this build. The Pro version is my personal laptop and has also been freshly installed. Ever since having the latest build installed on all three of these laptops, the lockscreen picture does not work, all three remain on the default blue bloom one. I have tried changing from spotlight to picture, restart, then switch to spotlight again with no success. I have deleted the contents of the Assets folder located under this folder MicrosoftWindowsContentDeliveryManagercw5n1h2txyewy , and also the settings folder, rebooted and had no success. I also tried the powershell script that registers the content delivery manager and had no success either I ran a dism check health and all three have no corruption detected, the same after running an sfc scannow. All this on three of these laptops. Then i decided to log on to the local Admin account of my work laptop and after a couple of minutes i locked the screen and the lockscreen picture changed I said to myself so it is working now, i signed out logged in with my domain account and the lockscreen defaulted back to the blue bloom picture. The same happened with the test laptop, i use a test domain user account for this, when i change to a local account the lockscreen picture changes, when i go back to a domain account it defaults to the blue picture. Also happens with my personal laptop where i use a microsoft account to log in. I am literally out of ideas what is causing this because using a local account makes the lockscreen spotlight work, when using a domain or Microsoft account it seems to break it. Thank you for any help.
