LibreOffice 7.5 on Windows 7

[SiliconWizard]

Has anyone else updated LibreOffice to 7.5 lately and running on Windows 7?

I have, and while I had absolutely zero problem with earlier versions, 7.5 has introduced major display bugs on Windows 7 - encountered them both in the Calc and Writer.

[Karel]

Have you checked this: https://www.libreoffice.org/get-help/system-requirements/

and specially this: https://wiki.documentfoundation.org/ReleaseNotes/7.1#Windows

[SiliconWizard]

I had updated my OS up to the latest updates before they stopped support, so yes I certainly have updates dating back to 2015.
Anyway, those are security updates, they have nothing to do with the display bugs I am encountering.

[coromonadalix]

do you have this KB,   even some kb updates  don't always install automatically,    Ie  you have to manually install some of them

 KB3063858 update

you have open office too    btw  ??

[SiliconWizard]

It is indeed installed, although I'm still wondering what possible impact a security update could have on display artefacts in LibreOffice. And no, I don't have OpenOffice installed.

One thing that came to mind is that the JDK I have installed is a third-party one, Liberica JDK. Didn't cause any issues before LibreOffice 7.5, but could this be the culprit?

I tried: unchecking JRE in advanced options, and messed around with graphics settings. Tried disabling Skia, but it didn't change a thing. Tried software rendering for Skia, didn't change a thing.
When I execute the graphics tests (display options), I get a number of "weird" results.

Example of artefacts I get, when importing a csv file. (Attached, img 1.)
Another one is that when double-clicking in a cell in a spreadsheet, instead of highlighting the content, the content becomes blank (invisible) until I deselect it.
Another one is when opening some odt documents, the text is all over the place. Seems to be particularly happening when there are images inside the document. (Attached, img 2.)

[SiliconWizard]

Updating the NVIDIA driver to the latest available version fixed the issue.
The previous driver version I had installed was definitely not that old. It was from early 2022.