Windows 10: Microsoft Blocks Classic Shell in Windows 10 Build 9879

Well, I have always used Start8, on 8/8.1/build 9841 (was that the name?), and it is currently installed on 9879, works and installed just fine.

As for Microsoft's new Windows 10 menu, I simply don't like it, so I use Start8. I also use Brink's shortcuts, for Charms Bar and Desktop swapping.

If I didn't have Start8 I doubt I would bother testing at all, you don't need the menu to test other aspects.

Besides, if so many people are using Classic Shell, or other 3rd party start menus, perhaps that should be telling Microsoft something (like maybe people don't like the new interface).
OMG!! ...slap my mouth.

 

Thunderbird and Firefox don't insert themselves into the shell.

 

Hi there

There IS a difference between programs like Thunderbird etc which are basic standard APPLICATION type programs and things like Classic shell which interact with the basic Kernel or underlying OS itself. There's no reason to block typical application (non "privileged") programs like Thunderbird whereas those like Classic shell that fundamentally interact with the internel OS / kernel ("Privileged" programs) should be prevented from executing if they risk breaking the OS.

Ms was merely ensuring the integrity of its OS by special programs -- I'm sure that if the developer re-writes code that doesn't risk de-stabilizing the OS it will work just fine.

Not sure though how much programs like Classic Shell are really needed though any more in this edition of Windows -- that's another matter though.

Cheers
jimbo

 

I been backing up and restoring my Linux partitions using Reflect for ~4 years. I read somewhere Reflect didn't backup Linux logical partition for awhile but that comment could of been wrong. That may have been true (pre-2010).
It's also possible that it may have been dependent on the Linux distro that was installed. *Smile

I had to install Ubuntu 10 in a Logical partition back in May 2010.
My Primary partitions had XP, W7 and Programs on them.
I started using Macrium at about the same time.

I kept that partition arrangement until September 2012.

 

Hi

I don't have an issue with Microsoft blocking Classic Shell in the preview builds.
The whole point is to get people to test the Windows interface etc.

I don't think they should block it when Windows 10 goes live.

I've found that I don't feel like I need it with Windows 10 anyway.
I've gotten used to it, and I always use RocketDock anyway, I've used it for years and it works fine with Windows 10.

Mike

 

Thunderbird and Firefox don't insert themselves into the shell. It does not matter if they insert them selves in the shell or not who says M$ will stop with Classic Shell that is a user choice not M$.

 

I got a little chuckle out of your statement, when you say;
"you have gotten used to Windows 10 interface", yet...
You use RocketDock (an OSX clone). So in other words. it doesn't matter to you what Microsoft puts out? ...because you don't use it any way? ... which I have no objection too.

But this leads us back to the bigger question, is the new Windows interface, really an improvement?

 

I got a little chuckle out of your statement, when you say;
"you have gotten used to Windows 10 interface", yet...
You use RocketDock (an OSX clone). So in other words. it doesn't matter to you what Microsoft puts out? ...because you don't use it any way? ... which I have no objection too.

But this leads us back to the bigger question, is the new Windows interface, really an improvement?
It's all going to based on personal performance. For me it is. And for others it's not.
I use classic shell for Win8.1.1 and I don't think I would have any need for it in Win10 when the final version comes out next year.

 

Why are we testing W-10?
To help Microsoft in the development of a new operating system.

Their will be things that do not work with W-10.
Part of that might be W-10 and part of that might be wanted added programs from 3rd parties.

Third part program creators I'm sure are doing a lot of testing to make sure their programs work with W-10.

In my opinion Microsoft in the early stages would like us to test W-10 not every 3rd party program one can come with.
Also in my opinion Microsoft doesn't need Classic Shell get in the way at this time.
Microsoft is trying to have a Start that is adjustable in many ways so users can have it as they want it.
Those who like Classic Shell will never be pleased with anything else. That's fine with me. Now we need to test W-10.
Use the Feedback with the problems using Classic Shell and wait for the final version of W-10.

I try to remember this is just not a Microsoft thing. Third party programers have to do their job also. I'm sure they are working over time to do their part.

Example:
The Intel SSD Toolbox didn't work properly in W-10 on my system. It's fixed now.
Did Microsoft fix it or did Intel fix it. I don't know and don't care, it's fixed.
I'm thinking they probably worked together to get the job done.
This is not only a testing process for Microsoft and us; it's also a testing process for 3rd party program creators.

I test some 3rd party programs. When they don't work as they should I just post here and Feedback and get on with my life. I will not decide one way or the other if I buy W-10 until the final version is out.

When the final version of W-10 comes out and their is a program I want or need that doesn't work with W-10 I will just contact the creator of the program. It's their job to make it work with W-10 not Microsoft's.

 

Layback Bear are you saying we shouldn't be testing 3rd party software at all?

 

Thunderbird and Firefox don't insert themselves into the shell. It does not matter if they insert them selves in the shell or not who says M$ will stop with Classic Shell that is a user choice not M$. This comment will surprise some people. I actually do agree with you labeeman. I really hate to say this, it is Microsoft choice what works with their operating system as long as it doesn't violate local laws or court rulings. Windows is not open source.

 

No I'm not saying that at all.

What I'm saying is you and I and other members will surly find programs that don't work with W-10 as they should.
Post your problem here and in the Feedback to Microsoft. This will allow the owners of the program that doesn't work and Microsoft to investigate the problem.

Just don't get in a lather when things don't work. It takes a lot of time to get W-10 and gazillion 3rd party programs to work together. Microsoft is not going to stop the progress on W-10 just so they can get somebodies pet program to work.
They most likely a priority they do things.

I still don't like the way Cleanmgr works and I have reported it a couple of times to Microsoft.
My next step is to wait and see if the problem gets fixed. I do believe it will get fixed, I just have to wait.

I have reported here and using Feedback programs that do and do not work on my system when using W-10.
This feedback from those of us who are testing W-10 is critical in my opinion.

The problem I'm seeing is some are complaining about things like it's the end of the world as we know it.
Post a problem and see if other can help. Give feedback to Microsoft and wait. It take time to repair such things.

I understand why (I think) why Classic Shell doesn't work properly in W-10.
Microsoft doesn't want Classic Shell at this time to get in the way of developing the Start Menu as so many have asked for.

Microsoft wants feedback on the changes they have made in the Start Menu not changes someone can come up with using Classic Shell.

The Start Menu was probably the number on complaint using W-8. They are trying to solve that problem using W-10 and giving customers option within W-10.

Microsoft is fully aware what Classic Shell is and what one can do with it. They in my opinion at this time don't care.
They are trying to make the Start Menu in Windows 10 flexible so the average user can make it like they want it without a 3rd party program.

Testing 3r party programs is a good thing but testing W-10 is my number one priority. The 3rd party programers will just have to catch up with W-10.

Here is a good example posted by A Guy of a program that doesn't work in all aspects with W-10.
I don't believe this problem will stop me from using W-10. I will just wait until the problem is fixed and then use the program. I like CPU-Z and use it often on my other systems. The world will still be okay until it works as it should.

Cpu-z 1.71.1

 

So that is why I kept getting blank pages coming out of the printer when I wanted to print a coupon that someone had sent me.*Mad I got suspicious when even printing to XPS Document Writer did not work. (IE worked.)

 

Thunderbird and Firefox don't insert themselves into the shell. It does not matter if they insert them selves in the shell or not who says M$ will stop with Classic Shell that is a user choice not M$. This comment will surprise some people. I actually do agree with you labeeman. I really hate to say this, it is Microsoft choice what works with their operating system as long as it doesn't violate local laws or court rulings. Windows is not open source. Actually, no, at least not entirely. There are many laws on the books that make anti-competitive actions illegal....

 

Indianatone
A simple rename of the install name will allow it be installed for now. It actually should be allowed with consumer preview though without having to rename it. As I said in my post they Microsoft want you to try the standard Windows 10 start menu. I know there is a work around. The important thing is to provide feedback on the new OS not on how Classic Shell works. Maybe the feedback is that some of us would like a start menu very like that which the Classic Shell provides.

After installing W10 I wanted to use 'Computer Management' to change the disk drive allocations. This is easy to find in the Classic Shell, but somewhat obscure in the stand W10 start menu.