

The last time I put together a puzzle, on the box it said 3-5 years…
Only took me about 2 hours
2026 CT5 350T(nm) AWD
It looks great! It’s practical. Fits 4 large Americans just fine. Plenty of truck space. Interior quality is decent-ish…
What I don’t get is who this actually for. In terms of luxury, it’s still very much entry level. Even with the “updated” interior for this MY it’s still not great. Performance is abysmal! The turbo 2 liter is weak AND requires premium fuel AND barely gets 25 mpg when driving ultra conservative.
The infotainment had a much needed upgrade BUT you can’t fully enjoy it unless you have an Android or sign in directly. Otherwise, if you want to use Car Play, you still have tiny real estate with massive bezels. Many other car makers have implemented better alternatives. That being said, I will highly praise Cadillac for keeping the physical climate control buttons!!
Anyways. Thoughts?
CcmSetup failed with error code 0x80004005
Client Version: 5.00.9146.1009 (upgrade)
Site Server Version: 2603
Since doing the Site Upgrade, I've been encountering several instances of endpoints exiting the ccmsetup client upgrade with 0x80004005
So far in my testing, if I run ccmrepair, the issue appears to self-correct. In addition, and this is the weird part, Windows throws the compatibility assistant asking if the install completed as expected or not.
I recall running into this a few times in the past but I'm 2/2 already.
I understand the difference between running in user and system context, but if I run a ccmrepair remotely from the Primary Site, should I expect the same result (but without the compatibility assistant dialog)? Has anyone else encountered this?
Upon drafting this, I'm reminded of a similar problem with deployment timeouts when the IP changed between eval cycles. Could this be related?