When i launch vs 2010 ultimate I get error 'cannot create window'. Any solutions?
A:
No clue if this will solve it, but I found this link which looks maybe-plausible:
Brian
2010-04-20 05:53:55
A:
Try this:
Rename msvcm100.dll to msvcm100.dll.old in c:\windows\system32
Run Visual Studio 2010 repair and msvcm100.dll should get recreated.
Nate Shoffner
2010-04-20 05:54:00
there is not msvcm100.dll in my folder c:\windows\system32
Max
2010-04-20 06:07:28
I personally haven't yet this problem thankfully, but from what it seems is to be a problem after installing Office 2010? Have you recently done that? Also, have you tried running Visual Studio 2010 repair to see if it fixes your issue?
Nate Shoffner
2010-04-20 06:17:49
About two month ago I had installed office 2010 and then I delete it. Ok, I'll try to repair vs 2010
Max
2010-04-20 06:39:17
I'm been getting the same problems with VS2010 RTM and haven't gone anywhere near Office 2010. Also no msvcm100.dll in my System32 folder.
Guy
2010-04-26 18:22:19
I would just love to point out that suddenly every answer except for vasmt's is downvoted..
Nate Shoffner
2010-04-26 19:54:24
A:
I repaired visual studio but it didn't fix problem. msvcm100.dll in my windows\system32 folder didn't created
vasmt
2010-04-20 21:06:57
A:
The same thing happened to me today for the first time while using VS2010 premium on Windows 7. The only thing different since the last time I used it (16hrs ago) was Windows Update which the System Restore utility says only affected an unrelated local app on my machine, Grooveshark.
Anyway, I restored to the point created immediately before the update, and VS2010 doesn't complain about not being able to "Create Window" anymore... don't think this was related to a recent Resharper 5 install.
Hope this helps!
asadiq
2010-05-30 03:27:30
A:
I am getting this error after running VS 2010 Premimum edition for around a month. I DOnt have office 2010 installed, msvcm100.dll is also not present at my system. Any solutions?
naveen
2010-09-08 11:08:03
A:
It's working fine on my system. 'windowscodecs.dll' was missing on system, I restored it and now VS 2010 is running fine.
Lalit Dwivedi
2010-09-09 06:40:42
A:
In my case, it was installing IBM Client Access v6.1 service pack SI37891. When it installed the .NET 4 data provider it broke the XML file.
The file in question can be found here: C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config
An additional data provider was installed and a spurious XML close tag was added incorrectly:
<DbProviderFactories>
<add name="IBM DB2 for i5/OS .NET Provider" ...... /></DbProviderFactories>
<add name="Microsoft SQL Server Compact Data Provider" ....../>
</DbProviderFactories>
alock
2010-09-16 10:44:13