KB4469342 Windows 10 Insider RP v1809 Build 17763.168 - Dec. 3  

Must be trickling out. Just got .168 on an RP in a VM thru WU. (too many acronyms!).

f14tomcat said:

Must be trickling out. Just got .168 on an RP in a VM thru WU. (too many acronyms!).

Does anyone know what this CU purports to fix or do, or what enhancements it has.

magilla said:

Does anyone know what this CU purports to fix or do, or what enhancements it has.

Yes. But they aren't telling anybody who wants to know. Shawn will squeeze it out of them.

glacourse said:

you mean they may have one that';s not broken this time?

It is working fine for me.

I couldn't reboot my Surface Pro 3 after manually installing the .cab file provided in earlier posts here. Eventually, I got the machine to boot by linking to a recovery UFD at boot-up, then running startup repairs. After that, the usual rollback to previous release worked. Still on .167 on that PC. Just fired off WU through Settings and the CU is now being offered to this PC. I'll report back on whether the update is successful or not. This one's been a bit of a roller-coaster for me.
--Ed--

[PS added 4 mins later] The update via WU worked like a champ: no issues whatsoever. Winver now showing .168, everything appears to be working OK. Will run DISM /startcomponentcleanup next and report on findings, then clean up and backup will follow.

[PPS added 15 mins later] Things keep breaking weird on this update. Saw a new error in DISM when I tried running startcomponentcleanup: sez "The operation cannot be performed because another transaction is depending on the fact that this property will not change." WTF! After a reboot, startcomponent cleanup jumps instantly to 20% complete, then marches into the low 80-percents, where it is currently sitting at 84.0% complete. I'll report further if it doesn't complete successfully. Something, however, is indisputably odd about this Cumulative Update -- on my Surface Pro 3, at least!

The error code, according to this MS Docs article is properly labeled Error_cant_break_transactional_dependency:

I've noticed that sometimes running startcomponentcleanup caused two progress bars to appear, one that stops short of 100% and a new one that kicks off and usually runs to completion. Could it be that a second process gets spawned when the first one hangs and that this time they conflicted with one another? Hard to think of another more likely cause here. Very interesting. The second attempt at startcomponentcleanup is still chugging along, now almost 30 minutes in, and is at 88.4% completion.