Pls fix the setup or help me fix this. Error code while installing: 2053 and 2052

Greedings,

is there any way to change shut down in start menu to log off for all users? Or is it possible to install Classic-Shell with this option by command line?

BR

Jens

I tried by myself without success till find that discussion;
http://www.classicshell.net/forum/viewtopic.php?f=7&t=4817

I believe alot of ppl trying to do it, would be good to have it in default skins.
MetroWin10.zip

Many of the inbuilt Windows apps are UWP now. It makes sense to take them out of the folder. Many people are getting Spotify from the Store but it shows up in the "Metro apps" folder.

In the latest release by Ivo, there is a white line above my modified start orb:

I am unsure if this is only an issue on my machine (if so, why?) or if it is widespread.
I am using a textured taskbar and custom start orb, with the Windows 7 style start menu skin.

Was the MIT license the license the original program used or is this a diff license?
Btw, Thanks for taking the time to rehost the code

Help to Share the poll if you care about this project.
https://tpfuser.typeform.com/to/ZNKbN8

(Results:)
https://tpfuser.typeform.com/report/ZNKbN8/MiUlWb2BRqaMvrq4

05/05/2018

Depend on the result of the poll, the new name will be: Classic Start

Future development will be made here: https://github.com/passionate-coder/Classic-Start

Nothing big, but really helpful. Also, older Windows had it.

you should add a link and a Description to the
https://github.com/Open-Shell/Open-Shell-Menu

best regards
Blacky

Classic explorer seems to break folder search within folders search bar becomes un clickable in folder search bar Win 10 1909

Hi there, I'd like to leave this feature request for anyone interested now that the project is open source.

The network flyout is one of the few remaining aspects of Windows 8/8.1 that can't be made to look like Windows 7 with current tools. I'm talking about this thing:

The Windows 7 network flyout was more compact and had more functionality. The Windows 8/8.1 one is uglier, takes a lot of space and in general is pretty dysfunctional. It's a nightmare when you use VPNs or different Wi-Fi networks. The Windows 10 one is only a minor improvement, but Windows 10 is such a disaster in general it's not particularly surprising.
I hope someone considers implementing the Windows 7 network flyout in Classic Shell. Although the original developer has repeatedly rejected the suggestion (so did the developer of StartIsBack), this is an important and widely used aspect of the OS that desperately needs a "classic" overhaul.

Here are some threads from the Classic Shell forum with this feature request, there may be more as well:
http://classicshell.net/forum/viewtopic.php?f=13&t=1608
http://classicshell.net/forum/viewtopic.php?f=13&t=4360
http://classicshell.net/forum/viewtopic.php?f=13&t=5051

I'd like to propose removal of these folders from source tree:
Binary,Executable
ClassicShellPDB

They are part of release, so they should be attached on Releases page.

Moreover they bloat repo history and every contributor has to unnecessarily download them during clone/fetch.

In fact there is no way to get rid of them from history (since they were pushed already), but at least there shouldn't be new binaries pushed to the repo in the future.

I am aware that you can change the name but I believe it should be like this by default

I typically have all the labels off on the taskbar in Win11 for programs. I just like to see icons. I've been having everything groups. I just let Win11 update after a few weeks and it decided to show text labels next to the icons. Of course there is now no way to disable it. I've tried. I guess I have to go back to permanently disabling windows update.

But if CS can add an option to enable and disable the labels it might solve a lot of problems for a lot of people. Turns out most people want the labels and was not getting them so MS "fixed" the problem as usual.

Classic Shell currently consists of a few separate components that are developed and released with one installer that can install one or all of them.

The different components however do different things and I think it would be better for development to make each component, a new software project with it's own name, installer, GitHub issues section and separate releases.

I don't really see any reason to keep all the components under one GitHub repository when they do different things.
One component is a Start Menu, one adds a toolbar to File Explorer (The Windows 8+ name for the Windows Explorer File Browser) and one restores the IE6 look to IE7+,

Each component having their own name would also help with the things talked about in issue #13 as each component could have their own, more accurate name instead of just being a component of Classic Shell.

It also benefit the users that only use one component of Classic Shell as it could be installed on it's own.

The "Classic Shell Update" tool wouldn't really work anymore but it could be replaced by a new software project that handles automatic installation of new versions of each the different programs.
The replacement software could be a build of Google's Omaha project which can handle the automatic checking for updates and update installation for multiple software projects.

