Won't Install: Windows XP Security Update KB2572067 .NET Framework Version 1.1

Security Update KB2572067 ".NET Framework Version 1.1" on Windows XP wouldn't install.

An update for .NET Framework Version 4 wouldn't install either, but fixing the problem above then allowed the .NET Framework Version 4 update to install.

  1. First, I downloaded the update from http://download.microsoft.com/download/4/9/A/49AD2B1B-0BDB-4816-AFCE-E7BB5D6FFCA5/NDP1.1sp1-KB2572067-X86.exe to my desktop.

  2. I ran it.

  3. It told me a service associated with .NET Framework Version 4 was disabled. I'm sorry, but I don't remember the exact wording.

  4. I agreed/accepted to enable it.

  5. It then said it couldn't find "netfx.msi" in the temp folder.

  6. I did a drive search for it, but it wasn't on my computer.

  7. I downloaded it from http://www30.zippyshare.com/d/40527752/719/NETFX.MSI also to my desktop for convenience sake.

  8. Amazingly, I could not find it available anywhere on microsoft.com — very strange.

  9. It scanned as clean.

  10. I ran NDP1.1sp1-KB2572067-X86.exe again; and that time when it prompted for netfx.msi, I browsed to the desktop and selected netfx.msi.

  11. That worked.

  12. After it was done updating, I rebooted.

  13. The system-tray icon still said there was an update.

  14. I clicked on it, and it disappeared, as expected.

  15. I still needed the .NET Framework Version 4 update installed, so I went to http://windowsupdate.microsoft.com/windowsupdate/v6/default.aspx?ln=en-us with MSIE and ran a scan.

  16. It came up with the .NET Framework Version 4 update of course, which I agreed to install.

  17. It did that but not flawlessly.

  18. Updates hanged (updates hung up, locked up, stalled).

  19. I could tell because there was no activity with the hard-drive light, and I also checked the Task Manager for processes (CPU activity from Window updates).

  20. I rebooted and did another scan at http://windowsupdate.microsoft.com/windowsupdate/v6/default.aspx?ln=en-us, which came up clean (meaning the hang came after the update had actually installed — I hope).

I just finished this process and decided to blog it while it's fresh in my mind. I did that for two reasons: 1) to help others and 2) to help me remember the workaround. Ordinarily (lately), I've taken to documenting my workarounds and repairs, etc. I have had to come back to several, so it has proven worthwhile.

If this helped you, let me know via a Thank You comment. If you have technical questions, I'm probably not your man. I'm good at focusing in on my own computer issues or where I can get my hands on a computer, but I'm not good at solving other people's problems so much when I can't see what's happening firsthand and try things.

I will say that from experience, I find doing Google advance searches on Microsoft.com as the domain helps hone in faster.

This proved helpful in that regard: http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_update/cannot-install-kb2572067-net-framework-11/ea70a776-352e-497e-af10-ceb0aecb54fe Depending upon how long this problem persists, more and more people may add to the thread there. Perhaps I'll post this.


The following should appear at the end of every post:

According to the IRS, "Know the law: Avoid political campaign intervention":

Tax-exempt section 501(c)(3) organizations like churches, universities, and hospitals must follow the law regarding political campaigns. Unfortunately, some don't know the law.

Under the Internal Revenue Code, all section 501(c)(3) organizations are prohibited from participating in any political campaign on behalf of (or in opposition to) any candidate for elective public office. The prohibition applies to campaigns at the federal, state and local level.

Violation of this prohibition may result in denial or revocation of tax-exempt status and the imposition of certain excise taxes. Section 501(c)(3) private foundations are subject to additional restrictions.

Political Campaign Intervention

Political campaign intervention includes any activities that favor or oppose one or more candidates for public office. The prohibition extends beyond candidate endorsements.

Contributions to political campaign funds, public statements of support or opposition (verbal or written) made by or on behalf of an organization, and the distribution of materials prepared by others that support or oppose any candidate for public office all violate the prohibition on political campaign intervention.

Factors in determining whether a communication results in political campaign intervention include the following:

  • Whether the statement identifies one or more candidates for a given public office
  • Whether the statement expresses approval or disapproval of one or more candidates' positions and/or actions
  • Whether the statement is delivered close in time to the election
  • Whether the statement makes reference to voting or an election
  • Whether the issue addressed distinguishes candidates for a given office

Many religious organizations believe, as we do, that the above constitutes a violation of the First Amendment of the US Constitution.

Congress shall make no law respecting an establishment of religion, or prohibiting the free exercise thereof; or abridging the freedom of speech, or of the press; or the right of the people peaceably to assemble, and to petition the Government for a redress of grievances.

That said, we make the following absolutely clear here:

  • The Real Liberal Christian Church and Christian Commons Project not only do not endorse any candidate for any secular office, we say that Christianity forbids voting in such elections.
  • Furthermore, when we discuss any public-office holder's position, policy, action or inaction, we definitely are not encouraging anyone to vote for that office holder's position.
  • We are not trying to influence secular elections but rather want people to come out from that entire fallen system.
  • When we analyze or discuss what is termed "public policy," we do it entirely from a theological standpoint with an eye to educating professing Christians and those to whom we are openly always proselytizing to convert to authentic Christianity.
  • It is impossible for us to fully evangelize and proselytize without directly discussing the pros and cons of public policy and the positions of secular-office holders, hence the unconstitutionality of the IRS code on the matter.
  • We are not rich and wouldn't be looking for a fight regardless. What we cannot do is compromise our faith (which seeks to harm nobody, quite the contrary).
  • We render unto Caesar what is Caesar's. We render unto God what is God's.
  • When Caesar says to us that unless we shut up about the unrighteousness of Caesar's policies and practices, we will lose the ability of people who donate to us to declare their donations as deductions on their federal and state income-tax returns, we say to Caesar that we cannot shut up while exercising our religion in a very reasonable way.
  • We consider the IRS code on this matter as deliberate economic duress (a form of coercion) and a direct attempt by the federal government to censor dissenting, free political and religious speech.
  • It's not freedom of religion if they tax it.

And when they were come to Capernaum, they that received tribute money came to Peter, and said, Doth not your master pay tribute? He saith, Yes. And when he was come into the house, Jesus prevented him, saying, What thinkest thou, Simon? of whom do the kings of the earth take custom or tribute? of their own children, or of strangers? Peter saith unto him, Of strangers. Jesus saith unto him, Then are the children free. (Matthew 17:24-26)

  • Subscribe

  • Tom Usher

    About Tom Usher

    Employment: 2008 - present, website developer and writer. 2015 - present, insurance broker. Education: Arizona State University, Bachelor of Science in Political Science. City University of Seattle, graduate studies in Public Administration. Volunteerism: 2007 - present, president of the Real Liberal Christian Church and Christian Commons Project.
    This entry was posted in Uncategorized. Bookmark the permalink.