VS 2008 64位安装项目msi无法自动修复/自动修复！ [英] VS 2008 64 bit setup project msi not auto healing / auto-repairing!
问题描述
一个小故事：
我发现当我的nifty安装程序在Windows 10 32位机器上运行时，启动已安装的程序后，msi将始终进入自动恢复模式。这就是请等待Windows配置<此类n'这样的程序>。我发现了原因，并通过删除带有orca的KeyPath条目并将fixit变换应用于msi来修复它。 - 好。
所以我想，我最好对我的64位版本的漂亮程序做同样的事情。但首先确保它首先以相同的方式失败会很好，所以我知道当我修复它时我确实做到了。
所以我带了一个处女64位安装程序（未应用转换）并将其安装在Windows 10 x64框中。令我惊讶的是，当我启动该程序时，它并没有像32位那样自动修复。所以我去删除了一个已部署的文件，看看它是否会自行修复。不，它没有！
我在我妻子的w10 x64笔记本电脑上尝试了同样的功能，并且没有自动愈合那么
无论如何我滥用已安装的文件组多少钱！
废话！
所以vs2008 x64安装项目不会自动修复??? - 在线程之后的互联网线程之后，无法禁用密钥路径删除的ouside？
帮助！
：Ron
我尝试了什么：
google搜索没有找到其他人甚至似乎都有这样的问题。
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.
推荐答案
与安装程序中的内容相比，密钥文件中的自动恢复仅触发器丢失或损坏。 />
或者，如果没有安装该功能，因为它被告知首次安装时安装。
如果文件在初始安装时正确放置，没有理由进行修复。
听起来32位版本有问题，而不是64位版本。
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.
实际上两个版本都没有部署文件，然后安装程序会在出路时删除它。这导致32位进入自动修复圈。
在32位windows 10 pc上，如果一切都稳定而且很酷，那么如果我重命名或删除其中一个已部署的文件，例如usersguide.pdf，启动后，msi将自动修复它。如果我在x64 windows 10上做同样的事情没有任何反应，用户指南找不到它的程序菜单快捷方式！
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!
这篇关于VS 2008 64位安装项目msi无法自动修复/自动修复！的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
