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

Let's see.. first of bunny is old enough and has enough experience to know what he needs in an OS. Second, the "we" that I was commenting on was concerning views that may not be held by all members here on the forum. If you have an opinion use "I" not "we".

That covers it.
Jeff

 

I am confused as well as the quote makes it look as if I wrote some of the text, which I did not.

 

• First Base: Who
• Second Base: What
• Third Base: I Don't Know
• Left field: Why
• Center field: Because
• Pitcher: Tomorrow
• Catcher: Today
• Shortstop: I Don't Care

*Thumbs


[youtube]airT-m9LcoY[/youtube]

 

I am confused as well as the quote makes it look as if I wrote some of the text, which I did not. Machare,
I was looking back, some of the quote tags didn't get posted correctly. That why I either use the name or nickname of the poster. This way they know who I am talking to. If I am talking to everyone I will say "All" or "Others" unless I post a new thread. I goof up some of the time by not saying who I am replying too.

 

I am confused as well as the quote makes it look as if I wrote some of the text, which I did not. Machare,
I was looking back, some of the quote tags didn't get posted correctly. That why I either use the name or nickname of the poster. This way they know who I am talking to. If I am talking to everyone I will say "All" or "Others" unless I post a new thread. I goof up some of the time by not saying who I am replying too. Wait a minute. I thought I wasn't in the game! *Tongue

 

Sorry about that, missed taking out some text. Fixed it.

As to the "we", for those pretending not to understand, the disparaging post I quoted was directed at those folks who rejected the start screen, and have retained their opinion that the start menu was, in fact, far far better, and that includes me, and many others. Chiming in that you did not understand that, is disingenuous at best.

 

Sorry about that, missed taking out some text. Fixed it.

As to the "we", for those pretending not to understand, the disparaging post I quoted was directed at those folks who rejected the start screen, and have retained their opinion that the start menu was, in fact, far far better, and that includes me, and many others. Chiming in that you did not understand that, is disingenuous at best. Rickkins,
Now I am *Confused . Are you saying you like the Window 10 start menu or don't like it? If, you like the start menu that fine with me, but there is a lot of people that don't which includes me. (For clarification, I don't like the windows 10 start menu). I admit there are a couple of nice features about the start menu that I do like, live titles and resizing titles. Actually as a disabled individual I do have trouble understanding really hard tech stuff.

 

Have to say I never noticed that...but even so, the program has been running reliably and predictably with 8.x all of this time, so calling it out by *name* in the Win10TP is very strange behavior--Microsoft's own documentation says "If it runs in 8.1 it should run in 10TP with no problem"...And indeed, once the program is installed by changing the name of the executable in Win10TP it runs without a problem. You'd think Microsoft would at least *test* a program before declaring that it is "incompatible," wouldn't you...?

 

I hardly doubt MS would ever state that, especially within a beta. Perhaps “Most programs will run”, but not all. Please reference where you come up with at least some of this stuff.

Please read all of the thread. Some stated they changed the name, were able to get it to install, but then ran into problems with it. Here’s one. There’s another in some other thread.

Microsoft Blocks Classic Shell in Windows 10 Build 9879

Again > Where do you come up with this stuff?

LOL! You just posted this yesterday:

Now MS needs to test third-party programs? Nay. It’s the other way around.

 

That's right. While Microsoft spends a great deal of effort to preserve backwards compatibility, it is mostly for software that plays by the rules and uses only documented OS features. Programs like Classic Shell or CPU-Z use undocumented and unsupported tricks.
And even then you can't expect all legitimate programs to works with a preview version. The TP build is how they discover incompatibilities to be fixed, after all.

As for Classic Shell, there are 2 outstanding issues that caused it to be blocked:
1) The start menu messes with the taskbar and causes the new taskbar buttons to overlap with the programs. This is because the start menu relies on undocumented internal structure of the taskbar, which was changed between 8.1 and 10.

2) Upgrading from one version of Windows to 10TP breaks the start menu. There are multiple technical issues here that I don't want to get into.

I am working on a fix for both. There should be a new beta version of Classic Shell by Thanksgiving.

 

Folks when someone finds a program that doesn't at this time work with W-10 there are three things to do.
1. Post your problem here.
2. Post your problem in Windows 10 Feedback.
3. If you can inform the owners of the program.

That is the big three.
I'm not here to design W-10 or 3rd party programs. I'm here to give input so W-10 will hopefully be a great operating system.
I will let the owners of the 3rd party programs and Microsoft work out the problems between them.

I'm as sure as one can be their will be things about W-10 that I would like different. That to me doesn't make W-10 is a no go.
I will have to decide whether watching my favorite game of puppies dancing in the bathtub is more important than W-10 to me.

In the end that is a decision we will all make.

Microsoft is trying to make a operating system that the masses will like and buy.

If third party programs don't work with W-10 the owners will just have to adjust their program so it does.

 

Thanks for expounding on that, Ivo and Layback Bear. *Thumbs

I spent a mere $110 on a copy of 8, then 8.1 was a free upgrade. This was all on a six-year-old tower at the time which continues to purr along yet another two years later. MS saved me money by keeping the OS footprint small enough and backward compatible enough to use on older hardware. Saved me money. And yet 10 runs pretty well on it along with Office 2013 Pro.

To some > Compare that to a Mac with the latest OS X or even a new WinTel. Let me know how that goes. *Wink

 

Ivo,
Referring to your post number 68 I don't think that the issue. It is the blocking of any 3rd party program including yours, it is what causing this uproar. I know renaming it fixes the issue but you shouldn't have to do that. Imagine if Microsoft blocked Google Chrome or Firefox even on the previews. Myself when I was testing windows 10 if most of my 3rd party software didn't work with windows 10 preview, then I wouldn't upgrade to windows 10 release. There is only so much you can do to test Windows 10. I actually found it boring-no offense meant to others. People will probably disagree with this or say this is double talk by Microsoft. Microsoft said somewhere. If there is an application/program you have installed in windows 7 or above, it should work with 10.

 

i dont a problem with microsoft blocking a program that could cause problems due to the way said program interact with the kernel of the OS. Even on windows 8.1 rtm there are programs that are blocked from being installed. im sure if firefox or chrome interacted with OS the same way as cpuz ms would block it too.

 

*Cool*Cool

I also went the route of seeing what 10 would do all by itself. My biggest problem was I just could not easily find my apps. Tiles cannot be arranged alpha and I was eye-jumping all over the screen trying to find an app, even with the app icons there. Sometimes it's just easier to have a nice columnar list like all programs in Classic Shell where you can mentally run your finger over the list to find. Some times you just don't remember exactly what something is called and seeing a list can jog your memory.

When I upgraded to 9879 it ate most of the Classic shell install. I used the rename installer trick, and it went to options which included Repair Classic Shell. Worked just fine. Reloaded my XML backup config and all was well.

Footnote: DO NOT use any "hover" options over start button. It makes the TP start screen act like a blinking red light at a four-way stop! Screen blinks on and off at the hover delay rate of 400ms.

Explorer toolbar options do nothing, so don't bother installing.

The safest "click" method I've found is Middle Click for Classic, shift-ctrl-right-click for Classic context menu, and all others leave as "do nothing" (let TP have them).

Just some of observations on Classic Shell in Win TP...

Enjoy!