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

More

:)

 

Classic shell needs to configure itself for the new OS.

Ignore the typical useless non-answer from Microsoft.

The Update to Build 10586 not only causes this problem to occur, but actively prevents Classic Shell from running its updater.

So it's another **** Windows 10 update from Microsoft.

To resolve this, you need to uninstall Classic Shell, then download the latest version from Classic Shell: Downloads and install manually.

 

I don't want Classic Shell on my hard-drive.

Original Tile: Classic Shell

What is CLASSIC SHELL? I have Windows 10, and a Hewlett-Packard Pavillion 14. The verified publisher of Classic Shell is neither Microsoft nor Hewlett-Packard, so I don't want it on my hard-drive. I also run KASPERSKY anti-virus.

By not having CLASSIC SHELL am I causing problems? Thanks for any help.

 

That's been mentioned in at least one other thread here. It's sort of a shame since it cuts down the options uses will have for the start they want or need.

MS really needs to expand on the options that are available for adjusting/setting up the start menu. The way it is now is just right for me and some others but some will need more fine tuning to meet their needs.

Jeff

 

*What


I wonder what Classic Shell response is. Why does just renaming it work? I was considering trying 9879 and the consumer preview but I am not so sure now. I may stick with windows 7, then go to Linux when unsupported. Does any know if takeownship reg file still work in 9879?

 

As mentioned in the article, there is a work around for installing Classic Shell for those who want to use it. Personally I have gotten used to the W8.1 Start Screen.

 

Classic Shell works just fine in Win8.x and Win7. So if I were you I would stick with Win7, it's going to be supported for some time.

 

In my Win8.1.1 instillation I use Classic Shell. I just like it a lot more than the start screen. Plus I still can access the start screen with classic shell. There's a icon to get there.

 

The very height of hubris. Smacks of arrogance and outright ignorance.
I wish I had known before I installed '79, as I would have avoided it.

 

In my Win8.1.1 instillation I use Classic Shell. I just like it a lot more than the start screen. Plus I still can access the start screen with classic shell. There's a icon to get there. Yup, I understand where you're coming from. The Start Menu is great for those who like it, but hopefully the Start Screen will also work on W10 desktops and not just touch screen devices.

 

In my Win8.1.1 instillation I use Classic Shell. I just like it a lot more than the start screen. Plus I still can access the start screen with classic shell. There's a icon to get there. Yup, I understand where you're coming from. The Start Menu is great for those who like it, but hopefully the Start Screen will also work on W10 desktops and not just touch screen devices. I totally agree. There should be a simple way to get to the start screen from the start menu.

Jeff

 

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.

 

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.

 

Personally, I've really lost interest in Windows 10. I don't think it's THAT much better than Windows 8.1 (I do like a Start Menu replacement with Windows 8.1 however). But I just don't understand what it is that's wowing everyone on this forum (no offence or anything like that meant). But to me, this program blockage just seals the deal. I'll stay with Vista x64 until April 2017 (or until this PC breaks down). Then I'll migrate to 8.1 x64 on a new UEFI capable machine.