Thank you for posting this mood. I have installed the new Classic Start (no longer Classic Shell) on my 2 pc's and it works fine. I was really happy to see GitHub take this over. One note to those installing it, be sure to save your XML settings for Classic Shell before you install Classic Start, or you will have to recreate your present set up. Everything installs in the Classic Start Folder for the new one.
On the settings page for Classic Shell there is a button at the bottom right called "Backup" - there you will find a dropdown with options to backup & restore etc
Miss Classic Shell? Classic Start comes to the rescue July 8, 2018 https://www.ghacks.net/2018/07/08/miss-classic-shell-classic-start-comes-to-the-rescue/
Is it needed to uninstall the Classic Shell before installation of this Classic Start or can it be installed over the Shell?
Better to uninstall the Shell because the Start creates the new own folder. The first impression: - it is Classic Shell in fact, it is not its fork, it is rebranded Shell - import of settings from the Shell does work - update via GUI doesn't work yet - selecting another language doesn't work yet - a link to the home webpage in GUI is still to the Shell All in all it is a pretty fine successor of the Shell.
Really pleased that Classic Shell is to be continued as Classic Start.. I was dreading time when a Windows update would kill it off.
I tried this yesterday, after StartIsBack++ stopped working. But as with Classic Shell and some other Start Menu replacements, it does not handle having a lot of of programs installed very well, leading to a delay between pressing the Windows key and the Start Menu opening. I've now switched back to StartIsBack++ again as it opens right away and is working again now. One day, when I finally manage to upgrade to the latest build of Windows 10, I'll switch back to the native Windows 10 Start Menu.
And that redirects to Open-Shell, https://github.com/Open-Shell/Open-Shell-Menu, "Reborn of Classic Shell (Ivo Beltchev) - Classic Start (passionate-coder)"
Thanks very much, mood. I read the line "Rebrand to Open-Shell (#36) (#58)", but I overlooked the (#36) and (#58) URLs.
I can`t figure out Github at all, is it pointless for Win7 users to update to this new fork ? (I presume any fixes are for W10 as on W7 it`s already stable.)
It's pointless not only for Win7, it is pointless at all. And if really, then maybe some for grandfathers and grandmothers who has planned to die with Win 8. None other people should not need for it because Win 7 and below already have their own and enough good startmenu, Windows 10 have even two startmenus, which both are very good and fully editable, if someone don't love defalt content and look. Why should someone need such a unstable handcraft? If you have bought anything for yourself, you should first learn how to use it. So - if You have bought or get Windows 10 somehow, customize the two existing start menus like you want - it should to be the first thing to do!
Not sure if this one offers the same feature as original, but as a user who is going to go to the end with the also outstanding Windows 8 besides accessing programs etc. the changing on the fly of the new/modified start button bitmap sort of gives things just a touch of personalization. Anyone? Classic Shell is been like an old wallpaper on these 8 systems.
Well, I don't think that's for you to decide, whether for someone else the use of a tool like Classic Shell or Open-Shell is pointless or not. Some people don't like the Windows 10, 8 or even 7 start menu and it's options for customization, and like to use a tool like Classic Shell or Open-Shell to customize a start menu. It's the same as with any option or any application, anyone can choose any tool that is most to one's liking.