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. D