Windows 10 - Program in StartUp folder doesn't start

On a production system with the last stable Windows 10 (vers. 1607, build 14393.447) I like to use a desktop tool, started to run autonatically at Startup.
For clarity, it's worth to say that this tool was installed just before making the win7-Win10 transition, where I chose to keep both files & applications.

Recently I made a complete new installation of the tool (for updating the version) and I could see that the tool does no more start automatically (even though I can see the related shortcut in the two Startup folders, the User one and the All User one), but it normally run if started manually.

Now, considering that :

• the old version of the tool worked well with the last stable version/build of Windows (cited above), meaning that it was automatically started
• the installation of the tool fails (no automatic start) by using both a new or old version

I guess to be on a situation where it's hard to say if the problem is due to the tool or to Windows 10 (which, I know, recently has changed the policy on the Startup folder) so I am stuck on how to solve the problem, or where to look for...

P.S. - In order to solve the issue, I am also in contact with the Customer Service of the tool asking for support, and that's why I cannot reveal for now the name of the tool.
Anyway, I think that it's irrelevant to know the tool name, because my suspects are mainly based on Windows 10 as responsible of the malfunctioning.

 

Try placing the shortcut in the following location:
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\

Alternatively, you could consider creating a scheduled task to start this program at logon.

 

@ WildByDesign

thanks for the suggestion.
I have checked the location you recommended and the shortcut is already there.
It seems that the StartUp folder in All Users happens to be a symbolic link of your location.

I'll check also the Scheduled task way...

 

Unfortunately can not give more advice, because here is so little data, but
1. do not ever make two auto start for the same program (as you said in the first post)
2. on Windows 10 does not work the old Startup folder system (or not work stable )
3. You should use Registry for auto start
4. If even then does not work is one of the two - Windows has been damaged or the given program is damaged

 

@ WildByDesign and kaljukass

I tried both with the Scheduled Task and the Registry keys way, but it doesn't work.

Once manually launched, the program does work.
Now let's suppose , for a moment, that Windows is damaged.
Is there a method to significantly check the system integrity, witout messing it or losing data/applications ?

 

Following the kaljukass's recommendations, I checked the system with the following steps :

1. SFC /scannow
   
2. Dism /Online /Cleanup-Image /CheckHealth
   
3. Dism /Online /Cleanup-Image /ScanHealth
   
4. SFC /scannow again

All is reported as being OK.

Is there anything else I could check ?

I am afraid something in Windows was greatly changed with reference to Security Policy with the last stable release...

Still in contact with the tool support.

 

@ stapp

thanks, it was very helpful.

Anyway, the procedure from Brink was a bit tricky; it worked but after a few seconds the application crashed.
Instead, the procedure from miken (on the same thread) can be considered as a good workaround; it's working, even if the application cannot be minimized in the System Tray.
Thanks again.

 

same as stapp - even when late. MS introduced this "feature" with windows 8 - if already working as full admin there is no difference, but limited or user there is. some need to create a scheduled task for startup. change was for security reason.

 

Understood, but the tool worked well up to Windows 10 version 1511.
I think, instead, that with the Anniversary Update things (such as Security Policies) have been further restricted.
In fact, from old screenshots of my Desktop (captured with 1511 release) the tool icon had a "normal" aspect, while with version 1607 the icon has also the well known "crossed shield", which indicates that the program needs admin approval to run.

If the "feature" was introduced with Windows 8, I do not understand why the issue did not happen at the tiime of Win7-Win10 transition...(custom update, choosing to keep files&apps).