MySQL安装程序开始安装，然后关闭
当我运行MySQL安装程序时，需要几秒钟然后关闭，然后在安装窗口消失之前，您可以看到标题'请等待“请等待Windows配置MySQL Installer -community -community -server'和下面的“收集”所需信息” - 之后，窗口消失了
<< a href =“ https://i.sstatic.net/i3qpc.png” rel =“ nofollow noreferrer”>
我尝试过：
- 代表管理员
- 在任务管理器中完成Windows安装程序的过程，并尝试重新启动MySQL Installer
- 尝试更改程序的版本，但没有任何更改
也许有人有这样的问题？
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
更新 ：我很长时间前在MySQL安装程序上写了一些东西。只要我检查安装程序的概念，就变得很长。我应该再次审查。
update ：此安装程序是一个修改的MSI文件，其中管理安装（基本上是从MSI中提取的荣耀文件），以及许多其他功能，该功能应该是MSI文件支持标准。企业环境需要这些功能来大规模部署产品（在许多具有自定义设置的计算机上安装无声安装）。您必须询问供应商为什么要阻止功能。
此修改后的非标准MSI安装了自己的设置启动器应用程序，进而可以触发通过自定义GUI安装的单个MSI文件。 此启动器应用程序需要.NET Framework版本4.5.2。确保已安装.NET。似乎有2个版本的MSI：一个具有嵌入式MSI文件的版本和一个仅安装启动器的Web version。
管理安装 ：您可以使用下面的命令行（技术技巧）强制执行在非标准MSI上执行的管理安装。您创建一个转换，该转换从启动器表中删除条目，并通过msiexec.exe命令行应用。可以使用orca -MSI SDK MSI编辑器工具来创建变换：
这将从MSI中提取所有嵌入式文件，您将看到启动器可执行文件和一个称为“产品缓存”的文件夹，其中包含所有嵌入式MSI文件。如果您安装了MSI的Web版本，则不是这种情况 - 仅包含启动器而没有嵌入式MSI文件（我假定）。单个MSI文件将通过启动器从Web下载。
通过提取所有设置，您可能只能安装它们的选择，或者按顺序安装所有设置。请注意，它们可能需要按特定顺序安装 - 我不知道。
下面的部署调试
是关于失败MSI安装程序的一些一般调试建议：
我将首先对明显的事情进行一些基本检查（这是原始的部署清单）：
1）验证您的安装媒体（重新下载），2）检查缺少Runtimes ，干净的虚拟（或其他物理计算机），3）带有Admin权利的运行设置，4）重新启动之前，请先尝试，5）检查磁盘空间，6）检查恶意软件，7）8）使用新的本地管理员帐户安装（如果有的话，可以工作用户配置文件错误），9）在启动设置之前禁用反病毒或恶意软件扫描仪（首先通过 ：//virustotal.com“ rel =“ nofollow noreferrer”> virustotal.com ），10）检查公司策略的防止交互式安装< /em>等...基本方法
以上是通用清单。通常有效的是创建和检查MSI日志文件。
MSI记录 ：我将启用
MSI全局记录策略通过修改此注册表密钥（或通过策略进行）：[HKEY_LOCAL_MACHINE \ SOFTWORD \ PALICIES \ MICROSOFT \ WINDOWS \ STARTER]]
“记录” =“ Voice Warmup”
“ debug” = dword：00000007
这将生成名为
msi*.log的日志文件，其中*是随机数在temp目录的每个基于MSI的设置。按时间/日期对
temp文件夹进行排序，并查找最新日志条目。打开您可以找到并查看的任何MSI日志文件。MSI日志检查 ：首先尝试搜索
“ value 3”的日志。可以在此处找到了解MSI日志文件的更多提示 - 查看“解释MSI日志文件”：。
链接：
UPDATE: I wrote up something on the MySQL installer quite some time ago. It became quite long as I was checking the installer concept. I should review it again.
UPDATE: This installer is a modified MSI file where administrative installation (basically a glorified file extraction from the MSI) has been disabled along with a number of other features that MSI files are supposed to support as standard. Corporate environments need these features for large scale deployment of the product (silent installation on many computers with customized settings). You would have to ask the vendor why the features are blocked.
This modified and non-standard MSI installs its own setup launcher application which in turn can trigger individual MSI files to be installed via a custom GUI. This launcher application requires the .NET Framework version 4.5.2. Make sure you have .NET installed. It seems there are 2 versions of the MSI: one with embedded MSI files and a WEB-version which installs the launcher only.
Administrative Installation: You can use the command line below (technical trick) to force an administrative installation to be performed on the non-standard MSI. You create a transform which deletes entries from the LaunchCondition table and apply it via the msiexec.exe command line. Transforms can be created with Orca - the MSI SDK MSI editor tool:
This will extract all embedded files from the MSI and you will see the launcher executables and a folder called "Product Cache" which contains all the embedded MSI files. This is not the case if you install the WEB-edition of the MSI - which contains only the launcher and no embedded MSI files (I presume). The individual MSI files will be downloaded from the web via the launcher it seems.
With all the setups extracted you could potentially install only a selection of them, or all of them in sequence. Note that they might need to be installed in a specific order - I don't know.
Deployment Debugging
Below are some general debugging suggestions for failing MSI installers:
I would run some basic checks on the obvious things first (here is the original deployment checklist):
1)Verify your installation media (re-download),2)check for missing runtimes,3)run setup with admin rights,4)reboot before trying again,5)check disk space,6)check for malware,7)try on a clean virtual (or another physical computer),8)install with a fresh local admin account (can work if there are user profile errors),9)disable anti-virus or malware scanners before launching setup (scan setup file first via virustotal.com),10)check for corporate policies preventing interactive installation,etc...Essential Approach
The above is a general purpose checklist. What usually works is to create and inspect an MSI log file though.
MSI Logging: I would enable
MSI global logging policyby modifying this registry key (or going via policy):[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"
"Debug"=dword:00000007
This will generate log files named
MSI*.logwhere*is arandom numberin theTEMP directoryfor each MSI based setup.Sort the
TEMP folderby time / date and look for the recent log entries on top. Open any MSI log file(s) you can find and have a look.MSI Log Inspection: The first thing to try is to search the log for
"value 3". Further tips for understanding MSI log files can be found here - look in section"Interpreting MSI Log Files":Enable installation logs for MSI installer without any command line arguments.
Links: