View Single Post
Old 09-27-2015, 10:14 PM   #12
AnotherCat
....
AnotherCat ought to be getting tired of karma fortunes by now.AnotherCat ought to be getting tired of karma fortunes by now.AnotherCat ought to be getting tired of karma fortunes by now.AnotherCat ought to be getting tired of karma fortunes by now.AnotherCat ought to be getting tired of karma fortunes by now.AnotherCat ought to be getting tired of karma fortunes by now.AnotherCat ought to be getting tired of karma fortunes by now.AnotherCat ought to be getting tired of karma fortunes by now.AnotherCat ought to be getting tired of karma fortunes by now.AnotherCat ought to be getting tired of karma fortunes by now.AnotherCat ought to be getting tired of karma fortunes by now.
 
Posts: 1,547
Karma: 18068960
Join Date: May 2012
Device: ....
Quote:
Originally Posted by BetterRed View Post
I would try these before AnotherCat's suggestion to modify permissions of C:\ProgramData\Microsoft\Windows\Start Menu...

...IMO it's better to avoid changing security settings on system owned folders such as the Start Menu folder because the changes will apply to all applications that use the folder...
There won't be any problem:

SYSTEM permission SHOULD be Full Control as stated

and Administrator accounts SHOULD be Full Control.

If worried about Everyone or non Administrator accounts just make them authorised for Read & Execute which is what they should be normally.

Of course, if SYSTEM and Administrator accounts are Full Control AND Everyone and non Administrator accounts are at least Read & Execute already then permissions are not likely to be the cause of the problem. But setting Everyone to Full Control is the killer test because if that doesn't work then the problem is almost certainly not permissions for that folder (one can afterwards always change it back again to its normal Read & Execute if concerned).

EDIT: Solved while I was typing

Last edited by AnotherCat; 09-27-2015 at 10:22 PM.
AnotherCat is offline   Reply With Quote