完全卸载vmware ----Setup has detected that vmware workstation is alrea...

本文介绍了解决VMware产品在Windows系统上卸载不完全的问题,包括使用官方提供的清理工具、手动清理注册表等步骤,确保后续安装顺利。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

 中文部分:

在安装VMware 的过程中由于各种各样的原因而中断安装进程,或者卸载旧的VMware版本,安装新的版本,结果安装进程出现错误,显示为:Setup has detected that vmware workstation is already installed on this machine. please uninstall this product through add/remove programs and try again.

一、为什么会发生不完全卸载的情况?
VMware不可以安装在已经安装有VMware产品的windows主机上,VMware是否已经安装在一台Windows主机上,是根据注册表的一些键值来判断的。当卸载VMware的时候,这些键值没有被删除,于是在下次安装VMware的时候,就会出现问题。

二、解决办法:

方法①:
1、以本地管理员帐户登陆你的主机
2、关闭主机上的所有的防火墙软件,一些防火墙软件会干涉安装的进程
3、利用Windows的“添加删除软件”功能删除VMware,如果VMware在添加删除程序的列表中
4、运行VMware注册表清理脚本,如果卸载不成功,则可以运行VMware_Install_Cleaner.exe也就   是我们常说的反安装软件。这个脚本可以清除 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 ,就可以清除由MSI安装包写入注册表的键值。注意:在命令行中要把你的当前目录设置到VMware-workstation-<version>.exe文件所在目录,如果使用这个命令不起作用,则再使用VMware_Install_Cleaner。。

其下载地址:http://kb.vmware.com/Platform/Publishing/attachments/1308_fVMware_Install_Cleaner.exe

5、重新启动计算机
    当你操作完第4点或者成功安装了VMware的时候请重新启动计算机。
6、使用Microsoft CleanUp utility
    具体使用方法support.microsoft.com/default.aspx?scid=kb;en-us;290301.

方法②:手动清除注册表
对注册表进行操作可能会导致系统无法正常启动,请在修改注册表之前备份注册表
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 http://kb.vmware.com/kb/1526.

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:
  1. 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.)

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

  3. Uninstall using Add/Remove Programs > Remove. If the VMware product is still listed inAdd/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.

  4. 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 theVMware_Install_Cleaner.exe script.

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

  6. 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
    http://support.microsoft.com/default.aspx?scid=kb;en-us;290301 .

  7. 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.
  1. Log onto the Windows host system as the Local Administrator or a member of the Local Administrators group.

  2. Stop the following services on the Windows host:
    - VMware Authentication Service
    - VMware Registration Service
    - VMware DHCP Service
    - VMware NAT Service

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

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

  5. Run VMware_Install_Cleaner.exe again.

  6. 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 VMwarefolder; 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.

  7. 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 VMwarefolder; 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.

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

  9. Delete the VMware shortcut icons from the desktop.

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

  11. Delete the __vmware_user__ local user and the __vmware__ local group from the Windows system if they exist.

  12. Reboot the Windows host system.
<think>好的,我现在需要处理用户提出的关于“Secure Boot Violation - Invalid Signature Detected. Check Secure Boot Policy in Setup”错误的问题。首先,我得理解这个错误的具体含义以及可能的原因。 Secure Boot是UEFI固件中的一项安全功能,用于确保设备只加载受信任的操作系统和驱动程序。当出现无效签名时,说明系统尝试加载的某个组件没有正确的数字签名,或者签名未被信任的机构颁发。接下来,我需要考虑可能导致此问题的各种原因,并给出相应的解决步骤。 首先,用户可能在启动时遇到了这个错误,可能是在安装新硬件、更新系统或操作系统之后。常见的原因包括:Secure Boot策略设置不正确、操作系统引导加载程序未正确签名、硬件变更导致驱动签名问题,或者固件/系统更新后配置不兼容。 接下来,我需要组织回答的结构,确保逐步引导用户排查问题。可能需要从检查Secure Boot策略开始,确认其是否启用且配置正确。然后检查操作系统是否支持Secure Boot,例如某些Linux发行版可能需要额外步骤。硬件变更也是一个因素,特别是新安装的硬件驱动未签名的情况。此外,固件问题或系统文件损坏也可能导致错误,建议更新BIOS/UEFI或修复系统。 需要注意的是,用户可能对UEFI设置不熟悉,所以需要详细说明如何进入BIOS/UEFI界面,通常在启动时按特定键(如F2、Del、Esc等)。另外,禁用Secure Boot虽然可以暂时解决问题,但会降低安全性,所以应作为最后手段,并提醒用户风险。 最后,要确保语言简洁明了,避免技术术语过于复杂,同时覆盖所有可能的解决方案,并建议联系制造商支持如果问题仍未解决。检查步骤的逻辑顺序,确保用户能一步步跟随操作,而不会遗漏关键点。</think>### Secure Boot违规提示解析:**“Invalid signature detected. Check Secure Boot Policy in Setup”** 此错误表明系统在启动过程中检测到未通过安全验证的组件(如操作系统引导程序、驱动程序或固件),因其数字签名无效或未被信任。以下是分步排查与解决方案: --- #### **1. 理解Secure Boot机制** - **功能**:Secure Boot是UEFI固件的安全协议,确保仅加载经可信机构(如微软、硬件厂商)签名的代码。 - **触发原因**:当系统尝试加载未签名、签名损坏或来自未授权来源的组件时,会提示此错误。 --- #### **2. 初步排查步骤** **步骤1:重启并进入UEFI/BIOS设置** - **操作**:开机时反复按**Del/F2/Esc**(具体键位因主板型号而异)。 - **目标**:检查Secure Boot状态及策略配置。 **步骤2:检查Secure Boot设置** - **路径**:在UEFI中找到`Security`或`Boot`选项卡 → 确认`Secure Boot`已启用(Enabled)。 - **策略调整**: - 若设为**“Standard”**(默认信任微软/厂商签名),尝试切换为**“Custom”**或**“Other OS”**(部分系统支持非Windows组件)。 - 若误设为**“Deployed Mode”**(严格模式),需重置为**“User Mode”**。 **步骤3:验证操作系统兼容性** - **Windows**:确保为官方镜像且启用安全启动支持(Windows 8+默认兼容)。 - **Linux**:部分发行版需启用**shim**或**PreLoader**签署的引导程序(如Ubuntu需勾选“Secure Boot支持”)。 --- #### **3. 常见场景及解决方法** **场景1:新安装硬件/驱动程序导致** - **问题**:新增硬件驱动未正确签名。 - **解决**: 1. 进入系统后卸载可疑驱动。 2. 通过设备管理器重新安装经WHQL认证的驱动。 **场景2:系统/固件更新后异常** - **问题**:更新后Secure Boot数据库(db)或吊销列表(dbx)未同步。 - **解决**: 1. 在UEFI中重置Secure Boot密钥至默认值(选项如**“Restore Factory Keys”**)。 2. 更新主板固件至最新版本。 **场景3:双系统引导冲突** - **问题**:Linux/其他系统引导程序(如GRUB)签名未被信任。 - **解决**: 1. 在UEFI中添加自定义签名(需MOK管理工具)。 2. 或暂时禁用Secure Boot(降低安全性,慎用)。 --- #### **4. 高级修复手段** **方法1:重建系统引导记录** - **Windows**: 1. 使用安装介质启动 → 选择“修复计算机” → 打开命令提示符。 2. 执行: ```bash bootrec /fixmbr bootrec /fixboot ``` - **Linux**:重新安装引导程序(如`grub-install`)并确保启用Secure Boot模块。 **方法2:清除TPM芯片(可选)** - **操作**:在UEFI中找到**TPM Configuration** → 选择**Clear TPM**。 --- #### **5. 注意事项** - **禁用Secure Boot的风险**:可能允许恶意软件劫持启动过程,仅建议临时测试。 - **硬件限制**:部分旧硬件或自定义组件(如显卡)可能固件签名不兼容,需联系厂商获取支持。 --- 若上述步骤无效,请联系设备制造商或操作系统供应商进一步诊断Secure Boot策略配置或硬件兼容性问题。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值