That's what I came here to fix, so I'm not giving up that easily. I found a one line PowerShell script to open the Start Menu; now I just have to decide on a place to put it and set up my own task to run it after Windows does its thing.
My comment about the 10 minute repeat actually related to the absence of any sign of repetition on mine.
I'm wondering if on yours if the 10 minute timeout on idle is triggered when the Start Menu is launched.
You said you couldn't modify parameters of the scheduled task you were able to identify when that was suggested to you.
You should be able to do so (as an experiment) by using PowerRun by Sordum (free).
But take precautions- create a Sytem restore point before using this. Could be like using a sledgehammer in a car engine.
If you disable that task you could at least prove that is responsible.
As for a script- you would somehow need to determine when to run it- and when not to. You could end up with having a Start Menu displayed when you don't want it.
Actually, I said
, but I never said I actually intended to edit it. Editing Windows' default configuration seems like a bad idea to me, particularly when it's something that most users wouldn't even know about, let alone change. M$ might change this in the future, which would likely erase whatever changes I might make.
My current thought is to create my own Scheduled Task, set to run after fifteen minutes idle (the next longest choice in Task Scheduler) - but apparently I have to specify which user to run it as, and "currently logged in user" is not a listed option - and the user to run as also needs some additional permission that I've never heard of.
I'm still looking for solutions, but it's definitely on the back burner now.
Quote