Can not confirm, both 5.3.3.2 and 5.2.7.2 builds install and run cleanly on Windows 10 Pro (or Home) v1703 64-bit or 32-bit.

Please be sure to clear your user profile %APPDATA%\LibreOffice and try again.

Also, since you are on 64-bit Windows did you clean install LibreOffice, or was it a carry over of the old install? And, is the version of LibreOffice 32-bit or 64-bit?

(In reply to V Stuart Foote from comment #1)
> Can not confirm, both 5.3.3.2 and 5.2.7.2 builds install and run cleanly on
> Windows 10 Pro (or Home) v1703 64-bit or 32-bit.
> 
> Please be sure to clear your user profile %APPDATA%\LibreOffice and try
> again.
> 
> Also, since you are on 64-bit Windows did you clean install LibreOffice, or
> was it a carry over of the old install? And, is the version of LibreOffice
> 32-bit or 64-bit?

Which folder in %APPDATA%\LibreOffice is the user profile? To get to the LO folder I show the path as AppData\Roaming\LibreOffice There is no folder named user profile. Are you talking about the "cache" folder under the folder LibreOffice\4?

(In reply to fdhealy54 from comment #2)
> Which folder in %APPDATA%\LibreOffice is the user profile? To get to the LO
> folder I show the path as AppData\Roaming\LibreOffice There is no folder
> named user profile. Are you talking about the "cache" folder under the
> folder LibreOffice\4?

All of that folder is the "profile"

%APPDATA% is defined per user, and normally will be C:\Users\<username>\AppData\Roaming and here simplest is to delete/rename the entire LibreOffice folder. 

However the most significant portion of user configuration is the registrymodifications.xcu in the %APPDATA%\LibreOffice\4\user folder.  Deleting, renaming that will reset to defaults--keeping copies of templates, dictionaries, etc. but breaking the linkage to them.

At 5.3 there is also a "Restart in Safe Mode" on the LO Help menu if you could get to it. It makes a temporary default profile helpful for testing.

(In reply to V Stuart Foote from comment #3)
> (In reply to fdhealy54 from comment #2)
> > Which folder in %APPDATA%\LibreOffice is the user profile? To get to the LO
> > folder I show the path as AppData\Roaming\LibreOffice There is no folder
> > named user profile. Are you talking about the "cache" folder under the
> > folder LibreOffice\4?
> 
> All of that folder is the "profile"
> 
> %APPDATA% is defined per user, and normally will be
> C:\Users\<username>\AppData\Roaming and here simplest is to delete/rename
> the entire LibreOffice folder. 
> 
> However the most significant portion of user configuration is the
> registrymodifications.xcu in the %APPDATA%\LibreOffice\4\user folder. 
> Deleting, renaming that will reset to defaults--keeping copies of templates,
> dictionaries, etc. but breaking the linkage to them.
> 
> At 5.3 there is also a "Restart in Safe Mode" on the LO Help menu if you
> could get to it. It makes a temporary default profile helpful for testing.

I found the file you are referring to but I would like to delete LO also and start over. I have deleted it before but now I cannot. when I try and delete it I get a box that says "The feature you are trying to use is on a network resource that is unavailable." The path to the installer file is correct.

We would need to see an uninstall log of the Microsoft Installer -- msiexec.exe -- from the command prompt for the attempt.

Chances are the Microsoft Installer service needs to be stopped and reregistered.

<Win>+X
select the Command Prompt (Admin) --or Power Shell (Admin) if enabled--
enter:  "msiexec.exe /unregister"
enter:  "msiexec.exe /regserver"

If errors, your Windows update is unstable. If no errors displayed, proceed a logged uninstall attempt (adjust the *.msi to match what you'd installed).

enter: "msiexec.exe /x LibreOffice_5.2.7.2_Win_x64.msi /L*v lo5272uninstall.txt"

Zip the log up and post it.

(In reply to V Stuart Foote from comment #5)
> We would need to see an uninstall log of the Microsoft Installer --
> msiexec.exe -- from the command prompt for the attempt.
> 
> Chances are the Microsoft Installer service needs to be stopped and
> reregistered.
> 
> <Win>+X
> select the Command Prompt (Admin) --or Power Shell (Admin) if enabled--
> enter:  "msiexec.exe /unregister"
> enter:  "msiexec.exe /regserver"
> 
> If errors, your Windows update is unstable. If no errors displayed, proceed
> a logged uninstall attempt (adjust the *.msi to match what you'd installed).
> 
> enter: "msiexec.exe /x LibreOffice_5.3.1.2_Win_x64.msi /L*v
> lo5272uninstall.txt"
> 
> Zip the log up and post it.

(In reply to V Stuart Foote from comment #5)
> We would need to see an uninstall log of the Microsoft Installer --
> msiexec.exe -- from the command prompt for the attempt.
> 
> Chances are the Microsoft Installer service needs to be stopped and
> reregistered.
> 
> <Win>+X
> select the Command Prompt (Admin) --or Power Shell (Admin) if enabled--
> enter:  "msiexec.exe /unregister"
> enter:  "msiexec.exe /regserver"
> 
> If errors, your Windows update is unstable. If no errors displayed, proceed
> a logged uninstall attempt (adjust the *.msi to match what you'd installed).
> 
> enter: "msiexec.exe /x LibreOffice_5.2.7.2_Win_x64.msi /L*v
> lo5272uninstall.txt"
> 
> Zip the log up and post it.

Did this and got no errors.
<Win>+X
select the Command Prompt (Admin) --or Power Shell (Admin) if enabled--
enter:  "msiexec.exe /unregister"
enter:  "msiexec.exe /regserver"

Did this:
enter: "msiexec.exe /x LibreOffice_5.3.1.2_Win_x64.msi /L*v
> lo5272uninstall.txt"
I got a box labeled "Windows Installer" and it said "This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package."

I don't know what you mean by zip the log and post it. Where is the log?

Dale

Where are the log files so I can zip them up and post them for you.

Dale

(In reply to fdhealy54 from comment #7)
> Where are the log files so I can zip them up and post them for you.

If you were able to change directory while in the command prompt into the folder holding the .msi installer package, the "/L*v ,somefilename> verbose log will be created with <somefilename> in that folder.

(In reply to V Stuart Foote from comment #8)
> (In reply to fdhealy54 from comment #7)
> > Where are the log files so I can zip them up and post them for you.
> 
> If you were able to change directory while in the command prompt into the
> folder holding the .msi installer package, the "/L*v ,somefilename> verbose
> log will be created with <somefilename> in that folder.

Sorry but that is beyond my pay grade so to say. Do you have the ability to remotely connect to my computer?

Dale

(In reply to fdhealy54 from comment #9)
> Sorry but that is beyond my pay grade so to say. Do you have the ability to
> remotely connect to my computer?
> 

Would prefer not to go down that route. Perhaps seek competent assistance in your neighborhood. Both to correct the MS Installer service, and completely clear residual installs and profiles. Then start again with a clean installation.

For now, lacking any actionable details, resolving this install issue as WORKSFORME as it is known functional.

If following cleanup and a new command line install attempt with logging, if still having issues zip and post the install log--we'll REOPEN.

(In reply to V Stuart Foote from comment #10)
> (In reply to fdhealy54 from comment #9)
> > Sorry but that is beyond my pay grade so to say. Do you have the ability to
> > remotely connect to my computer?
> > 
> 
> Would prefer not to go down that route. Perhaps seek competent assistance in
> your neighborhood. Both to correct the MS Installer service, and completely
> clear residual installs and profiles. Then start again with a clean
> installation.
> 
> For now, lacking any actionable details, resolving this install issue as
> WORKSFORME as it is known functional.
> 
> If following cleanup and a new command line install attempt with logging, if
> still having issues zip and post the install log--we'll REOPEN.

Do you have a list of files and registry items to remove for a manual uninstall?

Dale

This bug was never confirmed by a third person. Moving back to UNCONFIRMED

Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.

I can confirm the bug.

Installed versions of LO: 5.3.5.2 x64 and same behavior before also with 5.3.3 x64

Before creators update there where no problems at all.
Now with Windows10 1703 (Build 15063.502), in about 95% i cannot start up LO, even when using -safe-mode.

LO seems to hang during start up, there are two tasks present soffice.bin with around 15% CPU usage and soffice with 0%. The tasks stay forever, no entry is created in Windows Log.

In some cases immediately after booting i can open libre office. From then on i can open LO without problems during the entire session.

I found that during a installation of LO explorer crashes immediately when LO finishes installation (reproducable).

NEW per previous comment.

Btw. did you guys install Quickstarter?

To rule out OpenGL problems, you might want to merge this registry fragment: https://bugs.documentfoundation.org/attachment.cgi?id=118060

Getting a stack-trace of the hang would be very much appreciated - if possible =) Any chance of following these steps:
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg ?

Thanks !

(In reply to Michael Meeks from comment #16)
> Getting a stack-trace of the hang would be very much appreciated - if
> possible =) Any chance of following these steps:
> https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg ?
> 
> Thanks !

Right, do try with this build, which has all the debug goodies: http://dev-builds.libreoffice.org/daily/master/Win-x86@39/current/
Note this build is 32-bit, so launch the 32-bit WinDbg when starting to debug.

(In reply to Buovjaga from comment #15)
> 
> Btw. did you guys install Quickstarter?
> ... 

Personally I _never_ install Quickstarter for Windows builds (unfortunately that requires I always do a custom installation to do so)--though I and others have asked that this _anti-feature_ be dropped from defaults for interactive use, or purged from source...[1][2]

But believe we are still affected by bug 51529 on the Windows builds--and have to kill Quickstarter prior to performing an upgrade installation.

What is even more common is users confusing the build of LO they have installed and attempting to update with 32-bit over 64-bit, or vice-versa. And often not installing with Administrator credentials when they should be.

Anyhow this is still a WFM--on all instances 32-bit/64-bit of Windows 10 Creators ed. (ver 1703)

I will also normally have installed the current Visual C++ Redistributable for Visual Studio 2015 outside the LibreOffice installations [3] seems there have been a couple of issues there as well of late bug 108580

Setting this back to normal as it is rather not the norm, for these two instances there have been hundreds of successful installs.

Let's see what a stack trace shows if one appears in response to the NEEDINFO, and more MSI installation logs would help as well.

=-ref-=

[1] https://wiki.documentfoundation.org/Proposals_for_removing_features
[2] http://nabble.documentfoundation.org/minutes-of-ESC-call-tc4215632.html

[3] https://my.visualstudio.com/Downloads?pid=2082

(In reply to V Stuart Foote from comment #18)
> Setting this back to normal as it is rather not the norm, for these two
> instances there have been hundreds of successful installs.

Severity refers to how bad the effect is, not how common it is.

(In reply to Buovjaga from comment #19)
> (In reply to V Stuart Foote from comment #18)
> > Setting this back to normal as it is rather not the norm, for these two
> > instances there have been hundreds of successful installs.
> 
> Severity refers to how bad the effect is, not how common it is.


My point is that it is still essentially an unconfirmed issue with a number of potential issues that would have nothing to do with LibreOffice install. 

If it were really an issue with the Windows 10 Creators update--which installs by default to Windows 10 systems--we'd be swamped, it would be legitimately confirmed, and it would be critical.

As is we do not have valid STR, and lack verbose logging of the installation(s) this occurs in. Would like those in addition to a WinDbg stacktrace (e.g. ~* kp) with symbols of the hung soffice.bin process.

I do not have Quickstarter installed.

Some times LO is starting up perfectly, i still did not find out on why or under which conditions though. I am currently testing if it has something to do with Norton Antivirus or Commodo Firewall which i have installed on several of my machines. Could well be, as both programs have seen an update after windows creators update. 
OpenGL problems seem not likely to me as in this case it would not start up any time.
I will try to create a stack-trace if possible.

Cannot reproduce the problem any more. There have been updates of Comodo Firewall and also Norton Antivirus in the meantime.
I think that this was most probably an issue with Comodo blocking some functionality of LO during startup.
I could not reset the system to a state where LO will not start up so i cannot provide the stack trace to confirm, sorry.

fdhealy: are you running Comodo as well?

No I'm not running Comodo. I still have the problem though.

(In reply to fdhealy54 from comment #24)
> No I'm not running Comodo. I still have the problem though.

Ok, could you get some local Windows guru to help get a backtrace of the hang?

Because the hang happens upon starting, you have to use this method to attach the debugger to the process: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg#Automation

In the case of a hang like this, there is an additional step before doing "!analyze -v": you have to give this command in WinDbg:

~* kp

It will display the call stack for all threads and all of the parameters for each function that is called in the stack trace. Then you can give the !analyze -v command.

Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180502