That's Not Supposed to Happen - Autodesk Vault 2012 - 1328 Error Installing Update 1

“A sudden, bold, and unexpected question doth many times surprise a man and lay him open”
Francis Bacon, Sr.

Recently, I was adding Update 1 to Autodesk Vault 2012.  I've done it plenty of times.  Should be a walk in the park, right?

If this install were a walk in the park, I wouldn't be spending the time writing this post! 

I run in the install.  And I get this error:

Eh?  What the?

Windows installer error 1328?  Error Applying Patch?  What? 

I check, I double check.  I double check the double checks.  Vault 2012 hasn't been updated.  It's still at "Update 0".  So it can't be "updated by other means"!

Does the user have Local Admin?  Check!

Virus scanners off?  Check!

UAC off?  Check!

Eh?  

I resort to the "Big Stick" in an Application Engineer's arsenal.  That's right.  The I call in the geek's equivalent of a B-52 air strike.

I Google it.  

Now, little Windows error... You will die.

I find the following blog post in, "Cracking the Vault" that tells me this isn't the first time it's come up. It's a *.dll file that's acting up.  Apparently it only affects "Vanilla" Vault.  The licensed versions (Vault Workgroup, Collaboration, & Professional), aren't affected.

But the good news is, I know that I'm not alone in the dark.  Now, how to fix it?

I try another Google search, then another.  After a few minutes, I have my solution.

In my best "Darth Vader" voice, I say: "I have you now!"

Except this time the perky rebel gets it.

It's found on the Autodesk discussion group, here. Near the top of the page.

It's a new *.dll!  I download it, do some swapping of files, and all is suddenly good. Progress bars move and hard drives whirr musically.

So to use a buzzword out of the corporate dictionary, what's the "take away"?  The "call to action"?

1. The obvious one.  If you run into this error, here's one way to solve it!  That's why I wrote this!
2. Google is your friend.  It can help you find documented solutions, even some undocumented solutions.  Although be careful with those, sometimes they can get you in trouble!

This is also one of those things that shouldn't be needed unless you actually run into the error.  So don't start swapping *.dlls because you can.  It's a "when necessary tool".

But when you're pinned down, it can be just the ticket to get you out!

UPDATE!  New hotfix released to repair this issue!

In my travels about the web, I found this hotfix that addresses this issue.  If you get this error (or one similar).  Install the hotfix found here!