Not working Windows 22H2

[mongoled]

Hi, as per documentation.

The execuatable launches with the OS through task schedular, can be seen in task manager, but does not prevent "Rapid HPD" from kicking in.

If the program is ran manually from the excuatable it works as expected.

I noted that the execeutable does not appear in the system tray, ive added the option in "system settings" to show in the "taskbar" but this has made no difference.

Tried task schedular with "run with highest prvilages", no difference

Tried task schedular as "system", no difference

What am I doing wrong ?

Thanks

[daskiiii]

I've noticed the program attempting to start, show up in my task bar, and then disappear without doing anything, as well. Here's the error code I got:

Faulting application name: PersistentWindows.exe, version: 5.40.8379.25233, time stamp: 0x639501a2
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2913, time stamp: 0xa1c3e870
Exception code: 0xe0434352
Fault offset: 0x000000000002cf19
Faulting process id: 0x4140
Faulting application start time: 0x01d99645234864ae
Faulting application path: C:\Program Files\PersistentWindows-master\PersistentWindows.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 9841b030-83dc-49b5-b260-34e2730583e2
Faulting package full name:
Faulting package-relative application ID:

[kangyu-california]

older PW versions would crash on startup due to github webpage format change, please manually upgrade to 5.41

[daskiiii]

I updated manually shortly before I received this error, and have tested several variations of "-delay_start 10" with higher value, one to any effect.

[kangyu-california]

You may continue to use 5.40, just add "-check_upgrade=0" to command option to avoid crash.
or you may try the 5.41 patch which resolved some platform compatibility issues.

[daskiiii]

that update worked, thank you!

[kangyu-california]

Please take some time to review "Installation" or "Known Issues" section on readme, especially the "-delay_start 10" command option, which works for me.

[mongoled]

Well I have tried with the new patch.
No change for me.
The task runs on startup, PersistentWindows.exe is running in "Details" section of "Task Manager", the scheduled task never stops running and no icon appears in the taskbar.
I will try from a different Windows 10 install.
On the current OS I am running, the user folders main directories, i.e. doucments, downloads, desktop etc are not stored on the local machine but on a different machine (server). Could this be a possible cause? Looking at the notes in the readme, it does not seem this should be an issue

[mongoled]

Sorry, my last post should have been more clear.
The second Windows OS I tried is not saving to a server. Its a "regular" Windows 10 22H2 install with no tweaks.

I will try the executable you have linked and will report back.

Thank you

[mongoled]

Just tried the new executable, in the "regular" Windows 22HS OS and no change.

I checked the event logs and see no warnings/errors with regards to the executable.

Is there somewhere I can look to see why the executable is not loading to task bar ??

Thanks

** EDIT **
I tried placing the folder in "Program Files x86" and "C:"

[kangyu-california]

The trigger of the task should be "When user login" instead of "At system startup", otherwise PW would start too soon when user context is not ready yet.

I have wrote some script to create auto startup task for PW, in case you may want to give it a try
auto_start_task.zip

1. Delete the auto start task you manually created.
2. Unzip the content of auto_start_task.zip into existing PW installation dir
3. Launch a DOS command console with admin privilege, go to the PW installation dir, and run "auto_start_pw.bat"
4. Now press F5 key in task scheduler to refresh task list, and you will see a new task named "StartPersistentWindows..." be created with proper settings.
5. I have put "-delay_start 10" as default PW command option in the ps_auto_start_pw.ps1 file, feel free to modify the command option directly in task scheduler or modify the script, and you are all set.

[mongoled]

Hi again! There was me hoping it was just something I was missing/had done wrong.

So I set the trigger to "At log on", but the issue persists.

I will now take a look at the script.

Thanks for hanging in there for me :)

[mongoled]

OK, found out what I was doing wrong.

Initially I was setting "Run whether a user is logged on or not" from the "General" tab and not setting this from the "Triggers" tab as you kindly pointed out.

Once I set the "General" tab setting to "Run only when a user is logged on" along with the change to the "Trigger" it loads correctly now.

For those who are going to give the script a go. Here is what I did

Opened a powershell window as admin

Changed the directory to the root location of where the files were downloaded.

Ran the .bat file using ./
i.e. ./auto_start_pw.bat

After the task was created I updated the directory where PersistentWindows.exe resides in the "Actions" tab

Thanks ever so much for helping me with this and for the work you have done with this solution

:)