Advertisements I received this update yesterday (Friday) afternoon sometime. Last night when I got home I checked to see if update was received and network connection said pending restart. Since I had nothing being recorded at the time I did the restart. After restart everything looked OK. I record the 10P local news every night and then watch it from behind about 10 minutes to cut out the commercials. While watching the news from behind (it was still recording) the Tivo rebooted on it's own for no apparent reason. When it came back up I checked network connection and it had a successful connection at about 915P and the next connection would be at 10:50p. I thought that was a little bit weird. But I finished watching the news and went to bed. This morning (Sat) I was watching a recorded show (nothing being recorded at the time) and it rebooted again. After reboot I checked network connection and it had a successful connection about 45 minutes earlier (I guess that's what caused the reboot. Next connection was in about 45 minutes. After that successful connection it rebooted again with a network connection due in about an hour. It looks to me, like it's going to continue the connections and reboots from now on no matter what I do. Have never seen this happen before with either TE3 or TE4. I guess if I can't get it to stop I will have to go back to TE3 and see if that fixes the problem. FYI - I have a bolt vox which came with TE4 in Jan of 2018, but I downgraded to TE3. Have had TE4 since Feb and have had no problems at all (other than this). Any suggestions or help to fix this problem would be appreciated. I'm not going to spend the time on the phone with Tivo support, if I can't get it to stop rebooting I guess I'll just go back to TE3 and lose the few recordings I have. Update: Since posting my box has rebooted 7 additional times, always after a network connection. I have now disabled wifi (and ethernet) and did power reset to Tivo and tuning adapter. I am going to see if that somehow will fix the problem. It looks like no one else on this version has had this problem, but I can assure you it relates the v6 update I received last night. Prior to that everything was OK.