Fabian201110141
Contributor
Contributor

Vsphere Client and Windows 10

Jump to solution

Hello,

I just upgrade my admin PC to Windows 10 and since, I can launch it but I can't connect to Vcenter : Unable to create a secure channel SSL/TLS

I tried compatibility mode Windows XP/7/8 with the same result.

For information : ESX version and Client 4.1

0 Kudos
1 Solution

Accepted Solutions
TotesHagopes
VMware Employee
VMware Employee

The versions you referred to appear to not be supported with Windows 10. I wouldn't be surprised if the problem is due to the OS compatibility: VMware Knowledge Base

Operating System6.0 U36.0 U26.0 U16.05.5 U35.5 U25.5 U15.55.1 U35.1 U25.1 U15.15.0 U35.0 U25.0 U15.04.1 U24.0 U34.0 U4
Microsoft Windows 10YesYes

View solution in original post

0 Kudos
19 Replies
Kaustubhambulka
Enthusiast
Enthusiast

Please check vpxc.log file for "Win32 Certification error.."

0 Kudos
Fabian201110141
Contributor
Contributor

Hello K

0 Kudos
Fabian201110141
Contributor
Contributor

In my user profile, in found "viclient-xxxx.log" with the following message :

[    :startup :W: 1] 2015-08-24 16:08:05.531  Log for vSphere Client Launcher, pid=9488, version=4.1.0, build=build-491557, option=release
[    :QuickInf:P: 3] 2015-08-24 16:08:08.562  Retry HttpRequest GetResponse - 1
[    :QuickInf:P: 3] 2015-08-24 16:08:08.562  Retry HttpRequest GetResponse - 2
[    :QuickInf:P: 3] 2015-08-24 16:08:08.577  Retry HttpRequest GetResponse - 3
[    :Failed t:P: 3] 2015-08-24 16:08:08.640  System.Net.WebException: La demande a été abandonnée : Impossible de créer un canal sécurisé SSL/TLS.

Server stack trace:

   à System.Net.HttpWebRequest.GetResponse()

Exception rethrown at [0]:

...

   à System.Net.HttpWebRequest.GetResponse()

   à VirtualInfrastructure.Utils.WebDownload.GetResponse()

[    :Error   :M: 1] 2015-08-24 16:08:08.640  Error retrieving clients.xml

System.Net.WebException: La demande a été abandonnée : Impossible de créer un canal sécurisé SSL/TLS.

Server stack trace:

   à System.Net.HttpWebRequest.GetResponse()

Exception rethrown at [0]:

   à VpxClient.Login.ClientsXmlLoader.TryDownloadAllPorts(Exception& activeError)

   à VpxClient.Login.ClientsXmlLoader.Download(Object obj)

Direct connection to an ESX runs correctely but the connection to Vcenter fails.

0 Kudos
jagdish_rana
Enthusiast
Enthusiast

Hi,

Please disable the windows 10 firewall services and check.

Thanks

0 Kudos
Fabian201110141
Contributor
Contributor

Ok, I tried with Firewall disabled and with Firewall enabled and allowing in and out connection and that does not change anything.

0 Kudos
Fabian201110141
Contributor
Contributor

I tried with another computer with Windows 10 and I encountered the same issue.

0 Kudos
prakash9339
Enthusiast
Enthusiast

HI

can u try this once

1.Install Microsoft Visual C++ 2005 SP1 Redistributable Package (x86):

http://www.microsoft.com/en-us/download/details.aspx?id=5638

2.Re-register Microsoft foundation class in administrative command prompt:

regsvr32 mfc90.dll

0 Kudos
Fabian201110141
Contributor
Contributor

Ok, I Re-instelled Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) but the command "regsvr32 mfc90.dll" produce an error message "Failed to load the module mfc90.dll ... the specified module could not be found"

2015-08-25_135041.jpg

However, mfc90.dll is present in WinSxS folder...but only in this one.

In fact, I think viclient fails during the first step : Certificat exchange. If I try to connect directely to an ESX, I firstly obtain this window :

2015-08-25_135250.jpg

If I click on "Ignore", I manage to connect correctly but if I click on "Cancel", I obtain the same error message "Enable to create a secure channel SSL/TLS". Then, with connection to Vcenter, the issue is that I don't get this first certificate window, and then I can't Ignore or Install the certificat.

0 Kudos
Fabian201110141
Contributor
Contributor

I tried with viclient 5.5 with the same result ... strange

0 Kudos
wallybuilt
Contributor
Contributor

Exactly the same problem after upgrading from Windows 8 (64-bit) to Windows 10 Pro (64-bit).  I can successfully connect to ESXi hosts but not the vCenter (SSL/TLS connection error).  Also lost my "ctrl+alt+ins" operation but that may be something else.  Looks like I'm part of the Research and Development team again.

0 Kudos
wallybuilt
Contributor
Contributor

Maybe this picture will help somehow:


pastedImage_0.png

0 Kudos
Fabian201110141
Contributor
Contributor

Yes, it's exactly the error mesage I get but I don't understand why ...?

0 Kudos
acorrilo
Contributor
Contributor

Anyone every get results from this? All I got from vmware support is the "Well its windows 10 and not supported, ergo, we cant help you"...

0 Kudos
Fabian201110141
Contributor
Contributor

In my computer Framework 3.5 is installed and well enabled but always the same issue.

I suppose we have to wait that Vmware consent to create a patch ...

0 Kudos
ChetFarmer
Contributor
Contributor

Did you ever get an answer here? I'm also using older VMWare tools, and I can't connect to my VCenter from my new Win10 machine.

It DOES still work from my Win8 machine, just as you describe.

0 Kudos
love_you_y2king
Contributor
Contributor

My issue started after I changed my SSL and Cipher Suite acceptance policy using IISCrypto tool. I used "Best Practices" option to ensure that my system only accepts good cipher suites and protocols.

Pic1.png

Later, I realized that I can not connect to ESXi Host.

Then I checked "MD5", "SHA" check boxes under Hashes section and restarted my computer. After the restart, I was able to connect to ESXi host through VSphere Desktop Client. Hope It helps everyone.

Link for IIS Crypto Tool. https://www.nartac.com/Downloads/IISCrypto/IISCrypto.exe

Pic1.png

0 Kudos
TotesHagopes
VMware Employee
VMware Employee

The versions you referred to appear to not be supported with Windows 10. I wouldn't be surprised if the problem is due to the OS compatibility: VMware Knowledge Base

Operating System6.0 U36.0 U26.0 U16.05.5 U35.5 U25.5 U15.55.1 U35.1 U25.1 U15.15.0 U35.0 U25.0 U15.04.1 U24.0 U34.0 U4
Microsoft Windows 10YesYes

View solution in original post

0 Kudos