Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Flash update - Install failed. Fatal error during installation HRESULT: 0x80070643

I recently updated Patch Manager and applied the Microsoft KB2720211 Update. I generated a new self-signed cert and distributed it out to all PCs.

Since then it seems updates are only goin in on some PCs.

I push out a recent Flash Update, it gets downloaded successfully, but its installation is failing on 7 of 35 PCs with the error, Install failed. Fatal error during installation HRESULT: 0x80070643

This seems to be a generic error, any ideas?

Find more posts tagged with

Accepted answers

LGarvin

The 0x80070643 error is a generic MSI failure message, and is not related to the publishing certificate. (A publishing certificate issue would actually prevent the download of the installation file, thus it would never even get the chance to be launched.)

Generally when an MSI/MSP installation fails via the WUAgent, launching it interactively can sometimes provide feedback on the reason for the installation failure. If not, then enabling WMI Logging (which can be done with the Patch Manager "Check and Manage Computer Connectivity" tool and re-running the update deployment should produce a detailed installation logfile that can be used to identify the reason for the installation failure.

All comments

antwesor

I am still in the process of deploying the 2048 bit signed cert. Almost complete. I noticed that I did have to make sure when publishing patches to make sure it removed the 3rd party patch if it existed to get the 3rd party patch to the clients. I am slowly adding 3rd party patches as needed. I did have to decline all the patches and if I need to get an old 3rd party patch out there I tend to re-publish the package with the option to replace the existing patch if it exists and that has seemed to work the best for me.

Try republishing the flash update and see if that works.

LGarvin

acopian

Thanks for the information.

You were correct, by running update from PC manually, it informed me that Internet Explorer must be closed to install. I cancelled out, closed IE, and then wuauclt /detectnow to reinstall from WSUS. This time with IE closed the update went in.

So I assuming on the failed PCs, the user had IE open at the time the update was trying to install. Funny how I never had this happen with previous Flash updates.

Thanks again for the solution.

Joe

LGarvin

I've not seen that issue before either. I've forwarded this thread to our package creation team to look into this and see if we need to enhance how we build those packages.

In the interim, if you want to override this behavior, PackageBoot can be used to terminate the open IE sessions so the update will install.

The JRE packages have example code on how to terminate iexplore.exe.

LGarvin

What operating system, service pack, and version(s) of Internet Explorer did you encounter this behavior with?

Was this an upgrade or a fresh installation of Flash Active X?

if an upgrade, what previous version(s) of Flash were installed and what versions(s) were you installing?

acopian

It is a mixed bunch.

I have only confirmed that closing IE worked on 1 PC I was testing on, it was an XP SP2, IE8, and the Flash version was the most recent previous version, 11.3.300.270

5 of the PCs experiencing the issue were on XP SP2, IE8, Flash 11.3.300.270

2 were Windows 7 SP1, IE9, Flash 11.3.300.270

I'll be testing/updating the other PCs shortly and I can report back.

Joe

LGarvin

Thank you for the reply.

I notice that 5 of these 7 systems were on Windows XP Service Pack 2 systems, and they all were with an older version of Flash.

If you're able to reproduce this behavior with the Flash v11.4 package, or on a Windows XP Service Pack 3 system, we would definitely be interested in looking at it further.