virtualbox.org

"c:\windows\system32\dciman32.dll is not for running in windows OS or it has error..." This message appears immediately after I try to start VB.

I have been using this version (4.2.16) until today when this message appeared ... and keep apearing every time I start it.
VBox works on Windows 7 64bit.I had three virtual oracle linuxes.

Any ideas what happened ? I have found #10513 ticket and it looks like the same problem has been described. But no answer has been provided there




k.

Is this problem on your host or in a guest? VirtualBox does not add or remove files, except its own - and "dciman32.dll" is not part of VirtualBox. I suggest you Google to find your error.

ps. I don't see the connection between BugTracker ticket #10513 and your problem.

Post a log file if you want to discuss this further - see Minimum information needed for assistance. Note however that we can't help you with Windows support questions, only VirtualBox ones.

I spent a lot of time searching, asking, figuring out. Google says notbhing except THIS post. Generally it doesn't seems to be a VBox problem but anyway, it still exists and I can't use it, so maybe some of you have an idea.

The problem is exact as I wrote above:
I tried to run the newest VBOX (4.2.16) on my windows 7 x64. The message appears immediately after clicking icon VB. The message has title "VirtualBox.exe - bad image" and description as I wrote in the first post.
Program c:\windows\system32\DCIMAN32.dll is not designed to run in windows system either has an error. Reinstall it using original instalation media or contact system administrator

It doesn't generate any logs, there is no events in event log. Fresh install change nothing

The dll is a windows system file which somehow got corrupted.
You could try to fix this with the Windows Sytem File Checker tool ("sfc /scannow", see http://support.microsoft.com/kb/929833/en-us )

BINGO!
Hashes for file member \??\C:\Windows\System32\dciman32.dll do not match actual file [l:24{12}]"dciman32.dll"

So I replaced the file ( it was not a trivial copy/overwrite) and now VBox is working again.


thanks for your help
K.