Sure, but it's not related to Classic Shell. Right click the taskbar > Search (or Cortana) > Hidden. Same thing for that task view button. I've been using Classic Shell for years, great app. In an RDP session, WinKey+X > Command Prompt (Admin) > shutdown -r System will reboot in 30ish seconds.
Hmmm, always a question of personal preferences, there's no doubt. Still IMHO StartIsBack(+/+) uses the most sophisticated way to provide a Start Menu, since it hooks a DLL only when the Start Menu is invoked, else there's nothing in background at all. Classic Shell and afaik all others need a Service or EXE running constantly. Saw 2 machines become inaccessable due to such tools. None of the machines using SiB ever failed for this reason .
I wish I'd seen this before I went with Classic Shell. I now have CS tweaked the way I like it and it works great and I like it, but if I have any issues I'll switch to SiB.
When it comes to messing with system files/processes (i.e. Unsigned Theme Patches, etc.) there are to ways to handle them. One can alter the files directly or hook into the process in system RAM on-the-fly without touching the files. That's the big difference between e.g. UltimateThemePatcher.vX and Rafaels UXStyle . The latter does not need to fear any Windows Updates (never had problems myself over the last ~4 years since i found the version for Win 7). .... info to consider i assume .
ALT + F4 is even easier, but still having a menu right where you expect to find it, is better. BTW the main reason to use CS is the possibility of using the win 7 style start menu, coupled with the win95 style cascading all programs. AFAIK No other Start menu replacement can do this.
Service approach is way better. If you need to use the clean widows, w/o CS, just kill the CS service and restart explorer
In my observations it's quiet vice versa . Where should be the advantage of a constantly running service that might fail (even if you don't use the Menu at all) over a temporarily hooked dll.
I used it with Windows 8.1 but after messing around with Windows 10 for the past year I've adjusted to the new start button and I'm not using Classic Shell with Windows 10.
If the service fails nothing happens. The service is there just to launch CS. Unless Explorer is killed as well CS will say there, no matter if the service is running or not.
Classic Shell is free though. That was a heavily weighed factor in my decision to try it first since I've never tried any start menu replacement software before yesterday.
OK, noticed different behavior here, had to re-do two machines using Classic Shell and even more nasty Start8 on the other.
Even if SIB was fully in line with CS functionality (and it isn't), CS is free while SIB is paid, so CS still wins.
As my initial sentence stated, a matter of preference. What would be a thing that is missing in SiB in opposite to CS?
Mainly Skinning, customizations. Another thing is the different behavior on dual monitor setup. On some scenarios could be worth to have both installed at the same time because of this.
Ill have to +1 CS as well. Ive never used the start menu until 10 but the explorer bar and tweaks have been sat on my systems for as long as I can remember. Playing with CS Start for the last week and am very happy with it. I particularity like the Metro skin that follows the Windows accent theme. One major option I like and is going to come in handy for all my friends/family is the option to hover to open it. Im gonna try and get them accustomed to the new Start but they will always have a 'backup' Start to go to. Also the Transparent Taskbar is a nice touch SiB has the one option that CS doesnt and I have yet to find a separate tweak to mimic it > Large TaskBar Buttons.
I like the option in SiB to have the start Menu on both of my screens, spares a lot of mouse travels.
The last time I tested it it lacked that function. That's why I had both, installed. ATM I have abandoned the multimonitor setup to a dual notebook setup thanks to the great Synergy, so I can't test the latest evolution on that scenario.