Omaha is the project behind Google Updater that handles automatic update checks and automatic update installation of all Google software.

Omaha is a little bit complex but when setup, it can work quite well.
Here is how Omaha works:

1. Each program has their individual installers that automatically install Omaha when they are installed if it isn't already installed by another program.
2. The installer registers the program with Omaha via registry entry.
3. Omaha runs in the background at various times via the Task Scheduler function of Windows to check for new updates.
4. If an update is available then the programs new version installer is downloaded and installed slightly in the background when the program is not running.
5. Omaha will be uninstalled when the last program to register with it is uninstalled.

The fork could be called "[New Organization] Updater" where "[New Organization]" is the name of the new organization in GitHub as discussed in issue #13.

All the newly split out components could be repositories under this GitHub Organization too.

I want to implement the following:

• Reboot to Safe Mode
• Reboot to Firmware
• Reboot and Re-open running applications
• Shutdown for Fast Startup (or default "Shutdown" to this and add "Full Shutdown" when hybrid startup is enabled)
• Shutdown without Updating (#31)

It would be wonderful if you can get me back the full screen start menu with charms bar, also the aero taskbar, also teh old system icons.

Thanks so much!

Shawn

I have been using Classic Shell for quite some time with no problems. As of today, explorer.exe began using 30-50% CPU constantly when Classic Shell is running. Closing it immediately fixes the problem, and reopening it causes the problem to reoccur.

In process explorer, the offending thread is shcore.dll.

Here is the stack trace:
win32u.dll!NtGdiSelectBitmap+0x14
gdi32full.dll!SelectObjectImpl+0x1ed
user32.dll!CreateIconIndirect+0xf94
user32.dll!CreateIconIndirect+0xbaf
user32.dll!CreateIconIndirect+0xa6a
user32.dll!ReleaseDC+0x25a
user32.dll!CopyImage+0x66
comctl32.dll!ImageList_Create+0x1360
comctl32.dll!ImageList_Create+0xc9b
comctl32.dll!ImageList_ReplaceIcon+0x98
Explorer.EXE+0x4784c
Explorer.EXE+0x45681
Explorer.EXE+0x404b7
Explorer.EXE+0x3932c
Explorer.EXE+0x33b90
Explorer.EXE+0x32d42
user32.dll!CallWindowProcW+0x4dd
user32.dll!CallWindowProcW+0x8b
comctl32.dll!DefSubclassProc+0x2a5
comctl32.dll!DefSubclassProc+0x77
ClassicStartMenuDLL.dll!ToggleStartMenu+0x1370
comctl32.dll!DefSubclassProc+0x2fe
comctl32.dll!DefSubclassProc+0x142
user32.dll!CallWindowProcW+0x4dd
user32.dll!CallWindowProcW+0x1cc
user32.dll!CreateWindowExW+0x1210
ntdll.dll!KiUserCallbackDispatcher+0x24
win32u.dll!NtUserPeekMessage+0x14
user32.dll!PeekMessageW+0x88
Explorer.EXE+0x36a4d
Explorer.EXE+0x95db3
shcore.dll!Ordinal247+0x1b5
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

Hope I'm in the right place (is this the "official" fork of classic shell?)......when I do a "START cmd ENTER" I am wanting to open a command prompt. However, due to the way this works on classic shell, the selected file will typically either be some batch file (due to the .cmd extension) or sometimes a different shortcut like "GIT cmd".

I think better logic would be (and I don't think this should mess up anything for others?):

a) ignore file extensions
b) if there is an exact match (in this case cmd.exe), choose that as the default selected file

Since my PC updated Windows 10 to the April 2018 Update, Classic Start Menu does not appear anymore when I click on the Start button. Instead, I get the regular Windows 10 Start menu.

If I start it manually, then I have the Classic Star Menu until I log out or turn off the computer.
I have tried in the settings to uncheck "Start automatically for this user" under "General Behavior", restart the computer, check it again and restart again (Sometimes this technique works in other programs) but no way.
The only way I have found to bypass this issue is to add a link to Classic Start Menu in the Startup folder, but the option in the settings doesn't seem to work anymore.

When Classic Shell was released, its main intention was to bring back some of the useful things that Microsoft in their infinite stupidity had decided to remove or change into a less useful behaviour.
Classic Start Menu has three different styles: a Classic style, a classic with two columns and a Windows 7 style.
I use the Windows 7 style (in conjunction with cascading programs submenu) because this is the one that offers more useful options since it includes things that were introduced in Windows 7 and Vista but were not available in Windows XP (the classic Style).

