Same issue here across multiple sites after the latest plugin update. Deactivating and reactivating 2FA for the user is the temporary workaround, but that requires temporarily disabling WordFence via the filesystem to login in the first place.
Same issue here. After troubleshooting, I found that going to the “Advanced” tab in the plugin’s settings and selecting “Use Default Settings” next to “Advance Cache Fix” solved the issue.
