Telephone (US) +1 650-900-2039
Telephone (UK) +44 203 870 3205

"Error! Something went wrong" in LABS instrument

Last updated:

If you get this message when loading up a LABS instrument



1. Close your DAW

2. Launch the Spitfire Audio App and login

3. Find the instrument in question by searching in the top right hand corner

4. Click on the instrument artwork

5. Click "REPAIR" in the bottom right and follow the instructions on screen

6. Wait while the Spitfire Audio App re-downloads some content

7. Once done, launch your DAW again and you should be good to go!

Have more questions? Submit a request


  • Avatar
    Stephane Horeczko

    Sorry, this thing isn't working at all. 5 repairs and reinstallations on my PC running Windows 7 Pro with Cubase 9.5 and it is still showing the same error message 'Let's Fix It'. I give up, sorry guys!
    It's not possible to release something with many bugs like this. I'm very disappointed.
    A Spifire Audio library owner.

    Edited by Stephane Horeczko
  • Avatar
    Elliot Woodward

    I'm also getting issues. Windows 10 Home user with Pro Tools 11. Tried multiple times to repair but and when I open it up in Pro Tools it promps me with the 'Let's fix it' popup.

  • Avatar
    Bart In -t Veld

    How can Labs work in Cubase, which only accepts 64-bit plugins? What version of Cubase is used in the demo video (where it does load)? And will there be a 64-bit version?

  • Avatar
    sebastien james

    Hello, how to really fix it !
    when your application wants to get the location of the Labs folder, it's not the location of this folder but the location "inside" this folder !


  • Avatar
    andrew Croop

    I'm no programmer, but seems the issue is the path starts using forward slash halfway through the directories:

    [31 May 2018 14:05:29.093] (tid:0000000000001a48) Labs : failed to load patch : C:/Users/Audio/Spitfire/Spitfire Audio - LABS/Patches\LABS Soft Piano\v1.0.2\LABS_Soft_Piano.zmulti
    [31 May 2018 14:05:29.102] (tid:0000000000001a48) Labs : failed to load patch : C:/Users/Audio/Spitfire/Spitfire Audio - LABS/Patches\LABS Strings\v1.0.2\LABS_Strings_Ensemble.zmulti
    [31 May 2018 14:05:29.108] (tid:0000000000001a48) Labs : failed to load patch : C:/Users/Audio/Spitfire/Spitfire Audio - LABS/Patches\LABS Strings\v1.0.2\LABS_Strings_Long_Ensemble.zmulti
    [31 May 2018 14:05:29.116] (tid:0000000000001a48) Labs : failed to load patch : C:/Users/Audio/Spitfire/Spitfire Audio - LABS/Patches\LABS Strings\v1.0.2\LABS_Strings_Short_Ensemble.zmulti
    [31 May 2018 14:05:29.121] (tid:0000000000001a48) Labs : failed to load preset : C:/Users/Audio/Spitfire/Spitfire Audio - LABS/Presets\LABS Soft Piano\v1.0.2\LABS_Soft_Piano.zpreset
    [31 May 2018 14:05:29.125] (tid:0000000000001a48) Labs : failed to load preset : C:/Users/Audio/Spitfire/Spitfire Audio - LABS/Presets\LABS Strings\v1.0.2\LABS_STRINGS_ENSEMBLE.zpreset
    [31 May 2018 14:05:29.129] (tid:0000000000001a48) Labs : failed to load preset : C:/Users/Audio/Spitfire/Spitfire Audio - LABS/Presets\LABS Strings\v1.0.2\LABS_STRINGS_LONG.zpreset
    [31 May 2018 14:05:29.135] (tid:0000000000001a48) Labs : failed to load preset : C:/Users/Audio/Spitfire/Spitfire Audio - LABS/Presets\LABS Strings\v1.0.2\LABS_STRINGS_SHORT.zpreset
    [31 May 2018 14:05:29.138] (tid:0000000000001a48) Labs : preset and patch parsing took 0.048 seconds

  • Avatar
    Kevin Harris

    OS X Sierra and Ableton Live 10. Downloaded, installed, repaired, etc. Still doesn't work. My first foray into Spitfire software: disappointing. I shouldn't have to fiddle with library paths manually.

  • Avatar
    yann cornet

    Also on Win 10, and unable to load the plugin.

    i discovered in the log that even if I choose another path, all elements will be placed in the defaults.
    For example :
    unzipping D:/Musique/VST64/Spitfire Audio - LABS/876592.lm to C:/Program Files/VstPlugins
    2018-05-31 19:24:28.1187038 [1444] C:/Program Files/VstPlugins/LABS (64 Bit).dll

    So, as my VST folder is under D:\VST64, there was no chance I could get it to work.

    I had to cut-paste the LABS (64 Bit).dll in my own folder, but as I had previously uninstalled the Labs, there was no way to download it again.

    Then I downloaded the Piano, and it was all right.

    So at the moment I have a Piano working, and absent Strings - the Repair only re-downloads 80MB or so, which is not the whole of the samples.

    @Spitfire Audio, I think we have 2 issues :
    - to let the users know they have to move the required dll from the default location ( or better, upgrade the installer with a path to choose for the VST/AAX/etc. )
    - After uninstalling then reinstalling, then there will be no more download of the instrument that has already been donwnloaded.

    Hope it helps.

    PS : I checked the piano sound in Live... outstanding !
    Thank you very much indeed for this tool.

    Edited by yann cornet
  • Avatar
    andrei cristea

    Here's how I fixed mine, maybe it will help someone else:

    My paths were all messed up, along with a sample entry missing.

    Locate in: C:\Users\YourUserName\AppData\Roaming\Spitfire Audio\Settings

    and make sure there are at least two entries per category:


    "Labs": {
    "samples": [
    "D:/AudioShelf/Library/Spitfire/Spitfire Audio - LABS/Samples"
    "patches": [
    "D:/AudioShelf/Library/Spitfire/Spitfire Audio - LABS/Patches"
    "presets": [
    "D:/AudioShelf/Library/Spitfire/Spitfire Audio - LABS/Presets"

    This is how it was before, created by the Spitfire install:

    "Labs": {
    "samples": [
    "patches": [
    "D:\/AudioShelf\/Library\/Spitfire\/Spitfire Audio - LABS\/Patches"
    "presets": [
    "D:\/AudioShelf\/Library\/Spitfire\/Spitfire Audio - LABS\/Presets"

    Also I had problems locating the VST DLL because it got installed in an old location in ProgramFiles. (It might be in C:\Program Files\Steinberg\VstPlugins)

    If you'd like to change it so it points to your custom VST Folder, then open regedit, go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\VST and change VSTPluginsPath string (ex, D:\CustomVSTFolder).
    If it's missing, you can create the entry manually (this is what I did)
    This path is read by the Spitfire installer.

    Hope this helps!

    Edited by andrei cristea
  • Avatar
    Mike Mathison

    I'm on Windows 10 - but I do *not* run as an admin user.

    The installer (the Spitfire Audio app) has to run under an admin login though (as do most installers) and it is putting a file (called "") in a path for the *admin* user at:

    "[System Drive]:\Users\[Admin User Name]\AppData\Roaming\Spitfire Audio\Settings"

    but for the plugin to see this file when it is running (in the DAW under my normal user account) the file needs to be at:

    "[System Drive]:\Users\[My User Name]\AppData\Roaming\Spitfire Audio\Settings"

    I copied the file across - and now it works.

    I have a sordid history in software development, and I'm thinking this (the problem I was having anyway) could be a case of the 'not all users run as admin' problem?

    Edited by Mike Mathison
  • Avatar
    Denis Shadrin

    andrei cristea - thank you, I tried your corrections, but still got path errors in Labs log in VEPro 6.
    Win 10 x64.

    Vienna Ensemble Pro 6 VST - no way to use this libraries.

    Cubase 9.5 VST3 - found samples and patches after corrections in

    Edited by Denis Shadrin
  • Avatar
    Lukas Prochnow

    First of all: yes, this works. But obviously it has some problems.
    I'm no progammer either, but for the most the comment of @andrei cristea will work.

    But I had another problem which I would like to share with you, in case someone else is expecting it.
    First I installed it in my 'main VST Folder' (which led to the problem Andrei is talking about) so I re-installed it, but this time I didn't change the default directory, so I do not had to change the properties in '.../Spitfire/Settings'.
    But the download client didn't download the 'samples' for 'LABS - Strings' (samples of LABS - Piano were fine 'though) I tried to 'repair it' but this dont helped at all, so here is what I've done:
    - Deinstall the Library
    - Create or choose a Folder that's located at your desktop
    - Install the Library {into the desktop folder} (pay attention that it's installing right and it does not miss any data)
    > If you see any '.lm' or '.part' data then it propably had problems to install it -> re-install 'till it finally works <
    - Move the folders to your prefered directory
    - Make sure, the actual folder is matching with what's written in '.../Spitfire/Settings'.
    - Done!.. at least this worked for me ;)

    Finally, I want to thank Spitfire for this awesome (free) release!
    And aswell, I want to remind somebody that this is completely free - no one payed a single dime for it, so in my humble opinion, be more grate- and thankful - things go wrong and that's only human (...or mechanical? :D)


    a huge fanboy of Spitfire Audio.

  • Avatar
    Takahiro Eguchi

    I am in a state that only strings samples are not installed. I am enjoying softpiano, thank you for a good sound.

  • Avatar
    Andrew Evans

    At least it's not just me!,
    I have a number of Spitfire libraries which work fine for me but Reaper doesn't see either of the Labs instruments. I'm running on Windows 8 64 bit. I can't find the dll file which most vst's incorporate although I can see the sample pool and the instrument files. Sorry Guys, It's not happening for me;(

  • Avatar
    Edoardo Nicodemo

    i did it and it works...thx Spitfire!

    PS: i don't think it's right to complain about something that is given for free, my opinion!

  • Avatar
    Juan Mogica

    Thank u very much for the libraries, sounds very good and the interface is beautiful, so precious, I love it.

    About this repair method, I installed the libraries in a directory, then I moved it to the final destination, my Spitfire Strings folder, so I had to to the repair thing...

    Well, I think we should be able to do it without connecting to the internet, just a location prompt and ready to go...easier and friendly. Like kontakt when you move the library, asks to locate the folder and that's it...



    Edited by Juan Mogica
  • Avatar
    John Braner

    The app is trying to be too clever and "idiot proof".
    Just let us install the instruments, and then let us install the VST plugin (wherever we want it).
    Then when we run the VST instrument - let us point it to where the instruments are.

    Edited by John Braner
  • Avatar
    Marco Iannello

    Instead of clicking Repair as suggested, I clicked on the cog next to it and selected Locate. Then, I navigated to the "Spitfire Audio - LABS" folder (the one with the Patches, Presets, and Samples subfolders), and clicked the Locate button. Problem solved

  • Avatar
    Elliot Woodward

    I just did what Marco Iannello did to fix the 'Let's fix it' issue where the sampler can't find the instrument.

    To reiterate; Opened up the Spitfire Audio plugin, selected the instruments, bottom right is a little cog. Hit it and locate it to where your folder is for the plugins. It should be relocated to the 'Spitfire Audio - LABS' folder. Don't specifically try and locate it to the individual patches ect. Just the whole folder.

    Boom. Samples work and they're lush. Good luck to anyone else. Heads up again to Marco Iannello! Woo!

  • Avatar
    Marco Iannello

    Thank you, Elliot. Unfortunately, after closing my Cubase session and re-opening it, the "Let's fix it!" dialogue presented itself again. Relocating did not work, no matter how many times I tried. Hope you had better luck, Elliot! Also, one should not need to be connected to the Internet to be able to access the Locate functionality, really, as somebody already pointed out

  • Avatar
    Raimund Hepp

    O.k., this thing doesn't work!
    Yes, this is free so I do not have a right to complain... but if this is and experiment for upcoming products and a taste of what spitfire products might become in future, developing their own player... then: goodbye Spitfire.
    I like the sound of their libraries a  lot, and that decission would hurt, but I'm not willing to put up with another sampleplayer plugin that is a pain. Kontakt works perfectly fine.

    I have a degree in math and I am a programmer, but when I want to make music I don't want to deal with procedures like andrei cristea described...
    Again, this is free so I do not have a right to complain... but I hope there are no plans to bring this "thing" to regulary spitfire libraries...

    Edited by Raimund Hepp
  • Avatar
    Greg Middaugh

    I CANNOT seem to get the LABS instruments to show up in DP 9. Are they not compatible with it?

  • Avatar
    Raul Yebra

    The solution in my case was to repair the LABS instruments installed (strings and piano) and start cubase again.
    Thanks for something awesome (and free!) to play with!

  • Avatar
    Najib Husein

    Try To uninstalled the app and re-install, so it works...

  • Avatar
    Lionel Schmitt

    This folder is empty for me. Is it supposed to be empty?

    Spitfire Audio - LABS\Patches\LABS Strings\v1.0.2

    No matter how often I reinstall it - I dont even see "samples" and "presets" folders as suggested here... all strange... strange stuff.

  • Avatar
    james russell

    Hi guys, I'm having a few installation issues with LABS (Windows 10, Live 9.7)

    1. Problem: When installing LABS, the VST, a 32-bit .dll, is automatically written to the steinberg/vstplugins folder (I use a different folder and a 64-bit DAW).
    1. Fix: maybe give the user a 64-bit VST and the option to install it elsewhere.

    2.Problem: when installing the samples, presets and patches, this happens:
    "Labs": {
    "samples": [
    "E:\/Audio\/Spitfire Audio - LABS\/Samples"
    "patches": [
    "E:\/Audio\/Spitfire Audio - LABS\/Patches"
    "presets": [
    "E:\/Audio\/Spitfire Audio - LABS\/Presets"
    2. Fix: something in the installer is messing up \ and / on Windows machines.

    3. Problem: after manually repairing the file and bridging the VST, the player launches OK, it responds visually to MIDI input and I'm able to switch between Soft Piano and Strings, but they're both silent.

    3.Fix: haven't found it yet, I'll keep tinkering.

    Overall, there's a few glitches preventing the installation from running properly that need ironing out.



    Edit: removed everything and reinstalled, it's all better now. This time I got a 64bit dll and it all installed into the right places.

    Edited by james russell
  • Avatar
    carter james

    I have the exact same problem as james russell, here's part of the log:

    (tid:000016a0) Compressed read error while loading the cache for fileID 17978
    [2 Jun 2018 13:29:42.195] (tid:000016a0) Failed to load all of the cache requested for fileID 17978
    [2 Jun 2018 13:29:42.195] (tid:000016a0) Compressed read error while loading the cache for fileID 17965
    [2 Jun 2018 13:29:42.195] (tid:000016a0) Failed to load all of the cache requested for fileID 17965
    [2 Jun 2018 13:29:42.196] (tid:000016a0) Compressed read error while loading the cache for fileID 17932
    [2 Jun 2018 13:29:42.196] (tid:000016a0) Failed to load all of the cache requested for fileID 17932

    ... and it goes on and on with loads of other fileIDs

  • Avatar
    Marco Iannello

    I have been assuming that the messed-up file occurs in Windows only. Is anybody using a Mac experiencing any issue with this?
    I am a programmer myself, and working with folders always gives a bit of headache, based upon the programming language and editor being used. That said, one would normally assume that well-formed directory/folder paths on Windows should look something like this: E:\Audio\Spitfire Audio - LABS\Presets, that is, using the '\' as separator

  • Avatar
    Juan Mogica

    Hey Marco, I´m on Mac, High Sierra 10.13.5 and I'm not experiencing that issue. As I said days ago, I only had to reinstall the library via the annoying required internet connected app. I wish Spitfire find a way in the near future to do it without the on-line connection, only relocate the samples if we move the library to another location, the classic Kontakt way.

  • Avatar
    Marco Iannello

    At least you got it working, Juan, happy to hear that :) However, Widnows is usually a bit quirkier and requires a bit more effort. Last Thursday, Andrew Croop posted a bit of the error log file that shows how the paths start with a '/' and then continue on with a '\', instead. Unfortunately, changing the '/' to '\' gives a different error, that is, "Could not find any patch/preset to load", or something like that... I shall give it another try later, now I am just too knackered

  • Avatar
    Scott Mason

    I have tried everything from the Spitfire support team and everything that is mentioned here in the comments. I can not get it to work. Yes it is free and yes Spitfire are awesome but if this is how we are to receive LAB and/or other libraries, it needs to be sorted. Cheers.