As a result of our continuous prevention analysis, we detected patterns of connection attempts that seem to be at odds with normal TeamViewer usage. As this observation was limited to a small subgroup of endpoints, TeamViewer decided to invalidate and automatically re-assign all TeamViewer IDs within this subgroup. My interpretation of this explanation is that, rather than take the time to hunt down the hackers that are attempting to break into the computer homes of unsuspecting users, TeamViewer has instead decided to change the metaphorical locks on all the doors without telling the owners or anyone else that has a spare key and leaving them to figure it out all for themselves. That'll show those pesky thieves! Way to victim blame! I really wonder how this decision is going to keep said hackers from continuing exactly as they have been all along, randomly trying out new IDs and attempting connections? Also, I can only assume that by changing a "small" subgroup of IDs without notice TeamViewer's metrics for measuring connection attempts just got skewed by the actual, legitimate users now having numerous failed connection attempts, rather than the previous [users with successful connection attempts + hackers with failed connection attempts] metrics that led us into this situation in the first place.
... View more