成功运行几个月后，无法在MSVC开发人员控制台中运行CL.EXE
这真的很奇怪。这就是发生的事情：
我一直在使用X86和X64 MSVC开发人员控制台，具有管理员特权）几个月而没有任何问题。我只使用cl.exe程序来编译示例程序，例如：
cl 1_19_5_float.c /Fa1_19_5_float.asm /MD /Od /arch:IA32
15分钟前，我进行了一些编译，一切仍然很好。我离开了5分钟，没有人碰到我的计算机，两个控制台都保持打开状态。突然cl.exe无法正常工作。每次我运行命令时，它都会告诉我“此应用程序无法在您的PC上运行”，并在控制台中显示“访问权限”。
有什么办法可以追踪问题吗？我绝对不知道发生了什么。 I checked the cl.exe under C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\bin\Hostx86\x86< /code>和c：\ program Files（x86）\ Microsoft Visual Studio \ 2019 \ community \ vc \ tools \ msvc \ 14.29.30133 \ bin \ bin \ hostx64 \ x64 \ x64，两者都在那里。 tbh我只离开5分钟，可能出了什么问题？我什至检查了活动查看器，但没有任何可疑的注意力引起了我的注意。也没有Microsoft更新。
This is really weird. Here is what happened:
I have been using the X86 and X64 MSVC developer console )with Admin privilege) for a few months without any issue. I'm only using the cl.exe program to compile sample programs, such as:
cl 1_19_5_float.c /Fa1_19_5_float.asm /MD /Od /arch:IA32
15 minutes ago, I ran a few compiling and everything still worked fine. I left for 5 minutes, no one touched my computer and both consoles were kept open. Suddenly cl.exe failed to work. Every time I ran the command it kept telling me that "This app can't run on your PC", and showed "Access denied" in the console.
Is there any way to track the issue down? I absolutely have no idea what's going on. I checked the cl.exe under C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\bin\Hostx86\x86 and C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64 and both are still there. TBH I only left for 5 minutes, what could go wrong? I even checked Event Viewer but nothing suspicious caught my eye. There was no Microsoft Update either.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
好吧，我发现了什么问题。开发文件夹中有一个空的“ Cl.exe”和“ Cl”。我绝对有他们在这5分钟内进入的方式。它们可能是恶意软件的可能只是故障。某些命令以某种方式创建了它们。
OK I found what's wrong. There is an empty "cl.exe" and "cl" in the dev folder. I have absolutely how they got in in that 5 minutes. They might be malware more likely just glitches. Somehow, some commands created them.