Classic Shell no longer in development, and now open source

Page 25 of 79 FirstFirst ... 1523242526273575 ... LastLast

  1. Posts : 1,099
    Win 10 pro Upgraded from 8.1
       #241

    margrave55 said:
    I agree. Quite dodgy ... both the updates and the policy.
    What I don't see discussed here is security. Now then with most of us here in this forum we are educated and understand security most of us could get by without much AV or Malware software.
    But there are millions of computers out there being used by ordinary people that don't have a clue, don't want to have a clue all they want to do is log on to facebook or other social media. Don't think twice about opening attachments to email or even know that Malware and viruses come in by simply opening up a picture. For these people, I believe MS and other Software manufacture have to keep plugging security holes and making the whole experience easier from them. I work with these people all the time friends and friends of friends. So I believe that yes these updates do need to be force fed to them. It's only us that understand what going on that try to block them. People that don't care to educate themselves about computer/Devices are going to have to depend on tech support, Forums like this one and there local computer repair shop.
      My Computers


  2. Posts : 42,983
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #242

    JohnBurns said:
    I have installed and tried StartX Start Menu and while it is ok, it does not compare with Classic Shell Start Menu - I will put it away with Stardock Start 10 and StartIsBack, just in case I HAVE to use one of them in the future. Please, GitHub, convince MS to work on Classic Shell for future use. That along with a Dark Theme for web are my requests for the future. And, yes I have included these in "feedback" to MS.
    How about identifying features of CS you'd like to see in Start Menu X (which is the nearest I know of to CS) and asking the developer if they would consider them?

    I've asked about one small point- response after about 3 days.
      My Computers


  3. Posts : 622
    Windows 10 Pro x64
       #243

    I went back to Classic Shell right now it has the most features and it is stable. Start10 seams so unpolished but if CS is not forked and updated by the time RS5 goes final I will be forced to use Start10 as the W10 start menu is terribly limited.
      My Computer


  4. Posts : 1,811
    W7 Ultimate SP1 (64 bit), LM 19.2 MATE (64 bit), W10 Home 1703 (64 bit), W10 Pro 1703 (64 bit) VM
       #244

    Wynona said:
    Microsoft doesn't intentionally break anyone's software. It's up to the author(s) to follow Microsoft's guidelines, and if they can't, then it's their fault if their software won't work.
    MS doesn't tell anyone what they've changed until after they've done it.

    Wynona said:
    Security companies are able to keep their AVs up to date and working with Microsoft 10.
    MS "definitely" told Avast about all the changes they made.
    Avast Shares Fix for Broken Windows 10 April 2018 Update Machines

    Wynona said:
    They may be able to block an update for awhile, but I'm pretty sure licenses between Microsoft and corporations are far more stringent than those between an individual and Microsoft.
    The reasons for renting the Enterprise version are:

    • Permanent blocking of dodgy updates
    • SLA to force MS to fix your Windows installations


    Wynona said:
    Sorry, but I don't find Windows Updates dodgy. I don't block updates, nor do I find updates broken.
    Good to know that we can ignore the dozens of articles on multiple sites about W10 update/upgrade issues.
    Surface Pro (2017) owners hitting Win10 1803 update blue screens. Now we know why. | Computerworld
    Windows 10 version 1803 does not play nice with some Solid State Drives (SSD) - gHacks Tech News
    Windows 10 April 2018 Update biggest problems and complaints | Windows Central

    Also good to know that we can ignore the dozens (if not hundreds) of threads on TenForums too.
    Here are some examples from the start of May 2018:
    "Choose your keyboard layout" Problem
    Random Failure of keyboard and black screen - Windows 10 Forums
    Seems 1803 upgrade has problems, I rolled back to 1709 Solved - Windows 10 Forums
    Many 1803 Problems - Windows 10 Forums
    File explorer issues since windows update 1803 - Windows 10 Forums
    Windows update last night - laptop not working now - Windows 10 Forums
    fullscreen issues Win10 1803 update - Windows 10 Forums
    1709 and 1803 cause streaming video issues - Windows 10 Forums
    Reverting the inefficient right-click context menu for audio in 1803 - Windows 10 Forums

    Clintlgm said:
    For these people, I believe MS and other Software manufacture have to keep plugging security holes and making the whole experience easier from them. I work with these people all the time friends and friends of friends. So I believe that yes these updates do need to be force fed to them.
    The question is what's worse, a secure unproductive brick, or a vulnerable machine that still works?

    I notice that you like Macrium.
    Windows update last night - laptop not working now - Windows 10 Forums

    IMO you're probably better off relying on Macrium than MS.
    Researchers have uncovered a sophisticated rootkit-based adware, mainly prevalent on Windows 10 devices, that has been operating covertly for six years.
    ...
    Significantly, despite Windows 10 being fitted with in-built technology to protect users from rootkits, the overwhelming majority of samples, 90%, were found on devices running Microsoft's latest operating system.
    Zacinlo malware threatens Windows 10 PCs' security - Operating Systems - PC & Tech Authority
      My Computer


  5. Posts : 512
    Windows 10 Version 1909 (Build 18363.815
       #245

    This thread is beginning to sound like the US citizenry. It is divided, one side MS Haters, one side MS Fanboys. Guess it's just the way we have become accustomed to living. Sad!
      My Computer


  6. Posts : 17,661
    Windows 10 Pro
       #246

    JohnBurns said:
    This thread is beginning to sound like the US citizenry. It is divided, one side MS Haters, one side MS Fanboys. Guess it's just the way we have become accustomed to living. Sad!
    I must completely disagree! This is not about, and has nothing to do with MS haters and lovers / fanboys.

    Simple: Microsoft has the APIs for third party software makers to use to get their stuff to work with Windows. In this case, one software maker considered the pros (income through donations) and cons (semi-annual feature upgrade requiring major changes twice a year) and decided he / she has no more time / capacity / interest to keep updating the software.

    Microsoft did not kill Classic Shell. The programmer did.

    Kari
      My Computer


  7. Posts : 512
    Windows 10 Version 1909 (Build 18363.815
       #247

    Proof of what I stated, Kari, just read the posts.

    MS doesn't tell anyone what they've changed until after they've done it. (post 243)

    Microsoft did not kill Classic Shell. The programmer did. (post 245)
      My Computer


  8. Posts : 17,661
    Windows 10 Pro
       #248

    JohnBurns said:
    Proof of what I stated, Kari, just read the posts.
    So you are saying that your posts in this thread, and those of other members will explain the reasons better than the owner / programmer of Classic Shell told himself?

    From the original announcement:

    There were few factors that led to my decision:
    1) Lack of free time. I have other hobbies that demand my time, some related to software and some not. It requires a lot of effort to add new major features to Classic Shell and keep it relevant. Even keeping it running on newer version of Windows is a lot of work. That leads me to point #2

    2) Windows 10 is being updated way too frequently (twice a year) and each new version changes something that breaks Classic Shell. And

    3) Each new version of Windows moves further away from the classic Win32 programming model, which allowed room for a lot of tinkering. The new ways things are done make it very difficult to achieve the same customizations
    It might be the fact that I am not a native English speaker, that I really do not understand what I am reading, but to me it looks exactly as I said in my previous post: maker of Classic Shell did not want to continue after considering the pros and the cons.

    I completely fail to understand how that could be Microsoft's fault?

    Kari
      My Computer


  9. Posts : 512
    Windows 10 Version 1909 (Build 18363.815
       #249

    I am not arguing for either side. My point is someone need to find a way to make Classic Shell Start Menu work in the future and not quibble about whose fault it is or is not. Let's just solve the problem!
      My Computer


  10. Posts : 17,661
    Windows 10 Pro
       #250

    JohnBurns said:
    I am not arguing for either side. My point is someone need to find a way to make Classic Shell Start Menu work in the future and not quibble about whose fault it is or is not. Let's just solve the problem!
    I think the original creator of Classic Shell has made his mind, not even you can force him to continue. Why don't you just take over?

    So, moving forward, I am making the latest version of Classic Shell open-source and adding it back to SourceForge (Classic Shell download | SourceForge.net), where it all began. I encourage other people to fork it and go with it.
    Feel free to do it by yourself, or to find other interested coders to continue the work.

    Easy!

    Kari
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:38.
Find Us




Windows 10 Forums