adhesive.dll!CreateComponent (0x220ce65)

What is the issue you’re having?

adhesive.dll crash when starting FiveM, goes to the menu for a second and then crashes with the message above.

What have you tried already to fix the issue?

Updated to Windows 11, deleted Cache, used RevoUninstaller to delete FiveM (3x), Reinstalled FiveM (3x), verified integrity of game files (2x), edited CitizenFX.ini to force update FiveM (did canary and beta), updated GPU drivers, got another adhesive.dll file and replaced, and checked firewall/antivirus and whitelisted FiveM.

What server did you get this issue on?

can’t even get to the server list

Error screenshot(s)



CfxCrashDump_2025_03_20_20_12_11.zip (1.19 MB)

Windows version

Windows 11 23H2 22631.5039

System specifications

AMD Ryzen 7 7700X 8-Core Processor
64GB DDR5
RTX 3070 TI Super
1TB Boot Drive Crucial T700

Antivirus software

Windows Defender

CitizenFX crash zip file (‘Save information’ on a crash)

CfxCrashDump_2025_03_20_20_12_11.zip (1.19 MB)

Hello, this is a friendly reminder because this is your first time creating a topic (or it has been a while since your last topic) in this category.

Please note that most of the support is provided by the Cfx.re community on a voluntary basis. We ask you to be patient; there is no guarantee we have a solution to your problem(s). To avoid unnecessary/duplicate topics, please browse the forums before creating a topic.

To improve your chances of your issue(s) being solved, please provide as much information as possible about the issue(s) you are having. Also —whenever possible— please use the template given to you when creating a topic.

Thanks for keeping these forums tidy!
:mascot:

There is a fix released earlier today,
edit your CitizenFX.ini and add the following line UpdateChannel=canary it should work

I can try again in about an hour, but I believe I tried this earlier and got the same error.

can confirm, did not work.

It seems to be a fivem error, I also have this error, apparently about some windows 11 update

I doubt it’s related to Windows; I originally had this error on Windows 10 and tried updating to Windows 11 and am having the same error.