League Of Legends Install Process Already Running

[Amatista Sheeley]

Ive installed Riot's League of Legends and am trying to make it available to all users. On the administrator account on which I installed the game, it opens easily in about five seconds. On all the other accounts, the game won't open correctly. The first time I try to open it while watching Activity Monitor, the icon flashes for an instant, but the game doesn't open, nothing is in the dock, and nothing registers (that I can see) on Activity monitor. If I click it a second time, the icon appears but it hangs, and the message "Another instance of the launcher is already running. Do you want to terminate it?" with the options 'Cancel' and 'OK' available. If I cancel, the icon disappears instantly and it's over. If I click 'OK,' which I take to mean 'close this one and start another one,' the icon remains, hangs for about fifteen seconds, and everything quits.

League of Legends is a pretty good game and very popular. It works very well on Mac. I need a way for any user on my system to be able to use it, and I think it's important for Apple to help it work smoothly. Also, I *thought* I had upgraded to OS 10.9, but apparently that was all a sham (read:user error). I went ahead and upgraded to OS 10.9, but it's all the same story anyway, so hah.

I tried changing folder permission for all files and folders relevant to the application in Library, System, and other root level folders. Nothing shows up in Force Quit, Apple->Tab, or the Dock any time I (re-)start the application. I do manage to get some info by Sampling from the Console on a League of Legends (LoL) application called UserKernel, but I'm not sure what it's doing. I would appreciate anyone with the patience to give me a basic understanding of this output or where to go to find an example:

I'd suggest you boot to recovery mode to repair permissions, in the hope it is one you haven't changed, there is a real chance of breaking the system if you change permissions within /System - don't do it, Apple don't expect that at all.

For a while it was working. Then it reverted to the old behavior and will let one account access the application and the other can't. It doesn't seem to care if the account that installed it is an administrator or not. I understand that I could install two (3.5 GB) instances of the game, but that doesn't seem like a very Unix-y way to do things.

You are simply going to compound the problem by trying to run or install multiple copies of the game. The real issue may be because of the modified permissions or other things you have done to the OS.

To be honest you may be best backing up & reinstalling the OS. The default option should leave all your apps & user data in place & it should fix all the files that have altered permissions or other damage caused by your attempts to 'fix'.

I sometimes use Process Monitor for debugging software, and also play games online. Some of these games use BattlEye anti-cheat software, which refuses to allow the game to run after Process Monitor has been started on the system, showing this in the log:

Several other questions have answers about unloading drivers using net stop or sc stop, but the ProcMon driver isn't a service, so this doesn't work. I've also tried looking in Device Manager and enabling 'Show hidden devices', but none of the entries appear related to ProcMon. I can't delete the driver file, as it's not actually present on the filesystem; ProcMon stores the file in its executable and extracts it as needed.

Current versions of Process Monitor appear to remove the driver/service configuration from registry immediately after starting the driver. You can see this by monitoring ProcMon with itself. It is possible to manually re-add the service, with type 2 (kernel FS driver) and it will immediately show up as already running.

