Download https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF/current/LibreOfficeDev_26.2.0.0.alpha0_Win_x86-64.msi It has date 2025-Jun-27 01:31. Install it in an own directory, e.g. C:\Apps\LO_Dev Make a directory for a user, e.g. C:\AppsUser\LODev_de_user Start LO with e.g. C:\Apps\LO_Dev\program\soffice.exe -env:UserInstallation=file:///c:/AppsUser/LODev_en_user Click on any of the entries in the menu bar in start center. => CRASH
There is no crash with an administrative installation via "msiexec -a" and setting UserInstallation=$ORIGIN/.. in bootstrap.ini.
I've never tried an install nightly that way. When it ran was portion of profile .xcu built since you got to the StartCenter? Maybe some weird "paths" issue, did any of the Paths get an entry into the registrysettings.xcu? Maybe something is hinted at there. Doing /a installs and editing the bootstrap.ini: $ORIGIN would result in $(insturl) vs. $SYSUSERCONFIG which results in $(userurl) Otherwise WinDbg to follow along something in with init.cxx call to Bootstrap::ReloadData()? from /core/unotools/source/config/bootstrap.cxx /core/include/unotools/bootstrap.hxx
Created attachment 201536 [details] State of registrymodifications.xcu after first start (In reply to V Stuart Foote from comment #2) > I've never tried an install nightly that way. It has the advantage, that I can use the same build with a user with English UI and another user with German UI. That has worked all the time. Today was the first fail. When it ran was portion of > profile .xcu built since you got to the StartCenter? See attachment of registrymodifications.xcu. I had renamed the existing user profile for to be sure, that the error is not in the user profile.
OK poked at it with fresh /a admin installs of the nightly builds, and NOT editing the bootstrap.ini from defaults and initial launching from command line with -env:UserInstallation file path. No issue when I followed STR with the 20250626 TB77 build. Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e7201fd7c51743cb103bae82263d98830f5174cf CPU threads: 28; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded But also no issue with the 20250627 TB77 build Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 04bd455e36b054001e08a0a3256d508a009ffef3 CPU threads: 28; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Both were clean /a admin installs and were both first launches from command line with env set. The Bootstrap utility does have a bunch of diagnostic errors instrumented in https://opengrok.libreoffice.org/xref/core/desktop/source/app/app.cxx with their report strings in https://opengrok.libreoffice.org/xref/core/svtools/inc/errtxt.hrc I did get one of those error popups, an 'Inadmissible path' for "program../share/autotex/common does not exist" for the 20250628 WIX based build from TB78, but it ran otherwise.
(In reply to V Stuart Foote from comment #4) > OK poked at it with fresh /a admin installs of the nightly builds, and NOT > editing the bootstrap.ini from defaults and initial launching from command > line with -env:UserInstallation file path. Please notice my comment 1. There is _no_ crash with an administrative installation. You need to install it regularly to get the crash.
Created attachment 201541 [details] WinDbg stack of launch of 20250627 TB77 nightly /i installed to system to an INSTALLLOCATION (In reply to Regina Henschel from comment #5) > (In reply to V Stuart Foote from comment #4) > > OK poked at it with fresh /a admin installs of the nightly builds, and NOT > > editing the bootstrap.ini from defaults and initial launching from command > > line with -env:UserInstallation file path. > > Please notice my comment 1. There is _no_ crash with an administrative > installation. You need to install it regularly to get the crash. OK sorry. Missed that you'd done an msiexec.exe /i install. Went ahead and tested the 20250627 TB77 build. Could not reproduce an issue launched from the cmd line. C:\temp\LO_Dev\program\soffice.exe \ -env:UserInstallation=file:///c:/temp/LODev_en_user And, I also used WinDbg to 'Open Executable...' the with symbols. Get a few halts while loading modules, but able to 'g' continue for each: ntdll!LdrpDoDebuggerBreak C:\WINDOWS\SYSTEM32\MSVCP140.dll C:\temp\LO_Dev\program\icudt77.dll modules continue to load, but then start getting first chance errors (5874.74a0): C++ EH exception - code e06d7363 (first chance) and then a few vcl warnings warn:desktop.updater:22644:12556:desktop/source/app/updater.cxx:620: download did not succeed. Error code: 404 warn:desktop.updater:22644:12556:desktop/source/app/updater.cxx:786: error during the update check: download did not succeed warn:vcl:22644:29856:vcl/source/image/ImplImage.cxx:104: Failed to load scaled image from cmd/sc_signaturesmenu.png at 1 warn:vcl:22644:29856:vcl/source/image/ImplImage.cxx:127: Failed to load stock icon cmd/sc_signaturesmenu.png warn:vcl:22644:29856:vcl/source/image/ImplImage.cxx:104: Failed to load scaled image from cmd/sc_documentation.png at 1 warn:vcl:22644:29856:vcl/source/image/ImplImage.cxx:127: Failed to load stock icon cmd/sc_documentation.png warn:vcl:22644:29856:vcl/source/image/ImplImage.cxx:104: Failed to load scaled image from cmd/sc_safemode.png at 1 warn:vcl:22644:29856:vcl/source/image/ImplImage.cxx:127: Failed to load stock icon cmd/sc_safemode.png warn:vcl:22644:29856:vcl/source/image/ImplImage.cxx:104: Failed to load scaled image from cmd/sc_getinvolved.png at 1 warn:vcl:22644:29856:vcl/source/image/ImplImage.cxx:127: Failed to load stock icon cmd/sc_getinvolved.png warn:vcl:22644:29856:vcl/source/image/ImplImage.cxx:104: Failed to load scaled image from cmd/sc_showlicense.png at 1 warn:vcl:22644:29856:vcl/source/image/ImplImage.cxx:127: Failed to load stock icon cmd/sc_showlicense.png But nothing really jumps out. Anything else I should try to reproduce? =-testing-= msiexec.exe /i install of the .msi package with INSTALLLOCATION="C:\temp\LO_Dev" (note can't use the TARGETDIR= of normal /a admin install). And launch soffice.exe using the -env:UserInstallation=file:///c:/temp/LODev_en_user (already existing but empty) to create a new empty user profile Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 04bd455e36b054001e08a0a3256d508a009ffef3 CPU threads: 28; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
I've tried again with daily build of 2025-07-01. I have uninstalled previous daily build and its folders in AppData\Roaming\LibreOfficeDev\4. Restart Windows. Double-click the msi file. Choose customize installation to path c:/Apps/LO_dev. Select English-US and German for UI and dictionary. Choose to create a desktop icon. After finished, double-click msi file for English and German help. After finished, restart Windows. Use desktop icon to start LibreOffice. I get the start window. Click on menu Tools. => Crash. I have also tested in save mode. Same crash. What makes my installation different from yours, that it does not crash for you?
Well, I installed from command line with msiexec.exe /i, not a double click on the MSI adding the INSTALLLOCATION= variable. And then ran it from command line as you'd indicated with program\soffice.exe -env:UserInstallation=file:///c:/temp/LODev_en_user And that should *not* result in creation of AppData\Roaming\LibreOfficeDev\4 user profile, rather everything resident on the the UserInstallation path! I was using that when I attached it to WinDbg. But, I'll try it your way--with a double click GUI launch and the Custom install to set the installation path. Which I assume would not result in a LibreOfficeDev entry in %APPDATA% OK, just did that. Comes up clean and stable when launched to create new user outside my user profile. C:\temp\LO_Dev\program\soffice.exe / -env:UserInstallation=file:///c:/temp/LODev_en_user Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 04bd455e36b054001e08a0a3256d508a009ffef3 CPU threads: 28; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
I'm using a regular install, and also experiencing crashes. 1. Install latest master -> Launch crash. 2. Help -> Restart in safe mode -> Crashes (program doesn't work anymore) 4. Relaunching with desktop icon -> Working fine
The problem still exists. I have downloaded the daily build from 2025_07_17 from https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF/current/ I have de-installed the previous version and deleted the previous folder "...\AppData\Roaming\LibreOfficeDev". I have double-click the downloaded msi-file and made a customized installation: Target folder: "C:\Apps\LO_Dev" Dictionaries: EN-US and DE User Interfaces: EN-US and DE Create Desktop Icon I have started LibreOffice using the desktop icon. It starts. But using an application icon in the start center or using icon "Open" immediately crashes LibreOffice.
(In reply to Regina Henschel from comment #10) > The problem still exists. > > I have downloaded the daily build from 2025_07_17 from > https://dev-builds.libreoffice.org/daily/master/Win-x86_64@tb77-TDF/current/ > > I have de-installed the previous version and deleted the previous folder > "...\AppData\Roaming\LibreOfficeDev". > > I have double-click the downloaded msi-file and made a customized > installation: > Target folder: "C:\Apps\LO_Dev" > Dictionaries: EN-US and DE > User Interfaces: EN-US and DE > Create Desktop Icon > > I have started LibreOffice using the desktop icon. It starts. But using an > application icon in the start center or using icon "Open" immediately > crashes LibreOffice. Hmm, and I can not reproduce. No issue with launch from LO's StartCenter, the Desktop icon, or any of the Win Start Menu/JumpList launchers. I did a double click install of the MSI and accepted the un-signed installation as a custom to "C:\temp\LibreOfficeDev 26" install. I unchecked the defaults for MS Office prods. Did not specify a UI or locale, *just accepted defaults*. Initial launch via the Windows Start Menu's Writer icon. No issue. None for any of the other modules. The Open... menu brings up the Windows file manager. Configs written as expected into %APPDATA%. Of course I do not set a WRITE_REGISTRY=1 for these nightly build "--enable-release-build" so minimal recording into the Windows registry db, or C:\Windows. =-testing-= Download of the TB77 2025-07-17 nightly. Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 49279f6a01c4f07b723072c068a9c1eab5b7f292 CPU threads: 28; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Bug 167642 might be related to this.. at least for the comment 9 part