ucos在pc上运行
If you’re reading this article, then you probably spotted the Runtime Broker process in your Task Manager window and wondered what it was–and maybe even why it spikes CPU usage sometimes. We’ve got the answer for you.
如果您正在阅读本文,那么您可能在“ 任务管理器”窗口中发现了Runtime Broker进程,并想知道它是什么,甚至可能为什么有时会导致CPU使用率飙升。 我们为您找到了答案。
This article is part of our ongoing series explaining various processes found in Task Manager, like svchost.exe, dwm.exe, ctfmon.exe, mDNSResponder.exe, conhost.exe, rundll32.exe, Adobe_Updater.exe, and many others. Don’t know what those services are? Better start reading!
本文是我们正在进行的系列文章的一部分,解释了在任务管理器中发现的各种过程,例如svchost.exe , dwm.exe , ctfmon.exe , mDNSResponder.exe , conhost.exe , rundll32.exe , Adobe_Updater.exe以及许多其他过程 。 不知道这些服务是什么? 最好开始阅读!
那是什么? (So What Is It?)
Runtime Broker is an official Microsoft core process that debuted in Windows 8 and continues in Windows 10. It is used to determine whether universal apps you got from the Windows Store–which were called Metro apps in Windows 8–are declaring all of their permissions, like being able to access your location or microphone. Though it runs in the background all the time, you will likely see its activity rise when you launch a universal app. You can think of it like a middleman hooking your universal apps with the trust and privacy settings you’ve configured.
Runtime Broker是Microsoft的官方核心程序,它在Windows 8中首次出现并在Windows 10中继续运行。它用于确定从Windows应用商店获得的通用应用程序(在Windows 8中称为Metro应用程序)是否在声明其所有权限,例如可以访问您的位置信息或麦克风。 尽管它始终在后台运行,但是启动通用应用程序时,您的活动可能会增加。 您可以将其想象为一个中间人,将您的通用应用程序与已配置的信任和隐私设置挂钩。
为什么要使用内存? (Why Is It Using Memory?)
When it’s not active, Runtime Broker maintains a very low memory profile, typically taking up around 20-40 MB. When you launch a universal app, you will likely see the memory usage rise to anywhere from 500-700 MB.
不活动时,Runtime Broker会维持非常低的内存配置文件,通常占用大约20-40 MB。 启动通用应用程序时,您可能会看到内存使用量从500-700 MB上升到任何地方。
Launching additional universal apps should not cause Runtime Broker to consume additional memory. And when you close all open universal apps, Runtime Broker’s memory usage should drop back down to the 20-40 MB range.
启动其他通用应用程序不应导致Runtime Broker占用更多内存。 而且,当您关闭所有打开的通用应用程序时,Runtime Broker的内存使用量应回落到20-40 MB范围。
为什么会增加CPU使用率? (Why Is It Spiking My CPU Usage?)
When its just running in the background, Runtime Broker usually consumes 0% of your CPU. When you launch a universal app, that usage should briefly rise to 25-30% and then settle back down. That’s normal behavior. If you notice that Runtime Broker is consistently consuming 30% or more of your CPU, showing higher than expected memory usage, or spiking the usage even when you don’t have a universal app running, there are a couple of potential explanations.
当它仅在后台运行时,Runtime Broker通常会占用您CPU的0%。 当您启动通用应用程序时,该使用率应短暂上升到25-30%,然后再回落。 这是正常现象。 如果您发现Runtime Broker持续消耗30%或更多的CPU资源,显示高于预期的内存使用率或者甚至在您没有运行通用应用程序的情况下提高使用率,则有两种可能的解释。
If you’ve recently upgraded to Windows 10, you may have noticed that Windows likes to show you the occasional tip via notifications. For whatever reason, this activity behaves like a universal app and engages the Runtime Broker process. You can fix this by turning off tips. Head to Settings > System > Notifications & Actions, and then turn off the “Get tips, tricks, and suggestions as you use Windows” option.
如果您最近升级到Windows 10,则可能已经注意到Windows喜欢偶尔通过通知向您显示提示。 无论出于何种原因,此活动的行为都类似于通用应用程序,并且会参与Runtime Broker流程。 您可以通过关闭提示来解决此问题。 转到“设置”>“系统”>“通知和操作”,然后关闭“使用Windows时获取提示,技巧和建议”选项。
It’s also possible that you have a misbehaving app that’s causing Runtime Broker to use more resources than it should. If that’s the case, you’ll have to narrow down the app that’s causing the problem. Make sure the app is updated to the latest version. If that doesn’t work, try uninstalling and reinstalling the app. And if that fails, make sure you let the developer know about the problem (and, if you don’t need it, uninstall it in the meantime).
您的应用程序行为异常也有可能导致Runtime Broker使用的资源过多。 在这种情况下,您必须缩小导致问题的应用程序的范围。 确保该应用程序已更新为最新版本。 如果这样不起作用,请尝试卸载并重新安装该应用程序。 如果失败了,请确保让开发人员知道该问题(如果不需要,请同时将其卸载)。
我可以禁用它吗? (Can I Disable It?)
No, you can’t disable Runtime Broker. And you shouldn’t anyway. It’s vital for protecting your security and privacy when running universal apps. It’s also very lightweight when it’s running properly, so there’s not much reason to disable it. If you think it’s misbehaving, you could always kill the Runtime Broker process by right-clicking it in Task Manager and then choosing End Task.
不,您不能禁用Runtime Broker。 而且你不应该这样。 这对于在运行通用应用程序时保护您的安全和隐私至关重要。 当它正常运行时,它也非常轻巧,因此没有太多理由要禁用它。 如果您认为它的行为不正常,则始终可以通过在“任务管理器”中右键单击它,然后选择“结束任务”来终止Runtime Broker进程。
After a few moments, Runtime Broker will launch again automatically. Just be warned that for the few moments until it relaunches, universal apps won’t be able to successfully access trust settings and may not run at all.
片刻之后,Runtime Broker将再次自动启动。 请注意,在重新启动之前的短时间内,通用应用将无法成功访问信任设置,并且可能根本无法运行。
这个过程可能是病毒吗? (Could This Process Be a Virus?)
The process itself is an official Windows component. While it’s possible that a virus has replaced the real Runtime Broker with an executable of its own, it’s very unlikely. We’ve seen no reports of viruses that hijack this process. If you’d like to be sure, you can check out Runtime Broker’s underlying file location. In Task Manager, right-click Runtime Broker and choose the “Open File Location” option.
该过程本身是Windows的正式组件。 尽管病毒可能用自己的可执行文件代替了真正的Runtime Broker,但这种可能性很小。 我们还没有关于劫持此过程的病毒的报告。 如果您想确定的话,可以签出Runtime Broker的基础文件位置。 在任务管理器中,右键单击Runtime Broker,然后选择“打开文件位置”选项。
If the file is stored in your Windows\System32 folder, then you can be fairly certain you are not dealing with a virus.
如果文件存储在Windows \ System32文件夹中,则可以确定您没有在处理病毒。
That said, if you still want a little more peace of mind, you can always scan for viruses using your preferred virus scanner. Better safe than sorry!
就是说,如果您仍想更加放心,则可以始终使用首选的病毒扫描程序来扫描病毒 。 安全胜过遗憾!
翻译自: https://www.howtogeek.com/268240/what-is-runtime-broker-and-why-is-it-running-on-my-pc/
ucos在pc上运行