Wallpaper loads but disappear

[VegaPunkSquer]

Describe the bug
Simply doesn't work

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Turn on the PC'
2. Click on 'Lively Wallpaper start ups with Windows'
3. Scroll down to 'The wallpaper shows up and then turn back to the Windows wallpaper'
4. See error

Expected behavior
Turn on the PC and then load the Fluid wallpaper on the second screen

Screenshots/Video
No screenshots

Desktop (please complete the following information):

• OS: Microsoft Windows 11 Enterprise 10.0.22621
• Fluids.

Additional context
The wallpaper it's loaded buts disappear just after

Log file (Important)
20230817_143542.txt
2023-08-17 14:35:42.7408|INFO|Lively.App|
Lively v2.0.7.0 x64 desktop-bridge en-US
OS: Microsoft Windows 11 Enterprise 10.0.22621
CPU: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
GPU: NVIDIA GeForce GTX 1660

2023-08-17 14:35:44.1956|INFO|Lively.Helpers.WindowsStartup|Startup is enabled.
2023-08-17 14:35:44.1970|INFO|Lively.Services.TranslucentTBService|Taskbar theme: fluent
2023-08-17 14:35:44.1970|INFO|Lively.Services.TranslucentTBService|Taskbar theme service started.
2023-08-17 14:35:44.6408|INFO|Lively.Core.Suspend.Playback|Lockscreen Session ended!
2023-08-17 14:35:45.2729|INFO|Lively.Core.WinDesktopCore|Restoring wallpaper Fluids | C:\Users\User\AppData\Local\Lively Wallpaper\Library\wallpapers\0wj1biqk.f41
2023-08-17 14:35:45.2729|INFO|Lively.Core.WinDesktopCore|Setting wallpaper: Fluids | C:\Users\User\AppData\Local\Lively Wallpaper\Library\wallpapers\0wj1biqk.f41\fluid.html
2023-08-17 14:35:45.3650|INFO|Lively.Core.WinDesktopCore|Core initialized..
2023-08-17 14:35:45.3650|INFO|Lively.Core.Watchdog.WatchdogProcess|Starting watchdog service...
2023-08-17 14:35:45.9901|INFO|Lively.Core.Wallpapers.WebCefSharpProcess|Cef0: {"Type":0,"Hwnd":67942}
2023-08-17 14:35:46.0319|INFO|Lively.Core.WinDesktopCore|Sending wallpaper(Screen): \.\DISPLAY2 | {X=1920,Y=-1338,Width=1080,Height=2560}
2023-08-17 14:35:46.0688|INFO|Lively.Core.Watchdog.WatchdogProcess|Adding program to watchdog: 20928
2023-08-17 14:35:46.5741|INFO|Lively.Core.Wallpapers.WebCefSharpProcess|Cef0: {"Type":2,"Success":true}
2023-08-17 14:35:50.4826|ERROR|Lively.Core.WinDesktopCore|Failed to set lockscreen/desktop wallpaper: Unable to find the specified file.
2023-08-17 14:35:50.7806|ERROR|Lively.Core.Wallpapers.WebCefSharpProcess|Stdin write fail: Cannot access a disposed object.
Object name: 'System.Diagnostics.Process'.
2023-08-17 14:35:51.2769|ERROR|Lively.Core.Wallpapers.WebCefSharpProcess|Stdin write fail: Cannot access a disposed object.
Object name: 'System.Diagnostics.Process'.
2023-08-17 14:35:51.7767|ERROR|Lively.Core.Wallpapers.WebCefSharpProcess|Stdin write fail: Cannot access a disposed object.
Object name: 'System.Diagnostics.Process'.
2023-08-17 14:35:52.2752|ERROR|Lively.Core.Wallpapers.WebCefSharpProcess|Stdin write fail: Cannot access a disposed object.
Object name: 'System.Diagnostics.Process'.
2023-08-17 14:35:52.7763|ERROR|Lively.Core.Wallpapers.WebCefSharpProcess|Stdin write fail: Cannot access a disposed object.
Object name: 'System.Diagnostics.Process'.
2023-08-17 14:35:53.2765|ERROR|Lively.Core.Wallpapers.WebCefSharpProcess|Stdin write fail: Cannot access a disposed object.
Object name: 'System.Diagnostics.Process'.
2023-08-17 14:35:53.7772|ERROR|Lively.Core.Wallpapers.WebCefSharpProcess|Stdin write fail: Cannot access a disposed object.
Object name: 'System.Diagnostics.Process'.
2023-08-17 14:35:54.2769|ERROR|Lively.Core.Wallpapers.WebCefSharpProcess|Stdin write fail: Cannot access a disposed object.
...

[weicks]

I have the same problem at Win 11. But Lively Wallpaper worked without any trouble with all Wallpapers including Fluid after the first install. But after a restart of my pc it does not open Fluid or opens it for a second and then falls back to the default Windows background. Sometimes all other Wallpapers are working when selecting "change Background " at the taskbar. I think I have no other program installed which should interfere with Lively?! I don´t know but could it be because of something with the win11 updates?? Would be glad if someone could help here.