+ 0 Votes Same problem.... abelenky 7 years ago I have the same problem, and have not yet found a resolution. If you come up with anything new, please let me know. If I find a solution, it'll get posted here. + 0 Votes After working with MS Tech Support billmez 7 years ago It took a while to trace since it happened on several systems but here goes... The main problem was the permissions on the registry keys for all versions of xmlhttp since it appears that the update affected all of them. Adding the IUSR and IWAM anonymous users to the registry keys with read and execute access worked. It also had to be done with serverxml http. On one machine the update just didn't register properly and unregistering and re registering it with regsvr32 handled that problem. I have had permission issues on registry keys with selected com components in the past also for the anonymous web users and had to manually add them to the reg keys also. The system has had the IIS lockdown tool run on it which creates a new user group and places IUSR and IWAM into it to restrict access rights. We think this may be the reason for improper key security on these installation. Just a passing mention, that issues like this that result from an MS security update qualify for free MS support. The Regmon tool available on the MS web site was also instrumental in finding the keys that were being denied access. I hope this helps. Bill + 0 Votes Here's what I came up with.... abelenky 7 years ago After lots of poking around, I determined that i can no longer do a Server.CreateObject("MSXML2.XMLHTTP"). Instead, the class-string must now be "MSXML2.XMLHTTP.4.0" (I found a suggestion that .5.0 may also work in some cases). I can't explain it, but it seems to work for me. Good luck!