MS11-100 : KB2656353 Error Microsoft .NET Framework 1.1 — Internal Error 2705. Directory


The recent release of Microsoft Security Bulletin MS11-100 KB2656353 might fail on Windows XP/Windows 2003 systems.

The patch may fail with an error message: “Microsoft .NET Framework 1.1 — Internal Error 2705. Directory”

In fact, if you try to repair existing .Net Framework 1.1, you would receive the same error message: “Microsoft .NET Framework 1.1 — Internal Error 2705. Directory”

The above error message indicates that there is a directory tree definition problem on the machine (a directory references a parent that isn’t defined).  After digging it further, I found why the failure is happening. The root cause is that KB2656353 requires .Net Framework 1.1 SP1 to be registered against the .Net Framework 1.1 product, but it was not.  Even though Microsoft .Net Framework 1.1 SP1 may appear in add/remove programs, it may not be registered.  To determine if SP1 is registered check the install log.

As per the install LOG:
We do not see the 1.1 SP1 patch in the sequence.
MSI (s) (7C:1C) [15:58:37:948]: Final Patch Application Order:
MSI (s) (7C:1C) [15:58:37:948]: {2A3320D6-C805-4280-B423-B665BDE33D8F} –
MSI (s) (7C:1C) [15:58:37:948]: {EFCE7BE0-510E-4932-9475-F44CD90DE16A} –

.Net 1.1  SP1 is {411EDCF7-755D-414E-A74B-3DCD6583F589} and is missing from this list.

Resolution:

Just installing Microsoft .Net Framework 1.1 SP1 patch should resolve this issue. Please install Microsoft .Net Framework 1.1 SP1 http://www.microsoft.com/download/en/details.aspx?id=33 on the system and then install KB2656353.


Comments (20)

  1. Nath says:

    Many thanks, the problem is solved.

  2. Claire Martine says:

    Thank you very much, this posting was clear and concise, beyond helpful! Problem solved in no time!

  3. Nitish says:

    Awesome article

  4. Joe says:

    So how do you resolve this when you have thousands of computers with this issue and relying on WSUS?  I can't just reapply SP1 via WSUS.

  5. Why can't you reapply SP1 via WSUS?

  6. mark kaylor says:

    I can't install onto my WIN XP/SP3 image, keep getting "some patches could not be installed" , however MS UPDATE keeps fetching it and attempting to install.

    Any suggestions ???

  7. This seems to be a .Net Framework corruption issue. You may collect the verbose logs from the %temp% folder. If it is urgent, then you may try removing .Net 1.1 using the tool dotnetfx_cleanup_tool: http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog_Tools/dotnetfx_cleanup_tool.zip

  8. MP says:

    Thank you, Soumitra — reinstalling 1.1 SP1 (even though it was already installed) allowed me to then install the security update.

  9. Jp says:

    Hi i just followed your post..it fixed..thanks a million ( i was frustrated by not being able to install this update from last 1 year thanks again

  10. Jason says:

    Worked like a charm, just installed it(it was already installed) and able to run the KB2656353. Thanks.

  11. James says:

    Worked for me. Thanks

  12. Mark says:

    Worked like a charm. Thanks

  13. AC says:

    Installing Microsoft .Net Framework 1.1 SP1 patch did this:

    SL26A.tmp has encountered a problem and needs to close.  We are sorry for the inconvenience

  14. Steve says:

    Thanks for a simple solution.  It worked great for me.

  15. Alex says:

    Thanks a lot.  Shame on MS not resolving this issue.  The problem stuck with me for too long until I see you solution.   Posting it shows your great generosity.

  16. Boelie says:

    Worked like a charm, thanks for sharing this.

  17. Dave says:

    I tried this following the fail of KB2656370 and KB2698023 installation.

    The install failed with Error 1334. The File 'FL_mscorcfg_exe____X86.3643236F_FC70_11D3_A536_0090278A1BB8' cannot be installed because the file cannot be found in the cabinet file 'netfx1.cab'. This could indicate a network error, an error reading from the CD-ROM, or a problem with the package.  

    There is a suggestion to retry which is what I did but it failed again with the same error.  Any suggestions very welcome.

  18. Please try re-downloading those patches and manually install them. You may also follow the blog post: blogs.msdn.com/…/kb2698023-quot-error-1606-could-not-access-network-location.aspx

  19. Jojo says:

    Many thanks.  A perfect solution for me.

  20. roland says:

    Thanks. Worked perfertly. Thank you

Skip to main content