虚假特征“广告"状态导致卸载错误 1316 [英] Spurious feature "Advertised" state results in uninstall error 1316

查看：40
本文介绍了虚假特征“广告"状态导致卸载错误 1316的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

症状

用户有时在通过添加/删除程序(或应用和功能"设置应用)卸载时收到以下错误消息之一:

  • 错误 1316.指定的帐户已存在.

  • 错误 1316.尝试从文件:C:\WINDOWS\Installer\NameOfOriginalSetup.msi

实际上这两个是完全相同的错误，第一条消息仅在安装了 KB2918614(又名安全修复"补丁)并且产品未列入白名单时才会显示.只是错误代码被误解为一般的系统错误而不是在这种情况下，实际 MSI 错误.否则，KB2918614 无关紧要.

  • 错误 1406.无法将值写入键.确认您有足够的权限访问该密钥，或联系您的支持人员.

似乎不太常见.由于消息框包含一个忽略"按钮，它允许卸载继续进行，因此用户可能不太愿意报告此错误.

日志文件

通过msiexec -x {ProductCode} -l*vx LogFile.txt获得卸载日志文件.搜索value 3"会产生错误位置周围的部分:

MSI (s) (B0:9C) [15:18:10:427]:执行操作:FeatureUnpublish(Feature=ProductFeature,,Absent=2,Component=iJm4+0tc4@uTvD')YKUXZ{NA8`o569(2MdBLg[rJ)MSI (s) (B0:9C) [15:18:10:428]:注意:1:1402 2:UNKNOWN\Installer\Features\AFCEC7274CC7C0441A85705C47554DD5 3:2MSI (s) (B0:9C) [15:18:10:428]:执行操作:ActionStart(Name=InstallFiles,Description=Copying new files,Template=File: [1], Directory: [9], Size:[6])MSI (s) (B0:9C) [15:18:10:428]:执行操作:ProgressTotal(Total=5,Type=0,ByteEquivalent=1)MSI (s) (B0:9C) [15:18:10:428]:执行操作:SetTargetFolder(Folder=C:\Program Files\zett42\SpuriousFeatureAdvTest1\)MSI (s) (B0:9C) [15:18:10:428]:执行操作:SetSourceFolder(Folder=1\zett42\xipmcfby\|zett42\SpuriousFeatureAdvTest1\)MSI (s) (B0:9C) [15:18:10:428]: Executing op: ChangeMedia(,MediaPrompt=请插入磁盘:,MediaCabinet=1\cab1.cab,BytesPerTick=65536,CopierType=1,,,SignatureRequired=0,,,IsFirstPhysicalMedia=1)MSI (s) (B0:9C) [15:18:10:428]:执行操作:RegisterSharedComponentProvider(,,File=File2.txt,Component={3F28EEDB-866D-4201-8173-12532C657B6C},,ProductCode={727CECFA-7CC4-440C-A158-07C57455D45D},ProductVersion=1.0.0,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)MSI (s) (B0:9C) [15:18:10:428]:执行操作:FileCopy(SourceName=File2.txt,SourceCabKey=File2.txt,DestName=File2.txt,Attributes=512,FileSize=5,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPart1=1397189395,HashPart2=108432067,HashPart3=-1009892414,HashPart796637MSI (s) (B0:9C) [15:18:10:428]:文件:C:\Program Files\zett42\SpuriousFeatureAdvTest1\File2.txt；待安装；不会打补丁；没有现有文件MSI (s) (B0:9C) [15:18:10:428]:解析源.MSI (s) (B0:9C) [15:18:10:428]:使用缓存的产品上下文:为产品分配的机器:AFCEC7274CC7C0441A85705C47554DD5MSI (s) (B0:9C) [15:18:10:428]:使用缓存的产品上下文:为产品分配的机器:AFCEC7274CC7C0441A85705C47554DD5MSI (s) (B0:9C) [15:18:10:429]:将源解析为启动源.MSI (s) (B0:9C) [15:18:10:429]:将启动源设置为上次使用.MSI (s) (B0:9C) [15:18:10:429]:属性更改:添加 SourceDir 属性.它的值为C:\WINDOWS\Installer\".MSI (s) (B0:9C) [15:18:10:429]:属性更改:添加 SOURCEDIR 属性.它的值为C:\WINDOWS\Installer\".MSI (s) (B0:9C) [15:18:10:429]:属性更改:添加 SourcedirProduct 属性.它的值为{727CECFA-7CC4-440C-A158-07C57455D45D}".MSI (s) (B0:9C) [15:18:10:429]:SOURCEDIR ==>C:\WINDOWS\安装程序\MSI (s) (B0:9C) [15:18:10:429]:SOURCEDIR 产品 ==>{727CECFA-7CC4-440C-A158-07C57455D45D}MSI (s) (B0:9C) [15:18:10:429]:使用缓存的产品上下文:为产品分配的机器:AFCEC7274CC7C0441A85705C47554DD5MSI (s) (B0:9C) [15:18:10:429]:确定源类型MSI (s) (B0:9C) [15:18:10:429]:注意:1:2203 2:C:\WINDOWS\Installer\SpuriousFeatureAdvTest1.msi 3:-2147287038MSI (s) (B0:9C) [15:18:10:429]:注意:1:1316 2:C:\WINDOWS\Installer\SpuriousFeatureAdvTest1.msiMSI (s) (B0:9C) [15:18:10:429]:SECREPAIR:确定包源类型时出错MSI (s) (B0:9C) [15:18:10:429]:SECUREREPAIR:SecureRepair 失败.错误代码:524FD15800MSI (s) (B0:9C) [15:18:11:146]:注意:1:2205 2:3:错误MSI (s) (B0:9C) [15:18:11:146]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709MSI (s) (B0:9C) [15:18:11:146]:产品:zett42 SpuriousFeatureAdvTest1 -- 错误 1316.Das angegebene Konto ist bereits vorhanden.MSI (c) (C4:38) [15:18:10:436]:字体已创建.字符集:Req=0，Ret=0，字体:Req=MS Shell Dlg，Ret=MS Shell Dlg错误 1316. Das angegebene Konto ist bereits vorhanden.

(最后一行是指定的帐户已经存在."德语.)

从日志中可以看出，卸载尝试实际复制文件File2.txt"到硬盘驱动器(查找FileCopy条目).这似乎没有意义，当然在源不可用时它会失败.

同样有趣的是在日志中进一步显示的功能和组件状态:

MSI (s) (B0:9C) [15:18:10:387]: Feature: ProductFeature;安装:广告；请求:缺席；行动:缺席MSI (s) (B0:9C) [15:18:10:387]:组件:File1；已安装:未安装；请求:空；行动:空；客户端状态:未知MSI (s) (B0:9C) [15:18:10:387]:组件:File2；安装:本地；请求:空；行动:本地；客户状态:缺席

请注意，功能ProductFeature"具有已安装:广告"状态，尽管该功能是在本地安装的.组件File2"的Action: Local"与我们在日志中看到的相符，即 Windows Installer 希望在卸载过程中将文件安装本地！同样，这对我来说没有任何意义.

注册表缺陷

我发现在有问题的机器上，无法卸载的产品的随机组件注册表项丢失了:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\

手动添加缺失的注册表项(包括全新安装状态下的所有值)后，可以成功卸载产品.

事实证明，当缺少任何组件注册表项时，Windows Installer 会将包含这些组件的功能的状态确定为已发布".这仍然不足以在卸载时导致错误 1316.事实上，只有当磁盘上物理缺少组件文件时，Windows Installer 才会触发本地复制尝试.

最少的示例和重现步骤

我还没有能够自然地"重现这个问题，我.e.与在客户机器上发生的情况相同.只有手动删除上述组件注册表项之一，我才能人为地重现问题.

  1. 构建一个安装两个文件File1.txt"和File2.txt"的最小 WiX 设置:

<Package InstallerVersion="200" Compressed="yes" InstallScope="perMachine"/><MajorUpgrade DowngradeErrorMessage="已经安装了新版本的 $(var.ProductName)."/><媒体模板/><Feature Id="ProductFeature" Title="$(var.ProductName)" Level="1" AllowAdvertise="no" ><ComponentGroupRef Id="ProductComponents"/></功能><Directory Id="TARGETDIR" Name="SourceDir"><目录 ID="$(var.PlatformProgramFilesFolder)"><Directory Id="MANUFACTURERFOLDER" Name="$(var.Manufacturer)"><Directory Id="INSTALLFOLDER" Name="$(var.ProductName)"/></目录></目录></目录><ComponentGroup Id="ProductComponents" Directory="INSTALLFOLDER"><Component Id="File1" Guid="{19819F06-DD45-4B48-BD00-810DEF7C0297}"><File Source="File1.txt"/></组件><Component Id="File2" Guid="{3F28EEDB-866D-4201-8173-12532C657B6C}"><File Source="File2.txt"/></组件></组件组></产品></Wix>

  1. 安装 MSI 文件.

  2. 删除属于组件File1"的以下注册表项:

    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\60F9189154DD84B4DB0018D0FEC72079

  3. 删除属于同一功能的任何其他组件的密钥文件，在本例中为File2":

    c:\Program Files\zett42\SpuriousFeatureAdvTest1\File2.txt

  4. 尝试通过添加/删除程序"或应用和功能"卸载产品.

  5. 卸载失败并显示错误 1316"消息.

尝试的解决方案/变通方法

寻求支持:Microsoft 程序安装和卸载疑难解答 成功删除了有问题的产品.

我已尝试禁用广告功能()，但它没有改变任何东西.

问题

问题的可能原因是什么以及如何实际解决?

  • 违反设置中的组件规则.虽然我不能排除这个原因，但似乎不太可能，因为丢失的组件注册表项是随机的，并且只有一小部分用户受到影响.
  • 干扰 3rd 方软件，例如 AV 或注册表清理实用程序.
  • 磁盘或内存故障.
  • Windows 安装程序中的错误.
  • 还有什么吗?

搜索错误信息，发现问题很普遍.在某些情况中，错误是由在小升级期间更改 MSI 的文件名引起的.这绝对不是这里的情况，因为我们不做小升级，有问题的设置的 MSI 文件没有重命名.如上所述，很明显存在注册表缺陷.此处描述了可能类似的情况，但答案没有解释任何内容，它只是指向 MS 故障排除工具.

解决方案

我已经能够使用注册表清理器重现该问题.

重现步骤:

  1. 使用 Windows Installer 安装程序.
  2. 从程序文件夹中删除一个或多个作为其组件关键文件的文件.
  3. 运行注册表清理器.清洁工错误地确定不再需要 Windows Installer 组件注册表项(其密钥文件不存在).清洁器会删除注册表项.
  4. 从程序文件夹中删除更多作为其组件的关键文件的文件.
  5. 尝试卸载该程序.它失败并出现错误 1316.

即使没有第 4 步，此卸载也会中断，因为包含已删除组件的相同功能的组件安装的任何其他资源都不会被卸载.删除一个组件注册表项，整个功能将不再被卸载！

到了第 4 步，问题就变成了问题，因为整个卸载会回滚.当卸载作为需要先删除旧版本的主要升级的一部分运行时，它也可能变成安装问题.

虽然这些步骤看起来有些人为，但用户从程序安装文件夹中手动删除文件肯定不是不可能的.当程序安装在可移动磁盘上并且在移除磁盘后运行清理程序时，也可能会意外发生这种情况.可以考虑其他原因.

解决方案:

  • 不要使用注册表清理器.虽然有些可能确实有效，但始终存在破坏某些内容的风险.
  • 如果在卸载任何程序期间出现错误 1316 或 1406(可能也在主要升级期间，当旧版本被删除时)，请使用 Microsoft 程序安装和卸载疑难解答 处于卸载"模式.在某些情况下，您也可以通过重新运行用于安装程序的原始安装包来成功.

Symptoms

Users sometimes get one of the following error messages during uninstall through add/remove programs (or "Apps & Features" settings app):

  • Error 1316. The specified account already exists.

  • Error 1316. A network error occurred while attempting to read from the file: C:\WINDOWS\Installer\NameOfOriginalSetup.msi

Actually these two are the exact same error, the first message only shows up when KB2918614 (aka "Secure Repair" patch) is installed and the product is not white-listed. It's just that the error code gets misinterpreted as a general system error instead of the actual MSI error in this case. Otherwise, KB2918614 doesn't matter.

  • Error 1406. Could not write value to key . Verify that you have sufficient access to that key, or contact your support personnel.

Seems to be less common. As the message box contains an "Ignore" button, which allows the uninstall to continue anyway, users are propably less inclined to report this error.

Log File

Obtained uninstall log file through msiexec -x {ProductCode} -l*vx LogFile.txt. Searching for "value 3" yields the part around the error location:

MSI (s) (B0:9C) [15:18:10:427]: Executing op: FeatureUnpublish(Feature=ProductFeature,,Absent=2,Component=iJm4+0tc4@uTvD')YKUXZ{NA8`o569(2MdBLg[rJ)
MSI (s) (B0:9C) [15:18:10:428]: Note: 1: 1402 2: UNKNOWN\Installer\Features\AFCEC7274CC7C0441A85705C47554DD5 3: 2 
MSI (s) (B0:9C) [15:18:10:428]: Executing op: ActionStart(Name=InstallFiles,Description=Copying new files,Template=File: [1],  Directory: [9],  Size: [6])
MSI (s) (B0:9C) [15:18:10:428]: Executing op: ProgressTotal(Total=5,Type=0,ByteEquivalent=1)
MSI (s) (B0:9C) [15:18:10:428]: Executing op: SetTargetFolder(Folder=C:\Program Files\zett42\SpuriousFeatureAdvTest1\)
MSI (s) (B0:9C) [15:18:10:428]: Executing op: SetSourceFolder(Folder=1\zett42\xipmcfby\|zett42\SpuriousFeatureAdvTest1\)
MSI (s) (B0:9C) [15:18:10:428]: Executing op: ChangeMedia(,MediaPrompt=Please insert the disk: ,MediaCabinet=1\cab1.cab,BytesPerTick=65536,CopierType=1,,,SignatureRequired=0,,,IsFirstPhysicalMedia=1)
MSI (s) (B0:9C) [15:18:10:428]: Executing op: RegisterSharedComponentProvider(,,File=File2.txt,Component={3F28EEDB-866D-4201-8173-12532C657B6C},,ProductCode={727CECFA-7CC4-440C-A158-07C57455D45D},ProductVersion=1.0.0,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
MSI (s) (B0:9C) [15:18:10:428]: Executing op: FileCopy(SourceName=File2.txt,SourceCabKey=File2.txt,DestName=File2.txt,Attributes=512,FileSize=5,PerTick=65536,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPart1=1397189395,HashPart2=108432067,HashPart3=-1009892414,HashPart4=374579663,,)
MSI (s) (B0:9C) [15:18:10:428]: File: C:\Program Files\zett42\SpuriousFeatureAdvTest1\File2.txt;    To be installed;    Won't patch;    No existing file
MSI (s) (B0:9C) [15:18:10:428]: Resolving source.
MSI (s) (B0:9C) [15:18:10:428]: Using cached product context: machine assigned for product: AFCEC7274CC7C0441A85705C47554DD5
MSI (s) (B0:9C) [15:18:10:428]: Using cached product context: machine assigned for product: AFCEC7274CC7C0441A85705C47554DD5
MSI (s) (B0:9C) [15:18:10:429]: Resolving source to launched-from source.
MSI (s) (B0:9C) [15:18:10:429]: Setting launched-from source as last-used.
MSI (s) (B0:9C) [15:18:10:429]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\WINDOWS\Installer\'.
MSI (s) (B0:9C) [15:18:10:429]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\WINDOWS\Installer\'.
MSI (s) (B0:9C) [15:18:10:429]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{727CECFA-7CC4-440C-A158-07C57455D45D}'.
MSI (s) (B0:9C) [15:18:10:429]: SOURCEDIR ==> C:\WINDOWS\Installer\
MSI (s) (B0:9C) [15:18:10:429]: SOURCEDIR product ==> {727CECFA-7CC4-440C-A158-07C57455D45D}
MSI (s) (B0:9C) [15:18:10:429]: Using cached product context: machine assigned for product: AFCEC7274CC7C0441A85705C47554DD5
MSI (s) (B0:9C) [15:18:10:429]: Determining source type
MSI (s) (B0:9C) [15:18:10:429]: Note: 1: 2203 2: C:\WINDOWS\Installer\SpuriousFeatureAdvTest1.msi 3: -2147287038 
MSI (s) (B0:9C) [15:18:10:429]: Note: 1: 1316 2: C:\WINDOWS\Installer\SpuriousFeatureAdvTest1.msi 
MSI (s) (B0:9C) [15:18:10:429]: SECREPAIR: Error determining package source type
MSI (s) (B0:9C) [15:18:10:429]: SECUREREPAIR: SecureRepair Failed. Error code: 524FD15800
MSI (s) (B0:9C) [15:18:11:146]: Note: 1: 2205 2:  3: Error 
MSI (s) (B0:9C) [15:18:11:146]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 
MSI (s) (B0:9C) [15:18:11:146]: Product: zett42 SpuriousFeatureAdvTest1 -- Error 1316. Das angegebene Konto ist bereits vorhanden.


MSI (c) (C4:38) [15:18:10:436]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

Error 1316. Das angegebene Konto ist bereits vorhanden.

(The last log line is "The specified account already exists." in German.)

As can be seen from the log, the uninstallation tries to actually copy the file "File2.txt" to the hard drive (look for the FileCopy entry). This doesn't seem to make sense and of course it fails when the source is not available.

Also interesting are the feature and component states which are revealed further up in the log:

MSI (s) (B0:9C) [15:18:10:387]: Feature: ProductFeature; Installed: Advertise;   Request: Absent;   Action: Absent
MSI (s) (B0:9C) [15:18:10:387]: Component: File1; Installed: Absent;   Request: Null;   Action: Null;   Client State: Unknown
MSI (s) (B0:9C) [15:18:10:387]: Component: File2; Installed: Local;   Request: Null;   Action: Local;   Client State: Absent

Note that feature "ProductFeature" has "Installed: Advertise" state, though the feature was installed locally. The "Action: Local" for component "File2" matches what we saw in the log, that is Windows Installer wants the file installed locally during uninstall! Again, this doesn't make any sense to me.

Registry Defects

I've found out that on problem machines, random component registry keys of the product that could not be uninstalled, are missing:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\<ComponentKey>

After manually adding the missing registry key, including all values from a clean installation state, the product could be successfully uninstalled.

It turns out that when any of the component registry keys are missing, Windows Installer determines the state of the feature that contains these components, as being "advertised". This is still not sufficient to cause error 1316 on uninstall. In fact, only when component files are physically missing on disk, an attempt for local copy is triggered by Windows Installer.

Minimal Example and Repro Steps

I have not yet been able to reproduce the problem "naturally", i. e. in the same way as it happens on customers machines. Only by manually deleting one of the above mentioned component registry keys, I can artificially reproduce the problem.

  1. Build a minimal WiX setup that installs two files, "File1.txt" and "File2.txt":

<?xml version="1.0" encoding="UTF-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">
  <?define ProductName = "SpuriousFeatureAdvTest1"?>
  <?define Manufacturer = "zett42"?> 
  <?if $(var.Platform) = x64 ?>
    <?define PlatformProgramFilesFolder = "ProgramFiles64Folder" ?>
  <?else ?>
    <?define PlatformProgramFilesFolder = "ProgramFilesFolder" ?>
  <?endif ?>

  <Product Id="*" Name="$(var.Manufacturer) $(var.ProductName)" Language="1033" Version="1.0.0.0" Manufacturer="$(var.Manufacturer)" UpgradeCode="{65CEA630-EFC0-4199-86EE-88867AABEDEF}">
    <Package InstallerVersion="200" Compressed="yes" InstallScope="perMachine" />

    <MajorUpgrade DowngradeErrorMessage="A newer version of $(var.ProductName) is already installed." />
    <MediaTemplate />

    <Feature Id="ProductFeature" Title="$(var.ProductName)" Level="1" AllowAdvertise="no" >
        <ComponentGroupRef Id="ProductComponents" />
    </Feature>

    <Directory Id="TARGETDIR" Name="SourceDir">
      <Directory Id="$(var.PlatformProgramFilesFolder)">
        <Directory Id="MANUFACTURERFOLDER" Name="$(var.Manufacturer)">
          <Directory Id="INSTALLFOLDER" Name="$(var.ProductName)" />
        </Directory>
      </Directory>
    </Directory>

    <ComponentGroup Id="ProductComponents" Directory="INSTALLFOLDER">
      <Component Id="File1" Guid="{19819F06-DD45-4B48-BD00-810DEF7C0297}">
        <File Source="File1.txt"/>
      </Component>
      <Component Id="File2" Guid="{3F28EEDB-866D-4201-8173-12532C657B6C}">
        <File Source="File2.txt"/>
      </Component>
    </ComponentGroup>  
  </Product>
</Wix>

  1. Install the MSI file.

  2. Delete the following registry key that belongs to component "File1":

    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\60F9189154DD84B4DB0018D0FEC72079

  3. Delete a key file that belongs to any of the other components of the same feature, in this case "File2":

    c:\Program Files\zett42\SpuriousFeatureAdvTest1\File2.txt

  4. Try to uninstall the product via "Add/Remove Programs" or "Apps & Features".

  5. Uninstallation fails with "Error 1316" message.

Attempted solutions / workarounds

For support: The Microsoft Program Install and Uninstall troubleshooter successfully removes the problematic product.

I have tried to disable advertising of the feature (<Feature AllowAdvertise="no"/>), but it doesn't change anything.

Question

What could be possible causes of the problem and how to actually solve it?

  • Violation of component rules in the setup. Although I cannot exclude this cause, it seems unlikely as the missing component registry key(s) are random and only a small percentage of users is affected.
  • Interference of 3rd party software, like AV or registry cleanup utilities.
  • Disk or memory failures.
  • Bug in Windows Installer.
  • Anything else?

Searching for the error message shows that the problem is quite common. In some cases the error is caused by changing the file name of the MSI during a minor upgrade. This is definitely not the case here, because we don't do minor upgrades and the MSI files of the problematic setups were not renamed. As explained above it is very clear that there is a registry defect. A possibly similar case is described here, but the answer doesn't explain anything, it just points to the MS troubleshooting tool.

解决方案

I have been able to reproduce the problem using a registry cleaner.

Repro Steps:

  1. Install a program using Windows Installer.
  2. Delete one or more files that are keyfiles of their components from the program folder.
  3. Run the registry cleaner. The cleaner mistakenly determined that the Windows Installer component registry keys, who's keyfiles don't exist, are no longer needed. The cleaner deletes the registry keys.
  4. Delete more files that are keyfiles of their components from the program folder.
  5. Try to uninstall the program. It fails with error 1316.

Even without step 4, this uninstall will be broken, because any other resources installed by components of the same feature that contains the deleted components, won't be uninstalled. Delete one component registry key and the whole feature won't be uninstalled anymore!

With step 4, the issue turns into a problem, as the whole uninstall will rollback. It may also turn into an install problem, when the uninstall runs as part of a major upgrade that requires the older version to be removed first.

While the steps appear somewhat artificial, it is certainly not unlikely that users manually delete files from a programs installation folder. This could also happen accidentally when programs are installed on removable disks and the cleaner runs after the disk has been removed. Other reasons could be thought of.

Solution:

  • Don't use registry cleaners. While some may actually work, there is always the risk that they break something.
  • If error 1316 or 1406 occur during uninstall of any program (possibly also during major upgrade, when the older version gets removed), use Microsoft Program Install and Uninstall troubleshooter in "uninstall" mode. In some cases you may also succeed by rerunning the original setup package used to install the program.

这篇关于虚假特征“广告"状态导致卸载错误 1316的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！

查看全文
相关文章
其他开发最新文章
热门教程
热门工具
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