i just install classic shell ver. 4.1.0 on windows 10 and it's works!
all you have to do is to rename from classic shell to what ever name you want. i used softpedia.
it run smooth and no problem so far.
i'm pretty sure that classic shell will come up with new version to work with windows 10.
Unfortunately, I like or use some windows programs. Microsoft Works 7 Database (yes, a little old fashion)
Macrium free now restores Linux even if installed on logical partition but you still have to back it up through windows. I may have said this before, Windows 10 was suppose to be a mix between windows 7 and 8/8.1 One spokesperson said windows 10 would look more like windows 7-I do not see this. The reason for that is to move users from windows 7 to 10. I wonder if Microsoft gave up on windows 7 users from reports online, most businesses are going to stay with what they have for now. Let see how they do with the consumer preview, it will be interesting.
Last edited by groze; 20 Nov 2014 at 18:09.
There are any number of reasons why this may be the case. There may be a compatibility issue, and MS is preventing install for that reason.. or they may be trying to ensure that users actually test the new start menu instead of just replacing it.. You are, after all supposed to be testing their product.
Just like MS wanted to test upgrades with 9860, so didn't release an ISO, this may be just another case of wanting to make sure users test specific scenarios more thoroughly.
Having removed the apps on the right of the menu, I find it looks and works broadly similar to the menus that we have had in the past. I'm quite happy with it.
Oh Boy, it is finally happening. . .
I think Mystere is right about this. Microsoft merely wants people to use and provide feedback on Windows 10 start menu. Microsoft is providing the software free of charge for testing purposes and as such have the right to impose reasonable restrictions on it's use. This doesn't look like a serious attempt to block Classic Shell. If Microsoft really wanted to do so it could be done quite easily and far more effectively. Remember that this is a technical preview and intended for use by advanced users. Such users using Classic Shell could reasonably be expected to know about the Classic Shell Forum and how to evade the restriction.
I think it highly unlikely that this restriction would be in the final release, or even in the consumer preview. Microsoft has a long history of making third party software continue to work, even when the software developers engage in practices they were specifically warned against. Windows has a large internal database of incompatible applications and methods of making them work when installed or run. This occurs silently without the users knowledge. Microsoft has actually received much criticism for doing this.
Classic Shell developers are aware of the problem but have to plans for a workaround (other than renaming the installer). Changes in Windows 10 are coming too fast and any fixes might break in the next update.
Classic Shell ? View topic - Classic Shell and Windows 10 Compatibility
The new (desktop) Window Snapping in b9841 was just what I wanted (specifically 100% width, 50% height).
I could have used that enhanced Window Snapping feature a few days before b9841 came out.
There was an issue with Task Manager Window Snapping, but I almost never open Task Manger anyway (I use Process Explorer).
Of course MS broke Window Snapping in the last two W10 builds.
They did sort of fix the Task Manager Window Snapping though.
Apparently App Snapping has been broken in every build.
W10 seems to be following the pattern that the W8 previews followed.
The more W8 previews MS released, the worse W8 got (the W8.1 preview reversed that trend, slightly).
The bottom line is, I would consider upgrading from W7 to W10, provided MS don't break any more stuff.