Classic Shell: Forum

I presently have Classic Shell Start Menu installed without Classic Shell Explorer, Classic Shell IE, or Classic Shell Update. My current Windows installation is Windows 10 Version 1803 (OS Build 17133.73 (First part of the latest Spring Update put out April 10th). All is working fine with no problems.

My question is: Will Classic Shell Start Menu probably continue to work ok as long as CS Explorer and CS IE aren't installed? I have also not installed CS Update due to the current status of CS. I realize we never know what MS might do in the future, but for now I hope I can stick with Classic Shell Start Menu and be relatively safe. Appreciate any comments or suggestions. Thanks.

_________________
Windows 10 Build 1803 (OS Build 17134.48)
Windows Defender
MalwareBytes Pro 3.5.1
HitmanPro
WinPatrol Plus
Macrium Reflect Pro
Classic Shell Start Menu

classic start menu's functionality should be completely unrelated to the other components. However it may(likely will) still break eventually with a new version of windows.

Is the OS build 17133.73 the one that is not going to be released,
until MS fixes some kind of blocking bug, and who knows what else?

I don't have Spring Update yet, but I notice Classic Shell erosion started back
with the old Fall Creators update.
I used to always use the Classic Shell context menu to get to the Manage link.
Then got the error window, after big F update.
I can still right click on properties, then go to Device Manager from there.
All these little crippling changes, another one, no more scrollbar skinning in Win 10, do kind of take the wind out of skinning start menus,
but hey, one can still make great looking original/ported skins.
The one I'm porting over for Win 8/10 in the next week is DarkMatter Subspace.

17173.73 is the "middle" update. It was released to all Insiders on April 10. The bug was found in 17134.1 (rs4 release), the subsequent one. That still has only been released to Insiders on fast track. Luckily I did not get it. So, I have only about 1/2 of the Spring Update, I guess. However, Classic Shell Menu is still working great for me at this time. From what I can find about 17134.1 is that it will just fixes the "bug" some people have in 17173.73, with no significant changes. So, I guess for those of us who are lucky enough to be running ok with 17133.73, we have dodged the bullet for another six months or so.

UPDATE 04/20/2018 Just updated to Windows 10 Version 1803 (OS Build 17134.1 without any problems regarding Classic Shell Menu. It had a pop up reminding me to configure to new OS - and it evidently worked. Spring Update is now complete, I guess - congrats Classic Shell Menu!

_________________
Windows 10 Build 1803 (OS Build 17134.48)
Windows Defender
MalwareBytes Pro 3.5.1
HitmanPro
WinPatrol Plus
Macrium Reflect Pro
Classic Shell Start Menu