Faq Solo fails with mclstart unable to initialize PLS Toolbox library error message
Solo fails with "mclstart: Unable to initialize PLS_toolbox library check for missing plstoolbox.ctf file" or requires re-installation each startup.
This error message is most likely due to Windows having invoked one of its user account control safety features which creates a copy of parts of applications in a folder called "virtualstore". This works for some applications but not all. Applications that rely on relative folder paths (as does Solo's underlying library technology) will sometimes fail.
To resolve the issue:
- Go to the Start Menu and type the following in the "Start Search" box:
%userprofile%\AppData\local\VirtualStoreand press Enter to open the folder.
- In the VirtualStore folder, navigate to the "Program Files" directory and from there to the "EVRI" folder. Delete the entire EVRI folder. (Note: if you are running a 32-bit version of Solo in 64-bit Windows, you will need to locate the "Program Files (x86)" folder and delete the EVRI folder there)
- ONCE: run Solo as administrator (right-click the shortcut and say "run as administrator")
This should resolve any issues with starting. If it doesn't we've had a user report that the following steps solved the problem:
- Search where the plstoolbox.crf file is located. In my case it was in : C:\Program Files\EVRI\Solo\application\runtime\win64
- In the same folder right click the "extractCTF64.exe" file and click on run as administrator.
- It comes up with several error, saying that some .dll files are missing (e.g. ctfarchiver.dll, etc)
- Locate the folder that contains the missing files (it's usually one folder that contains them).
- Copy paste ALL the files from the folder (step 4) into the folder from step 1.
- Go to C:\Program Files\EVRI\Solo, Solo file and click run as admin again.
Still having problems? Please contact our helpdesk at firstname.lastname@example.org