This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello,
I had a recent windows update on 15th January 2025. I have an update failure showing for - Dolby - SoftwareComponent - 3.30702.720.0 - Install Error - 0x8007013
Anyone else experienced this or any advise as to how to resolve?
I have tried running the updates again but get the same result.
Thanks in advance.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi, I am Dave, I will help you with this.
That is a problem many people report with the drivers that Windows Updates tries to install, if that update is continually failing, then the best option is to use to official Microsoft Show/Hide Tool to hide that driver update to stop Windows continually trying to install that driver.
I was curious if you ever got the issue resolved. Any idea if this is an issue Lenovo or Microsoft will correct. What's odd is it shows up in the Update history??? I've tried most of what's mentioned in this blog to no avail. Went so far as to reinstall windows 11. A bit extreme but never the less. Maybe time will take care of the issue.
Jeff
I solve with this 😀
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
