New
#11
Since I don't have this particular problem (and I'm a little surprised that you do) I cannot really give a definite answer. But here's a few clues:
- The taksbar folder is located at %AppData%\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar. So you could try using the trick upon the content of that folder directly. Don't change the folder's security (unless it is suspicious), just the files in it. I don't know what side effects may occur if you reduce or increase the security of the folder itself, and it is probably best not to find out.
- If what you are pinning has been marked in some way as "from the internet and unsigned" it gives Windows an excuse to worry about security. Try removing the pinning, shutting down the program, and then putting a shortcut in a desktop folder, use the trick upon it, and only then use it to start a program that you then pin on the taskbar.
- If there's anything peculiar attached to the actual executable file via NTFS ADS (Google it, tho' it should not usually in itself cause a problem) then you can clear all that out by MOVING the file to a FAT drive and then moving it back to the NTFS drive. That's the easiest and quickest way to kill off all streams under ADS.
- Finally, where does the EXE reside (not the shortcut) that you are effectively pinning to the taskbar? Is it where most programs are - the protected area under Program Files or Program Files (x86)? Or is it on an external source such as a NAS or a networked PC elsewhere. This might also be prompting Windows to be a pain about security. Put the program somewhere local and possibly hand-place it into an appropriate place under the programs folders.
- Last of all (and really this should have been first!) check that the shortcut is not configured for "Run As Administrator" under either the advance settings or the compatibility settings. Also check that Windows hasn't slapped compatibility settings of ANY kind upon the EXE itself - if it has, you may be onto a loser. In the same vein, consider whether the developer has implanted a Manifest with the EXE that causes it to demand to be elevated whenever it is run. This incidentally might in some circumstances cause additional issues if the developer has not also provided some kind of application security certificate. All of these last cases come under the hat of "legitimate" UAC causes. Windows is, after all, trying its level best to protect you.
I am intrigued, so if you do manage to work it out or have any further info, then please post again :)
Last edited by BigAlUK; 13 Jan 2019 at 21:06.