Windows Server 2025 24H4 is not useable anymore after Nov. Update KB5068861

Yep, we are seeing this same exact issue and symptoms as ArnDal. We noticed that its specifically when the 2025 server VMs are clones of each other. Sometimes we clone servers, then on the new server VM before its connected to the network, we change its name and join a workgroup. We then change the IP, connect the VM to the network and join it the domain with the new name. This is when we see this problem on these type of cloned machines.... they cannot talk to each other over UNC path (SMB). It does NOT happen if we use two manually created Server 2025 machines without cloning. We believe it has something to do with the computer SID, which you can see with this command: 

(Get-LocalUser -Name "Administrator").SID.AccountDomainSid.ToString()

The only fix we have found so far is to sysprep at least one of the machines (so they're no longer duplicate SIDs), but that can be very disruptive to an IIS web server because all the app pool passwords and configs get wiped out.