Nil wrote:

Bob Henson wrote:

Again, it works just fine - it would seem that Microsoft only has
it in for Classic Shell.

That may be what it "seems" to you, but I don't buy it. I think it's
more likely that there is something specific in the programming of
Classic Shell that conflicts with Windows 10's security or interface. I
expect that Classic Shell will adjust things to make it more compatible
before long.

The Windows 10 Consumer Preview release (which will be dubbed Windows 10
"Technical Preview for Consumers" - to confuse it with the "Technical
Preview" release - Microsoft loves confusion) will be "released early
2015". Early does not equate to Q1 or Q2 so "early" doesn't really
specify when. It is expected the RTM (release to manufacturing) release
will occupy a bit before the expiration of the Consumer Preview release.

"We have a Consumer Preview in early 2015, the Developer Preview in
April, followed by the launch of the final version by the end of the
year. Technical Preview is not the way to get an idea of what to expect
in the Consumer Preview, also not a place for developers to try to
develop an application in Windows 10 it is intended for users of our
company, " a Microsoft statement.

ClassicShell has stated they will not address code changes to make their
product compatible with Windows 10 until there is a release candidate or
RTM (release to manufacturing) release. So ClassicShell may not fix its
Win10 compatiblities until late spring or summer of 2015 or maybe even
for more than a year from now.

ClassicShell has admitted they have compatibility problems with Windows
10 TP. Yet they don't mention what they are. If the incompatibility is
only with their installer and not their application, perhaps they should
provide an alternate installation method so ClassicShell enthusiasts
could volunteer their testing time to assist ClassicShell.