Quote from: Xardas2014 on December 23, 2016, 06:57:47 AM

Quote from: golden0707 on December 23, 2016, 06:40:31 AM

Quote from: Xardas2014 on December 23, 2016, 06:27:47 AM

Quote from: golden0707 on December 23, 2016, 05:53:38 AM

Quote from: DebitMe on December 23, 2016, 05:39:21 AM

Any advice, how would I get this to auto start up when Windows 10 starts up?

Hi! Create a link to .bat-file, run shell:common startup , place in this windows . Thats it.

That solution will not work if you have a user password. Unfortunately I'm stuck in that situation on one rig(windows isn't registered so it won't let me remove the password) and I have to teamviewer in, which gets windows to the desktop, so the .bat in startfolder loads Sad

EDIT: After posting my reply I reread and noticed a slight difference. I have my shortcut in shell:startup, not shell:common startup. I see that using common startup is in the ProgramData tree, instead of the AppData tree. So I'll have to test it.

Hmmmm.... I have same situation. W 10 with teamviewer, Windows not registered. Windows autostarts , .bat starts automaticaly.

All ive done : remove user password, remove power sleep, remove auto lock screen, put link in autostart. Have hardware watchdog installed and all going fine for months.

My bet it is because of the difference between shell:startup and shell:common startup. My guess would be that since shell:common startup is in the Program Data folder tree, W10 runs it more like a service so it starts at bootup BEFORE you visit the desktop using team viewer. I'll test it a bit and try to remember to post results. I've put a shortcut into the shell:common startup since I have frequent power outages(3-4 times a month grrrrr) and see what happens. With the shortcut in shell:startup you have to sign into the desktop before the .bat gets activated.

Thanks for the tip about shell:startup, I think the same. Then I searched Internet for the autostart method they allmost all pointed to shell:common startup.