This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I´m getting this error since a couple of weeks now on every fresh installed device.
Office 365 Updates are showing up in Software Center but the download does not start because of the error 0x80040154
A quick internet search leads me to this solution:
http://sccm.ie/how-to/78-sccm-office-365-update-error-0x80040154-2147221164-class-not-registered
After I run the PS Script everything is fine and the O365 Updates are getting installed but in the end I´m not quite happy to have to run a repair script on every fresh installed device.
I´ve seen that this error is popping up here and there for a couple of years now and my question is if there is somebody who knows another way to get rid of that? Eventually a trick while doing the Build & Capture of the image?
Actually I´m using SCCM 2010, W10 20H2 19042.804 and Office 2002 (12527.21504)
Thank you,
best regards
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(102.4, 99%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
I had this error on a lot of our machines, most of them was HP Elitedesk 800 G4.
I've tried the MS script that re-register the COM object's but it didn't help.
After lot's of troubleshooting I found the root cause on our machines.
HP have a driver that install a HP Analytics service on the machine that prevent access to "Component Services - > COM+ Applications"
I added two lines in the top of the MS Script and deployed it to all the affected machines and the error diapered.
$svc_name = "HpTouchpointAnalyticsService"
Get-Service $svc_name | Stop-Service -PassThru | Set-Service -StartupType Disabled
BR
Stefan
Hi @PuDerBaer ,
We may not have to run a repair script on every fresh installed device, there might be two methods to achieve it:
1.using task sequence. It has been provided in your link. We could try this method.
2.deploying powershell script simply by sccm. We could refer to this link:
https://systemcenterdudes.com/sccm-deploy-powershell-script/
Note: This is non-official Microsoft article just for your reference.
Besides, we could install the office 365 update on a PC manually to check if it is normal. If not, it seems there is something wrong with Office 365 update.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @Amandayou-MSFT
thank you for your answer!
Yes of course there are several methods to run a script to get everything fixed.
But my question is why do I have to delete and re-create the COM+ App OfficeC2RCom on a completely fresh installed machine?
Btw there are several other methods to fix the problem. I can manually remove and re-install O365 or I can install the O365 Update manually on the device. After that the updates are deploying via SCCM again.
But, no viable solution for a couple of thousand devices.....
Hi,
no viable solution for a couple of thousand devices.....
We could deploy the script to thousands devices, and once the client have received the policy, the powershell could be run in every fresh installed machine, please refer to this screenshot:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 93%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
Did you ever get a valid answer to this as to why it happens in the first place so we can prevent it? Running the script is a workaround but we need to know how to prevent the error from occurring at all. It should not be happening on newly installed O365 computers, still a decade later.