New: r3dfox (July 15, 2025), Platform 30.0.4 (July 15, 2025)
1,100+ portable packages, 1.2 billion downloads
We are operating at a loss, please donate today
Might be a glitch somewhere. Just downloaded and installed apps> install new app the latest release LibreOffice 4.00.
Refuses to start from portableapps menu. and also refuses to start from individual executables in the LO directory within portableapps platform.
Best wishes,
Hugh
Please help support us by making a donation so we can keep bringing you awesome free software. We accept credit card, wire transfer, PayPal, cryptocurrency, and more.
If you recently donated, thank you!
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Do you see the LibreOffice splash screen, an error message, or nothing?
Are any or all of LibreOfficePortable.exe, soffice.bin and soffice.exe running in Windows Task Manager after trying to launch?
None of the executables will launch, no error, no splash screen...
Tried from command line too, no errors, just doesn't work
I'm running under Server 2012 64bit, did not check Win8 yet.
Maybe some missing .dll?? I opted for language removal during install.
Sergio
Please try running soffice.exe directly within the App\LibreOffice\bin folder. You're likely missing a required runtime on the local machine.
Sometimes, the impossible can become possible, if you're awesome!
I had the same problem -- when I tried running soffice.exe directly, I got this error message:
The program can't start because MSVCR100.dll is missing from your computer. Try reinstalling the program to fix this problem.
Next step -- download directly (from the PortableApps web page, not using the PortableApps launcher update/install features) and run the installer.
If the government wants us to respect the law, it should set a better example.
the program can't start because MSVCR100.dll is missing from your computer. Try reinstalling the program to fix this problem.
Now what? Hunt the web for a suitable dll?
edit: just seen the post above mine. I did actually download from the green button in the first instance and installed the paf as described in my first post.
edit again: I see run the paf executable directly. OK I'll try that.
Hugh
Next step -- download directly (from the PortableApps web page, not using the PortableApps launcher update/install features) and run the installer.
That didn't change anything for me.
isn't that a very common dll normally somewhere on our windows systems (mine is Windows 7)?
Did the previous versions of portable LO not make use of it? They all ran without errors except for blasted java but that is no longer an issue,
Hugh
I copied the missing MSCVP100.dll (note: not mscvr100) from another portableapp folder to this folder:
C:\portableapps\PortableApps\LibreOfficePortable\App\libreoffice\program
and now LO 4.0 bursts into life.
All the best,
Hugh
Following John's instructions, detected that two dll are needed:
MSVCP100.dll
MSVCR100.dll
I am using Windows 7 starter ed., SP-1, spanish.
LO, ver 4, worked.
Some add ons were inabilitated (they use java) and read that this version is less dependent of java.
To install the missing runtime, you can do it from here:
http://www.microsoft.com/en-us/download/details.aspx?id=5555
We *may* be able to include it directly depending on LibreOffice's compilation. I'm looking into it.
Sometimes, the impossible can become possible, if you're awesome!
You can find the missing DLL's on this site:
http://www.dll-files.com
Download the zip-files for both missing DLL's, unzip them en copy them to the directory mentioned above.
I have that runtime installed and it still didn't work. What I did was to copy the DLL's from another portable app into: LibreOfficePortable\App\libreoffice\program\ as suggested in a post above - this worked.
I can see both DLL's inside my c:\Windows\System32\ folder, only they have a different size than the DLL's I found inside another portable app. The DLL's inside c:\Windows\System32\ don't fix the LO problem. I suspect it might be because I have installed the 64 bit version of the runtime, and LO needs the 32 bits version of the DLL's to run?
Exactly the same for me
You're most welcome - glad it helped!
This is fixed in LibreOffice Portable 4.0.0.3. Platform users will automatically get a 1MB quick-install patch. Users without the platform can manually download it using the link in the first comment in the announcement.
https://portableapps.com/news/2013-02-09--libreoffice-portable-4.0.0.3-r...
Sometimes, the impossible can become possible, if you're awesome!
Stills fails here.
I'm running XP with SP3 on 32 bit.
Any ideas
Got it
vcllo.dll was missing, extracted it from installer.
I had do disable on access scan from Sophos. Seems like Sophos is blocking it.
I had antivirus troubles too, Panda Cloud AV detected smime3.dll as 'suspicious' (which I believe means it's a heuristic rather than signature detection) and deleted it. I assumed it was a false positive - just hope I'm right.
With our apps, it's always a false positive. At least it has been every time for the last 8 years.
Sometimes, the impossible can become possible, if you're awesome!
I went to launch LibreOffice today for the first time, which I do every day, and it simply refuses to launch at all. No splash screen, no anything popping up or running. I've reinstalled the app twice and it still isn't working. The only thing that's been installed since my last successful launch is an update for Windows Defender today. I'm running Win7 64.
This was the update,
Definition Update for Windows Defender - KB915597 (Definition 1.249.1034.0)
Installation date: 8/15/2017 11:16 AM
Your issue is unrelated to this topic: https://portableapps.com/node/56647
Sometimes, the impossible can become possible, if you're awesome!
I ran into the same problem with LibreOfficePortable not running. I fixed the issue by coping another copy of libxml2.dll to libreofficeportable\app\libreoffice\URE\bin
not sure why norton does the quarantine
Please report Norton's false positive issue to them. They need to fix the error in their definitions.
This is also completely unrelated to this bug.
Sometimes, the impossible can become possible, if you're awesome!