Forum Discussion
Solved
26063 deduplication data corruption is still there.
From Server 2022 up to this newest 26063 build, they all have the same problem, as described here: https://techcommunity.microsoft.com/t5/windows-server-insiders/server-vnext-26040-and-server-2022-de...
- Thanks, Joachim. I updated the bug report to note that 26080 is included.
Michael
2026 October build 29683.1000 - I can still perfectly reproduce this on AMD Ryzen 5950 and Intel Xeon 6226R... (on the latter as nested on host Server 2019 HPE DL 380 since customer which allows me testing).
Error is either Memory Management, or other random messages that some driver died.
I know the bug got "squased down since nested V not supported in this scenario", but keep in mind: I am running Server 2025 on this Ryzen 5950, and it happens on bare metal as well, without nested.
I still hope it will be fixed among the thousands of AI-discovered bugs, but for 2026-10 update: Not yet :D.