Additionally, PROCMON23 now registers itself as a filesystem minifilter driver through the Filter Manager (FltDrv). You can see it in the output of fltmc, but attempting to externally unload it also fails (possibly because the driver doesn't have the unload routine):

Since the "official" CLI tool is unable to remove the filter from FltMgr, and FltMgr itself is a 'critical' driver that cannot be restarted without reboot, it would seem that there's no way to unload PROCMON23 or PROCMON24.

But the most interesting part: After doing the above checks with procmon 3.40, I found that the latest version on the website is 3.50 (which uses a newer PROCMON24 driver). Upon starting the new version, I was informed that an older version of the driver was already on the system and that I should reboot.

In addition to an excellent answer by user1686 which concludes that there is no way to unload it, I'd like to add that normal reboot on Windows 10 does not help either, because Windows 10 nowadays persists some memory and reloads it upon boot up, so the driver ends up in memory even after reboot.

The problematic PROCMON23.SYS filter driver is installed by ProcMon when it isrun. If the fileC:\Windows\system32\Drivers\PROCMON23.SYSdoes not exist at the time, then ProcMon will write it.The PROCMON23.SYS file itself is included as a binary resource inside theexecutable of ProcMon.

Conclusion : PROCMON23.SYS and the later PROCMON24.SYS are badly programmed.The developer has not foreseen that anybody would ever wish to unload hisdriver and has not included the necessary routine in it.Therefore this driver cannot be unloaded.

I'm unable to run League of Legends on a guest account on my mac. Is there something I need to do to be able to do that? I've given all privileges I can give to the guest account in System Preferences.

This article is referring to a LoL folder on mac, -Mac-Administrator-Settings-and-File-Folder-Permissions , I don't know if they mean the app in the applications folder or something else but the app itself has permissions to read and write by everyone.

I am assuming you are getting the same error that I got when trying to launch the LoL client as a different user than who installed it. The error is something along the lines of: "You do not have permission to launch League of Legends" or "This application cannot be opened".

The above commands set file permissions using the CHMOD command on the "League of Legends.app" package and any files/folders below it (-R). The command allow everyone to read and write as well as open/execute the application (777).

Then open LoL, and give it a good minute to start up, and make sure not to touch anything else on the computer until it gets past the logo. If you've waited a minute and nothing has happened after the logo showing, open it again when it tells you another instance is already running, press yes to cancel the old instance and open a new instance.

I had the same problem. There are two different ways to solve this: 1.Way: You go to Finder>Applications>LeagueofLegends>rightclick>Informations>Rights>everyone>No rights. then the computer will ask for the admin password, and thats it.2.Way: You download LoL as a guest and, after starting this program, drag LoL to Applications and type in the admin password. But then the program will be deleted by logging out the guest account.You can choose ;)

Downloaded CS5.5 for Windows Trial edition. When the Adobe Download Assistant completed the download, it did not install the software, and I received the error message "Adobe Installer is already running."

Nothing else is running on this machine, as I shut down all programs and the Windows firewall. Went to the Adobe InDesign file on C: amd opened the file and clicked set-up and received the same message.

We encountered a similar problem. We tried stopping set-up.exe but this did not resolve the issue. We firstly checked that adobe reader and flash player were up to date, and not auto updating in the background. After some head scratching we discovered that the creative cloud update was trying to install and failed and was stuck on 2% with an error code 207. Once we cancelled the creative cloud update we were able to install without the message appearing again.

It's getting to be about that time, and I must once again extend to you our quadrennial anti-cheat greetings. I'm "mirageofpenguins," an anti-cheat artisan with lifetime 85 million bans served, and I'm manifesting today to talk to y'all about Vanguard.

You actually may've already suffered through our LoL anti-cheat literature in the past, and here is some of the recommended prerequisite reading. Feel free to skim through it, but this material is now known to the state of California to cause bone lengthening and will not be on this semester's midterm.

League of Legends is a fairly secure video game. The server simulates the entirety of the game state, and the client is really only responsible for making "requests" to it. Often referred to as an authoritative model, it essentially means that our server is the final arbiter of truth, and things like "sending spells on cooldown" should fail once we've added enough server validation. This is why we don't see as many exploits anymore, and instead, most cheaters resort to input automation, or more colloquially, "scripting."

Scripting developers create platforms that are essentially wrappers for the LoL client. They rebroadcast the game as an event stream and allow the end-user to create (or more likely, copy and paste) a selection of "scripts" that automate certain behaviors in response to these events. The end result is usually a frame-perfect Zeri kiting on what appears to be a near-lethal dose of caffeine or a god-touched Cassiopeia that, through the power of prayer, has been rendered untouchable by any skillshot. It's not fun to play against cheaters, and worse, once you know scripts are out there, it's hard not to suspect other players of using them.

Throughout 2023, the lovable rascals on our anti-cheat team have been sneaking detections into the LoL client that offer glimpses into the size of the scripting epidemic. These cheeky security maneuvers, also called "honeypots" or "spicy values," only work once, as any bans issued on them will be met with excess scrutiny, followed by their immediate discovery in cheat communities. We only have so many tricks up our sleeves, so this pattern is about as sustainable as bunker fuel. However, we now have access to mankind's greatest weapon: Statistics.

3a8082e126