<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Libre Office 7.0.0.1 RC1 installation crashes - a renewed installation goes to the wrong folder - Libre office 6.4 doesn't start with renewed installation after uninstall of 7.0.0.1 RC1 - error: vcruntime140_1.dll missing"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134849#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - Libre Office 7.0.0.1 RC1 installation crashes - a renewed installation goes to the wrong folder - Libre office 6.4 doesn't start with renewed installation after uninstall of 7.0.0.1 RC1 - error: vcruntime140_1.dll missing"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=134849">bug 134849</a>
from <span class="vcard"><a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> <span class="fn">Mike Kaganski</span></a>
</span></b>
<pre>Several factors here, and they seem unrelated to each other, the initial crash
being the main (likely random) problem, and others coming from
misunderstanding/confusion.
It looks like you were expecting to have two versions side-by-side by choosing
a different directory. But in fact, no matter which directory you choose, the
installer for RC1 (as any installer built with "release" configuration) would
*replace* any previous installed release version: it will find those older
versions, call their uninstaller in the process of own installation, then
proceed. So in any case, installing into "programme\libreoffice7" would
normally still result in a single version on your system.
This is not the case for alpha and beta installers, that are installed
separately. There is a way to have multiple releases "installed" (actually
unpacked, but not registered) side-by-side [1].
The "an warning ... that i have to close firefox and windows explorer.
this bothers me too": LibreOffice creates several registry keys, installs a
system component (visual c++ redistributable) and an explorer extension (a
library used for e.g. thumbnail display of ODF documents, which may be used not
only in Windows Explorer, but with any Windows-provided file dialog). Another
system-wide thing is fonts it installs. Installer internally builds a list of
all files and registry keys it needs deleting/modifying; and if some process
happens to hold some of them, it notifies you. There's nothing to do here;
previously (many versions ago), it simply told that it needs a restart in the
end - now we made it to show a detailed list, and that creates questions absent
before.
With older version not starting - possibly you just need to reset user profile
[2].
So the only problem here that I see is to test if the scenario when there's an
older version installed in one place, and you try to install into a different
place, results in a reproducible problem. Will try to test it ASAP (but if
someone beats me here, bit thanks - I'm quite busy now, and I don't see this
too pressing).
[1] <a href="https://wiki.documentfoundation.org/Installing_in_parallel/Windows">https://wiki.documentfoundation.org/Installing_in_parallel/Windows</a>
[2] <a href="https://wiki.documentfoundation.org/UserProfile">https://wiki.documentfoundation.org/UserProfile</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>