Server 2025 Hyper-V deduplication corruption is still there

I can still reproduce this with 100% confidence on two VERY different machines and hosts with my "easy to reproduce" package:

 - AMD Ryzen 5950 with Windows 11 23H2 (self built)

 - Dual Xeon 6226R with Server 2019 (HP Proliant DL 380).

As I posted quite often now: If you use deduplication for Hyper-V, i.e. where the virtual machines reside, you will get data corruptions, your virtual machines will crash, and you may even get a filesystem corruption on the drive hosting the machines.

For more details see here: 26063 deduplication data corruption is still there. - Microsoft Community Hub

As for now: If you used deduplication in Hyper-V scenario, like you used it with Server 2012 up to server 2019, don't bother with Server 2022 and Server 2025 until that bug is fixed.

My offer still stands for a live demonstration how I reproduce and talk about the differences how Microsoft tried to reproduce this and how I reproduce this.

This is the result for "right about now" albeit without "funk soul brother"...