Some unknown occurrence today caused a Windows 10 BSOD (never had one before; only using W10 since mid-year). After rebooting, LMS produced strange error messages (didn't capture them) and wouldn't display the usual interface. I could not access its Settings, but it did offer a selection of interfaces for me to choose. I clicked 'Classic' (my usual i/f), but it showed a weird interface in Firefox [v107.0.1 (64-bit); my default browser].
After spending hours Googling, trying stuff and not getting anywhere, I uninstalled LMS and reinstalled it from LogitechMediaServer-8.3.0-1658898470.exe.
After going through the setup and media scanning, for a short while I had my usual interface back. But after clicking <F5> (refresh), the odd interface shown in the attached screen-shot displayed in Firefox. Chrome displayed slightly better, but still didn't display the standard 'Classic' interface with a 'Settings' button at the bottom, and wouldn't allow me to horizontally resize the two halves. And neither showed (in Settings) a way to change the interface selection!
Can anyone please shed some light on what's going wrong and how I can fix it. The attached server.log might contain a few server restarts.
![Name: LMS_bad_interface.png
Views: 36
Size: 147.6 KB]()
![Name: LMS_bad_interface(Chrome).png
Views: 30
Size: 133.0 KB]()
server.log
![Name: W10_SysInfo.png
Views: 30
Size: 14.6 KB]()
After spending hours Googling, trying stuff and not getting anywhere, I uninstalled LMS and reinstalled it from LogitechMediaServer-8.3.0-1658898470.exe.
After going through the setup and media scanning, for a short while I had my usual interface back. But after clicking <F5> (refresh), the odd interface shown in the attached screen-shot displayed in Firefox. Chrome displayed slightly better, but still didn't display the standard 'Classic' interface with a 'Settings' button at the bottom, and wouldn't allow me to horizontally resize the two halves. And neither showed (in Settings) a way to change the interface selection!
Can anyone please shed some light on what's going wrong and how I can fix it. The attached server.log might contain a few server restarts.
server.log