View Issue Details

IDProjectCategoryView StatusLast Update
0030631RunnerWindowsPublic2021-07-12 14:38
ReporterDanAssigned ToDan 
PriorityMediumSeverityB - MajorReproducibility100%
Status ResolvedResolutionSuspended 
PlatformWindows VMOSWindows 10OS VersionPro x64
Product Version2.2.1 
Target Version2.3.1Fixed in Version 
Summary0030631: Windows: Corsair K55 RGB keyboard causes increasing delay starting the runner at the end of builds
DescriptionWe have a handful of reports that the Corsair K55 RGB keyboard causes an increasing delay starting the runner at the end of builds. The delay before the runner starts builds up over each project build, until it can be minutes between the output window saying the game is starting and the game actually appearing.

Simply unplugging the keyboard, waiting a second or two, and then plugging it back in has been confirmed to "reset" the issue. Rebooting the PC will do the same.
Steps To Reproduce1. Have one of these keyboards.
2. Build a project in GMS2, stop the game, build again, repeat.
3. Observe the delay between the output window saying the game is launching and the game actually launching starts to grow.
Additional Information
1.4 Found In
2.x Runtime Found In2.2.1.287
2.x Runtime Verified In



2019-03-19 14:02

Adminstrator   ~0063528

Going back in our tickets, we actually have a ticket from last August which I believe to be the same issue. In that one, the user's DXDiag contained a number of crashes in CorsairLink4.Service.exe, which I had Googled at the time and found a number of irate threads about this service causing CPU drains and other instability problems for a variety of other software programs.

For anyone with this issue now, please see if you have the same crash messages for CorsairLink4.Service.exe in a DXDiag report or Windows Event Viewer.

This may not be fixable by us.


2019-03-19 14:14

Adminstrator   ~0063529

One of our new tickets has a Corsair Service crash in it also:

+++ WER4 +++:
Fault bucket 1296645125711721986, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Corsair.Service.exe
P3: 5c18ea7c
P4: System.Management
P5: 4.7.3056.0
P6: 5a8e5a11
P7: 8a
P8: 51


2019-11-12 11:53

Adminstrator   ~0065101

Last edited: 2019-11-12 12:08

View 2 revisions

IDE v2.2.4.474 Runtime v2.2.4.374

Appeared to reproduce yesterday by simply using the keyboard for a couple of hours and running projects. Didn't need to install any drivers/software manually, but the keyboard will install its own driver via USB after a short delay. I did not do anything with setting up key macros or customising the keyboard, etc.

I didn't get the Corsair service crash in Windows Events, but I did get a few "Application Hang"s saying the runner had issues with AppHangXProcB1 (.wer attached below)

Looks like the runner gains a child process, which you can see in Task Manager - "Capability Access Manager Service".

Trying to test gamepads when this issue was going on made the runner hang when connecting/disconnecting any pad and made getting your async events very unreliable.


2019-11-12 12:08


Report.wer (16,862 bytes)


2020-09-25 13:23

Adminstrator   ~0065649 is exactly the same as above, but a K63 model.


2021-05-10 09:15

Adminstrator   ~0065835

We do now have a customer report that installing Corsair's optional iCue software appears to fix the issue - the customer had not installed the update that long before letting us know, but initial signs are good.

The iCue software will apparently check your firmware the first time you run it, but if no issues are found, force a firmware update yourself, and this then seems to stop the issue. (After that, you can close and stop iCue from starting up with Windows, and the fix should stay in place.)


2021-07-12 14:37

Developer   ~0066121

Issue unresolved - still happens in recent build, moved over to current database to be fixed


2021-07-12 14:38

Developer   ~0066122

Moved over to current bug DB to be fixed