I've been using BGinfo to set the wallpaper for user logins with a command that runs at startup. It's configured like this: `"C:Program FilesBgInfoBginfo64.exe" "C:Program Filesbginfowstat.bgi" /timer:0 /nolicprompt`. While this works and the users can't modify that folder, I've noticed that occasionally the wallpaper changes to a black screen for no clear reason. This issue seems to occur after rebooting, even though the BGinfo information is still present on the black wallpaper. I've observed this on both my personal machine and on virtual machines, but I can't pinpoint exactly why it happens since it works fine after a reboot. We aren't managing wallpapers via Group Policy and are using Windows 11 versions 23H2 and 24H2. Any thoughts on what might be going wrong?
4 Answers
I see this happen all the time, especially with RDP logins. It could be related to how the remote desktop protocol handles wallpapers. Sometimes it switches to black when it can't properly load the image, especially if the connection is lagging.
This might sound a bit out there, but I've heard that some RDP clients switch the desktop background to black to improve performance. It's possible that's what's happening if you're using RDP frequently.
Is the image you're using for the wallpaper saved locally or on a network share? It’s best to keep it local to avoid issues. That being said, if you're already using a local image, could you check if the image path is still valid after a reboot?
What might be happening is that BGinfo is triggered too early during startup. If it tries to set the wallpaper before Windows has fully loaded the desktop environment, it could default to black. Consider adding a delay to the execution to see if that helps!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures