Windows Spotlight Problem

ChatGPT said:

Hi rogstern — thanks for the clear description. This is a fairly common Spotlight/Theme/profile-quartet problem (lock screen Spotlight still updates while the Desktop Spotlight image does not), and there are a few likely causes and fixes. Below are focused diagnostic steps and safe fixes — do them in order and report back what changes.
Quick checks first

1. In the affected account go to Settings → Personalization → Background and confirm “Windows Spotlight” is selected for the Desktop (there is a separate option from Lock screen).
2. Is the affected account a standard (non‑admin) account, a domain/managed account, or controlled by Group Policy? Managed accounts can have wallpaper/Spotlight disabled by policy.

If those are OK, follow these steps.
Step 1 — short test: new local user

• Create a new local (not domain/Microsoft) user and sign in.
• Enable Desktop Spotlight there. If Desktop Spotlight works in the new account, the issue is confined to the original user profile (profile corruption, theme files or permissions). If it also fails, it’s system-wide and we take different steps. (Creating a new user is the fastest way to isolate user vs system issues.)

Step 2 — check Themes folder + TranscodedWallpaper

• Spotlight/desktop themes use files in: %USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes
• While signed in to the problem account, open that folder and temporarily move (don’t delete yet) the files TranscodedWallpaper.jpg, roaming.lock, settings.dat and any *.theme files to a backup folder on Desktop. Sign out and sign back in. Windows will regenerate defaults. This often fixes desktop not changing because a stale TranscodedWallpaper or theme file is locking the wallpaper. (Many forum solutions use this Themes-folder reset approach.)

Step 3 — clear Spotlight cache (ContentDeliveryManager assets)

• Desktop/lock-screen Spotlight images come from the ContentDeliveryManager package. Clear its cache:
  1. Open File Explorer and go to: %LocalAppData%\Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\LocalState\Assets
  2. Copy that Assets folder somewhere (backup), then delete the files inside Assets (these are cached images).
  3. Sign out/sign in (or restart).
• If Desktop Spotlight still won’t update, you can reset the package registration (see Step 4). Clearing Assets is a documented troubleshooting step to force Spotlight to fetch fresh images.

Step 4 — re-register the ContentDeliveryManager package (safe first, then fuller reset)

• Re-registering is safer than removing the package. Run PowerShell as the affected user (or as admin) and execute:
  • Get-AppxPackage -AllUsers Microsoft.Windows.ContentDeliveryManager | Foreach { Add-AppxPackage -Register "$($_.InstallLocation)\AppxManifest.xml" -DisableDevelopmentMode }
• After that, sign out and sign in. This forces Windows to re-register the Spotlight app and often regenerates roaming.lock / settings files correctly. (If you prefer, make a System Restore point before this.)

Step 5 — permissions / file lock checks

• If roaming.lock wasn’t recreated when you renamed it, there may be permissions or ownership problems on the Themes folder or on the ContentDeliveryManager LocalState folder. Check with:
  • In elevated command prompt: icacls "%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes"
  • If permissions look wrong, take ownership and reset them (only if you’re comfortable): takeown /f "%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes" /r /d y then icacls "%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes" /reset /t
• After fixing permissions, repeat Step 2 and sign out/in. Incorrect permissions on the Themes or LocalState folders commonly block recreation of lock files.

Step 6 — Theme / Settings toggle (quick)

• Switch the user to a built‑in theme (e.g., “Windows Light”), sign out, then switch back to Spotlight. Some users reported a theme switch fixed the Spotlight desktop. If that works, leave it on and watch for updates.

Workarounds (if you need an immediate fix)

• If you just want the desktop image to change while you troubleshoot, you can copy Spotlight images from the Assets folder, rename to .jpg and set as desktop manually or use a small startup script to set a new image periodically (forum threads show people using this when Spotlight misbehaves). That’s a pragmatic workaround while you fix the root cause.

If none of the above works

• Tell me:
  1. Are you using a Microsoft account, a local account, or domain account on that user?
  2. What Windows 11 build (Settings → System → About) are you on?
  3. Any error messages in Event Viewer around the time you sign in or when you toggle Spotlight?
  4. Did re-registering ContentDeliveryManager already recreate roaming.lock or not?

Warnings and notes

• Make a System Restore point before re-registering/removing system provisioned packages or changing ownership/ACLs.
• Removing the ContentDeliveryManager package entirely can have side effects; prefer re-registering first.

If you want, I can give the exact PowerShell commands and a short script to:

• back up and clear the Assets folder,
• backup/rename the Themes files,
• re-register ContentDeliveryManager,
  and verify permissions — tell me if you prefer step-by-step commands or want me to walk you through them interactively.

Click to expand...

Thank you for your advice. I will try the steps you suggested. By the way Spotlight does work with another user account on the same computer

Good — that the Spotlight desktop works in another account on the same PC tells us this is almost certainly a user‑profile issue (not a system/service-wide bug). That narrows the troubleshooting and lets you focus on the Themes/Spotlight cache and permissions for the affected account. Below is a short prioritized checklist you can follow now (I kept commands copy/paste ready). Do them in order and tell me what you see after the key steps.
Before you start

• Make a System Restore point (Settings → System → Recovery → Create a restore point) and sign out of any other users.
• Run the commands or File Explorer steps while signed into the problem account (some fixes require the user context).

1) Quick GUI check (one more time)

• Settings → Personalization → Background: confirm Desktop is set to “Windows Spotlight” (not just Lock screen).
  (You said lock screen updates, so this is probably already set.

2) Backup & remove the per‑user theme files (fast, often fixes it)

• Open File Explorer and paste:
  %USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes
• Copy that whole Themes folder to your Desktop (or another backup location).
• In the original Themes folder, move (don’t permanently delete) these files to the backup folder: TranscodedWallpaper.jpg, roaming.lock, settings.dat and any *.theme files.
• Sign out and sign back in (or restart).
• Check if Desktop Spotlight now updates.

If that fixes it, great — leave Windows to regenerate fresh files and watch for normal behavior. If not, continue.
3) Clear Spotlight cache (ContentDeliveryManager assets)

• Run these from an elevated Command Prompt or PowerShell (run as the affected user if possible; elevated if needed):
  Backup cached assets:
  mkdir "%USERPROFILE%\Desktop\SpotlightAssetsBackup"
  xcopy "%LocalAppData%\Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\LocalState\Assets" "%USERPROFILE%\Desktop\SpotlightAssetsBackup" /s
  Delete the cached assets:
  del "%LocalAppData%\Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\LocalState\Assets*" /q
• Sign out and sign back in. This forces Spotlight to download fresh images.

4) Re‑register the ContentDeliveryManager app (safe)

• Open PowerShell as Administrator and run:
  Get-AppxPackage -AllUsers Microsoft.Windows.ContentDeliveryManager | Foreach { Add-AppxPackage -Register "$($_.InstallLocation)\AppxManifest.xml" -DisableDevelopmentMode }
• Sign out/in again and check the Themes folder to see if roaming.lock/settings.dat are recreated:
  dir "%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes"

5) Check and fix permissions on Themes (if roaming.lock didn’t reappear)

• In an elevated Command Prompt run:
  icacls "%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes"
  takeown /f "%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes" /r /d y
  icacls "%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes" /reset /t
• Then repeat step 2 (move old files away) and sign out/in.

6) Theme switch test (fast & harmless)

• In the problem account switch to a built‑in theme (e.g., Windows Light). Sign out and in. Then switch back to Windows Spotlight. Sometimes switching forces regeneration and fixes the desktop Spotlight.

7) Check Event Viewer for errors (if still failing)

• Open Event Viewer → Windows Logs → Application and System. Filter around time of sign‑in and when you change Spotlight and look for errors mentioning ContentDeliveryManager, Themes, or shell/Explorer. Copy any error messages here if you see them.

If nothing above recreates roaming.lock or fixes the desktop

• Option A (practical): Create a new user and migrate data. Because Spotlight works in another account, creating a new user and copying Documents/Desktop/AppData where needed often solves persistent profile corruption.
• Option B (diagnostic): I can provide a small PowerShell script that automates backing up Themes, clearing Assets, re-registering the package and verifying permissions — tell me if you want that and I’ll paste it.

A couple of final notes

• You mentioned you previously renamed roaming.lock and it didn’t regenerate — that’s a strong sign of either file/ACL issues or the ContentDeliveryManager process not being able to write into that folder under that account. The permission steps above are the most likely cure.
• If this is a domain/managed account, group policy or a management tool may be preventing recreation; confirm it’s a local/Microsoft account. (You said another user on same PC works — if that other account is local and the affected one is domain-managed, that’s relevant.

Tell me which step you try and what happened (especially whether roaming.lock or settings.dat got recreated after any step). If you want the automated script, say “yes — script” and whether you prefer a PowerShell script you can run as Administrator or a step-by-step command list.

Recreating Files in the Theme folder did not solve the problem.

Clearing the cache didn't work because %LocalAppData%\Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\LocalState\Assets doesn't exist

Re registering the ContentDeliveryApp recreated the files in the Theme folder but that did not fix the problem.

Could not find anything in Event Viewer.

I should also tell you that Spotlight works on a local user account but not my account which is a Microsoft account.

Any other suggestions.

I'm worried about creating a new user account and somehow messing up my settings.

Thanks — the additional details (Spotlight works in a local account, the Assets folder didn’t exist, re‑registering recreated Theme files but didn’t fix desktop Spotlight) are very helpful. That pattern strongly points to a Microsoft‑account / per‑user sync or per‑profile configuration issue rather than a system bug — the local account working is the key clue.
Below are targeted next steps (ordered from least invasive to more intrusive). I include exact places/commands and safety notes. Before you start, create a System Restore point (Settings → System → Recovery → Create a restore point).
Why this set of steps

• Desktop Spotlight behavior is influenced by per‑user ContentDeliveryManager state and by the Microsoft account theme/sync settings. Clearing cached files works only if Windows is allowed to download new Spotlight assets; if the MS account is syncing or a per‑user registry value blocks Spotlight for Desktop, the Assets folder will never appear and Spotlight won’t fetch desktop images. The steps below focus on those per‑user settings and the MS account sync state.

1) Turn off Theme/Personalization sync for your Microsoft account (quick, reversible)

• Settings → Accounts → Windows backup (or “Sync your settings” on older builds). Turn off “Theme” (or turn off all sync temporarily).
• Sign out, sign back in, then set Desktop → Windows Spotlight.
  Why: If the cloud‑synced theme data for your Microsoft account is corrupted it can keep reapplying a broken configuration. Turning off sync forces the local profile to stop reusing potentially bad cloud data.

2) Toggle Spotlight off/on for Desktop + Lock screen

• Settings → Personalization → Background: set to Picture (any image), sign out and sign in.
• Then set Background back to Windows Spotlight. Also toggle the Lock screen Spotlight setting (turn off then on).
  Why: Forces Windows to re-request/configure Spotlight for your user context.

3) Reset the per‑user ContentDeliveryManager registry values (safe if you export first)

• Run regedit (while signed in to the affected MS account) and export this key as a backup:
  HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager
• After export, right‑click the ContentDeliveryManager key and Export again (to have a restore), then delete the key (or rename it by adding “.old” to the key name). Sign out and sign in — Windows will recreate defaults. Then set Desktop → Windows Spotlight again.
  Why: This removes any stuck per‑user flags that prevent desktop Spotlight from fetching/using images. (You exported so you can restore the values if needed.

4) Recreate Themes / ensure permissions (you tried some of this, repeat after sync/registry reset)

• In the affected account:
  • Backup the Themes folder: copy %USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes to Desktop.
  • From the original Themes folder move (not delete) TranscodedWallpaper.jpg, roaming.lock, settings.dat and any .theme files to the backup folder.
• Ensure the folder permissions are correct (run in elevated CMD):
  icacls "%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes"
  (If permissions look wrong, then: takeown /f "%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes" /r /d y then icacls "%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Themes" /reset /t.
• Sign out/in and check whether roaming.lock and settings.dat are created and whether Desktop Spotlight updates.
  Why: If the MS account profile has an ACL or ownership problem, Spotlight cannot write its state files and so desktop changes won’t occur.

5) If Assets folder still missing and desktop still fails: temporarily convert your MS account to a local account and back (non‑destructive, but do a backup first)

• Settings → Accounts → Your info → Sign in with a local account instead. Follow prompts and sign out/in. Then test Spotlight (set Background → Windows Spotlight). If Desktop Spotlight now works, convert back to MS account: Settings → Accounts → Sign in with a Microsoft account. After converting back, check Spotlight again.
  Why: This refreshes the MS‑account sync data for your profile and is often the thing that clears corruption in cloud‑synced preferences. It’s reversible and won’t delete your files; it will only change how your account signs in. Still — export your important settings or make a restore point first.

6) If you still prefer not to touch account sign in: create a short temporary local admin for a final test

• Create a new local Administrator (Settings → Accounts → Family & other users → Add account → I don’t have this person’s sign‑in info → Add a user without a Microsoft account). Test Desktop Spotlight there. We know it works on a local account already; this is just a last isolation step to be 100% sure it’s the MS account sync. If the local admin works, you can remove it later.

7) If the above fixes don’t work — safe migration option

• Because the problem is isolated to the MS account profile and you’re worried about losing settings, a conservative approach is:
  • Create a new local account (non‑MS) and sign in. Manually copy personal data (Documents, Pictures, Desktop) from the old profile to the new one; do NOT copy AppData except for small app-specific data you know. Leave system settings alone. Optionally, after you are happy with the new account you can sign that account into your Microsoft account. This avoids migrating corrupted user hive settings that likely caused Spotlight failure.
    I note you said you’re reluctant to create a new user — I understand. The “convert MS→local and back” trick is usually less work and often successful, so try the sync/registry toggles above first.

What I need from you if this still fails

• Your Windows 11 build (Settings → System → About) — some builds have Spotlight changes/bugs.
• The exact contents (copy/paste) of the ContentDeliveryManager key you exported (or a screenshot) — I can scan for suspicious values.
• Confirm whether you turned off Theme sync and whether converting to a local account changed behavior.

If you want I can:

• Provide the exact .reg export command and the PowerShell/CMD commands so you can copy/paste safely.
• Produce a small script that: exports the registry key, backs up Themes, resets ACLs, deletes the ContentDeliveryManager key, and re-registers ContentDeliveryManager. You run it only if you’re comfortable.

Summary (short)

• Likely cause: per‑user MS account sync/corrupted personalization state or an ACL stopping the profile from writing the desktop Spotlight state. Try turning off Theme sync, deleting/resetting the HKCU ContentDeliveryManager key (export first), and then set Spotlight again. If that fails, temporarily convert your MS account to a local account and test; converting back often clears corrupt cloud state.

Tell me which of the above you want exact commands for (registry export/delete, or the convert‑to‑local steps) and I’ll paste them with copy/paste‑ready commands and the exact undo steps.