Windows spotlight can stop showing new images or appear to “disappear” if the feature is disabled by policy, replaced by a custom background, or affected by recent updates.
Key points from current behavior and documentation:
- On Windows 10 and Windows 11 Enterprise/Education, Windows spotlight is the feature that rotates daily images on the lock screen and desktop background and can show suggestions, tips, and organizational messages.
- After installing certain updates (for example, KB5046633 on Windows 11 or KB5048652 on Windows 10), the default wallpaper behavior can change so that Windows spotlight becomes the default background. This can also be modified again by policy or by user settings, which may make it look like Spotlight has “disappeared.”
- If an organization deploys a custom lock screen or desktop background image via policy (Intune/MDM, Group Policy, or CSP), that custom image replaces the Windows spotlight image, even though Spotlight content (tips, messages) can still appear.
- Windows spotlight itself is controlled by policy settings such as
AllowWindowsSpotlight and ConfigureWindowsSpotlightOnLockScreen. If these are disabled or overridden, Spotlight images will no longer appear.
To verify and restore Spotlight on a single device (if supported by the edition):
- Open Settings → Personalization → Lock screen.
- Under Personalize your lock screen, select Windows spotlight.
- On Windows 11/10 desktop background, open Settings → Personalization → Background, and under Personalize your background choose Windows spotlight if available.
If the device is managed (Insider, corporate, or school device):
- An administrator may have configured a custom lock screen or disabled Spotlight via Group Policy or MDM (Experience Policy CSP). In that case, the Spotlight image will not show even if it previously did.
Because this is an Insider scenario and behavior can change with builds, checking with other Insiders in the same channel and build, or reviewing any recent policy changes, is the most direct way to confirm whether this is a broader issue or specific to the device/policy configuration.
References: