New: DiskMon (Feb 02, 2023), Platform 24.0 (Jan 30, 2023)
450+ real apps (49GB), 1 billion downloads, Please donate.
This morning I DL Libreoffice 5.4 from portable apps but I cannot open program.
Please suggest me.
Upon launching LibreOffice Portable:
LibreOffice has stopped working - part of the message:
Problem Event Name: APPCRASH
Application Name: soffice.exe
Application Version: 22.214.171.124
Application Timestamp: 59783957
Fault Module Name: ntdll.dll
On Windows 8.1 64-bit.
after 5.4 update i cannot open Libreoffice
The same here but with other is better that alone.
Same for me (Win 10, newest creator build) this morning.
Someone has not been doing their release testing.
For a quick fix:
- go to http://download.documentfoundation.org/libreoffice/portable/5.3.4/
- download the 5.3.4 distribution you are using (a few vs all languages)
- install it manually over the crashing 5.4.0
- decline all future 5.4.0 updates suggested by the platform
If someone from the PA platform does read this:
Could you please disable the 5.4.0 update as long as this has not been fixed?
I've confirmed that this is an issue due to missing libraries. If you're missing the VC 2015 runtimes on your PC, LibreOffice will fail to start. LibreOffice compilation changed with 5.4.0 and I didn't notice the difference before packaging. I'm working on a fix. There's no need to post additional error messages or confirmations at this time.
Sometimes, the impossible can become possible, if you're awesome!
Please download the LO Portable 5.4.0 Rev 2 Dev Test 1 Patch (3.9MB) and apply it to your LibreOffice Portable 5.4.0 install. This will add the VC 2015 runtime libraries to your install which should allow it to work on machines that are missing these runtime libraries. Report back your results and we can get this pushed out soon.
(I'm surprised I just remembered my old login id, lol)
John, this patch enabled me to launch every app in the 5.4.0 LO suite. Mine was also previously not launching.
The patch fixed the issue. I'm now able to launch the app.
Thanks for the quick fix John, it's much appreciated.
Just reapplied the update (LO fails) and then the patch (LO works).
It's still a mystery to me why a VC 2015 application just silently vanishes when one of its vital components is missing. Windows used to have the ability to report missing DLLs and even missing entry points within a wrong versioned DLL as part of the appliction launch process. At what point in time was that "optimized out"? I did check the Windows event logs yesterday and didn't find any trace of what had just happened or indeed not happened.
Anyway, thanks again for the good work on the PA platform.
Thank for your help, I can use on my PC
PortableApps LibreOffice not the only program getting caught by this. See https://answers.microsoft.com/en-us/windows/forum/windows_10-update/miss... . You can discover the issue by trying to execute the program directly in the installed PortableApps path: LibreOfficePortable/App/libreoffice/program/s*.exe
And just so it is clear, a fix (other than the temp patch given above) that works for all applications, is to install the x86 -=AND=- x64 missing vcruntime140.dll which is part of the Microsoft Visual Studio C++ 2015 redistributable. See the link https://www.microsoft.com/en-us/download/details.aspx?id=52685 in the above referenced Answer for the installers. The x86 works for LibreOffice. The x64 is for other applications that likely need it. Note that this is simply placing the DLL in your folder and not doing a formal "install" that can be uninstalled. These are coming from Microsoft directly.
Added vc_redist.x86.exe and fixed application startup fix.
I think we've had enough people test the fix, is there any chance Rev 2 can be pushed out?
I built it and sent it to the publisher today. We have to wait for them to post it. It can take up to 2 weeks.
PortableApps.com Platform users will automatically receive the LibreOffice Portable 5.4.0 Rev 2 patch on the next update check. I'll be releasing the full Rev 2 installers as soon as LibreOffice posts them.
This is fixed in 5.4.0 Rev 2 which has been posted by The Document Foundation. Platform users should have already received a small patch to upgrade.