BGInfo - Win10 with locked background/wallpaper not working RRS feed

  • Question

  • Hi all,

    We're trying to configure BGInfo to work with our Win10 environment, in Win7 we had the same setup and it worked without a problem.

    We have the latest BGInfo, we have Win10 1709/1809, when we run, either configured in startup or via a group policy, the info is not displayed (our company have enforced a company Theme and Background/Wallpaper and users are unable to change it) If we disable the GPO that enforces these settings then BGInfo is shown as designed.  The wallpaper bmp is stored in an accesible location, and BGInfo is writing to the %TEMP%.  Does anyone have a solution to this, or a workaround, or even a good reason why this isn't going to work?

    Many thanks all,


    Thursday, September 19, 2019 10:55 AM

All replies

  • You could start taking a Procmon log to see what's going on on the system while BGINFO runs..

    Some days ago I took a log with roaming profile enforced and noticed that Explorer is part of the game in windows 10:

    12:47:06,5707582 Bginfo64.exe 9012 10712 WriteFile C:\Users\pippo\AppData\Local\Temp\BGInfo.bmp SUCCESS Offset: 14, Length: 40

    12:47:06,5817230 Bginfo64.exe 9012 10712 RegSetValue HKU\S-1-5-21-697359679-39553803-2418864162-448711\Control Panel\Desktop\Wallpaper SUCCESS Type: REG_SZ, Length: 96, Data: C:\Users\pippo\AppData\Local\Temp\BGInfo.bmp

    12:47:06,6175032 Explorer.EXE 10248 1788 RegSetValue HKU\S-1-5-21-697359679-39553803-2418864162-448711\Software\Microsoft\Windows\CurrentVersion\Explorer\Wallpapers\BackgroundHistoryPath0 SUCCESS Type: REG_SZ, Length: 96, Data: C:\Users\pippo\AppData\Local\Temp\BGInfo.bmp

    12:47:11,6965419 Explorer.EXE 10248 5656 WriteFile C:\Users\pippo\AppData\Roaming\Microsoft\Windows\Themes\CachedFiles\CachedImage_1600_1200_POS1.jpg SUCCESS Offset: 172.032, Length: 3.491

    SO, may be that in your case Explorer is enforcing the GPO setting, prohibiting BGINFO to change the wallpaper registry key "HKU\<Sid>\Control Panel\Desktop\Wallpaper".

    If this is happening at boot, take a procmon boot log so you can see all the sequence happening.


    Thursday, September 19, 2019 11:24 AM
  • Thanks Mario,

    Procmon showed the process works all the way to the registry, so this key is updated, it just doesn't change the wallpaper.

    I think we'll need to investigate other solutions, which is a shame as BGInfo has been a great tool.


    Wednesday, October 9, 2019 3:31 PM