Hi Mike.
Yes, we actually resolved our issue. The issue was due to our VDIs (VMs) having been migrated from Windows 8 to 10 rather than having been given a clean Windows 10 install by our server team.
What happened was that upon restart of our VDIs the LogonUI.exe thread which is present when at the login screen, was being duplicated over and over again on the VDIs, so ever few minutes a new thread would popup, leaving after a short while, tens if not hundreds of copies of the LogonUI.exe thread.
This in turn made it impossible for Blue Prism to attach and interface with the "correct" thread of LogonUI.exe. But that was not all really, since a "true" LogonUI.exe thread consumes around 10-30 Mb of memory, these fake ones only consumed on the order of 400-800 Kb of memory. So something was fundamentally broken in the LogonUI.exe thread. Funny thing though, doing a RDP to one of the VDIs would login the machine correctly for some reason.
Reinstalling Windows 10 from scratch fixed this issue, and this fixed our LoginAgent issues. Your issue may of course be different, but this is what happened in our case.
Best regards,
Jesper
------------------------------
Jesper Hededam
Developer
Codan
Europe/Copenhagen
------------------------------