Microsoft Blocks Classic Shell in Windows 10 Build 9879

labeeman said:

Thunderbird and Firefox have compatibility issues with windows 10 in that they do not print. I do not see M$ trying to block them.

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. I got suspicious when even printing to XPS Document Writer did not work. (IE worked.)

groze said:

labeeman said:

Mystere said:

labeeman said:

Thunderbird and Firefox have compatibility issues with windows 10 in that they do not print. I do not see M$ trying to block them.

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 said:

groze said:

Indianatone said:

I made the decision to try 10 without classic shell to try out what they Microsoft came up with. It is simply that. Microsoft want users to try the start menu and provide feedback from the standard 10 start menu.
Classic shell had better work with the RTM version or there will be trouble.

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.

machare said:

Indianatone said:

groze said:

Indianatone said:

I made the decision to try 10 without classic shell to try out what they Microsoft came up with. It is simply that. Microsoft want users to try the start menu and provide feedback from the standard 10 start menu.
Classic shell had better work with the RTM version or there will be trouble.

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.

I'm glad you said some of us, I don't want a Start Menu, also, if you know what you're looking for, why not do a search and then pin it to the task bar.

Let me clarify that, I'll accept the Start Menu they have, but only because so many people seem lost without it.

machare said:

Indianatone said:

groze said:

Indianatone said:

I made the decision to try 10 without classic shell to try out what they Microsoft came up with. It is simply that. Microsoft want users to try the start menu and provide feedback from the standard 10 start menu.
Classic shell had better work with the RTM version or there will be trouble.

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.

right click on the start menu icon open a little menu with lots of useful programs and shortcuts.

Ivo said:

I have received notice from Microsoft that Classic Shell is blocked because of a few compatibility issues. I am working with them on finding a solution. Stay tuned.

In the meantime you can rename the installer to work around the block.

Well, then maybe you can also have Microsoft explain why CPU-Z (for cryin' out loud) suffers the same fate--and HWmonitor, too....? All these programs do is read hardware configurations, so why should they not work since they worked fine under 8.1?

But just like with Classic Shell, renaming the executable solves the problem--and the programs install and run! I got the tip for CPU-Z from this thread, btw--tried it, and it worked fine.

It's nigh inexplicable why Microsoft would hardcode the OS not to run certain executables *by name*--but not *explain* it in a note somewhere? That's nuts, imo. Why would Microsoft not want me to run CPU-Z???? Since they are bringing back the start menu, Classic Shell is at least rationally understandable (to a point)--but CPU-Z? Bizarre.

machare said:

labeeman said:

Thunderbird and Firefox have compatibility issues with windows 10 in that they do not print. I do not see M$ trying to block them.

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. I got suspicious when even printing to XPS Document Writer did not work. (IE worked.)

In this case, try and remember that Win10 is *beta*--it's full, chock full of bugs of all kinds. Microsoft can control and adapt IE to some things in Win10 because Microsoft controls both--but it's not up to Microsoft to guarantee the running of Firefox inside Windows 10 or any other Windows--that's up to Mozilla, strictly between you and them. (And it's early to start bitching at Mozilla about Win10, imo...)

BunnyJ said:

I think that at this point in the testing MS is more interested in finding out what testers think of the new start menu rather than have them just use a tool like Classic Shell and then report back that it works. Well, of course it works but that's not the point of this testing. It's to check out the new start menu and to get feed back on how to change and adjust it for future builds.

I'm still betting that tools like Classic Shell will work fine in the final release of Win10.

CPU-Z issue is a bit bizarre..

Jeff

Yes, I can understand the Classic Shell thing at this stage--but the CPU-Z thing is bizarro world. I commented in Technet about it--got no response--but, what else is new in Technet?... More often than not when I have a problem I bother writing up out there I draw the ire of some "hotshot" who wants to tell me why my reasoning is flawed but then offers not one shred of assistance...!...

Check it out:

CPU-Z CPUID - System & hardware benchmark, monitoring, reporting

Weird.

blaze007 said:

right click on the start menu icon open a little menu with lots of useful programs and shortcuts.

Thanks, now I know where it was hidden.