# Defunct install code usage claims, seems fishy

**URL:** <https://the.fmsoup.org/t/defunct-install-code-usage-claims-seems-fishy/305>\
**Category:** Lounge (Discussions)\
**Created:** [August 20, 2019, 8:19pm UTC](https://the.fmsoup.org/t/defunct-install-code-usage-claims-seems-fishy/305 "2019-08-20T20:19:15Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![anon45965781](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@anon45965781](https://the.fmsoup.org/u/anon45965781)\
**Post date:** [August 21, 2019, 10:10am UTC](https://the.fmsoup.org/t/defunct-install-code-usage-claims-seems-fishy/305/21 "2019-08-21T10:10:42Z")

</div>

INITIAL IDEA -- Set up a firewall rule to keep FMS from phoning home.

_UPDATE: Later I read that keeping FMS from phoning home could make it stop working or, worse yet, getting a call from FMI sales. Therefore, the idea of using a firewall to stop phoning home ... evolved over time to appear to not be workable from that new information._

I can not find where FMI states, in writing, what it uploads and states how I can OPT OUT of that data collection.

* * *

Windows 10 is another prime example you can't disable phoning home (except Enterprise version) where the first part of any Windows install is a registry hack and firewall rules creation.

---

_[View the full topic](https://the.fmsoup.org/t/defunct-install-code-usage-claims-seems-fishy/305)._