Bob Henson wrote:

On 13/11/2014 5:05 PM, VanguardLH wrote:
Bob Henson wrote:

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something
better than I've tried so far.

Can you enable/disable the Program Compatibility Assistant (as you
could, say, in Windows 7) using the following instructions?

http://www.sevenforums.com/tutorials...e-disable.html
http://www.howtogeek.com/howto/4161/...s-7-and-vista/

Here's an example of someone that hit the same dialog in Windows 8
regarding Acronis TrueImage (a backup program):

http://superuser.com/questions/49960...t-in-windows-8

Obviously ClassicShell is not yet advertising they are compatible with a
tech preview (pre-release) of Windows. Most software vendors long ago
gave up trying to guess where Microsoft would go in a new version. They
were told things would be one way by Microsoft but found out after the
release that wasn't so. Software authors prefer the expense of just one
development cycle for a release of Windows. If you want compatibility
as designed by the developers then wait until Windows 10 is actually
released and until ClassicShell eventually announces compatibility with
Windows 10 released version.


I realise the author of Classic Shell is not going to be writing for
Windows 10 for a long time yet. However, it worked perfectly all the way
through the change from Windows 7 to Windows 8 and Windows 8.1 and the
first two builds of Windows 10 - so I'm thinking that it has been
deliberately blocked by Microsoft if Windows 8 compatibility mode won't
work - which is doesn't. I'll have a look at the suggestions you posted,
but if that doesn't work I'll happily delete Windows 10. I don't think
Microsoft will be too concerned if yours truly is not giving them the
benefit of my wisdom any more :-) I'm never going to use it, I'm just
learning because folk will ask me questions about it in my volunteer
job. Thanks for the tips.

I believe Windows comes with an included list in the registry of
programs that require compability mode or checking, like under
HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags. So
the update probably also included changing the compability list.
Microsoft may have found something really nasty happens in Windows if
ClassicShell attempt to usurp the desktop manager or file explorer.

I suppose you could delete the appcomp flag entry in the registry that
lists ClassicShell but I'd go with disabling the Compability Assistant's
checking. After, if you're going to override the compatibility check
and protection for one program then you'll do it for another and another
and another. However, disabling the compatibility assistant also means
it won't amend the environ for a program that requires compatibility
settings, so [old] programs that ran before may cease to function or
start misbehaving.

Note that registry entries for some programs include their own AppCompat
subkey. Not all compatibility settings are listed by Microsoft all
together under one registry key, Microsoft may not know all apps that
require a compatibility environ, and apps that come out later may
realize they need to use a compatibility setup for them to work (i.e.,
these are apps after the release of Windows that add their own
compatibility settings and are listed as a subkey under that program's
registry entry). A program that requires a compatibility environ is not
saying it will run in one of the compatibility modes (Windows 9x, XP,
Vista, etc) which makes a whole slew of changes to the environ for a
process, including those that are not necessary for that program to
behave. I'm talking about shims the program needs to use under a
version of Windows so that program works okay there; see
http://technet.microsoft.com/en-us/l...(v=WS.10).aspx.
However, I don't know if the Compatibility Assistent is required to
implement the shim (I'm not that deep into Windows programming). The
shim may be the only code needed by a program for it to work in a later
version of Windows than it was original coded for.