Windows中的设置过程在尝试创建"uc.micro"时无法拒绝访问.文件夹 [英] 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 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节以获取信息:

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).
        • 我已经看到几个安装程序，它们要求通过Internet聊天，但在无法进行安装时失败了.
        • 您正在安装具有 Unicode名称(日语，韩语，中文，阿拉伯语等)的文件夹，并且由于安装程序中的错误，安装程序无法正确完成.
        • Windows搜索是否正在运行并导致锁或错误的问题? (可笑的是，但是让我们沉迷于这种疑问的情绪).
        • 我猜想各种版本控制系统可以在文件系统中维护意外的锁定. Internet文件共享解决方案或网络服务器(?)也可以.
        • 我认为NT特权的自定义配置可能会导致安装程序中的某些操作锁定并无法完成.此处第13节中的一些信息:
        • 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".

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