Autostart creates instance in task manager that doesn't work

[logarythmic]

I've tried uninstalling and messing around with my startup app settings and task scheduler in order to get this fixed without any luck. When it's started in either two of those ways it will run as a Background process with 1 MB of memory but not work at all. Only when I manually click on does it launch a new instance that takes up 2.5 - 4MB of memory does it work.

Any help would be much appreciated.

[RamonUnch]

Try to add a 10s delay in the task scheduler.
Have a look to #15 and stefansundin/altdrag#77

EDIT:
SOLUTION 1: Use my config

1. Download this AltDrag-task.zip file.
2. Extract its content: AltDrag.xml
3. In the Task Scheduler, select Action->Import Task... and select the AltDrag.xml file
4. Go into Actions, double click on the path to AltDrag.exe and Update it.

SOLUTION 2: Manual config
Good parameters for the task:

1. Run as Users and highest priviledge
   

2. Enable AltDrag autostart even whe disconnected from AC Poser:
   

3. Do not kill AltDrag After 3 days!
   

4. Add a 10s delay to startup
   

[logarythmic]

I saw that and gave it a try, but that also led to an instance of 1.3 MB instance that did not work. There was also a bat file I tried to run that killed any running instances before launching it again after a delay. The file path I'm using in Task Scheduler is C:\Users\Logarythmic\AppData\Roaming\AltDrag\AltDrag.exe

[RamonUnch]

Strange, so you mean that when you lunch AltDrag from the autostart it does not work.
Does it work at least when you lunch it by doubleclick after a clean restart?
I think this old bat served to kill a AltDrag when it was stuck in an infinite loop that has been fixed a while back now.

I have no idea what could cause the problem then.
Just in case give me your ini file (you can zip it and attach it in a post).
Which version of windows are you using?
I guess you are trying to lunch AltDrag as admin?

[RamonUnch]

Does the same thing happen with the original AltDrag?

[logarythmic]

Anytime I manually launch or double click it works perfectly. I actually switched to your version in the hopes of fixing this. It only happened in the past week while trying to task schedule my way out of the annoying UAC prompt. Everything but autostart works perfectly, it's really weird.

(AltDrag.zip)

Currently on OS build: 19042.928 of Windows 10 Home

[RamonUnch]

Ok, I will try to get a deeper look into this.
I guess I will make a version that logs out all the possible information.

You mean that the "normal" autostart (that can be checked in the config dialog) does not work either?
The only problem is when using the task scheduler?

It is true that I did not test much using the task scheduler. As I said I will investigate more because there seems to be some reproducible problems around here...

[logarythmic]

Awesome thank you! I'm really curious to see what the issue is. I've been experimenting with having autostart on and off in tandem with task scheduler with no success. I'll let you know if I can think of anything else that might lead you in the right direction.

[RamonUnch]

Try with this combo AltDrag.exe+Hooks.dll:
AltDrag_log.zip

rename the old altdrag.exe+Hooks.dll in something different and copy the new ones.
AltDrag should create a ad.log in its dirrectorry when lunched, thus:
Try to lunch AltDrag by double-click, in this case everything should work fine.
then exit AltDrag,
then rename the ad.log in ad-normal.log, you ca give it a read if you like.
Then keep AltDrag off, set up the autostart in your tasks, restart and rename the new ad.log in ad-sched.log, then send me both logs and we will see.

[logarythmic]

I think I did this right, take a look and let me know if that's what you were looking for. It did the thing it usually does, so I hope it was accurately captured.

Logs.zip

[RamonUnch]

Could you try again a restart with the scheduled task?
The log should logically always start with ALTDRAG STARTED WITH HINSTANCE 0x... something.
Even if AltDrag does not work I except this message because it is the first one. It seems the ad-sched.log you gave me was taken in the midle of the execution.
So just leave ad.log alone, and restart with the scheduled task again, Quit AltDrag and send me again the new ad.log.
the ad-normal.log does contain all the info and finishes at Starting AltDrag message loop... which is what should be the only display until AltDrag is exited.

[logarythmic]

I think I just figured it out after googling a bit about the task scheduler. I changed it from to "Run weather user is logged on or not" to "Run only when user is logged on" which fixed it at least for this current restart. No idea why the autostart within the app itself wasn't working, but at least there is a workaround for the moment.

Here is ad for when I exited out and manually ran the task:
ad-nousertsched.log

[RamonUnch]

"Run only when user is logged on"

This is actually expected, AltDrag can not do anything for the current user if he is not logged on.
AltDrag is not like a driver and only hooks the keyboard and mouse of the current user, this mean that there are no interactions with other users even if you use elevated mode.
AltDrag also needs for the proper display of the tray icon that the taskbar is lunched.
I guess This is why it was not working. I thought that this option was the default and I did not think about it, but it make sense.

Anyway your probles should be fixed. It should not be possible for AltDrag to work if the option is "Run weather user is logged on or not" and there is no possible way to make it work like this.
However the "normal" autostart should be fixed still.
I will add to the txt file the details on how to prepare this scheduled task

EDIT: This Also explains why the log file was partial, because it contained only the messages triggered by the Logon to the system with altdrag already running.

[logarythmic]

Ah okay, that's really good to know! Thanks so much for the help, I really appreciate it.

[RamonUnch]

First response was updated with details to help setting Autostart