I would never accuse a single employee of being a bad supporter. I was referring to Stardock!

You write that these hints in the thread lead to success  - my experience is that under certain circumstances it then occurs again.

Finding out exactly what those circumstances are is determining the root cause. Now if you delete a whole folder with lots of files (C:\Programdata\Stardock\Fences\) you just know that the problem was somewhere in that folder. I've also been a software developer for ~30 years and an ISTQB-Certified Tester - that might explain my passion for pinning a bug

Now to get a little productive:

I didn't delete the whole folder at once, just the file "Cache.dat" which was around 900 bytes in size and an "Update" directory where "Fences.exe" was located.

That was unsuccessful - a day later, the update message and the "Cache.dat" file were there again.

Just one file is still there: "License.sig" 1054 bytes in size. I didn't delete it.

Lots of settings and data which will only fully understand by the devs ,are in the registry. You can find an export of this here:

https://ott-bs.de/bin/Stardock.reg

Hope this helps nailing it... Tell me if you need some other data... Thx!

Regards Sascha

Oh, right, the button is always there... I thought in combination with the "Stop update check" function it would be useful. Anyway - I don't need necessarily a GUI element if this is too much work - a working solution for stopping update checks would be enough.

What was asked?? 

Holy cow 🙄 I spare my time and stop talking with a "support" like this.