1. Marcel,

    Don’t you know you shouldn’t install beta software on production machines / laptops? ๐Ÿ˜‰

    Nice adventure…err…post though! ๐Ÿ™‚


  2. hi marcel

    My pc configuration is:
    256 ram,80 gb harddisk 2.4 gh processor speed, xp professional sp2 ,

    whenever i installed a vs-2005 it gives error the following error
    “The ENU is not encountered a problem during setup.The set is failed to installed”.

    May u please tell me wat is this error and how i resolve this?

    thnx in advance.



  3. @Abhishek: The solution to your problem is simple, you do not have enough RAM. Upgrade to at least 1 GB or prefably to 2 GB ram to run VS 2005 properly.


  4. Thank you!
    I had the exact same problem – low disk space (2gb is low?) caused the SP install to fail. Even the Office 2007 beta stopped working after that.
    Although I used a different method (the sysinternals filemon application to check why the office applications failed), the Google search for MSVCR80.dll + SP led me right here.
    Everything works now so I am going to reinstall VS 2005 and try again ๐Ÿ™‚


  5. Thank you!!!!

    I experienced the exact same problem you did. I tried to install SP1 Beta for VS 2005 on a machine with 1 GB of free space and ran out of room. I uninstalled the .NET 2.0 framework and tried to reinstall, only to recieve the the fusion.dll error.

    The difference in my problem is that the msvcp80.dll did exist on my system, only under a different folder (it was under C:WINDOWSWinSxSx86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd). I decided to rename this folder to match the path you mentioned above, and was then able to install .NET 2.0.

    I have since reinstalled my Visual Studio and and back up and running. Again, thanks very much.


  6. Adding in another chime of thanks!

    This problem still exists on the final release of VS 2005 SP1; I ran out of disk space on installation and during the rollback it apparently deleted msvcp80.dll and the related VC80 runtime files from WinSxS. Even uninstalling the .NET Framework 2.0 and reinstalling wouldn’t fix the problem, I guess since some registry setting somewhere was fooling the .NET 2.0 installer into thinking the files were already there, safe and sound, and so they didn’t need to be installed.

    Copying the files from the VS.NET 2005 redist directory into their proper location in WinSxS fixed the problem and got the Framework and Visual Studio back up and running.

    Timothy Fries

  7. Exactly the same problem here with the final release of SP1. What a bloody cockup! Half the programs on my PC now crash, and I can’t do any development at all.

    Hopefully the tips here will help me fix it….

    Brian Smith

  8. The problem is that when SP1 setup is doing rollback, it is not cleaning correctly the shared C runtime libraries. The WindowsWinSxS contains set of directories with the various shared installations. In addition there are directories named “Policies” and “Menifests”. These directories contain files which are used to find out the correct version of a given library (DLL) to use with a specific application.

    The problem is that SP1 setup remove the shared C runtime (CRT) directory without removing the corresponding data in the Menifest and Policies directory. The result is that loading any software that try to use the version 8 of the C runtime library will fail doing so.

    To solve this issue you can do one of two things:

    1. Create a directrory with the right name (or use the empty one if this is the case) and copy the runtime DLLs to there. Make sure that you copy the right versions otherwise most things will work, but some may not…


    2. Remove the orphan policy and menifest entries (that what I did).

    Yuval Rakavy

  9. Your solution did fix the devenv.exe crash. Thanks for taking the time and posting it

    Arunkumar Viswanathan

  10. Thanks from me as well. It is unbelievable to me that Microsoft can’t be bothered to check disk space and prevent this. Windows has really become a mess lately. DLLs were never as bad as this mess of abstractions has become.

    Scott Cantor

  11. Thank you wery much for this solution.
    I to can’t bolive that guys at Microsoft put out SP which breaks more things then it fixes…

    Chandler Bing

  12. Thank you!
    Exactly the same problem with the final release of SP1.
    SP1 is destructive!!!


  13. pls can u tel….whenever i start my system a message is displayed on the screen is that “the application failed to intialize properly (0xc0000034).” please can u solve my problem….

    shiva netha

  14. Happened exactly the same to me. 3 GB wasn’t enough for SP1. Thanks a lot, it helped a lot.

    Attila Bleier

  15. Same thing happened to me with release – 3+ GB of space. 2+ months later and still the simple disk-check would’ve saved me a ton of heartache…I wish I saw this ahead of time…


  16. Same thing here, but I guess it was more polite with me and *JUST* waste a couple of hours for watching progress ( lol ) bar going back and forth and after the rollback the VS 2005 Team System is still alive. I just hope it didn’t broke something and hide it somewhere without telling me today :/
    How they could release SP without including the checking first if it will fit the hdd free space ? :/


  17. Thanks Marcel de Vries for the post. I’m installing the final SP1 (not beta) but it gives me the same error – (Not enough space) – but i’ve 3.72 GB. Now i’m stuck in that part where it says not enough disk space. after reading ur post, i’m not sure what to click! anyway… thanks for this post. Might help me in fixing the problems that i’ll encounter in the next few hours. By the way i was thinking about System Restore. Can it be helpful?


  18. Hi, i have same error like descibed above. I restore MSVCP80.dll (found using dependecy walker in fusion.dll) But in fusion.dll there is one more file missing – dwmapi.dll. Is this missing file reason of error Product: Microsoft .NET Framework 2.0 — Error 25007.Error occurred while initializing fusion. Setup could not load fusion with LoadLibraryShim(). Error: The handle is invalid.

    when I trying to repair .NET 2.0?

    Jindrich Brezina

  19. Lucky…. http://www.alexhopmann.com/article%202006-12-26.htm?c=h solved problem of .NET 2.0 repair.

    Jindrich Brezina

  20. Yep, happened to me also. I’m getting really tired of constantly doing battle with Microsoft products. Wasted so much time and frustration getting Windows to work again.

    A simple disk space check should be a mandatory part of all installations. Microsoft, I hope you’re listening. You owe a lot of people a beer or two.

    Rod Weir

  21. Very informative article! Thanks for posting this.
    Saved me alot of time as I was going through the same errors. Thanks again.


  22. Thank you! I also was bitten by insufficient space, but this was with a release version of sp1. You’ve saved me a lot of time!

    Eric Wasgatt

  23. “Don’t you know you shouldn’t install beta software on production machines / laptops”

    This problem still exists. I experienced it on a VPC and the primary VHD ran out of space. It completely destroys the installation and is incapable of rolling back correctly.

    I think this sucks how their software doesn’t remove itself correctly and the “repair” installation doesn’t actually repair anything… What’s the point in it!

    Cheers for the info in your blog!


  24. Once again, thank you for posting this. I can see it would have been very unlikely that I would have been able to figure this out on my own!

    Tobin Pipkin

  25. Thanks sooo much for your tip Marcel. In my case, right folder name was another (x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6b128700) i think. Anyway, it could finally install NET Framework 2.0. Finally.

    Thanks again.

    Luis Alberto Mendieta

Comments are closed.