We have confirmed this issue was caused byKB5032288andKB5033375.

This issue is not likely to occur on home networks.

At the moment, the issue only affects Windows 11 production builds.