Will Classic Shell work on Windows 10

f14tomcat · 20 May 2016

@badrobot - it will install with a bit of trickery....

Will Classic Shell work on Windows 10-2016-05-20_11h50_35.jpg

Ivo · 20 May 2016

machare said:

Attachment 80644

I have tried installing Classic Shell as an Administrator but it makes no difference.

The installation process itself appears to run OK. The problem is running the ClassicStartMenu.exe it just produces the above UAC pop up.

Is there a way to get round this problem?

I think the problem is that the certificate that signed the EXE was revoked few days ago. I had to revoke it and get a new one because the old certificate didn't satisfy the security requirements that Microsoft enabled earlier this year.

There will be an update to Classic Shell tomorrow that should fix the problem.
There will also be a new beta version with a ton of new features and better support for the latest Insider builds.

f14tomcat · 20 May 2016

Ivo said:

I think the problem is that the certificate that signed the EXE was revoked few days ago. I had to revoke it and get a new one because the old certificate didn't satisfy the security requirements that Microsoft enabled earlier this year.

There will be an update to Classic Shell tomorrow that should fix the problem.
There will also be a new beta version with a ton of new features and better support for the latest Insider builds.

Bravo, Ivo!!

Be looking for it!

Berton · 20 May 2016

I just downloaded and installed the latest stable version and it worked after I changed the file name from ClassicShellSetup_4_2_5.exe to TestClassicShellSetup425.exe. But it works fine on Win10 Insider Preview Build 14342.1001.

f14tomcat · 20 May 2016

Berton said:

I just downloaded and installed the latest stable version and it worked after I changed the file name from ClassicShellSetup_4_2_5.exe to TestClassicShellSetup425.exe. But it works fine on Win10 Insider Preview Build 14342.1001.

Glad to hear. That's why I suggested that above. Enjoy!

machare · 20 May 2016

Ivo said:

I think the problem is that the certificate that signed the EXE was revoked few days ago. I had to revoke it and get a new one because the old certificate didn't satisfy the security requirements that Microsoft enabled earlier this year.

There will be an update to Classic Shell tomorrow that should fix the problem.
There will also be a new beta version with a ton of new features and better support for the latest Insider builds.

Well thank you - I certainly like it!:)

simrick · 20 May 2016

Ivo said:

I think the problem is that the certificate that signed the EXE was revoked few days ago. I had to revoke it and get a new one because the old certificate didn't satisfy the security requirements that Microsoft enabled earlier this year.

There will be an update to Classic Shell tomorrow that should fix the problem.
There will also be a new beta version with a ton of new features and better support for the latest Insider builds.

Thank you very much! You program has been a lifesaver for many! :)

f14tomcat · 20 May 2016

simrick said:

Thank you very much! You program has been a lifesaver for many! :)

Superfly · 20 May 2016

Yup, Ivo must up his game as MS changes things - keeps him on his toes...LOL

BTW: He's done an excellent job keeping up.. can't be easy!

davidhk · 20 May 2016

Ivo said:

I think the problem is that the certificate that signed the EXE was revoked few days ago. I had to revoke it and get a new one because the old certificate didn't satisfy the security requirements that Microsoft enabled earlier this year.

There will be an update to Classic Shell tomorrow that should fix the problem.
There will also be a new beta version with a ton of new features and better support for the latest Insider builds.

That will be very much welcome for the 32-bit users.