twlesno.blogg.se

This goes on for more than an hour taking up 22 GBs – talk about a tiny deadlock! 20:18:37, Info CBS Lock: Error found, inverse lock order, current lock held: CCbsSession, level: 66, lock attempted: CCbsWorkerQueue, level: 60. 20:18:37, Info CBS Lock: Error found, inverse lock order, current lock held: CCbsExecutionCommunication, level: 130, lock attempted: CCbsWorkerQueue, level: 60. 20:18:37, Info CBS Exec: Asynchrous operation, session completes later 20:18:37, Info DPX Ended DPX phase: Resume and Download Job 20:18:37, Info DPX CJob::Resume completed with status: 0x0 20:18:37, Info DPX Ended DPX phase: Apply Deltas Provided In File 20:18:37, Info DPX Started DPX phase: Apply Deltas Provided In File 20:18:37, Info DPX Started DPX phase: Resume and Download Job 20:18:37, Info CBS Session: 30539793_3012262845 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null It seems like that there was "some" deadlock. Looking at the CBS directory, back from when the KB3176934 was failing I see a 22GB (!) log file. If someone already has a solution – even better. My purpose is to find other who has exactly this same problem and figure out a solution. I didn't find out the root cause and how to prevent it. Some days ago it was repeatedly failing KB3176934 with the same 0x800F0922. So this is a Windows 10 Pro 64 bit version 1607 system, Insider edition on a slow ring.