Error install Cumulative Update for .NET on Server 24H2 (0x80070bc9)

Hi robajz,

I'd focus on this entry in the CBS log:

System Protection / luainstall.dll / 0x80070003

Right after that, CBS reports 0x800F0922 and rolls back the update.

The first error points to a missing path, but the screenshot doesn't show which one. That's what I'd investigate next, rather than running DISM or clearing the update cache again.

Can you post around 30–50 lines from CBS.log immediately before the failure at 07:32:02? Preferably as text, with any sensitive information removed.

I wouldn't touch the servicing registry or pending files until we know exactly what's failing.

On other thing worth checking is the Windows Modules Installer service configuration:

sc.exe qc TrustedInstaller

I'm not suggesting the service is necessarily the problem, but it would help rule out an unusual startup configuration.

Your Server 24H2 VM has repeatedly failed .NET servicing despite cache resets, DISM, SFC, and pending-reboot checks. Error 0x80070BC9 means the operation requires a reboot to roll back changes; it does not identify a particular defective update by itself. Microsoft documents a persistent case involving pending servicing and corrupted transactional entries. Compare your CBS log around the failed installation with that documented signature, particularly failures to obtain transaction state. Since you already performed the basic repairs, repeating cache resets is unlikely to provide useful evidence. Record the DISM/SFC outcomes and the relevant CBS sequence, then involve Microsoft support if the signature is unclear. For the documented transactional-corruption scenario, Microsoft recommends an in-place upgrade. Plan that repair only after a verified, application-consistent backup and compatibility review. Do not delete servicing registry entries or pending files based solely on the error code.