Classic Shell: Forum

Recently I observed Classic Shell doing an update check via an http: (port 80) request of http://www.classicshell.net. This was when I logged-in. This is fine, expected, and I've allowed it, but I would like to ask:

I saw several other communications attempts by Explorer.exe happen in the same second, one of which was a check of ctldl.windowsupdate.com (which my firewall blocked), and of crl.microsoft.com (which was allowed)...

Explorer.exe is NOT in the normal habit of communicating online. This is the first time I've seen Explorer try to make an online connection in over a month. The Classic Shell update check I fully understand, as that's where you have to run to implement your Start Menu, but the other comms bother me. Let's just say I'm sensitive to Microsoft pushing things on me that I haven't approved.

I've seen such comms on Win 7, 8.1, and 10 systems. In fact, they all happened in the past 24 hours on all three different operating systems.

I don't believe it's Classic Shell doing or causing this ctldl.windowsupdate.com check because it has been observed happening without a classicshell.net query as well, but I was wondering:

Do you have any insight as to why Explorer only VERY occasionally attempts online communications, especially with ctldl.windowsupdate.com?

I have only a minimum of shell extensions and these systems are definitely infection-free. I have also disabled the Windows Update service on all systems, and reconfigure when I want to check for updates.

Also, is there a setting I can throw that would make Classic Shell only check for updates when I request it?

-Noel

You can disable the Classic Shell checks from the "Classic Shell Update" tool. Uncheck "Automatically check for new versions".

I don't know why Explorer would try to check for updates. Maybe some new patch added such feature.

It might have something to do with SmartScreen built into Windows 8 and above. Explorer verifies the digital signature on signed software by contacting the signing authority which can be Comodo, Verisign etc. Certificate checks are performed when signed software is executed. Windows also automatically updates root certificates from the URL you mentioned according to this page: https://technet.microsoft.com/en-us/lib ... 65983.aspx

_________________
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.

Per my observations usually it's a windows service running under svchost, System, or the Local Security Authority Service that do certificate revocation checks online. Only VERY rarely does Explorer try to communicate at all. That's what caught my eye.

And I have SmartScreen completely disabled.

Thanks for the link, Gaurav. I see now that ctldl.windowsupdate.com probably should be allowed through the firewall.

Thanks for the tip on disabling the auto-update checks, Ivo. Somehow I missed seeing that little checkbox on my Win 8.1 system. I had disabled it on my Win 7 system, so now I know that Classic Shell's auto-update check had nothing to do with the comms on that system.

I have no problem remembering to do update checks myself, and now I can continue to watch for other Explorer comms on the Win 8.1 system and know that Classic Shell isn't causing them.

-Noel