Error message upon login to system

[kylec]

Hello,

Recently I've had two systems which started showing an error message whenever a user logs onto the system. This message persists even after uninstalling the application which was built using Advanced Installer 11.3. So far this has happened on just two systems one being Windows 8.1 and the other after upgrading from Windows 10 (build 10071) to the latest Windows 10 (build 10130). At first I suspected it was due to a Windows update, but I went and removed any updates that were installed after the message started, but it persists.

Has anybody else come across this issue, and is there any way to resolve it? It almost seems as if there is some hidden registry key remaining on the system.

Capture.jpg (14.54 KiB) Viewed 3722 times

Thank you.

[Dan]

Hello,

Can you please take a look in the Windows Event Viewer and see if you can find useful details about this error message?

Also, can you please check to see if there is any schedule task to run at the user login? The related scheduled task could be created by a setup package built with Advanced Installer which need to resume after a system restart triggered by a pre-install prerequisite installation.

Please let me know if that helped.

Best regards,
Dan

[kylec]

Dan,

Thank you for pointing me into the right direction on this. I did not find anything in the event viewer, however I did find that there were a couple items in the Windows Task Scheduler. After deleting these items from the task scheduler the errors have stopped when logging into the system.

These installer projects have not changed in a way that would cause this from what I can tell as they've been fairly static. Also, while one of the projects does use the updates feature it is set to manual, and not to use the task scheduler. The other project which seems to have caused this does not use the update feature.

Any other reports of this kind of issue and is there any thoughts on what may have caused this suddenly?

[Dan]

You're welcome,

I'm glad you got this working.

I'm not sure why you encountered this behaviour. As I said earlier, the related scheduled task could be created by a setup package built with Advanced Installer which need to resume after a system restart triggered by a pre-install prerequisite installation.

Best regards,
Dan