Bug 103817 - 5.3.3 install failed and erased previous version. Now inoperable.
Summary: 5.3.3 install failed and erased previous version. Now inoperable.
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
5.2.3.3 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-09 22:35 UTC by spam60613
Modified: 2016-11-10 03:30 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description spam60613 2016-11-09 22:35:35 UTC
Description:
Using older 5.2 and previous for years.  Prompt led me t try 5.3 install. Failed for lack of "admin" access, which was never required before.  Now I find ALL LibreOffice is deleted!  Can't install 5.3- still requires admin access.  So I guess I'll just have to buy a corp office product?

-Mike-

Steps to Reproduce:
1.Download 5.3.3
2.Commence install
3.Fail notice- needs 'admin" access.

Actual Results:  
install fail- with all previous LibreOffice deleted.  All previously created work files (WP, spreadsheets) unreadable.  Attempts to re-install all fail.

Expected Results:
Expected newest LibreOffice.


Reproducible: Always

User Profile Reset: No

Additional Info:
Windows 7 home premium on HP Pavilion g7 notebook


User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0
Comment 1 V Stuart Foote 2016-11-10 03:30:23 UTC
As 5.3.3 has not be built or release, you must mean 5.2.3.3

You might verify the HASH signature of the package you've downloaded and attempted to install. If it doesn't match its not valid. And be careful that if you have the 64-bit version installed you are not trying to upgrade it with the 32-bit version--we see that too often.

Also, issue like this often occur when user has left an instance of a program running, and after an upgrade attempt leaves the MSIexec package manager in an unhappy state.

Either case there will usually be some error message in the event log about the installation attempt.

https://msdn.microsoft.com/en-us/library/windows/desktop/aa372835(v=vs.85).aspx

But, if you simply run a Windows command prompt "as administrator" and clear this by unregistering the service.

msiexec.exe /unregister

msiexec.exe /register

Personally when I install software I always "run as administrator" or run the installation from the CLI "run as administrator" so the system files and registry that must be written to can be.