Well after some investigation, i found out that the "LayoutSwitcher.ini" file is probably the one causing all this stuff, because it's "Date of change" is 31.5.2025 13:09, which if i am not mistaken, this is basically when the looping started again, because the last few days the looping started happening everyday, for now i edited the file "systemColors.ini" (which it's "Date of change" was 11.06.2016) and the looping for now it's not happening, but i am gonna wait few days if it happens again, and i am gonna check if the "Date of change" of the "LayoutSwitcher.ini" file is changed again, then if it got changed, then i am gonna edit the file so i can be 100% sure that this was the file causing the issues, and to be sure that this is not happening againAs for [MeasureRunSetLayout1] (running xcopy) which triggers [MeasureRunLayout1Confirm] (running mshta) and similar, they are only triggered to run from the context menu of that skin, see ContextAction5 from that skin's [Rainmeter] section, so it can't technically produce a loop. That being said, having Update=1 in the [Rainmeter] section of that skin, is definitely not recommended (and confusing from the start, since in practice the lowest possible Update is 16 ms), unless the skin is animated or needs near realtime reactions, which I doubt it's the case. Sure, almost all measures there have UpdateDivider=-1 so the impact of Update=1 is more or less canceled, but you can, if you want, set that Update to a typical value of 1000 and see if there aren't any functional drawbacks to that.
I imagine there are other inconsistencies (probably not critical) in the said suite, but well, the code particularities are the skin designer choice and you can't guarantee that everyone is fully aware of the consequences of various parts of a code.
Statistics: Posted by Mario_Kunchev — Yesterday, 8:38 pm