This is the reason you should never attempt to run runtimebroker.exe. A security risk, no matter how tiny, is a security risk.
In the first paragraph, it states “We have no idea why they’re doing this, but we can’t see their problem.” Which is why we decided to run it in script instead.
A couple of things: 1) You don’t need to run it in batch (which we’re not doing) because you can’t run it in a shell in either case. 2) The second part of the statement can mean either “It’s a script that runs when the executable is run” or “It’s a script that runs when the executable is run” depending on which part you read. You can’t run it in a shell either, so you have to run it in script.
To run the event, we have to look at the value of the event id. This is a little bit tricky because it doesn’t seem to be a hexadecimal number, but we need a hexadecimal number to read the value of. Looking at the value of the event id, the most likely cause is because it’s on the list of events scheduled to run at the runtimebroker.exe process. For what it’s worth, the event id is 1074.
That’s the reason for the event id. 1074 is a number from 0x0 to 0xFFFFFFFF. This is the maximum allowed by the Windows Runtime. So this is the number of processes running at the runtimebroker.exe. This is the process id for the runtimebroker.exe. This is the process id that is in the list of processes that the runtimebroker.exe is scheduled to run.
I’ve been running the runtimebroker.exe on a number of occasions without incident, always when I have the time. But I’ve never done anything with the eventid 1074, and a couple of times I’ve seen it pop up in the logs, but not enough to worry about.
It’s a number that has been around for a long time. A number that is used by the Windows Debugger. A number that is used by the Windows Script Host and by the Windows Task Manager. A number that is used by the Windows Performance Monitor.
The reason is because my system is being used by a bunch of people who are not on the same server at the same time (which is fine, I guess). When you use the right program for the right task, it’s the right program for the right task.
The runtime broker is actually a Windows service that allows programs to bind to the same registry key with the same name as the program. This allows the runtime broker to load the program and allow it to execute on another computer without the need for the program to be written specifically for the runtime broker. This allows two computers to bind to the same program which is great for game scripts.
The problem is that the runtime broker is also called runtimebinder.exe, which is a part of Visual Studio. If you’re using Visual Studio, then you have to use the correct runtime broker to get your game to run. For instance, the runtime broker will not load a game for you if Visual Studio is not already loaded.