So this is a really odd little bug, and I swear it didn't exist before the latest Xbox One update. But when Button.DPadUp is pressed it is also "pressing" the key Keys.ChatPadOrange. Honestly I have absolutely no use for Keys.ChatPadOrange so I just manually adjusted my code to ignore this key.
It's really not a huge deal, but the reason it surfaced for me was because I had a place in my game where I'm handling scrolling through menus and checking what the most recent button/key down event was, well since the most recent was Keys.ChatPadOrange it made it so scrolling didn't work with DPad Up. So based on what peoples input handling setups are it could definitely have an impact, so I thought I'd bring it up.