The settings tab on both of those say Read Binary File node version 1 (Deprecated). Deprecated is normally supposed to mean “still supported, but may be gone soon.” In this case I think it means “is most likely broken so use the new one instead.” The only difference between the two is the top one includes "alwaysOutputData": false in the underlying JSON, which maybe makes it incompatible enough that it doesn’t work in recent versions of n8n. In any case, the Read Binary File node is gone. It has been replaced with the Read/Write Files from Disk node.
n8n development is very active and new/changed stuff is being released constantly. I’m sure the devs make a best effort to keep things backwards compatible but it’s not always possible. So, as a rule with n8n, any time an older workflow or node doesn’t work quite right, one of the first things to try is to create a brand new node of the same (or congruent) type, transfer over the parameters, and delete the old one.