I have tried both the framework-dependent and standalone versions. Neither runs. I tried both versions, before and after the 20 April 2025 update. Same result. The Advanced Launcher never appears. I have tried launching from Steam and double clicking the file. When I revert to the default launcher it runs fine.
Years ago this mod worked fine for me. It may have been on a different machine.
Hi, I had the same issue; I got this error: Faulting application name: BmLauncher.exe, version: 2.0.0.3, time stamp: 0x666c0000 Faulting module name: KERNELBASE.dll, version: 10.0.26100.4202, time stamp: 0xfc5b8f29 Exception code: 0xe0434352 Fault offset: 0x00000000000c85ea
The program struggles to read the config files it should have created. If your config folder is still empty, then your system is prohibiting the launcher from creating files. You need to unblock the application.
EDIT: Are you sure you deleted the correct config files? Specifically the ones in your Documents folder. It's weird that the launcher can initialize this far without files being present.
I am not sure if this is intended, but everytime I update NVIDIA Drivers to a new release the Ambient Oclussion goes off and I need to enable it again.
Not major issue, just I need to remember that every new driver that I install I need to run the launcher, enable admin rights and tick ambient oclusion on. Just making sure is not a bug.
Does the launcher have TexMod support? If so I can't find it, and it's getting annoying to have to use the TexMod launcher instead every time I want to use the Joker AK skin. I suppose I could if I didn't see a reason to use the AL anymore, but I'm just going through all my options first.
The legacy version has Texmod support, the current version doesn't. Texmod is generally considered obsolete and mods should be ported for TFC Installer.
I am having trouble running the game. the log says it cant find ambient occlusion and that hbao+ = false, along with higher privileges being denied. I'm not sure if its because of the launcher or not. I'll paste the full log if you need me to.
If you're trying to run the launcher with elevated permissions (as admin), you have to grant it permissions by clicking 'yes' when Windows prompts you. You don't need to run it as admin though, only when you are trying to enable hbao+.
How do I enable hbao+? the launcher doesnt open at all because its disabled, and i wasnt able to find it in any of the setting files. the launcher did not open even when i ran it as administrator, just immediately logged the error with the same issue as before.
Seems like the launcher isn't allowed to create or edit config files. This could be related to your AV/UAC settings or you might have manually set the config files to read-only in the past. That is something you have to check on your end. You can also try right-clicking the application, open up properties and select the checkbox to unblock the program.
what settings would i possibly have to change in the control panel? i just checked if they were read only, they were at first but i realized it was because i wasnt selecting the file (?) no clue what settings to change, I would appreciate if you told me which setting in control panel needs to be changed.
I have checked everything you said to,m as far as I know it should have the necessary permissions to change other files. would config files having perms cause problems?
I haven't told you to do anything in your control panel. Config files that you have edited and set to read-only in the past cause problems because the program can't overwrite files you made read-only. Either remove the read-only mark on all config files or delete them and let the launcher regenerate them.
will do, I will get back to you if it doesnt work. I will just try verifying iontegrity files if this doesn't work. I just realized I should have said this earlier, but I was getting a cloud unhandled exception before I installed the advanced launcher. as far as i know though, that was onedrive not being on or having to reinstall .net runtime 60
Verifying integrity won't actually do anything for your config files. You don't have to waste your time with that. Another thing you can do is try running the launcher, then open Event Viewer -> Windows Logs -> Application. Find the error in there and see what it says.
Love the launcher. But it would be even better if it let the user create separate secondary keybinds for the counter/aim gadget actions like you can with the original launcher.
Hey! Fresh PC (7900xtx, 9800x3d) and am having quite a few issues with this game. Just installed this mod, and when trying to launch the game, I get a general protection fault error, I will post the entire message below. Really wish I could get this game running but its seeming like a less and less likelihood of being able to :(
I have the same issue. Installed the game, ran it once and it ran fine. Copied the files from here into the Binaries folder and am getting the exact same error.
91 comments
Years ago this mod worked fine for me. It may have been on a different machine.
If that doesn't fix it try opening the launcher, then go to Event Viewer -> Windows Logs -> Application and post the error that pops up.
Faulting module name: KERNELBASE.dll, version: 10.0.26100.4202, time stamp: 0xfc5b8f29
Exception code: 0xe0434352
Fault offset: 0x00000000000c85ea
I don't provide support for outdated versions.
Try deleting the config files as I mentioned above and download the new version.
Edit: Downloaded the updated file and got this error on event viewer:
Fault bucket 2075954498561839808, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: BmLauncher.exe
P2: 2.1.0.4
P3: 67d40000
P4: KERNELBASE.dll
P5: 10.0.26100.4202
P6: fc5b8f29
P7: e0434352
P8: 00000000000c85ea
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e6faa105-5881-4870-8b7a-a50a8b60fc68.tmp.WERInternalMetadata.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_BmLauncher.exe_512f72935b22bf9d65eeeb457365cb1f78ce77b9_79779090_4620ef7a-ae32-413d-bca8-3bdcc4c333b8
Analysis symbol:
Rechecking for solution: 0
Report Id: 066eb993-d491-482f-be89-0da7e518d35f
Report Status: 268435456
Hashed bucket: fb754e4f8f4a74148ccf459e18a712c0
Cab Guid: 0
2025-06-17 10:45:32.0969|INFO|AsylumLauncher.Program|InitializeProgram - Starting logs at 10:45:32 on Tuesday, 17 June 2025.
2025-06-17 10:45:32.0997|INFO|AsylumLauncher.Program|InitializeProgram - Current application version: 2.1.0.4
2025-06-17 10:45:32.0997|INFO|AsylumLauncher.Program|InitializeProgram - Elevated Privileges: False
2025-06-17 10:45:32.1163|INFO|AsylumLauncher.Program|InitFonts - Necessary fonts installed.
2025-06-17 10:45:32.1758|DEBUG|AsylumLauncher.NvidiaHandler|Constructor - NVIDIA API initialized.
2025-06-17 10:45:32.3173|WARN|AsylumLauncher.NvidiaHandler|InitialSetHbaoPlus - Couldn't find ambient occlusion settings. Generating settings with default(0) values now.
2025-06-17 10:45:32.3352|DEBUG|AsylumLauncher.NvidiaHandler|InitialSetHbaoPlus - HBAO+ is currently False.
2025-06-17 10:45:32.3352|INFO|AsylumLauncher.NvidiaHandler|Constructor - NVIDIA profile fully processed.
2025-06-17 10:45:32.3352|INFO|AsylumLauncher.FileHandler|Constructor - Successfully initialized FileHandler.
2025-06-17 10:45:32.3511|INFO|AsylumLauncher.IniHandler|Constructor - Successfully initialized IniHandler.
2025-06-17 10:45:32.3511|INFO|AsylumLauncher.InputHandler|Constructor - Successfully initialized InputHandler.
2025-06-17 10:45:32.3511|INFO|AsylumLauncher.SystemHandler|Constructor - Successfully initialized SystemHandler.
2025-06-17 10:45:33.4148|INFO|AsylumLauncher.SystemHandler|InitializeCPU - Recognized CPU as 13th Gen Intel(R) Core(TM) i7-13700F with a base clock speed of 2.1GHz.
2025-06-17 10:45:33.4148|INFO|AsylumLauncher.SystemHandler|InitializeGPUValues - Recognized GPU as NVIDIA GeForce RTX 4070 with a total VRAM amount of 11GB.
2025-06-17 10:45:33.4148|DEBUG|AsylumLauncher.Resolution|GetResolutions - found a total of 15 available resolutions.
2025-06-17 10:45:33.4284|INFO|AsylumLauncher.IniReader|InitDisplay - Successfully initialized display settings.
2025-06-17 10:45:33.4284|INFO|AsylumLauncher.InputReader|Constructor - Successfully initialized InputReader.
If your config folder is still empty, then your system is prohibiting the launcher from creating files.
You need to unblock the application.
EDIT:
Are you sure you deleted the correct config files? Specifically the ones in your Documents folder. It's weird that the launcher can initialize this far without files being present.
I'll publish a fix in a week or two.
I've uploaded a new version.Not major issue, just I need to remember that every new driver that I install I need to run the launcher, enable admin rights and tick ambient oclusion on. Just making sure is not a bug.
Thanks!
You don't need to run it as admin though, only when you are trying to enable hbao+.
2025-04-11 11:10:40.6807|INFO|AsylumLauncher.Program|InitializeProgram - Current application version: 2.0.0.5
2025-04-11 11:10:40.6807|INFO|AsylumLauncher.Program|InitializeProgram - Elevated Privileges: False
2025-04-11 11:10:40.6975|INFO|AsylumLauncher.Program|InitFonts - Necessary fonts installed.
2025-04-11 11:10:40.8017|DEBUG|AsylumLauncher.NvidiaHandler|Constructor - NVIDIA API initialized.
2025-04-11 11:10:41.0831|WARN|AsylumLauncher.NvidiaHandler|InitialSetHbaoPlus - Couldn't find ambient occlusion settings. Generating settings with default(0) values now.
2025-04-11 11:10:42.2643|DEBUG|AsylumLauncher.NvidiaHandler|InitialSetHbaoPlus - HBAO+ is currently False.
2025-04-11 11:10:42.2643|INFO|AsylumLauncher.NvidiaHandler|Constructor - NVIDIA profile fully processed.
You can also try right-clicking the application, open up properties and select the checkbox to unblock the program.
Config files that you have edited and set to read-only in the past cause problems because the program can't overwrite files you made read-only. Either remove the read-only mark on all config files or delete them and let the launcher regenerate them.
Another thing you can do is try running the launcher, then open Event Viewer -> Windows Logs -> Application. Find the error in there and see what it says.
The message is: https://imgur.com/th85GTh
This does not look like a launcher issue.