It happens that Windows 10 has also introduced some useful things in its Start Menu (not much but a few) but these things are not available in Classic Start Menu. One of them is an icon to access the Configuration window. We still have the Control Panel but many options have been moved to the Configuration window so nowadays you have to use it like it or not. I think a link to the Configuration in the right column would be great.

The other thing I miss is the mosaics panel introduced with Metro. I know many people hates this mosaic but it can be useful for many people too, so It wouldn't hurt anyone if Classic Start Menu had the option to include it as a third rightmost column that could be disabled in the settings for the people who prefer to not have it.

I know you can still access the regular Windows 10 start menu by shift-clicking Start, but it would be easier for the user experience to include this two things directly into Classic Start Menu.

Last but not least, we should also look into what Windows 8 and 10 have introduced to the File Explorer that we are missing by using Classic Explorer. (I don't want to get into details here but I think this could be a theme for another discussion).

I noticed the power button menu (ie the flyout with sleep, hibernate, shutdown etc) does not honour the settings made in Control panel's power options.

If you go to CP -> Power Options -> "Choose what the power buttons do", there is a pane with "shut-down settings" that has 4 checkboxes. 3 of these turn the power menu's buttons on or off (or rather show/hide them). Unchecking any of them doesn't affect the menu,

In the code (CMenuContainer::ToggleStartMenu), I noticed there was code to detect the power options from the OS (using GetPwrCapabilities) but this only returns power capabilities, not the control panel choices.

The choice of showing the buttons is stored in the registry, in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FlyoutMenuSettings

I don't know if there is a system API to retrieve these.

Greetings!

Please see this...

https://answers.microsoft.com/en-us/microsoftedge/forum/msedge_open-msedge_win10/how-can-i-delete-an-old-ms-edge-icon-stub-in-apps/fd413321-6a3d-427c-8e6c-a5f16de01d48

Any help appreciated.

TIA :)

Hi I hope someone might be able to help. We have Open 4_4_142 on two laptops. There have been no problems over the years until my wife suddenly had things go wrong. The W10 start andW10 desktop with basic tiles appeared in place of the Open setup and desk top shortcuts she uses. The taskbar was the basic W10 one as well. I have uninstalled and after re downloading and reinstalled Open Shell, I used my setting but its now a mix of open shell start batten, click on it and the Open Shell W7 style start is there but with The W10 desktop and task bar. To confuse things as I have tried things the old desktop can be seen on occasion but it goes back to the W10 one. Sorry if this is a bit confusing, it in my younger years it would be an interesting challenge, but now its just a pain and my wife is finding it very difficult to cope with the screen as it is.

This is important because more settings are moving to the settings app (from the Control Panel) and new settings are being added to the settings app.

This is a very serious issue that hits me with the slow ring build 17692:
The first click on the start button opens Classic Start Menu normally; The second click only opens half of it; Then all subsequent clicks display nothing. Shift+click displays the native Windows start menu normally.
The same problem was also reported on the Classic Shell forum for the fast ring build 17704:
http://www.classicshell.net/forum/viewtopic.php?f=12&t=8457
(Side issue: It's not possible to register on that forum anymore, as the captcha system it uses is shut down.)

Update: I just noticed that the problem was already known and reported there:
https://github.com/passionate-coder/Classic-Start/issues/11

Since idk how to reach you on a better way...
How about suggest Ivo Beltchev to buy http://www.classicshell.net/ and continue to maintain the domain there?

it would be nice to have this code build automatically on appveyor.com.

ho installato Open-Shell per poter spostare la barra delle applicazioni a sinistra del monitor, cosa non possibile in Windows11, purtroppo neanche Open-Shell sembra in grado di farlo, forse qualcuno sa come fare, senza fare troppi danni al sistema.
grazie Rolando

shutdown -g does a restart AND after logging in it automatically reopens your apps that were open at the time of restart. it is what it does when you 'update and restart', except you can trigger it manually without also updating.

windows has no native GUI for this, but can CS add this as an item in the shutdown menu?

thanks!

don't know where hydrated reboot comes from, I just saw a Microsoft engineer using the term on reddit

I have seen the blog post and I have read articles about Windows 10 being awful.

Would it be possible to improve ReactOS' compatibility with Classic-Shell?

Best regards,
Blacky

EDIT by @XenHat: Improved wording.