Forum Discussion
Joachim_Otahal
Feb 26, 2024Iron Contributor
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...
MSBernstein
Microsoft
Feb 27, 2024Hi, Joachim. Sorry you are feeling frustrated about this -- we do have a lot of different demands on our time in any given day; we are as human as you are. I work in engineering, not marketing. I'm trying to see if the de-dup team has enough data to diagnose this, given the feedback you've provided.
Thanks,
Michael Bernstein (MSFT)
Thanks,
Michael Bernstein (MSFT)
- Joachim_OtahalFeb 29, 2024Iron ContributorIf you want to look how it plays out with Server 2022 and nVext: I recorded a video which is on my home page https://www.joumxyzptlk.de/tmp/microsoft/S2022-Nested_Deduplication_VDI-Hyperv_profile_kills_filesystem_v2.mp4
Video was created on AMD Ryzen 5950 with Win11 as host, but is the same on Dual Xeon 6226R with Server 2019 (HP ProLiant DL380) as host.- MSBernsteinFeb 29, 2024
Microsoft
Thanks, Joachim! I attached that video to the bug report to provide additional context for the engineering team.- Joachim_OtahalMar 07, 2024Iron ContributorCould the engineering reproduce this bug, maybe even as easy as I can? I don't expect a fix so fast, but if they could reproduce it would be a good feedback.
- Joachim_OtahalFeb 29, 2024Iron ContributorThank you for your reply! The problematic part is actually it applies to Server 2022 too. I can reproduce it with both.