Install failed - Pipe is being closed

[Anonymous]

I've got a few users that for some odd reason, when they attempt to download/install the Inventor 2019.4 update, they are getting the "Install Failed - Pipe is being closed" error.

Why?

[Mark.Lancaster]

@Anonymous 

Where are they doing this from?  Desktop App?

[Anonymous]

@Mark.Lancaster, No, the exe file is on a shared network drive.

[Mark.Lancaster]

@Anonymous 

Sounds like a network issue at your end if you downloaded the update..

Copy the update locally and see if the issue is still there.

[Anonymous]

@Mark.Lancaster,

I've got the user attempting this as we speak.

I'll let you know.

[Anonymous]

Nope, same deal.

[Anonymous]

Can you post a copy of the log file it refers to?

[Anonymous]

@Anonymous, @Mark.Lancaster , See attached.

[Mark.Lancaster]

@Anonymous 

In researching this error it appears to be related to a registry issue or a missing entry in the registry.

You may want to run a registry cleaner (at your own risk).

Were there any other dot releases applied to Inventor?

[Anonymous]

@Mark.Lancaster, he's at 2019.1 currently.

[Anonymous]

What language is your Inventor set to? Looking at the install log it seems to be hiccupping on this particular language pack...

Product or related product not found: {7F4DD591-2364-0001-1029-7107D70F3DB4}

I wonder if downloading the English language pack would help?

https://knowledge.autodesk.com/support/inventor-products/troubleshooting/caas/downloads/content/inve...

Just a wild guess though as I haven't seen this error before...

[Anonymous]

It's set to English.

Other users have been using this exe file with this one user having this issue.

I've forwarded this all to IT in hopes they an dig into it deeper than I can as I don't dare mess with registries and such.

[Anonymous]

Actually, the value is not the same, it's slightly different - I was too tired to notice yesterday. 

Could you please let us know if your IT finds the cause of the issue, it could help future users with the same issue.

[Anonymous · Accepted solution]

Well, no idea what happened.

A repair install did not fix the issue.

Had to completely uninstall and then reinstall the application to get the update (4.3) installed.

All is running fine now.

[Anonymous · Accepted solution]

***Update***

Found out the actual root cause of this...the user did not disable his anti-virus prior to running the install process.

Ugh...never even thought about it since it's (what I thought) common knowledge.

Another lesson that you can never, ever take things for granted.