First of all thanks a lot for your fast feedback! ![:great:]( "Great")
We basically think that the problem is related to Windows or a Third-Party tool we use in our environment which maybe access the rainmeter.ini in the time Rainmeter tries to start. That would also explain why it happens only sometimes on a client.
After the error message has been acknowledged Rainmeter starts automatically and doesn't need to be started manually - but that's maybe part of the starting process of Rainmeter I think.
We enabled debugging mode and maybe we can see here some more information what's going on. So we keep up monitoring the issue and trying to find the root cause of it - if we found it, we will tell you. Unfortunately we see no alternative to Rainmeter so we want to keep it installed on our clients.
We basically think that the problem is related to Windows or a Third-Party tool we use in our environment which maybe access the rainmeter.ini in the time Rainmeter tries to start. That would also explain why it happens only sometimes on a client.
After the error message has been acknowledged Rainmeter starts automatically and doesn't need to be started manually - but that's maybe part of the starting process of Rainmeter I think.
We enabled debugging mode and maybe we can see here some more information what's going on. So we keep up monitoring the issue and trying to find the root cause of it - if we found it, we will tell you. Unfortunately we see no alternative to Rainmeter so we want to keep it installed on our clients.
Statistics: Posted by sw-deploy — 4 minutes ago