Bug 93158 - windows 10 installed
Summary: windows 10 installed
Status: RESOLVED DUPLICATE of bug 69066
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-05 20:29 UTC by siggy
Modified: 2015-11-15 02:02 UTC (History)
2 users (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 siggy 2015-08-05 20:29:48 UTC
After installing Win 10 need to upgrade Libre then win 10 requires Windows Explorer to be turned off. Doing so the screen will go black but continue with Libre upgrade.  Once upgrade complete need to open ( ctl alt del) Task Manager , add new process "Explorer" screen will return.

Didn't know where else to let others know. If you do maybe you can paste this saving others the exercise.
Comment 1 tommy27 2015-10-04 15:40:38 UTC
hi, are you still seeing this issue with latest upgrade of LibreOffice under Win10 ?  the latest stable release is 4.4.5.2

status NEEDINFO
Comment 2 tommy27 2015-10-06 03:55:44 UTC
siggy answered me by mail telling that:
----------------------------------------------
Pc has Windows 10.0 Build 10240 loaded.
Just upgraded to ver 5.0.2.2 and had the same problem.
when installing Libre  warning message says close all apps. I had to close
Chrome and Windows Explorer. Screen went black soon as I closed Windows
Explorer except for the install window.The install window says close 2312
and 6140 (what ever they are).  I was lost so closed the install window.

Used old solution opening Task Manager (ctl alt del) and new process
"Explorer" and back to normal. New Libre looks good.
----------------------------------------------

I don't have Win10 to test so another QA member has to take care of this.
sorry I can't offer additional help

status back to UNCONFIRMED
Comment 3 Adolfo Jayme Barrientos 2015-11-15 00:51:04 UTC

*** This bug has been marked as a duplicate of bug 69066 ***
Comment 4 siggy 2015-11-15 02:02:39 UTC
UsinWin 10, upgraded to ver 5.0.3.2 and there were no problems.