Description: I have used "WinToUsb" to do a "Windows To Go" installation of Windows 8.1 Pro on an external USB SSD. It works perfectly. when I try to install LibreOffice 6.1.6, the installation doesn't work : it doesn't goes to the end, without any error message. I have tried with LibreOffice 5.7.2 and it works perfectly... What's the matter with 6.1.6 ? It should work on windows 8.1 Steps to Reproduce: 1.Make a "windows To Go" installation of Windows 8.1 Pro on external usb ssd. 2.Try to Install LibreOffice 6.1.6 on it. 3. Actual Results: Installation doesn't go to the end, without any error message : It's just blocked. Expected Results: A happy end... Reproducible: Always User Profile Reset: No Additional Info:
Hi. Could you please clarify what "It's just blocked" mean? Does it hang indefinitely? Or does it roll back saying "installation didn't succeed"? Please read the FAQ [1]; and please provide an installation log, as described in the FAQ's last section. Thanks. [1] https://wiki.documentfoundation.org/Faq/General/General_Installation_Issues_(Windows)
Created attachment 151359 [details] screen capture
Hello, It hangs indefinitely without any error message. After 20 minutes waiting, I've killed the install process... I give you a screen capture on where it hangs. I've made a log file, but it seems too big to add to that bug report (17.7 MO !). Here is the link to upload it : www.grosfichiers.com/syJMtJZpNf6 (You'll just have to click on 'libreoffice-install.log' to get it) Goog luck
Thanks (though of course the FAQ mentioned that the log file should be ZIPped before submission;-)) - and could you please try to kill wusa.exe instead?
Created attachment 151361 [details] Error message when I run LibreOffice In case I kill wusa.exe during install process
If I kill wusa.exe installation goes to the end. BUT, when I run LibreOffice, there is an error message.
Created attachment 151362 [details] Zipped Log file
For some reason, Windows Update cannot install a required update KB2999226 on your system. You may find a link to that update on the FAQ page - please try to download and install it manually. Doing that would resolve the error when starting LibreOffice. Please report back of that succeeded. Thanks!
(In reply to Mike Kaganski from comment #8) > For some reason, Windows Update cannot install a required update KB2999226 > on your system. You may find a link to that update on the FAQ page - please > try to download and install it manually. Doing that would resolve the error > when starting LibreOffice. Please report back of that succeeded. Thanks! Hello! I've uploaded 'Windows8.1-KB2999226-x64' but when I try to install it, it hangs... I've tried "Windows update" and it hangs too.. Maybe is there a problem on Microsoft update server, or maybe updates doesn't works on "windows to Go" 8.1 installations. So, it would be an OS problem, and not a LibreOffice Bug. If so, I'll install oldest LibreOffice 5.7.2 Thanks for your work.
Things to try: 1. Stop Windows Update service (*do not disable!*) and start installation of the update package - so that the update would start the service itself. It is reported that in some cases, that helps. 2. Stop Windows Update service, and *remove* C:\Windows\SoftwareDistribution. Then start Windows Update service to re-create the directory anew.
(In reply to Mike Kaganski from comment #10) > Things to try: > > 1. Stop Windows Update service (*do not disable!*) and start installation of > the update package - so that the update would start the service itself. It > is reported that in some cases, that helps. > 2. Stop Windows Update service, and *remove* > C:\Windows\SoftwareDistribution. Then start Windows Update service to > re-create the directory anew. Hello! Unfortunately, what you suggested didn't worked... But, I have manage to make 'Windows update' work again on my win 8.1 pc, with kb3138615. After that, LibreOffice 6.1.6 installation worked perfectly. Thank you very much for your help!
(In reply to jlucschoon from comment #11) Thank you for the notice! Based on your information, I assume that that was a problem with a system component (Windows Update), and problem was resolved after fixing that component state. Thus, I close this as NOTOURBUG. Thank you!