VS 2008 64 bit setup project msi not auto healing / auto-repairing!

Question

0.00/5 (No votes)

See more:

A little back story:

I found that when my nifty installer was run on a windows 10 32 bit machine here, upon launching the installed program, the msi would always go into autoheal mode. That is the "Please wait while Windows configures <such n' such a program>". I found out why, and fixed it by deleting KeyPath entries with orca and applying the fixit transform to the msi. - Good.

So I thought, well I better do the same to my 64 bit version of the nifty program. But first it would be good to make sure it fails in the same way first so I know when I fix it that I really did.

So I took a virgin 64bit installer (no transform applied) and installed it on a windows 10 x64 box. To my surprise, when I launched the program it did not autoheal as the 32 bit one did. So I went and deleted one of the deployed files to see if it would then fix itself. And no, it does not!

I tried the same on my wife's w10 x64 laptop and no auto-heal there either
no matter how much I abuse the installed group of files!

Crap!

So vs2008 x64 setup projects won't autoheal??? - After the internet thread after thread that it is impossible to disable ouside of keypath deletion?

Help!

:Ron

What I have tried:

googling without finding anyone else that even seems to have an issue like this.

Posted 4-Sep-17 10:39am

Ron Anders

Updated 4-Sep-17 12:37pm

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2017-09-04T11:34:00

Solution 1

Autoheal only triggers in the key files are missing or damaged compared to what's in the installer.

OR, if the feature was not installed because it was told to install on first run.

If the files were laid down correctly upon the initial installation, there's no reason to heal.

It sounds like the 32-bit version had a problem, not the 64-bit version.

Posted 4-Sep-17 11:34am

Dave Kreskowiak

Comments

Ron Anders 4-Sep-17 19:02pm

Thanks for the help.

The 64 bit installer is virgin with no keypaths gone. As a matter of fact, the keypath is in place for usersguide.pdf for example in both the 32 bit and 64 bit installers. Only the 32bit os seems to detect a change.

Dave Kreskowiak 4-Sep-17 21:18pm

Got an advertised shortcut pointing to that file?

Ron Anders 4-Sep-17 22:03pm

No I know bout that too. Ok that file was a bad example. Any file will pop off a auto heal.

This is one of those , No Ron, Just you.

That's ok.

Ron Anders 4-Sep-17 22:05pm

When I go to work tomorrow I will have an opportunity to play with other 64 bit windows os's so thanks for playin' I'll just deal with it.

Ron Anders · Answer 2 · 2017-09-04T12:37:00

Solution 2

No actually both versions deploy a file then the installer deletes it on the way out. That was causing the 32 bit to go in an auto-heal circle.

On the 32 bit windows 10 pc, if everything is stable and cool, then if I rename or delete one of the deployed files such as the usersguide.pdf, upon launch the msi will autoheal it. If I do the same on a x64 windows 10 pc nothing happens and the users guide is not found via it's program menu shortcut!

Posted 4-Sep-17 12:37pm

Ron Anders

Comments

Dave Kreskowiak 4-Sep-17 18:56pm

You posted this as a solution, not a reply. Click "Have a Question or Comment".

Since you posted a solution, I didn't get a message that said you replied to my post.

Dave Kreskowiak 4-Sep-17 18:57pm

If you removed all the key file paths, that will break healing. The KeyFiles MUST be there for it to work.