Forum Discussion

Tonnny's avatar
Tonnny
Occasional Reader
Oct 05, 2026

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!

2 Replies

  • Your tests already isolate this beyond the per-user Spotlight cache: a fresh account fails, the Assets folder stays empty, and both ContentDeliveryManager tasks return 0x80004002, which is an interface-registration failure. Desktop Spotlight working rules out a general service outage. Stop broad package re-registration, since file-lock and core-package errors can leave servicing in a less predictable state. Install pending Windows and Microsoft Store updates, restart, set the lock screen to Picture, then switch it back to Windows spotlight and retest the scheduled tasks. If the HRESULT remains, use Settings > System > Recovery > Fix problems using Windows Update > Reinstall now. Microsoft documents that repair as reinstalling the Windows version while preserving apps, files, and settings, so it is safer than a reset and is not a feature upgrade. If the option is unavailable on a managed device, collect Feedback Hub diagnostics and have IT open a Microsoft support case.

  • Hi there!

    Have you tried this command to re-register?

    Get-AppxPackage -Name Microsoft.Windows.ContentDeliveryManager | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -Verbose}