Solved Start Up folder - Why won't this program start?

[TrunkMonkey]

Yes this is all under admin. I can get it to launch using a task, however no dice on the notification which is what I am really after here.

 

[TrunkMonkey]

Solved

Ok, here's what you need to get speedfan to startup AND give you the notification, all of it elevated:

1) SpeedFan Shortcut Launcher



This task launches "sdfn", which is the task created Brink's first tutorial.
But SpeedFan requires 2 starts, 1 for the process, and 1 for the notification. This one is for the notification and is 30 second delayed.

==================================================================

2) Launch SpeedFan the process



This task starts the speedfan process. You will hear your fans kick down about 10 seconds after log
in.

Not true you can do it with just the first part now that the "Add Arguments" was added. I will leave the 2nd part just because it does work, but it launches a 2nd session of SpeedFan which is no good when you're trying to control fan speeds.

 

[Brink]

I'm happy to hear that you got it sorted TrunkMonkey. Thank you for posting back with your results.

 

[TrunkMonkey]

Yeah you were right. What I was missing was the "add arguments" part of the SHORTCUT. You may want to look at the tutorial. I very well may have just missed it, but it seemed like that wasn't clear enough. Probably because it's a shortcut to a TASK, and not a program. Maybe worth mentioning.

 

[Brink]

I added a tip under step 15 to help with that.

http://www.sevenforums.com/tutorials/67503-task-create-run-program-startup-log.html

 

[A Guy]

Glad you got it sorted I mentioned starting a 2nd and then stopping the first

http://www.sevenforums.com/software/291209-start-up-folder-why-wont-program-start-2.html#post2411552

That is said to fix the issue of it wanting interaction.

A Guy

 

[TrunkMonkey]

Can't get this to work again

After a fresh install of Win 7 I'm again trying to get SpeedFan to start up. So I followed the 2 tutorials to the letter and have yet to make it work again. I think part of my problem may lie here:



When you browse to the target shortcut, you get this:



That path is where the short cut POINTS TO (Task Scheduler), instead of pointing to the shortcut itself and running it.

I have also tried "C:\SpeedFanStart" and "C:\SpeedFanStart.lnk" however neither has worked (I put the shortcut in the root directory of the C: drive)

I know the shortcut works, as I can double click on it and SpeedFan starts running.

Help

 

[Brink]

TrunkMonkey,

The issue is that Windows will not run elevated programs at startup by default.

If you like, instead of doing that, you could use the tutorial below to create an elevated shortcut of SpeedFan, then place the elevated shortcut in your Startup folder.

http://www.sevenforums.com/tutorials/11949-elevated-program-shortcut-without-uac-prompt-create.html

Hope this helps,
Shawn

 

[TrunkMonkey]

Hey Brink,

Thanks for the reply. However I have already completed the tutorial and have a fully functioning shortcut which launches SpeedFan with no UAC prompt. It just won't start up. I'm wondering if it's something to do with Step 16 in the "How to Create a Task to Run a Program at Startup and Log On in Windows 7" tutorial. You show it launching a program or .exe, which you can browse to. However when I browse to my shortcut created in the first tutorial, it shows the path in my attached picture. I was hoping that would help. Read my post again and see what you think the problem is.

Thanks.

 

[TrunkMonkey]

Easy Fix

It finally dawned on me to simply try dumping the shortcut which launches SpeedFan without UAC prompt into the Startup folder in the START menu. Voila, SpeedFan runs at startup without issue.

From what I can gather, the tutorial "How to Create a Task to Run a Program at Startup and Log On in Windows 7" works for executable files, but not for launching shortcuts which point to Scheduled Tasks. However, I could be wrong...

Regardless, problem solved!

 

[A Guy]

It finally dawned on me to simply try dumping the shortcut which launches SpeedFan without UAC prompt into the Startup folder in the START menu. Voila, SpeedFan runs at startup without issue.

From what I can gather, the tutorial "How to Create a Task to Run a Program at Startup and Log On in Windows 7" works for executable files, but not for launching shortcuts which point to Scheduled Tasks. However, I could be wrong...

Regardless, problem solved!

Errr, from Brink's post above

If you like, instead of doing that, you could use the tutorial below to create an elevated shortcut of SpeedFan, then place the elevated shortcut in your Startup folder.

A Guy

 

[TrunkMonkey]

Ha! So it was. Although since I didn't see it I'm still taking credit for this great discovery

What confused me were posts #2 and #6 which both direct me to create another task to be able to run at startup. Nothing about the startup folder. I think the tutorial should be modified to mention it. Shortcuts to scheduled tasks cannot be launched at startup using tutorial "How to Create a Task to Run a Program at Startup and Log On in Windows 7". Shortcuts to executables can, however.

However, you could use the tutorial as a workaround to create a task for an elevated shortcut that will run SpeedFan without getting a UAC prompt, then at step 23, use the "run at startup as a task" option to create another task to run the elevated shortcut from the first task.

If so, be sure to create a second task using the run at startup as a task option to create a second task to run the elevated shortcut.

 

[A Guy]

There is a difference between creating a task, and just placing an item in the startup folder. I think it would just be confusing to put that in a scheduled task tutorial. A Guy

 

[TrunkMonkey]

...unless you're trying to launch at start up a shortcut to a scheduled task (which is what you create in "How to Create an Elevated Program Shortcut without a UAC Prompt in Windows"). It would have saved me hours of dilly dallying to know prior to today that for my situation it wouldn't work. Plus, I was instructed to use a scheduled task at startup. Twice. Surely a small notation in the tutorial wouldn't be a deal breaker for folks in my situation.