Why does activated Fences keep trying to phone home even after reg entry?

from Stardock Forums

If fences.exe knows it's blocked (it is), and knows the app is registered (it is), and knows the registry entry is set (it is) then why in the world would it continue to try to phone home?  

In this case Stardock is trying to hit activate.api.stardock.net port 443 using explorer.exe (!!!) after we've blocked fences.exe and followed the Stardocks instructions for preventing further "update checks" through registry entry.

This seems like very bad behaviour.  

We've registered, activated, and don't want the app going outside of the network for any reason. 

Is there no way to accomplish this? 

 

 

fences
9,978 views 4 replies
Reply #1 from Stardock Forums Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

AzDude
Stardock Community Assistant

Reply #2 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

We've registered, activated, and don't want the app going outside of the network for any reason. 
End of quote

Fences, as does all our apps, will phone home to ensure it still has a valid license.  As I am sure you are accustomed, this is a standard practice for software.

In this case Stardock is trying to hit activate.api.stardock.net port 443 using explorer.exe (!!!)
End of quote

Because Fences runs in the WinExplorer process. 

Sean Drohan
Stardock Support Manager

 

Start11 - Customize the Start Menu and Taskbar in Windows 10/11.
Reply #3 from Stardock Forums Top

Rohan, 

Stardocks licensing/activation process is pretty secure from what I've seen. Is it correct that before a second computer could be activated with the same license key, that previously activated license would need to be released/deactivated? So no need to check if any specific license is "valid" because one way or the other the license is made 1:1 for a single device and is either in an activated or ready-to-activate state. It is nice of Stardock to create that process to migrate the license though.

Very unethical to attempted to hijack a ride out through WinExplorer when you've previously attempted through Fences.exe unsuccessfully.  The only reason fences runs in WinExplorer is to do the job it's purchased to do. That decision specifically seems like a huge legal risk for less than $10 license. EULA's aside, the only thing I've ever seen attempting to hijack a way out through explorer.exe like this is Fences and actual malware/viruses. 

You should also consider being more transparent with users when giving them the HKCU "fix" to stop the update checks and phoning home. The "fix" doesn't stop the phoning home, it just stops reporting that it has. Tricky! :) I'm sure Stardock knows the intent of the users on these forums requesting this solution is not so much to stop the nags, but to polietly ask you, as customers, to stop you from phoning home from a program that has been purchased, registered, and fully activated.

 

 

Reply #4 from Stardock Forums Top

Jaypub,

I think you believe this to be more sinister than it actually is.

Quoting jaypub, reply 3

You should also consider being more transparent with users when giving them the HKCU "fix" to stop the update checks and phoning home.
End of jaypub's quote

We are:

https://forums.stardock.com/486084/fences-support-faq#disableupdate

Quoting jaypub, reply 3

The "fix" doesn't stop the phoning home, it just stops reporting that it has. Tricky!

End of jaypub's quote
 You seem to be conflating the version update check with the phoning home of having a valid license - they are entirely separate things.  We make no claim that it will stop a perfectly legit phone home license check process.  Again, this is a standard practice for software.   

Thank you for your feedback.

Sean Drohan
Stardock Support Manager