You don't have to disable all wake timers. Bring up your Task Manager (CTL/ALT/DEL and select Task Manager) and identify Teamviewer running as a process in the background.
Bring up an Admin Command Prompt and type in...
powercfg -waketimers, it should provide all the wake timers activated on your system. Teamviewer will probably be listed there.
The most recent update to Teamviewer has included the software to run as a process in the background even though you have not opened Teamviewer or have it starting up at the start of Windows as a program. However, it is starting up as a "service".
Type "Services" into your Windows Search bar and go to the application in PC Settings. Find Teamviewer, right click and select properties. You want to first "Stop" the service and then change the start up to "Manual". Then, restart your computer.
Repeat the step in the first sentence in your command prompt and Teamviewer should no longer be listed as a wake timer. This way should still allow you to use Teamviewer but now you have full control on whether it stays open as a process. It also allows you to keep any other wake timers if you choose for other maintenance programs.
I had the same issue myself after upgrading to Windows 10 Pro but I also remembered updating Teamviewer. I used Admin Command Prompt to check my last wake (powercfg -lastwake) and sure enough, it was Teamviewer. I also tested opening Teamviewer and exiting it after performing the solution and it will no longer run as a process in the background.
HINT: You can always go to your Task Manager and see what is running as processes in the background.
IonIan11 :
So, I recently updated Teamviewer to the latest version (10). Since then my computer has been randomly waking up between 5 minutes and an hour after I put it into sleep mode. This has happened 4 times now. According to event viewer, the computer was woken by 'Timer - generic' all 4 times. The 'WakeTimerOwner' is "\Device\HarddiskVolume3\Program Files (x86)\TeamViewer\TeamViewer_Service.exe". I have not done anything with Teamviewer's 'Wake on LAN' feature, and really have no idea how this has been happening. Any solutions would be appreciated. Thank you so much!