-
:转载时请以超链接形式标明文章原始出处和作者信息及
折腾了两天,一切都源自于升级了Ubuntu9.10,而且是从9.04升上去,一切噩梦就自此开始。
其实整个升级过程还不算麻烦。但是刚升级完突然发现jdk5.0没了,查了一下发现可恶的拉里准备不再更新5.0了,谷歌又不支持6.0去编译Droid。google了一下发现竟然已经有人在我前面做了,方法不难,把9.04的源加上后强制安装5.0,然后把源去掉。整个过程我终于确认以前的新西兰源速度已经不行了,换成99cn了,速度还是很好,不错。
完成后突然发现共享又不行了。重新安装一下,竟然报从来没见的编译错误。编了几遍都一样,换了open-vm-tools也不行。只好卸载vmware6.5,下载7了。正安装时,突然蓝屏了。本想重启安一下就OK了,没想到竟然认为已经装了不让再装了。又开始一遍一遍的试,{zh1}按照网上一篇文档才整好,几乎把所有Vmware相关的全部都卸载了。{zh1}终于搞定了,但又因为卸载不当把键盘驱动干掉了,又重装了intel主板驱动才算告一段落。
{zh1}附上xx手动卸载Vmware的文档(中&英)。
方法①:
1、以本地管理员帐户登陆你的主机
2、关闭主机上的所有的防火墙软件,一些防火墙软件会干涉安装的进程
3、利用Windows的“添加删除软件”功能删除VMware,如果VMware在添加删除程序的列表中
4、运行VMware注册表清理脚本,如果卸载不成功,则可以运行VMware_Install_Cleaner.exe也就 是我们常说的反安装软件。这个脚本可以xx Workstation 3.1, Workstation 3.2, Workstation 4.x, Workstation 5.x, GSX Server 2.x, GSX Server 3.0, GSX Server 3.1, ACE Manager 1.0, ACE 1.0, VmPerl 2.0, VmPerl 3.0, VmCOM 2.0, and VmCOM 3.0安装的时候,写入Windows的注册表键值。 如果你的VMware Workstation 的版本是5系列,则只需在命令行下输入VMware-workstation-<version>.exe /c ,就可以xx由MSI安装包写入注册表的键值。注意:在命令行中要把你的当前目录设置到VMware-workstation-<version>.exe文件所在目录,如果使用这个命令不起作用,则再使用VMware_Install_Cleaner。。其下载地址:
5、重新启动计算机
当你操作完第4点或者成功安装了VMware的时候请重新启动计算机。
6、使用Microsoft CleanUp utility
具体使用方法support.microsoft.com/default.aspx?scid=kb;en-us;290301.方法②:手动xx注册表
对注册表进行操作可能会导致系统无法正常启动,请在修改注册表之前备份注册表
1、以管理员的身份登陆本地计算机
2、停止以下服务
VMware Authentication Service
VMware Registration Service
VMware DHCP Service
VMware NAT Service
3、卸载VMware network bridge
开始>设置> 网络连接>右键任何网络适配器>属性
选择VMware Bridge Protocol 并卸载
4、卸载VMware安装的设备
计算机管理>设备管理器>查看>显示隐藏的设备
双击非即插即用驱动程序,删除如下:
hcmon
VMware Network Application Interface
VMparport
vmx86
VMware Bridge Protocol
双击网络适配器
卸载含有VMware字样的网络设备
5、运行VMware_Install_Cleaner.exe
6、删除你的安装程序所在的文件夹默认的安装位置为C:\Program Files\VMware,具体的位置根据你安装软件的时候设定的位置,注意:如果你的虚拟系统也在这个目录下,请删除前保存虚拟系统文件
7、删除应用程序信息文件夹 默认在C:\Documents and Settings\All Users\Application Data\VMware\.
8、删除VMware程序组文件夹,默认位置在 C:\Documents and Settings\All Users\Start Menu\Programs\VMware\.
9、删除桌面的快捷方式图标
10、删除如下文件在系统文件夹
%SystemDrive%\WINNT\system32\vmnat.exe
%SystemDrive%\WINNT\system32\vmnetbridge.exe
%SystemDrive%\WINNT\system32\vmnetdhcp.conf
%SystemDrive%\WINNT\system32\VMNetDHCP.exe
%SystemDrive%\WINNT\system32\vmnetdhcp.leases
%SystemDrive%\WINNT\system32\vmnetnat.conf
%SystemDrive%\WINNT\system32\vmxw2ksetup.dll
%SystemDrive%\WINNT\system32\vnetprobe.exe
%SystemDrive%\WINNT\system32\vnetprobelib.dll
%SystemDrive%\WINNT\system32\vnetinst.dll
%SystemDrive%\WINNT\system32\vnetlib.dll
%SystemDrive%\WINNT\system32\vnetlib.exe
%SystemDrive%\WINNT\system32\drivers\vmnet.sys
%SystemDrive%\WINNT\system32\drivers\vmnetx.sys
%SystemDrive%\WINNT\system32\drivers\VMparport.sys
%SystemDrive%\WINNT\system32\drivers\vmx86.sys
%SystemDrive%\WINNT\system32\drivers\vmnetadapter.sys
%SystemDrive%\WINNT\system32\drivers\vmnetbridge.sys
%SystemDrive%\WINNT\system32\drivers\vmnetuserif.sys
%SystemDrive%\WINNT\system32\drivers\hcmon.sys
%SystemDrive%\WINNT\system32\drivers\vmusb.sys
11、删除__vmware_user__用户和__vmware__用户组在本地用户组管理中
12、重新启动计算机英文部分:
I tried to uninstall a VMware product from my Windows host, but the uninstallation failed, or it seemed to work but I am unable to install again on the same host. What is going on?
This article describes the procedures for cleaning up after an incomplete uninstallation of various VMware products, including VMware ACE Manager on an administrator's computer. If you need information on cleaning up after an incomplete uninstallation of a VMware ACE package on an end user's computer, please see knowledge base article 1526 at .Note: The utility VMware_Install_Cleaner.exe, described in this article, cleans incomplete uninstallations of VMware Tools (versions 1.0.0.x — 3.1.0.x) in addition to incomplete uninstallations of VMware products.
Why This Problem Might Occur
VMware products might not install on Windows hosts if the installer detects certain other VMware products on the computer.Sometimes registry keys that should be removed during the uninstallation of a product are left behind. This can happen if, for example, the host computer hangs or resets while you are uninstalling the previous product. When the installer finds these registry keys, it interprets their presence as an indication that the previous product is still installed.
Solving This Issue
To troubleshoot an incomplete installation:
Be a Local Administrator. Make sure you are logged onto the Windows host as a Local Administrator. (A Domain Administrator imposes the wrong permissions on components the installer must access.)
Disable firewalls on protected systems. If your security policy allows this, disable any firewall software you have installed. Some firewalls can interfere with the installation process.
Uninstall using Add/Remove Programs > Remove. If the VMware product is still listed in Add/Remove Programs, try rebooting and uninstalling the VMware product:
a. Reboot the Windows host.
b. From the Control Panel, select Add/Remove Programs.
c. Select the VMware product in the list.
d. Click Remove.
e. Reboot the Windows host again.
f. Reinstall the VMware software.
Run the VMware registry cleaner script. If the uninstaller is not available, or if it does not run successfully, download and run the script VMware_Install_Cleaner.exe. Find it in the attachments section at the end of this document.Remember to run this script and the installer when you are logged on as a member of the Local Administrators group.
The registry cleaner utility removes all registry keys used by the installers for Workstation 3.1, Workstation 3.2, Workstation 4.x, Workstation 5.x, Workstation 6.x, GSX Server 2.x, GSX Server 3.0, GSX Server 3.1, ACE Manager 1.0, ACE 1.0, VmPerl 2.0, VmPerl 3.0, VmCOM 2.0, and VmCOM 3.0.
If you are running the Workstation 5.x or 6.x installer, don't run this script yet. Run the installer command with the /c switch, which automatically removes the MSI installer registration information for VMware Workstation.
VMware-workstation-<version>.exe /c
For example:
VMware-workstation-5.0.0-13124.exe /c VMware-workstation-5.5.0-18463.exe /c
If running the installer with the /c switch doesn't work, then try running the VMware_Install_Cleaner.exe script.
Reboot. After you run the cleaner script or the installer, reboot. It's a good idea to reboot after you install or uninstall any programs on your system, and after you run any other programs that make changes to the registry.
Try the Microsoft CleanUp utility.
If this previous steps prove unsuccessful, you might find a utility provided by Microsoft helpful. You can find instructions and a link to the utility in Microsoft knowledge base article 290301 at .
Clean the registry manually. See the following section.
Manually Cleaning the Registry
Caution: This procedure involves modifying the registry. Incorrect changes to the registry can leave your system unstable or unable to run. Always back up the registry before editing it, and exercise caution in making changes to the registry. VMware takes no responsibility for problems that might arise.
Log onto the Windows host system as the Local Administrator or a member of the Local Administrators group.
Stop the following services on the Windows host:
- VMware Authentication Service
- VMware Registration Service
- VMware DHCP Service
- VMware NAT Service
Uninstall the VMware network bridge adapter.
a. Choose Start > Settings > Network and Dial-up Connections.
b. Right-click any network adapter icon and choose Properties.
c. Select VMware Bridge Protocol and click Uninstall.
Uninstall all VMware devices.
a. Right-click My Computer and choose Manage.
b. Click Device Manager.
c. Double-click Network Adapters.
d. Right-click each adapter whose name begins with VMware and choose Uninstall.
e. Choose Show hidden devices from the View menu.
f. Double-click Non-Plug and Play Drivers.
g. Right-click the following devices and choose Uninstall.
- hcmon
- VMware Network Application Interface
- VMparport
- vmx86
- VMware Bridge Protocol
Run VMware_Install_Cleaner.exe again.
Delete the program folder in which the VMware product was installed. The default installation directory is C:\Program Files\VMware\. (The drive letter is different if your Program Files folder is on a different drive.) If you have installed only one VMware product, you can delete the entire VMware folder; if you have installed other products, such as VirtualCenter Client, delete only the relevant subfolders for the product you are trying to remove. On a GSX Server machine, you should remove the subfolders for VMware GSX Server, VMware Management Interface, VMware Scripting API, and either VMware Virtual Machine Console or VMware Remote Console.Note: If you have stored virtual machines in a folder under the program folder and want to save them, move them to a different folder before you delete the VMware program folder.
Delete the application data folder. The default locations are C:\Documents and Settings\All Users\Application Data\VMware\ and C:\Documents and Settings\<username>\Application Data\VMware. If you have installed only one VMware product, you can delete the entire VMware folder; if you have installed other products, such as VirtualCenter Client, delete only the relevant subfolders for the product you are trying to remove. On a GSX Server machine, you should remove the subfolders for VMware GSX Server, VMware Management Interface, VMware Scripting API, and either VMware Virtual Machine Console or VMware Remote Console.
Delete the VMware program group folder. The default location is C:\Documents and Settings\All Users\Start Menu\Programs\VMware\. If you have installed only one VMware product, you can delete the entire VMware folder; if you have installed other products, such as VirtualCenter Client, delete only the relevant subfolders for the product you are trying to remove. On a GSX Server machine, you should remove the subfolders for VMware GSX Server, VMware Management Interface, VMware Scripting API, and either VMware Virtual Machine Console or VMware Remote Console.
Delete the VMware shortcut icons from the desktop.
Delete the files below from the Windows system folder. (Not all systems have all of these files installed.)
%SystemDrive%\WINNT\system32\vmnat.exe
%SystemDrive%\WINNT\system32\vmnetbridge.exe
%SystemDrive%\WINNT\system32\vmnetdhcp.conf
%SystemDrive%\WINNT\system32\VMNetDHCP.exe
%SystemDrive%\WINNT\system32\vmnetdhcp.leases
%SystemDrive%\WINNT\system32\vmnetnat.conf
%SystemDrive%\WINNT\system32\vmxw2ksetup.dll
%SystemDrive%\WINNT\system32\vnetprobe.exe
%SystemDrive%\WINNT\system32\vnetprobelib.dll
%SystemDrive%\WINNT\system32\vnetinst.dll
%SystemDrive%\WINNT\system32\vnetlib.dll
%SystemDrive%\WINNT\system32\vnetlib.exe
%SystemDrive%\WINNT\system32\drivers\vmnet.sys
%SystemDrive%\WINNT\system32\drivers\vmnetx.sys
%SystemDrive%\WINNT\system32\drivers\VMparport.sys
%SystemDrive%\WINNT\system32\drivers\vmx86.sys
%SystemDrive%\WINNT\system32\drivers\vmnetadapter.sys
%SystemDrive%\WINNT\system32\drivers\vmnetbridge.sys
%SystemDrive%\WINNT\system32\drivers\vmnetuserif.sys
%SystemDrive%\WINNT\system32\drivers\hcmon.sys
%SystemDrive%\WINNT\system32\drivers\vmusb.sys
Delete the __vmware_user__ local user and the __vmware__ local group from the Windows system if they exist.
Reboot the Windows host system.