BCD memory Badpages doesn’t seem to work on Windows 11 (25H2).

I have a faulty DDR5 RAM module that always errors at the same physical addresses. I know the general process: run MemTest86 Pro, export the failing addresses, then add them to the BCD store using badmemory / badpages (so Windows should avoid those pages).

On Windows 11 25H2, I can add the addresses and I can query them back (so they are stored in BCD), but Windows does not appear to actually exclude/avoid them during use. On Linux I can solve this, but on Windows I can’t.

Questions:

1. Is there any known change/limitation in Windows 11 (especially 25H2) that prevents badpages/badmemory from being enforced?
2. Are there any specific requirements (Secure Boot / memory integrity / VBS / Hyper-V / kernel DMA protection, etc.) that might stop it from working?
3. What alternative approaches exist on Windows to work around a small number of consistently failing RAM addresses?

Replacing the RAM is not an option for this project. This is not a productive/production environment—it’s a fun gaming PC project. I would never run a system like this in a critical environment.

Thanks in advance.