On some computers, LibreOffice Portable 3.5.3 will mistakenly detect that the MS Visual C++ 2008 runtime is not installed when it actually is. We're looking into the exact cause at the moment. If you are affected, you can help us by providing us information on what operating system it's running on and searching your C: drive for the file msvcr90.dll and letting us know where it is installed. We already have a partial fix working, but this could help provide us with a complete one encompassing any edge cases.
Fix 2: Better detection
First, please try LibreOfficePortable.exe launcher fix 2. Download and replace your current launcher in the LibreOfficePortable directory. It has correct detection of an installed VC runtimes.
Workaround: Patched Launcher
After that, if you'd like to turn off the message, just download this this patched LibreOfficePortable.exe launcher. You can replace the existing one in your LibreOfficePortable directory. This patched launcher has VC runtime detection disabled so you don't have to worry about the message appearing every time you run it.
We'll have a fixed version up in the next few days. Thanks for your patience.
I am affected.
Windows 7 32-bit.
C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4940_none_50916076bcb9a742\msvcr90.dll
Also, after I clicked "No" on that messasage offering to install VC runtime, application did not start. LibreOfficeWriterPortable.exe process was running, I had to kill it, but I could not start new one, it was telling me that another instance is already trying to start.
What happens if you allow it to install? Does LibreOffice then work?
Sometimes, the impossible can become possible, if you're awesome!
I uninstalled LibreOffice, made sure that LibreOfficePortable directory is deleted, then installed it again, replaced LibreOfficePortable.exe with patched version, started LibreOffice Writer - nothing happened. In processes I see LibreOfficePortable.exe running and nothing else.
PS: LibreOffice 3.5.2 was working fine.
This is exactly what I am getting too - see my post at the end of this thread:
https://portableapps.com/node/31300
Andy.
Yeah, looks like you we have the same issue. But it has nothing to do with that topic, I think. It's something related to 3.5.3 only.
Please head over here: https://portableapps.com/node/32165
Sometimes, the impossible can become possible, if you're awesome!
My operating system is WinXP updated through this week's updates.
msvcr90.dll appears in lots of PortableApps directories, including:
[PortableAppsDir\]LibreOffice\App\libreoffice\program
[PortableAppsDir\]LibreOffice\App\libreoffice\URE\bin
(Note that I imposed my own application directory name, "LibreOffice", vs. the default "LibreOfficePortable")
It also appears in several directories of form:
C:\Windows\WinSxS\x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.?????
... where ????? is a mishmash of alphanumeric text.
Dismounting the TrueCrypt volume gives me this warning after running LO:
--
Volume contains files or folders being used by applications or system.
Force dismount?
--
This is with both the auto-install and an independent version of VC runtime. Selecting either Yes or No on the message offering to install VC runtime makes no difference.
I also get this warning, but when I click "No" LibreOffice does start and work OK.
I added a new fix with improved detection. Could folks who had issues previously please try this new fix and see if it properly detects that you have VC installed?
Sometimes, the impossible can become possible, if you're awesome!
I don`t know what kind of improvement you done. But it does not work in my case. So I begin.
OS: Win XP Pro SP3 x32
msvcr90.dll folders:
x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_* (previously installed)
x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.6161_x-ww_* (installed from your package)
As I realise your early code check for accurate version of MSVC. But it`s too difficult to cover all versions in this way. I found another solution in one Inno setup topic forum (http://forum.oszone.net/post-1862872-844.html). Maybe it will be useful:
For NSIS it`s look like this:
It work fine on my system.
Best regards, Paul.
Your approach makes sense, though we'd check 32-bit only. We don't care if the 64-bit version is installed as LibreOffice, a 32-bit app, can't use it.
It's also odd that the exact same check running on your system can't find the just-installed VC runtime while it can on mine. I think this is why I found dozens and dozens of different implementations.
Sometimes, the impossible can become possible, if you're awesome!
Win 7 Ultimate x64 - the new detection fix doesn't properly detect.
(feels almost like a zombie movie Anyway, )
I run Win7, 64-bits, Home Premium.
msvcr90.dll is located in the Audacity PortableApps folder (specifically: "B:\Apps\PortableApps\AudacityPortable\App\Audacity\msvcr90.dll" - and also at "D:\Dropbox\Apps\PortableApps\AudacityPortable\App\Audacity\msvcr90.dll" - I SUBSTed that folder)
I just use the 'fix 1' file and overwrote the old launcher. This did not fix the situation. Pressing "no", however, doesn't matter - whatever I say (Yes or No), LibreOffice just starts as planned (note: I try this by doubleclicking an excel file - oh, just tried running it normally, didn't matter).
The second fix version of the launcher works beautifully
Thank you!!!
Fix 2 properly fixes the font and the VC runtime issues. Please give this a try even if fix 1 or the strip fix worked for you. Thanks!
Sometimes, the impossible can become possible, if you're awesome!
This is fixed in 3.5.4 using improved detection of installed runtimes.
Sometimes, the impossible can become possible, if you're awesome!
I just installed 3.5.4 and it offers to install VC runtime. I did a clean install via PA platform - same. Tested in virtual machine with clean Windows 7 32-bit - same.
Are you absolutely sure the 32-bit version of the VC runtime is installed on said machines? If attemping to instantiate it (which should work unless something is borked or a bad antivirus is running) as well as checking the 4 uninstall keys for all known versions as well as checking HKLM\SOFTWARE\Microsoft\DevDiv\VC\Servicing\9.0\RED (which should exist when ANY VC runtime 9.0 is installed anywhere) *ALL* fail, then something has to be borked about the install.
Sometimes, the impossible can become possible, if you're awesome!
This runtime is included with Windows 7 SP1 and does not need to be installed. Check my first comment in this thread:
Windows 7 32-bit.
C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4940_none_50916076bcb9a742\msvcr90.dll
If I refuse to install VC runtime, LO starts just fine.
This is still not fixed with latest LibreOfficePortable.
I get the same error when installing LO3.55 (this error occurs since 3.5x)
"This comuter is missing a component required for LibreOfficePortable. Install Microsoft Visual C++ 2008 runtime ?"
But I use the portable version of LO because I use diffrent PCs and I cannot install applications on all machines.
I use WinXP SP2 or above on the diffrent PCs
It would b great if this problem coulb be solved.
Thanks
Grisu2
On WinXP it's probably really required. Without VC runtime LibreOffice won't run at all. But this runtime is included with Windows 7, and still LibreOfficePortable thinks it's not installed.
LO 355 runs fine on w7, XP it makes no complains
today I tried on my w2k machine at work.
Here it does complain about missing runtime, but when I cancel, nothing happens, the LO starts fine and does what is asked to do.
Otto Sykora
Basel, Switzerland
Sorry, I couldn't get it clear. Do you think the issue definitely fixed?
What about the launchers for special doc-types (e.g. LibreOfficeWriterPortable.exe) ?
My case may be a bit extraordinary: I sometimes use PortableApps and LibOP too under wine, this on Kubuntu. LibO is a bit slow then but it works.
msvcr90.dll surrogate is present in the [home].wine/drive_c/windows/system32 folder. It is not correctly detected even with the most recent versions PA 10.1.2, LibOP 3.5.5.3.
After rejecting the offer to install VC runtime everything is o.k.
Will this issue be addressed too?
PS
Under Windows XP SP3 I did never see the issue.
On a relatively newly installed and clean system, I downloaded and installed PA Platform 10.1.2 and used that to install LibreOffice 3.5.5(2012-07-13). On trying to run it the first time it comes up with "This computer is missing a component required for LibreOffice Portable to function. Install Microsoft Visual C++ 2008 runtime?"
On searching C: for the file "msvcr90.dll" it is only present in 2 places:
(1)"C:\Documents and Settings\JohnW\My Documents\PortableApps\PortableApps\LibreOfficePortable\App\libreoffice\program"
(2)"C:\Documents and Settings\JohnW\My Documents\PortableApps\PortableApps\LibreOfficePortable\App\libreoffice\URE\bin"
Both of which are within LibreOffice itself.
I answered "No" to see what would happen and it would not start. I tried starting LibreOffice Writer again and did not get the error, but neither did it work (I did see a splash screen however). Further tries to start it gave no indication of any result. I tried starting LibreOffice Draw with similarly little result except after a while it came up with a crash error "Due to an unexpected error, LibreOffice crached. All the files you were working on will now be saved..." etc. On trying to start LibreOffice Draw again I got the original error "This computer is missing ... Visual C++ ...". So this time I decided to try answering "Yes".
This time it did something (as indicated by the egg-timer cursor) and LibreOffice Draw came up running! So I shut it down and did another search for "msvcr90.dll" on C:. This time I found it in "C:\WINDOWS\WinSxS\x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.6161_x-ww_31a54e43" as well as the other two places where it was previously.
So it seems to be working now but having to copy msvcr90.dll to Windows is not stealthy and may have been a problem if I wasn't logged on as an administrator.
JohnW
I am using the latest version of LOP that is available, but still I get this error about the missing runtime lib on a certain machine running Windows-XP. Unfortunately, I don't have admin access to this machine, and the network proxy won't let me download anything suspicious. (And a file ending in ".exe" looks very much suspicious to this proxy!)
So I downloaded this patched launcher at home and put it onto my USB stick. Let's hope it will do as promised, when I am back at this sick machine tomorrow morning.
What can I do if it doesn't? What alternatives do I have? I need to get LOP working on that machine, otherwise I can't access any of my files. Any help is very much appreciated!
Over here: https://portableapps.com/news/2012-08-31--libreoffice-portable-3.6.1-rel...
You saw that already, I think. So, use that. If that Windows XP machine doesn't have the proper runtime on it, LibreOffice won't work in any form, portable or not.
Sometimes, the impossible can become possible, if you're awesome!
Ok: now I found three different patched versions of LibreOfficePortable.exe. They all have different file sizes, so I dare say they are different. I will try them all and hopefully one of them is going to let me work tomorrow.
Supplement:
It is Saturday morning and I had a very unpleasant Friday.
I had three different versions of LibreOfficePortable.exe with me on my USB stick, neither of which worked. I also had the complete download version of LO portable with me that can be found at libreoffice.org and I was able to add it to my portable apps. But I still got this stupid error about this missing dll.
All this try & error took me nearly 90 minutes. I never thought that such slow machines still existed in 2012.
Anyway: the machine I was using identifies itself as as some AMD processor (sorry: forgot which one...), running Windows XP, version 2002, service 3.
Still the question remains: what can I do to make LO portable work on that machine?
Can older versions of LOP still be found somewhere?
I really need a running version of LOP!
There is only a SINGLE current patched version of LibreOfficePortable.exe available that applies to this situation. This one: https://portableapps.com/node/34272#comment-198129
You install LibreOffice Portable 3.6.1 and then replace the LibreOfficePortable.exe in the LibreOfficePortable directory with that new one you download. It does not magically make LibreOffice not need Visual C++ runtime anymore. It just does a better job of detecting when it is missing.
If you don't have it installed on your Windows XP machine, it will offer to install it. If you refuse, LibreOffice will fail to run. LibreOffice, both regular and portable, requires this Visual C++ runtime installed locally. Without it, it can't run. Period. End of story.
Please follow the steps above. If they fail, please list your exact process and the exact errors you see happen.
Sometimes, the impossible can become possible, if you're awesome!
You're right about the numbers of files: I confused the patched version 3.5.3 and 3.6.1. Sorry about that!
Still, there's something that puzzles me very much:
This is the first time I encountered a machine where my portable apps don't work. I always thought "portable" meant that those apps would always run on a host machine, regardless of how the machine is configured. That should be the most important meaning of the word "portable".
And, frankly, that's what is written on portableapps.com: "PortableApps.com lets you carry all your favorite apps on a portable device or cloud drive and use them on any PC."
Now I learn that portable apps do very much depend on some dll files that need to be installed on the host machine. I don't thing that this is what "portable" and "on any PC" really means. I really would expect portable apps to be independent of the host machine's configuration.
Isn't there any way that those stupid dll files can compiled into LOP, or put onto the USB stick, where LOP can find them? What about some portable version of those files?
In my opinion asking if these missing files should be installed on the host machine not only violates the true meaning of the word "portable", it also is a big security breach. Apart from sometimes being not allowed to install anything on the host machine, it can also get the user in big trouble when the machine's owner or administrator finds out that something has been added to the machine that was not there before, for whatever reason.
I really thing that portable apps should not install anything on a host machine. They should leave the machine the same way that it was before.
Before freaking out further and ascribing this to some grand conspiracy or defect ... remember that this is a single app. And the issue is an outdated or corrupted Visual C++ runtime. This runtime is included with Windows Vista, Windows 7 and Windows 8. And most Windows XP machines already have it installed. Due to the way LibreOffice is coded, it doesn't properly use the bundled C++ runtime in the portable package. Yes, it is included, just the way we do with dozens of other apps that work with a portable version of these files. But LO doesn't work with it and HAS to have a locally installed one for a few of its components.
So, this only affects a small percentage of outdated Windows XP machines that lack the runtime, either because they are fully clean and patched instances of XP with no software installed and IE not updated or because they are hopelessly out of date. So, we could either ditch LibreOffice Portable, or come up with a handy workaround for these few lacking machines, rather than LibreOffice simply crashing on them. We chose the latter. That's the way it works. Either update the machine, or don't use the app on it. Those are your only two choices with this app and this particular machine. There is currently no other solution.
Sometimes, the impossible can become possible, if you're awesome!
I'm neither freaking out nor am I blaming you for anything. It's just that I haven't encountered this situation before and it is pretty annoying, because I can't access my files while I am forced to use this machine. And, like I said: I always thought that "portable" also meant "independent".
It's really too bad that there is no solution to this problem, because I have no admin rights on that machine and I will not be granted those rights, no need to ask the administrator.
Unfortunately, I can't even boot the machine into Linux.
I really hope that someone will come up with a better way to deal with these dependencies in some future version of LO. In the mean time all I can do is to convert all my files to MS-Office file types and use those copies on this specific machine, hoping the damage will not be too big.