Classic Shell: Forum

XP Skin Pack 1.0-X64 + Classic Shell 3.6.7. Operating System Windows 7 x64.

After Installation Classic Shell: Internet Explorer 10 can't start process. No window.

IE9 & IE8 can.

S.J.

Run the installer again, then select Change. Uncheck the Classic IE9 component to uninstall it. See if that gets IE10 going. It is unlikely Classic Shell alone is the problem though. I've been using it with IE10 on Win7 64-bit for a year with no problem. It may be some incompatibility between multiple programs.

Yup. Done.

With Classic IE9, without. If you installed Classic Shell, you can not use Internet Explorer 10. More, you can not even if you uninstalled Classic Shell — only sfc /scannow result in status quo.

S.J.

What does "With Classic IE9, without." mean? Does not compute.

+ Classic IE9 In Installation Settings, - Classic IE 9 In Installation Settings. Result in one thing, I mean.

S.J.

Possibly, you can do nothing.

But you can think about it.

S.J.

Thank you for effort. Try solve reported bug.

Sorry, no understand. What you are saying does not parse as a valid sentence in any language I know.
Are you saying that regardless if you install Classic IE9 or not the result is the same? If so, what is the result? If not, what are you saying?
I do not see what is on your monitor and I do not read minds. If you use complete and coherent sentences you have a better chance to be understood.

If after uninstalling Classic IE IE10 does not start, it means the problem is unlikely to be related to Classic Shell as it only includes an addon for IE which is removed when that component is uninstalled. IE is not modified in any other way.

Try using System Restore to revert to a point before Classic Shell was installed.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

> it means the problem is unlikely to be related to Classic Shell as it only includes an addon for IE which is removed when that component is uninstalled

Useful Information. Thank you.

But: It's 100% related to Classic Shell as it happens strictly after Classic Shell installed.

> Try using System Restore to revert to a point before Classic Shell was installed.

I said, I used sfc /scannow.

Better than.

S.J.

Seems I find solution.
Bad way, but good solution.

sfc /scannow is only useful for restoring system files. Classic Shell does not touch system files to break anything. It installs a DLL addon for IE. So if that DLL is uninstalled, IE should revert to original behavior.

System Restore will help you troubleshoot the issue. It will revert the registry and program files to a state before the program was installed without affecting other data. Try reverting using System Restore to a point before Classic Shell was installed. Then try if IE works. If it still doesn't work, then something else broke IE.

If it works, then try installing the Classic IE component again and see if it breaks again. That will confirm it. Also, if you get any error message in the Event Log's (eventvwr.exe) in the Windows Logs -> Application log category about IE and some DLL, please post it here.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

> sfc /scannow is only useful for restoring system files.

Yup. Yes, It Is only useful for restoring system files.

> Classic Shell does not touch system files to break anything. It installs a DLL addon for IE. So if that DLL is uninstalled, IE should revert to original behavior.

More Useful Information. Again, thank you. I understand situation deeper.

> System Restore will help you troubleshoot the issue. It will revert the registry and program files to a state before the program was installed without affecting other data. Try reverting using System Restore to a point before Classic Shell was installed. Then try if IE works. If it still doesn't work, then something else broke IE.

No, I don't have any needs in System Restore. sfc /scannow = 100% Restoration of IE10.

> If it works, then try installing the Classic IE component again and see if it breaks again. That will confirm it. Also, if you get any error message in the Event Log's (eventvwr.exe) in the Windows Logs -> Application log category about IE and some DLL, please post it here.

That confirmed it already. When I begin this discussion, I already knew it.

But: It's not trouble that comes from _Classic IE_. From _Classic Shell_. Classic Shell Installed Without Classic IE = IE10 can't start process. I don't need Classic IE at all; only Classic Shell.

S.J.

Classic Shell is the name of the suite that includes Classic Start Menu, Classic Explorer and Classic IE. If you installed only the Start menu component and didn't install the IE component, and yet your IE is broken, then it's not Classic Shell's fault. It may be possible that whatever broke IE happened coincidentally right after you installed the Start menu. Millions of PCs have Classic Shell installed and IE works without issue.

The Start Menu is just a regular program like Firefox. Since you refuse to use System Restore, I don't know how to repair your IE. You could one more option. Try opening Internet Options from Control Panel (inetcpl.cpl) and on its Advanced tab, click "Reset...".

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

> Since you refuse to use System Restore, I don't know how to repair your IE.

! "No, I don't have any needs in System Restore. sfc /scannow = 100% Restoration of IE10". !

S.J.

> It may be possible that whatever broke IE happened coincidentally right after you installed the Start menu.

No, Three Installations of Classic Shell Without Classic IE — After Installation IE can't start process; then we repairing IE with sfc /scannow (Classic Shell removed before), then Second Installation Again — After Second Installation IE can't start process; then we repairing IE again (Classic Shell removed before again), then Third Installation — After Third Installation IE can't start; repairing IE third time (without Classic Shell in system).

I can send you Image of System — it's one and only way to reproduce bug.
But if you don't want do it, you don't.

S.J.

So, You Can Hear My Solution.

1 INSTALL CLASSIC SHELL BEFORE ANY INTERFACE IMPROVEMENTS IN OPERATING SYSTEM WINDOWS 7 64-BIT.
2 RUN COMMAND LINE — sfc /scannow
(Don't Use System Restore, It Is Useless In This Case)
3 NOTICE: sfc /scannow BACKING ANY INTERFACE IMPROVEMENTS.
4. IMPROVE INTERFACE AS YOU WISH AND WANT.

Done.

S.J.

I offer 1$(?) donation + 1$(?) payment for code-in bugfix.
(not only for GauravK, Classic Shell Is Open Source Software)

Just because bad bug is bad bug.

S.J.

Does sfc /scannow report what it repaired? If we know what file or registry setting was modified it would be possible to identify the problem.

I just has one thought.

I think I can fix it by myself.

Then you can implement bugfix if you wish.

S.J.

Yup. Done. Correct Solution:

1 INSTALL XP SKIN PACK 1.0-X64
2 REMOVE shell32.dll FROM INSTALLATION CUSTOMIZATION
3 INSTALL CLASSIC SHELL 3.6.7

shell32.exe FROM XP SKIN PACK 1.0-X64 causes incompatibility with CLASSIC SHELL 3.6.7.
(50% IE10 don't work with stand-alone XP Skin Pack 1.0-X64; 100% with both software pieces)

Work is done, question is closed.

S.J.

Any software which modifies system files can cause a problem. Good to know it wasn't Classic Shell's fault at all as it's a cleanly designed safe application.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.