.Net Framework 3.5 fails to install with error code 0x800F081F

Anonymous
2013-01-25T19:11:49+00:00

Original Title: Error installing .net framework 3.5 sp1

I did a refresh of my install of windows 8 pro (64 bit), because Weather and several other apps were failing (they started, then the main window closed, but the small window stayed in the task list to the left; event viewer gave access permissions errors).

This seemed to sort most of the apps BUT now I cannot re-install many programs as they need .net framework 3.5 and this fails to install with error 0x800F081F. I even tried downloading the full installer and running locally but it still gives the same error!

I need the framework to work with OpenXML development, a large part of my work.

(I should also point out the refresh says most apps are retained - it fails to mention all applications are removed!)

Windows for home | Previous Windows versions | Apps

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2013-01-26T07:12:12+00:00

Hi Andy,

Thank you for posting your query in Microsoft Community and giving us an opportunity to assist you.

From the issue description, you are facing issues with installing .Net Framework 3.5 and receiving error code 0x800F081F.

There is a Microsoft Knowledge Base article that provides methods to troubleshoot this issue. I would suggest that you visit the link and use the methods to resolve the issue.

Error codes when you try to install the .NET Framework 3.5 in Windows 8 or in Windows Server 2012

http://support.microsoft.com/kb/2734782

You may also refer this link for more information:

Installing the .NET Framework 3.5 on Windows 8

http://msdn.microsoft.com/en-us/library/hh506443.aspx

Hope this information helps. Let us know if you need any further assistance related to Windows.

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

80 additional answers

Sort by: Newest
  1. Anonymous
    2014-09-23T14:43:55+00:00

    I have Surface Pro 3 and I tried everything. Removed the mentioned updates (KB2966828), tried manual installation from Win 8 disc image and everything between those options that I could find with Google.

    Finally the solution for me was to reset the Surface Pro 3 to default settings. Then started it as a new device, selected in the beginning not to use Windows update. When the machine was started the first thing to do was to enable the .NET 3.5 from Programs (add feature). Now it finally worked. I should have done this at the very beginning, now I wasted at least one working day to find the solution for this. (Damn AutoCAD requires this .NET 3.5 :) )

    Fortunatelly I hadn't installed much of other software, so this didn't cause much "damage" to me.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-09-16T14:36:07+00:00

    Confirmed again! I just had KB2966828 and once removed I was able to install from Program and Features for a Surface Pro 3.  This article is a security update for Windows Update and Different .Net Frameworks which is probably why it was denying the update.  This should be fixed to identify a legit install of the Framework.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-09-13T17:09:34+00:00

    Correct. If you do not have the offending KBXXX26 and KBXXX28 updates installed, you obviously cannot remove them. The only fix in this case is to rebuild as you did, or you can install Visual Studio 2008 or 2010 which will correctly install the .NET Framework 3/3.5. Service packs, updates, rollups, etc. all seem to continue to work once you have the framework installed. Why this is a component of Windows and not an installable runtime as it historically always was, is beyond me and makes no sense.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-09-04T10:41:46+00:00

    Confirm! After several attempts, the solution was unistalling security updates KB2966826 and KB2966828. Thank you very much.

    Was this answer helpful?

    0 comments No comments