As mentioned in this earlyer question of mine from 2023-06-xy, I am using the same installation of my current version of LibreOffice with two different user profiles under Win 10.
- The first one uses the default path ending with
\Roaming\LibreOffice\4\user. - The second one uses the path
\Roaming\LibreOffice\clean\user. - The second one is called via a link with the correct
-env:setting.
One of the reasons for working with two profiles is that I use the default profile also for “preserved” and rarely needed templates, and for lots of Basic code, while the clean profile only contains what I always need, (and one additional template). I often use both profile versions at the same time.
This is when I am logged-in with admin rights.
This worked flawlessly for a long time now, and all LibO version updates were done the standard way once “for all users” in one go.
Since about a week now reproducibly the following happens if I try to run LibO with the “clean” profile :
- The well known LibreOfiice imagelet shows in a short flash.
- Then Win asks for permission to allow a “verified”
update.exelocated in a new -partly cryptic- subfolder of myAppData\Roamingto change the system. - After I have denied, LibreOffice opens with the deault profile.
- Whether having closed this instance or not, A next call for LibO with the clean profile results in the creation of an instance with the clean profile as expected.
Current version: 25.8.2.2
Any clue what might be the reason?