- Vsphere 6.0 client install crashes on windows 8.1 install#
- Vsphere 6.0 client install crashes on windows 8.1 update#
- Vsphere 6.0 client install crashes on windows 8.1 software#
- Vsphere 6.0 client install crashes on windows 8.1 windows 8.1#
- Vsphere 6.0 client install crashes on windows 8.1 windows 8#
Check this post for the vSphere client download links.
Vsphere 6.0 client install crashes on windows 8.1 update#
If you are running vSphere 5.0., there is an update that has been released lately that should work fine on Windows 8. It works on my vSphere 4.1 but according to here, it works on 5.0 as well. Woola…that’s the workaround that saved my day. click OK to save the setting, and launch VMware-viclient.exe to start the installation again. Go to Compatibility tab, and check the option “Run this program in compatibility mode for” and pick Windows 7 from the list.ģ. Go to the extracted folder, bin sub-folder, right click VMware-viclient.exe and choose Properties. If you have 7Zip installed, you can simply right click the executable file, go to 7Zip, and choose Extract to folder name.Ģ. Assume you already have the executable installation file, extract the content out of it to a folder.
Vsphere 6.0 client install crashes on windows 8.1 windows 8#
Well, Windows 8 is above XP SP2, isn’t it? Not sure who to blame but I guessed that a workaround would be needed to get me over this silly error.ġ. This product can only be installed on Windows XP Sp2 and above
Vsphere 6.0 client install crashes on windows 8.1 install#
But when I tried to install it on my Windows 8 machine, this is what I got. It’s a basic but essential tool I need to manage my Virtual environment. IE11 11. vSphere Client is a client tool to manage VMware ESX and its VMs. VCenter Server 6.0 U2 on server 2012 R2 ver I still use FireFox most of the time and IE11 has not had any issues with vCenter since I’ve not accessed vCenter with FireFox. It appears in my case, IE11 and FireFox have an issue. So, I went back through the steps again and now IE11 is working without the message and all functionality is back. The next time I used IE11 I received the above message again. I had used FireFox again since it’s my browser of choice to do some quick tasks in vCenter. Went to the vCenter server URL and logged in. Then checked to be sure the FQDN was still in Local Intranet zone. Originally I had saved the Client Integration tools installer versus running it. Right clicked the installer and ran as admin.
Vsphere 6.0 client install crashes on windows 8.1 software#
Be sure to check the parent folder before uninstalling to be sure you don’t delete other VMware software installation files. Uninstalled the Client Integration tools from Program and Featuresīrowsed to the VMware folder and removed all residuals from the Client Integration tools installation. On this Discussion, I followed ericmowatt and BKNZC’s suggestions with these changes. I added the FQDN to the Local Intranet zone in IE11, but was still receiving the message. I had been using IE11 for weeks without issue. I started receiving this message after running Windows Updates on 10 Enterprise when opening IE11. I spoke with a VMware engineer at a VMUG and he stated to use either Chrome preferably or IE11. I had been using FireFox, but there is some functionality that is not working/available in FireFox.
Vsphere 6.0 client install crashes on windows 8.1 windows 8.1#
It might just be a very early bug on Windows 8.1 and my early suspicions is that it has something to do with software permissions and UAC in Windows 8.1. When you change IE11 back to IE9 compatibility, the option to log in is available, but when ticked, does not pick up your username.Īs I said, I don't know whether anybody else picked up on this and would like to hear your views. I don't think this is necessarily a Vmware or Google problem, because.Ģ)Using IE11 in either Windows 8 mode or Desktop mode, the plugin is not recognised as installed (Option to use local user authentication is greyed out). VMware vSphere Client 6.0 Update 2a: VMware-viclient-all-6.0.0-4437566.exe VMware vSphere Client 6.0 Update 3: VMware-viclient-all-6.0.0-5112508.exe It’s worth noting that the vSphere client tends to be backwards compatible, you can check this out using VMware’s interoperability matrix. The remote console option within the web client also prompts for an installation of the plugin. (This will probably be the default for a lot of users, which is fine and hence the absence of related topics on Google Search)Īs soon as you switch Chrome over to Windows 8 mode, the plugin is not recognised as installed (Option to use local user authentication is greyed out) and prompts you to download. When you access the vSphere Web Client on Windows 8.1 -ġ)Using Google Chrome in Desktop Mode, the web integration plugin works fine and you can authenticate with your current AD user account and launch the remote console as well. I don't know whether anybody else have come across this:
0 kommentar(er)
