Re:The woes of Windows 10
by marcosdumay on Thursday February 02, 2017 @05:21PM
(#13555409)
> I don't really get why
I got looking. It's an acknowledged bug. MS isn't even calling it a feature. It's just about as old as Windows 10, and unfixed.
I'm not what the point is, given there are probably hundreds of bugs that somebody would say "This is the #1 worst bug in Windows 10." But for me, this is the #1 worst bug in Windows 10.
Assuming they're honest, and in their defence, MS has been much more honest and transparent recently: could you imagine being the one poor soul who's been working on that bug for almost two years now? People keep reporting that bug, and you keep ruling out possible explanations.
Re:The woes of Windows 10
by marcosdumay on Friday February 03, 2017 @06:24AM
(#13559075)
I've indeed seen that kind of thing happen, so yes, there can be some poor soul doing this. But it's still more likely that MS doesn't think Windows not letting you run your programs is a high priority problem.
I've basically given up. I just use [Launchy](http://www.launchy.net/) instead.
Although it's discontinued, so I should really find a replacement.
My workflow for a decade or more was to hit the Windows key then start typing to find indexed apps. It's almost useless to me now and I don't really get why.