安装VS2008 .net framework Failed to open XML file 问题解决办法

最新推荐文章于 2025-07-11 13:12:32 发布

原创最新推荐文章于 2025-07-11 13:12:32 发布 · 5.3k 阅读

1 ·

CC 4.0 BY-SA版权

文章标签：

#.net #file #xml #action #microsoft #system

当MSXML注册不完整时，.NET Framework 3.5安装可能会失败，导致修改web_mediumtrust.config文件时出错。解决方案包括通过DOS运行regsvr32 msxml3.dll重新注册XML，或者从微软官网下载并重新安装MSXML3包。

Possible .NET Framework 3.5 installation failure caused by broken MSXML registration

The .NET Framework 3.5 can fail to install on a system where MSXML is not properly registered. There is a custom action that runs during .NET Framework 3.5 setup that tries to use some APIs in MSXML to modify some information in the web_mediumtrust.config file that is a part of the .NET Framework 2.0. In the cases that we've seen of this issue so far, one of the MSXML CLSID values was somehow unregistered on the system, and that causes this custom action to fail.

DOS下运行regsvr32 msxml3.dll 把XML注册进去就行了~~~

How to diagnose this issue from the .NET Framework 3.5 setup log file

This issue will cause the following information to be written to the verbose MSI log file for the .NET Framework 3.5 component (named %temp%/dd_net_framework35_MSI*.txt):

MSI (s) (58:94) [11:11:11:829]: Invoking remote custom action. DLL: C:/WINDOWS/Installer/MSI35C6.tmp, Entrypoint: ExecXmlConfig
MSI (s) (58:F0) [11:11:11:829]: Generating random cookie.
MSI (s) (58:F0) [11:11:11:829]: Created Custom Action Server with PID 4936 (0x1348).
MSI (s) (58:74) [11:11:11:860]: Running as a service.
MSI (s) (58:00) [11:11:11:860]: Hello, I'm your 32bit Elevated custom action server.
ExecXmlConfig: Error 0x80040154: failed to load XML file: C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/CONFIG/web_mediumtrust.config
MSI (s) (58!50) [11:11:11:954]: Product: Microsoft .NET Framework 3.5 -- Error 25541.Failed to open XML file C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/CONFIG/web_mediumtrust.config, system error: -2147221164

How to work around this issue

You can use one of the following options to work around this issue if you encounter it during .NET Framework 3.5 setup. Note that these workarounds are only useful for this exact error and HRESULT value. They will not help fix all possible .NET Framework 3.5 setup failures.