尝试创建“uc.micro"时，windows 中的设置过程失败访问被拒绝.文件夹 [英] The setup process in windows fails access denied when trying to create "uc.micro" folder

问题描述

我无法安装该软件(在 Windows 10 中)，是否有其他人处理过这个问题?

I just can't install the software (in Windows 10), have somebody else handled this issue?

推荐答案

安全软件干扰(误报检测)

这只是拒绝访问警告吗?看起来可能是安全软件问题 - 文件夹被识别为恶意软件.随着安全软件针对当今条件加强安全性，此问题越来越普遍:https://github.com/Microsoft/vscode/issues/13559

Security Software Interference (False Positive Detection)

Is that just an access denied warning? It looks like it might be a security software issue - the folder is being recognized as malware. This problem is more and more prevalent as security software tightens security for today's conditions: https://github.com/Microsoft/vscode/issues/13559

禁用防病毒或安全软件，然后重试.如果这不起作用，请阅读下面的一些进一步建议.

Disable your anti-virus or security software and try again. If that doesn't work, please read some further suggestions below.

请报告导致您问题的安全软件 - 如果有的话.这对社区很重要.我们看到越来越多的这些问题，一开始它们可能非常神秘.

Please report what security software caused the problem for you - if any. This is important for the community. We are seeing more and more of these problems, and they can be very mysterious at first.

警告:请注意，现在某些安全软件可能会直接从超级隐藏的本地缓存文件夹中隔离整个 MSI 文件！当这种情况发生时，你真的有问题.请阅读此答案中的第 7 节以获取信息:如何避免使用我的 WiX/MSI 包触发 MSI 自我修复?(不要被问题名称所欺骗 - 第 7 节相关).您可能会遇到无法卸载和无法升级的软件包.

