IE during sign-in, getting "blocked this website from displaying content with security certificat...

[Flugelman]

I just received a new Win.7 desktop and Internet Explorer, when logging into Adobe.com, is getting a "Internet Explorer blocked this website from displaying content with security certificate errors."  message that I cannot get past.  I've added adobe.com to Trusted Sites.  I tried lowering the Security level.  I downloaded FireFox and it seems to work fine.  So it has to be a setting in IE.  Anybody else resolved this problem ?

[iAnkitkhurana]

Hi Flugelman,

Try and start IE in No Add-ons mode and see if that resolves the issue.

Click on Start>> All Programs>> Accessories>> System Tools>> Internet Explorer (No add-ons).

If that doesn't resolve the issue then reset the IE settings, check it here: http://support.microsoft.com/kb/923737.

Thanks!

Ankit

[Flugelman]

Sorry, its still not working, even after running inetcpl.cpl.   I can get passed it in FireFox, but run into another roadblock.  After downloading the initial CC Set-up file, when I run it, I receive a "No Internet Connection".  The Chat tech. support tried a few things then told me the problem was in our Group Policy settings on the corp. network.  Said that we had set a "proxy for installation of Adobe software".  I'm checking on that.  So far, nothing but stumbling blocks every way I turn trying to install the new Creative Suite.  CDs were so much easier.  You would think that would still be an option for this new software.  Almost two days lost todate with no end in sight.

[Flugelman · Accepted solution]

a PC Tech resolved both my problems.  The techs. have a Certificates file on one of their servers.  He ran that and it updated the Adobe certificate allowing IE to sign-in to Adobe.com.  Secondly, I was receiving a "No Internet Connection" message when trying to run the CreativeCloudSetup file.  We started Symantec Enpoint Protection, and then stopped it again.  That worked.  No matter that I already had it turned off.  Rebooted the PC several times.  Starting and Stopping worked.  Hope this helps somebody else out there.