Click here to Skip to main content
15,113,295 members
Please Sign up or sign in to vote.
1.80/5 (3 votes)
See more:
When I try to run a project in visual studio 2008 Its showing an error message as below

"A Visual Studio DLL, coloader8O.dll, is not correctly installed. Please
repairyour Visual Studio installation via ‘Add or Remove Programs’ in
Control Panel.
If the problem persists, you can manually register coloader8O.dll from
the command prompt with ‘regsvr32
"%CommonProgramFiles%\Microsoft
Shared\VS7Debug\coloader8O.dll".


I tried to register it again but no hope. How can I solve this issue?
Posted
Updated 20-Jun-17 20:57pm
v2
Comments
[no name] 6-Aug-12 17:31pm
   
What does "no hope mean"? Did it register or didn't it? Did you repair your installation?
Reji Ab 10-Aug-12 1:55am
   
I repaired the installation but one component failed to install, but still having the same problem.
when I tried to register the dll manually It shows following error :

"<the path of the dll> was loaded but the call to DllRegisterServer failed
with error code 0x80070005". I logged in as an administrator in order to register the dll through command prompt

A bit late, but better late than never...

If you happen to be on a 64bit Windows, please note that the coloader80.dll is to be found in the (x86) subpath, so the correct magic wand movement would be to execute
regsvr32 "%CommonProgramFiles(x86)%\Microsoft Shared\VS7Debug\coloader80.dll"
instead of the above from a command line started with administrative rights.

NB: this doesn't mean "log in as an administrator", this means "right-click cmd.exe and select 'Run with administrative rights'" (or however that's shown in your local language).

[Edit 2017-12-27:]
Also - this may not be sufficient. Sometimes, this symptom comes from an error in the oleaut32.dll registration (yes, really), and the regsvr32 invocation doesn't change anything. In this case, download and install OleAutClean.msi from Microsoft (the link may change over time, but the name should be easily findable). Afterwards, run the following from a command line started with administrative rights:
regsvr32 oleaut32.dll
regsvr32 "%CommonProgramFiles(x86)%\Microsoft Shared\VS7Debug\coloader80.dll"
(without the (x86) part if you're on a 32 bit system).

That should do the trick in any case.
   
v6
Comments
Bob1000 9-Mar-17 14:37pm
   
Due to an&*%l retentive idiot, previous message regarding this solution was deleted - you have to wonder at the small mindedness of some people!

But for those of you trying to use the solution there is a typo in the above solution line.

regsvr32 "%CommonProgramFiles(x86)%\Microsoft Shared\VS7Debug\coloader80.dll"

Its a zero not an 'O' as in Oscar required at the end. Otherwise arakula solution works a treat.

Thank you so much arakula you saved my day!
fby42 25-Mar-17 9:31am
   
Thanks a lot - saved my VS2010 installation after VS2017 had crushed it.
Mauro Gagna 29-Mar-17 16:00pm
   
I had the same problem after installing VS2017. That command fixed it. Thanks
arakula 27-Dec-17 13:46pm
   
Years later ... I finally updated the O to 0 above.
Other people seem to have found a solution to this problem:
http://social.msdn.microsoft.com/Forums/uk/vsdebug/thread/d5ae3b4d-c6e8-4eca-8701-0bd68af09343[^]
   
Comments
Reji Ab 8-Aug-12 4:07am
   
Its showing an error when I tried to register the dll
Solution is here. So annoying when the solution is buried under old stuff...

Thank you for reporting this problem. A fix will be released. The following work-around should work with all updates (it's the actual fix).

Fix the following registry key

Computer\HKEY_CLASSES_ROOT\TypeLib\{6A1A7D39-8449-4287-8EF0-CE256582C940}\8.0\0\win32

Change the default value from

C:\Program Files (x86)\Common Files\Microsoft Shared\VS7Debug\\coloader80.dll

to

C:\Program Files (x86)\Common Files\Microsoft Shared\VS7Debug\\coloader80.tlb

Best regards,
Huy Nguyen, Visual Studio team
   
Comments
CHill60 3-Apr-17 6:10am
   
"when the solution is buried under old stuff..." like a 4 year old question for example? Your link explicitly mentions VS2017 which wasn't around in 2012, so you may get some downvotes for resurrecting this old post

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)




CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900