You may have received an upgrade to your Roku software, and you just need to restart your Roku. [Note: If you have a Roku TV with "Fast TV Start" enabled, turning it off/on just puts it in/out of a standby mode and does not give you a full restart, sonuse the methods below.]
Depending on your Roku model you'll find the "System restart" option under "Settings > System > Power" or if you don't have a "Power" option, under "Settings > System".
If a restart doesn't do it, or if you don't have sufficient control with the remote to navigate the Roku menus, you can also restart by pulling the power plug to the Roku for a few seconds then plugging it back in and waiting for it to restart.
That fixed it. Thank you.
I followed these steps posted and did the system update and the system restart and it worked (so far!) My express started doing this a couple days ago. Thanks for the post in how to get it to stop skipping over channels
Both of my Roku remotes are doing this too. It is infuriating! I’ve had to resort to using the Roku remote app, in order to change channels, etc. Considering MANY of us are experiencing this…you might want to FIX it, Roku!!
I have been having the same issues, I have a Roku stick on one regular tv, worked fine before, now skips, randomly.
in the main app selection menu it is fine, but once in day peacock or Hulu it skips so certain accou s I can’t use, but prime i tried and it’s fine there.
not sure why or how, but this is annoying
See if this post helps: https://community.roku.com/t5/Remotes/Remote-skips-or-jumps-over-multiple-channels/m-p/893028/highli...
Restarting the Roku fixed my problem.
Whew hew.. Thank you. System restart worked
None of the solutions worked shown here. I have been having problems with two Roku LT Ethernet boxes that jump for every keypress. First one started, then another. It might be a firmware issue. This is a total pain in the Arse. Suddenly, Tech issues require me to blow a bunch of time fixing their issues, as usual.
System restart seemed to work for one, but minutes later, it was back to the same thing. This is most likely a firmware issue that came up with an update.