Oh dear, it seems that Windows UAC doesn't like Web Display!
I could think of two things that might be causing the problem, UAC or a missing DLL - UAC was the more likely if WD had previously been working.
I believe that a fairly recent Windows 11 update has changed the way in which application security (UAC as was) works.
WD as-built requests administrator privileges as it needs to open a specific (configured) socket to support the web server it hosts.
Please can you try the same commands again, but this time start the command window with 'Run as administrator' - I'd like to see if WD is allowed to run.
If it is then I would suggest changing PF3 to 'Run as administrator' to see if that fixes things - anything that PF3 starts should inherit its privileges.
Martin
PS Dave does himself a disservice - I had to deal with far worse during my long career in IT