WARNING: Please note that certain security software may quarantine whole MSI files directly from the super-hidden, local cache folder these days! When this happens you really have a problem. Please read section 7 in this answer for information: How do I avoid triggering MSI self-repair with my WiX / MSI package? (don't be deceived by the question name - section 7 is relevant). You may be stuck with an un-uninstallable and un-upgradeable package.

部署问题往往集中在:某事锁定资源(正在使用)，某事阻止/阻止访问(安全软件干预，网络无法访问)，某事是拒绝权限(ACL、特权)、某些内容损坏(数据文件、操作系统设置)、不满足运行时要求(缺少依赖项).

Deployment problems tend to center around: something is locking resources (in use), something is blocking / preventing access (security software intervention, network unreachable), something is denying permission (ACL, privileges), something is corrupted (data file, OS settings), a runtime requirement is not met (missing dependencies).

请考虑这些简单、通用的措施来尽量减少问题:

Please consider these easy, general measures to minimize problems:

核心

• 在尝试其他任何事情之前，先在干净的系统(虚拟机)上尝试一个失败的安装程序.
• 如果您发现部署问题，一定要关闭安全软件和防病毒软件.
• 在安装前关闭尽可能多的应用程序和软件解决方案.
• 验证目标磁盘是否有足够的可用空间(对于当今的笔记本电脑 SD 磁盘和巨大的媒体文件来说，这是一个比预期更常见的问题).
• 如果您的本地化安装程序失败，是否有英文版本可用?

• Try a failed installer on a clean system (virtual machine) before trying anything else.
• Definitely shut down security software and anti-virus if you see deployment problems.
• Shut down as many applications and software solutions as possible before installing.
• Verify that the target disk has enough free space available (a more common problem than expected with today's laptop SD-disks and huge media files).
• If your localized installer fails, is there an English version available?

进一步

• 确保没有远程用户登录或访问共享资源.
• 如果可能，请验证您下载的安装程序文件的完整性.
• 检查目标安装盘是否存在文件系统或表面错误.
• 在部署之前进行恶意软件检查(如果之前的部署失败).
• 检查目标位置的自定义权限 (ACL) 是否安装失败.

我现在能想到的设置失败的潜在原因主要围绕锁定问题、连接问题、数据损坏问题、系统<强>设置干扰和各种模糊.这份清单有点疯狂——尤其是在结尾处——简直就是脑残.

Potential causes of setup failures that I can think of right now center around locking issues, connectivity issue, data corruption issues, system settings interference and various obscurities. This list is a bit mad - especially towards the end - it is just a brain dump.

1. 盒子(Visual Studio?)上的运行工具有一个文件夹锁定.关闭嫌疑人并重试.或者如果安装到网络驱动器(不要)，则网络连接可能会丢失.
   • 如上所述，您的情况中的锁定可能来自安全软件阻止您的安装程序，因为它试图创建一个识别为恶意软件的文件夹(误报 - 可能).
   • 其他工具也可能有问题，包括 Windows 中的计划任务或开发工具或类似的涉及"或高级"软件.或者就此事而言，常规的简单软件(但那些在文件夹结构中做得如此深的人会做什么?).Windows 服务 也会干扰.多种可能性.
   • 我想您可能会安装到网络驱动器，并且连接可能会丢失.
   • 我想您可能要安装到共享文件夹，并且网络上的某个人可能锁定了您的安装程序试图替换的文件.
   • 我想一个文件夹可以以某种方式加密，而不是解密和写入?(我不使用此功能 - 另外，加密安装目录会很奇怪.
   • 既然我们已经陷入困境，那么如果用户通过远程桌面连接并且锁定了目标文件夹呢?
   • 域管理员可以随时在您的本地磁盘上工作，锁定资源而不会为您提供任何可见的痕迹.

1. There is a lock on the folder by a running tool on the box (Visual Studio?). Close down suspects and try again. Or network connectivity could be lost if installing to a network drive (don't).
   • As stated above the lock in your case is probably from a security software blocking your installer as it tries to create a folder recognized as malware (false positive - probably).
   • Other tools could also be at fault, including scheduled tasks in Windows or development tools or similarly "involved" or "advanced" software. Or regular, simple software for that matter (but what would those be doing so deep in the folder structure?). Windows services can also interfere. Many possibilities.
   • I suppose you could be installing to a network drive, and connectivity could be lost.
   • I suppose you could be installing into a folder that is shared, and someone on the network may have a lock on a file your installer is trying to replace.
   • I suppose a folder could be encrypted somehow, and not decrypted and available for writing? (I don't use this feature - also, it would be weird to encrypt an installation directory.
   • Since we are out on a limb already, how about if a user is connected by remote desktop and has a lock in the target folder?
   • A domain admin could be working on your local disk at any time, locking resources without any visible trace for you.

• 除了下载不完整和安全软件干扰之外，其他因素也会导致文件损坏.真正的恶意软件，一方面是网络连接问题、SAMBA(Linux/Windows 文件共享技术)或其他相关工具(解压缩器等)中的错误，以及许多其他问题，更隐晦的原因，等等...
• 甚至是硬件问题，例如针对尖端 I/O 组件(例如超快速 NVMe 磁盘)的坏驱动程序.后者会给你带来无尽的悲伤.还有闪存驱动器磨损和耗尽的问题.
• 如果可以，请使用 Virustotal.com 检查您的下载.您可能已经知道您自己的安全软件将设置检测为恶意软件，看看其他安全软件是否同意?这是对未知安装者的一般建议 - 您的安装者可能没问题.
• 文件可能太大而无法上传到 Virustotal.com(或其他在线恶意软件扫描程序).您还可以使用来自 Sysinternals 的 procexp64.exe 以交互方式检查恶意软件的运行进程(直接下载Sysinternals Process Explorer)在测试安装后扫描所有正在运行的进程.在此处查看该工具的一些建议使用步骤.

• Besides incomplete download and security software interference other things can also cause the file to become corrupt. Real malware for one thing, network connectivity issues, bugs in SAMBA (Linux / Windows file sharing technology) or other relevant tools (decompressors etc...), and many other, more obscure reasons, etc...
• Even hardware issues such as bad drivers for cutting edge I/O components such as super fast NVMe disks. No end to grief the latter can cause you. And there is the issue of flash drive wear and exhaustion.
• If you can, check your download with Virustotal.com. You may already know that your own security software detects the setup as malware, see if other security software agree? This is general advice for unknown installers - your installer is probably fine.
• The file may be too large to upload to Virustotal.com (or other online malware scanners). You can also use procexp64.exe from Sysinternals to check running processes for malware interactively (direct download of Sysinternals Process Explorer) to scan all your running processes after test installation. See some suggested usage steps for the tool here.

• 这可能是破坏了某些东西的真正的恶意软件.我对你的情况表示怀疑.
• 这可能是您对各种 Windows 设置和配置的自己的修补和测试.
  • 您可以设置一些拒绝 ACL 来为某人锁定文件夹，但它们会产生很多副作用.
  • 我对组策略几乎一无所知，但它有大量设置对工作站和服务器都有影响.
  • This could be real malware having destroyed something. I doubt it in your case.
  • It could be your own tinkering and testing of various Windows settings and configurations.
    • You could have set some deny ACLs to lock folders for someone, and they have a lot of side-effects.
    • I know next to nothing about group policy, but it has a serious amount of settings that have impact on workstations and servers alike.
    • 您可以检查该文件夹的情况 - 只需将其重命名并为其名称添加 _OLD 后缀，然后再次尝试运行.
    • 或者在虚拟机上运行测试安装 - 如果有的话 - 看看它是否在干净的机器上完成.
    • You could check what is up with that folder - just renaming it adding an _OLD suffix to its name and then try to run again.
    • Or run a test install on a virtual machine perhaps - if you got one - to see if it finishes on a clean machine.
    • 这种情况可能很少见(对于台式机)，但有可能目标磁盘或分区已满(对于笔记本电脑来说并不罕见?).
    • 信不信由你，但是安装程序的目标路径可能太长了！如果是这种情况，我认为这样的设置不会成功，但也许(Windows Installer 会可能会在文件复制开始之前失败).
    • 在您的设置中发生自定义操作或自定义操作时，在代码或逻辑运行时遇到缺少运行时依赖项的故障点并非不可能.我认为在这种情况下不太可能.
      • 例如:安装程序托管代码自定义操作或操作的 .NET 运行时可能已损坏或丢失.
      • 对于嵌入在设置中的托管代码，代码访问安全性是否也会失败?坦率地说，我不确定 - 在 MSI 中，大多数自定义操作都会提升.
      • It might be rare (for desktops), but it is possible that the target disk or partition is full (not so rare for laptops?).
      • Believe it or not, but the installer target path can be too long! I don't think such a setup would get off the ground if this was the case, but maybe (Windows Installer would probably fail before file copy starts).
      • It is not impossible that a custom action or custom operation may be happening in your setup at the point of failure where code or logic is running that suffers missing runtime dependencies. Not likely in this case I think.
        • For example: the .NET runtime may be broken or missing for an installer managed code custom action or operation.
        • Could Code Access Security also fail for managed code embedded in the setup? Frankly I am not sure - in MSI most custom actions run elevated.
        • 某些服务器操作系统机器在安装某些设置时可能会出现问题.
        • 具有特殊角色的服务器机器(AD 域控制器，
        • 虚拟化服务器、终端服务器、瘦客户端等...
        • 您正在运行未升级的安装操作，并且安装程序突然尝试写入受保护的位置.
        • 目标文件夹是奇怪的东西" - 就像一个 硬链接或软链接.现在这是我从未见过的，只是列出我想到的任何内容.
        • 您的安装程序已升级，但突然尝试以非法方式(GAC、WinSxS 等)写入非常受保护的系统位置...)(可能由于各种原因在某些系统上发生 - 例如，由于安装程序中的错误而使用不同语言的系统).
        • You are running an un-elevated installation operation and the setup suddenly tries to write to a protected location.
        • The target folder is "something weird" - like a hard or soft link. Now this I have never seen, just listing whatever comes to mind.
        • Your installer is elevated, but suddenly tries to write to a very protected system location in an illegal way (GAC, WinSxS, etc...) (can happen on some systems for various reasons - for example a system in a different language due to errors in the installer).
        • 我见过几个安装人员要求通过互联网聊天，但在不可能时却失败了.
        • 您正在安装到具有 Unicode 名称(日语、韩语、中文、阿拉伯语等)的文件夹中，并且由于设置中的错误，安装程序无法正确完成.
        • Windows 搜索是否会运行并导致锁定或错误问题?(是的，这很荒谬，但让我们放纵一下这种质疑的心情).
        • 我猜各种版本控制系统可能会在文件系统中维护意外锁定.Internet 文件共享解决方案 或网络服务器 (?) 也是如此.
        • 我认为 NT 权限的自定义配置可能会导致设置中的某些操作锁定并且无法完成.此处第 13 节中的一些信息:如何避免 WiX/MSI 部署解决方案中的常见设计缺陷?.
        • 更糟糕的是:系统时间在安装过程中出错，安装程序因此而停止?(Windows Update 肯定会发生).也许您甚至在安装过程中切换到了不同的时区，并且出现了崩溃或混淆的情况.没见过这个.也许您在大西洋中部的 777 安装 Visual Studio Code(这显示了其他问题 - 只是说)，同时拒绝与您旁边的怪人交谈.提示:在这种情况下，你可能是个怪人:-).
        • 问题现在已经很模糊了，是时候结束这个列表了.重点是:安装人员非常容易受到很多我们几乎从未考虑过的事情的影响.幸运的是，大多数时候事情似乎都有效——当出现问题时，解决问题变得更加笨拙.话虽如此，后面的一些观点可能接近荒谬.但不要低估所有计算领域的顽疾".
        • I have seen a couple of installers that demanded to chat over the Internet and failed when that was not possible.
        • You are installing into a folder with a Unicode name (Japanese, Korean, Chinese, Arabic, etc...), and the installer fails to complete correctly due to bugs in the setup.
        • Could Windows Search be running and causing problems with locks or bugs? (getting ridiculous yes, but let's indulge this interrogative mood).
        • I guess various version control systems could maintain unexpected locks in the file system. As could Internet file sharing solutions or web servers (?).
        • I suppose custom configuration for NT privileges could cause certain operations in a setup to lock up and be unable to complete. Some info in section 13 here: How do I avoid common design flaws in my WiX / MSI deployment solution?.
        • And worse and worse: the system time is wrong during installation and the setup halts because of it? (can certainly happen with Windows Update). Perhaps you even switched to a different time zone during the install and something crashed or got confused. Never seen this. Perhaps you are mid-Atlantic in a 777 installing Visual Studio Code (this shows other issues - just sayin') whilst refusing to speak to the weirdo next to you . Hint: chances are you might be the weirdo in such a scenario :-).
        • The issues are so obscure now that it is time to end the list. The point is just this: installers are terribly vulnerable to a lot of things that we hardly ever think about. Luckily things seem to work most of the time - making it all the more clunky to work things out when problems result. With that said, some of these latter points may border on the verge of being ridiculous. But don't underestimate "the resident evil in all things computing".

        这篇关于尝试创建“uc.micro"时，windows 中的设置过程失败访问被拒绝.文件夹的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！