https://bugs.documentfoundation.org/show_bug.cgi?id=164862
--- Comment #2 from [email protected] --- (In reply to V Stuart Foote from comment #1) > Can not confirm. > > Version: 24.8.4.2 (X86_64) / LibreOffice Community > Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002 > CPU threads: 8; OS: Windows 10 X86_64 (10.0 build 19045); UI render: > Skia/Raster; VCL: win > Locale: en-US (en_US); UI: en-US > Calc: CL threaded > > > Could be something new with the Win11 (24H2) release build you're on. I don't know. It's the current release, and has been since the first day of last October. It's been the current dev build for nearly a year. > This loss of file association (e.g. scalc.exe not associated with .ods ODF > spreadsheet, and soffice.exe instead) should not happen, but we have seen > past instances on Windows os/DE when MS Office product install has corrupted > the registration of the soffice.bin associated .exe wrapper programs. No MS Office products are installed except OneNote, which came pre-installed with Windows 11. What does soffice.bin have to do with soffice.exe being registered as the executable for every action for most LibreOffice file types? > Use the os/DE file association manager, LibreOffice provides a launcher from > its Tools -> Options -> General 'Windows Default Apps' button. > > Find the LibreOffice listed in the dialog, and use its 'Manage' button. > > You'll see the MS API provided handling of "File type and protocol > associations" as currently registered on your system. Unfortunately, that won't help. That will show LibreOffice as the file type and "OpenDocument Spreadsheet" under it. The reason is because soffice.exe is specified in the Windows registry for each action for the file type (hence that UI shows "LibreOffice" instead of "LibreOffice Calc", as it should). The fact that it states "OpenDocument Spreadsheet" is meaningless because that UI just shows the value of the FriendlyTypeName string within the corresponding registry key. > If you like you could try to fully uninstall LibreOffice, clean the windows > registry of any LibreOffice associations and rename or delete any of the > LibreOffice user profiles. And then reinstall clean from the MSI package. > > Let us know if after the clean install you still are missing file > associations in the either the Win11 "File Explorer" and in the Win11: > Settings -> Default Apps -> Set defaults by app reviewing the LibreOffice > "File type and Protocol associations". Thank you for the offer, but no, I would not like. I can fix the problem manually much faster by simply editing the registry. I spent my time reporting this bug so it can be fixed for all and to improve the quality of LibreOffice, not as a self-serving act. I do appreciate your well-intentioned instructions. I think it will be best to improve LibreOffice in three (3) specific areas: 1. During all LibreOffice installs and upgrades, to set the file type associations correctly (when the user selects the corresponding options). Given that a LibreOffice upgrade was just performed, the LibreOffice installer should have fixed this problem (whether LibreOffice caused it, or something else caused it). But the LibreOffice installer failed to correctly set file type associations. 2. In LibreOffice, when the user selects "Tools > Options > General > Perform check for default file associations on start-up", problems like this need to be fixed. Currently, LibreOffice fails to do so. 3. For the option mentioned in #2, the UI needs to be clarified to specify which "start-up" those words apply. System start-up? User login? LibreOffice start-up? Adding a single word before "start-up" will significantly improve the UX in this area. I am not familiar with The Document Foundation's protocol for setting the status field for bug reports. Thus, I will not touch it and will leave it as "NEEDINFO". Please set it to what you determine is appropriate. If you like, you can let me know if I was responsible for changing it when posting this reply, and next time, I will do so. -- You are receiving this mail because: You are the assignee for the bug.
