[PR #3711] [MERGED] Core: Include older Windows 11 builds in the address space workaround #3672

New issue

Closed

opened 2026-02-27 22:04:34 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 22:04:34 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/shadps4-emu/shadPS4/pull/3711
Author: @StevenMiller123
Created: 10/5/2025
Status: ✅ Merged
Merged: 10/5/2025
Merged by: @squidbus

Base: main ← Head: hotfix-addr

📝 Commits (1)

22469cb Include older Windows 11 builds in the address space workaround

📊 Changes

1 file changed (+4 additions, -3 deletions)

View changed files

📝 src/core/address_space.cpp (+4 -3)

📄 Description

I've received reports that older Windows 11 builds are affected by the same VirtualAlloc2 bug seen in Windows 10, so increase the build number we apply the reduced USER_MAX value to.

For now, I've hardcoded the build number used by Windows 11 22H2, to correspond with the fact that Windows 10 22H2 was affected. I've only seen issue reports for up to Windows 11 21H2 though.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/shadps4-emu/shadPS4/pull/3711 **Author:** [@StevenMiller123](https://github.com/StevenMiller123) **Created:** 10/5/2025 **Status:** ✅ Merged **Merged:** 10/5/2025 **Merged by:** [@squidbus](https://github.com/squidbus) **Base:** `main` ← **Head:** `hotfix-addr` --- ### 📝 Commits (1) - [`22469cb`](https://github.com/shadps4-emu/shadPS4/commit/22469cbac28b0ac8cd7456be4106aa8f37148448) Include older Windows 11 builds in the address space workaround ### 📊 Changes **1 file changed** (+4 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `src/core/address_space.cpp` (+4 -3) </details> ### 📄 Description I've received reports that older Windows 11 builds are affected by the same VirtualAlloc2 bug seen in Windows 10, so increase the build number we apply the reduced USER_MAX value to. For now, I've hardcoded the build number used by Windows 11 22H2, to correspond with the fact that Windows 10 22H2 was affected. I've only seen issue reports for up to Windows 11 21H2 though. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>