If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
startup issue
Hi All,
Windows 10-1809 home I copied a short cut into startup. If I click on it, it won't run. No error message. Just nothing. It runs from the command line (std user) just fine. And I can run it from startup if I elevate to Administrator. What the heck???? -T p.s. I wish folks would stop buying the home edition! |
Ads |
#2
|
|||
|
|||
startup issue
T wrote:
Windows 10-1809 home I copied a short cut into startup. If I click on it, it won't run. No error message. Just nothing. It runs from the command line (std user) just fine. And I can run it from startup if I elevate to Administrator. So why not right-click on the shortcut, select Properties from the context menu, Shortcut tab, Advanced button, and enable the shortcut to run with administrator privilege tokens? You will get a UAC prompt if that is enabled because, after all, you are trying to run a program with admin privs, just like if you ran regedit.exe. Sounds like your "command line" (aka command prompt aka command shell), well, the shortcut to it or you selecting it from the searchbox which picked the admin tokens, is loading with admin privs, so anything you load within it will inherit the same privilege tokens. Since the program loads okay when loaded inside a command shell that have been given admin tokens, that should've clued you in that the program requires admin tokens and you needed to define the shortcut to also require admin tokens. Since this is a startup item (to load soon after Windows starts), why not add a scheduled event in Task Scheduler. You can run programs on startup and with admin privs with no UAC prompt. A disadvantage in loading programs using Task Scheduler, is that you don't have an option to load the program with its window minimized, and not all programs load minimized (to a tray icon). Shortcuts lets you specify the behavior of the program's window (normal, minimized, maximized). The trick is to then create a shortcut to the program, put the .lnk file somewhere it won't get accidentally deleted, and specify the .lnk file as the command of what to load in the scheduled event in Task Scheduler. p.s. I wish folks would stop buying the home edition! Not everyone is an admin (despite many users think so because, gee, they can fobble with the OS) and figure they don't need to pay another $100 for features they don't expect to use, don't think they will need, and probably won't know how to use. For company use, yes, they should be buying the Pro edition; however, many SOHOs are pretty small, like just 1 or 2 people, and startup costs are personal costs. If they had the expertise, they'd probably determine which OS they need last: first determine which programs they need for their business and then decide on which OS they run. They might end up saving a bundle without the privacy invasion of buying Windows 10 buy going with Mint or some other user-friendly Linux distro. Alas, those aren't the users that would be paying you to support their computing setup. They want to play games, too, and that kills Linux as a candidate OS. They use their company computer as a personal computer. |
#3
|
|||
|
|||
startup issue
T wrote:
Windows 10-1809 home I copied a short cut into startup.Â* If I click on it, it won't run.Â* No error message.Â* Just nothing. It runs from the command line (std user) just fine.Â* And I can run it from startup if I elevate to Administrator. What the heck???? Had a similar issue recently on win8.1 Industry Pro, where syswow64 was involved due to a 32 bit app trying to run from a shortcut ... |
Thread Tools | |
Display Modes | Rate This Thread |
|
|