The same can be said about Rockstar Games’ Red Dead Redemption 2, which at some point, became unaccessible for Windows 11 users running version 21H2. If you have low FPS while playing RDR2, we can show you how to fix it, regardless of the CPU you are using on your rig. Also, we’ve prepared a list of the best VPNs for playing Red Dead Redemption 2 Online (RDO), in case your country is not on the supported list.

Microsoft announced that the problem is fixed

There’s no hiding the fact that when Windows 11 version 22H2 first hit, there were plenty of user reports online regarding issues related to gaming on the new feature update. Soon after, Microsoft confirmed the problems and placed upgrade blocks on affected systems. These issues were finally resolved by around mid-December when Microsoft pushed KB5020044. And, while Windows 11 21H2 was considered a safe version, it looks like the roles are reversed now as Rockstar Games’ Red Dead Redemption 2 failed to launch on the original Windows 11 release. The problem was triggered when attempting to launch the title from the Rockstar Games Launcher wherein the game does not open when selecting the Play button from the Launcher. The tech giant stated that the only workaround to mitigate the issue for those affected was to upgrade Windows 11 21H2 systems to 22H2. In truth, this pesky issue actually began with the KB5023774 update that was released earlier today. However, you don’t have to worry about that anymore. Now, Microsoft confirmed that the issue has been fixed with the latest game update. On the Windows release health dashboard, the Redmond company updated the issue status to resolved. Thus, after updating to the latest version of the game, you should be able to open it as expected. This can be done from the Rockstar launcher and it usually happens automatically. That being said, users should be able to launch the game via the Rockstar Games launcher on Windows 11 21H2 as well. Have you encountered any other problems with RDR 2 on Windows 11? Be sure to share these findings with us in the comments section below.

Name * Email * Commenting as . Not you? Save information for future comments
Comment

Δ