# FMOD Studio 2.02 won't start in Jenkins job **URL:** \ **Category:** FMOD Studio\ **Tags:** windows\ **Created:** [March 16, 2023, 3:45pm UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978 "2023-03-16T15:45:49Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![pzn](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@pzn](https://qa.fmod.com/u/pzn)\ **Post date:** [March 16, 2023, 3:45pm UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978/1 "2023-03-16T15:45:49Z")
Hello! I’m trying to build fmod banks in a jenkins job. I am using this command: ```auto fmodstudiocl.exe -build project.fspro ``` It used to work when I tested it some time ago, but now it freezes. If I try to start Studio in an RDP session (remote host) it shows the error “loadlibrary failed with error 87 the parameter is incorrect”. FMOD Studio version 2.02.09. Tried the latest and several older versions. 2.0.22 works out of everything I’ve tried. I’m assuming this issue is related to Qt. I did a dumpbin /depends for fmodstudiocl.exe and it is linked to fmodstudioui.dll which is linked to Qt libraries. I tried workarounds for Qt like disabling WDDM driver for RDP in Group Policies and updating graphics driver but it didn helped. The Jenkins machine is running Windows 10 2H22 19045.2728 with automatic updates enabled. ---
**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\ **Post date:** [March 20, 2023, 1:50am UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978/2 "2023-03-20T01:50:28Z")
Hi, Unfortunately, I haven’t been able to reproduce your issues. Is there anything particularly non-standard about how you’ve installed Studio on your Jenkins machine? Are you able to run the same command via RDP yourself, and on your local machine, without issue? As for the “LoadLibrary failed with error 87” issue, if possible, can I get you to provide some more info on your graphics hardware and graphics drivers version? Since you’ve already updated your graphics drivers to no effect, I can’t offer much advice there besides potentially performing a clean reinstall of them, but it’s strange that they would be causing issues - one of our developers has informed me that while there are Qt libs being used in the command line version of Studio, the GUI/GFX related stuff isn’t used. ---
**Author:** ![pzn](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@pzn](https://qa.fmod.com/u/pzn)\ **Post date:** [March 20, 2023, 11:23am UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978/3 "2023-03-20T11:23:20Z")
The FMOD Studio is installed as usual (“next”-“next”-…-“finish”). The same command running via RDP on the Jenkins machine produced the error 87. I can run it on my machine no problem. The graphics card is Radeon HD 2600XT and the driver version is 15.200.1062.1004. I never worked with Qt myself, but I think the GUI/GFX is somehow intialized even when not called directly from an app. Here is the stack of fmodstudiocl.exe: ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/7/73ddd4e5576eebe6eea8b1777f962884267b9fed.png) The process dump was made when the “error 87” window appeared. Looking at that stack I decided to try to change the graphics driver to “Standard VGA Graphics Adapter” and it worked! Mannually changed the driver to AMD again and it still works. So your advice to reinstall the driver worked, thanks! ---
**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\ **Post date:** [March 20, 2023, 9:32pm UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978/4 "2023-03-20T21:32:53Z")
No problem, happy to see you’ve resolved the issue! ---
**Author:** ![korbinian](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/korbinian/32/8857_2.png) [@korbinian](https://qa.fmod.com/u/korbinian)\ **Post date:** [August 1, 2025, 9:22am UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978/5 "2025-08-01T09:22:51Z")
This is BTW still happening, also here with a rather old Radeon card – but ideally you could find a way to avoid initializing the entire Qt stack in the command line tool? ---
**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\ **Post date:** [August 4, 2025, 6:10am UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978/6 "2025-08-04T06:10:18Z")
Thanks for letting us know. I’ve passed your suggestion along to the development team for consideration. ---
**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\ **Post date:** [August 22, 2025, 4:06am UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978/7 "2025-08-22T04:06:19Z")
Just to follow up on this, it should be possible to run fmodstudiocl without the graphics stack by using the correct Qt lib, and running the executable with the command line argument `-platform minimal`. The lib needed isn’t shipped with Studio at the moment, but I’d be happy to upload it to your [FMOD user profile](https://www.fmod.com/profile#uploads)[](https://www.fmod.com/profile)for you to test on your end and confirm that it works for you - just let me know what version of FMOD Studio you’re using! ---
**Author:** ![korbinian](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/korbinian/32/8857_2.png) [@korbinian](https://qa.fmod.com/u/korbinian)\ **Post date:** [August 26, 2025, 7:23am UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978/8 "2025-08-26T07:23:10Z")
Oh, that would be great! Our fmodstudiocl currently has version 2.3.8! ---
**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\ **Post date:** [August 27, 2025, 3:17am UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978/9 "2025-08-27T03:17:32Z")
qminimal.dll for Studio 2.03 has been uploaded to your [user profile](https://www.fmod.com/profile#uploads). To run fmodstudiocl.exe without the graphics stack, place it in the `./platforms` folder in your FMOD Studio install directory, and specify the `minimal` platform like so: ```auto fmodstudiocl.exe -platform minimal ``` Give that a shot and let me know how it goes. ---
**Author:** ![korbinian](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/korbinian/32/8857_2.png) [@korbinian](https://qa.fmod.com/u/korbinian)\ **Post date:** [September 1, 2025, 1:05pm UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978/10 "2025-09-01T13:05:49Z")
Ok, wonderful, it works now on a machine that previously had that problem. This makes it easier to keep old hardware alive as build or test machines. 😉 Thank you! Three things remaining: - I get the error message “This plugin does not support createPlatformOpenGLContext!” when I use the minimal platform - The minimal platform should be the default for everyone. Because why not? I’m sure it’s doing less work. - In an ideal world, the whole Qt stack shouldn’t be needed at all, in a command line tool. I’m guessing this isn’t trivial, so maybe more of a long term goal? ---
**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\ **Post date:** [September 3, 2025, 12:00am UTC](https://qa.fmod.com/t/fmod-studio-2-02-wont-start-in-jenkins-job/19978/11 "2025-09-03T00:00:26Z")
No problem, happy to hear > [@korbinian](#): > > I get the error message “This plugin does not support createPlatformOpenGLContext!” when I use the minimal platform Just to be clear, does this interfere with any expected functionality for you? Or does it seem to be benign? > [@korbinian](#): > > - The minimal platform should be the default for everyone. Because why not? I’m sure it’s doing less work. > - In an ideal world, the whole Qt stack shouldn’t be needed at all, in a command line tool. I’m guessing this isn’t trivial, so maybe more of a long term goal? I’ll pass both of these points on to the development team.