How to install vcdrom.exe and the sys file.

Anonymous
2012-01-08T17:32:27+00:00

i installed vcdrom.exe and copied vcdrom.sys to windows/system32/drivers like instructed, but when i try to select vcdrom.sys in the install driver list it's not even visible. but when i go to said location ouside the program i find it no problem, i tried running the program as admin, i tried setting the sys file to full control and it makes no difference. what should i do?

Windows for home | Previous Windows versions | Apps

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2013-05-10T12:02:17+00:00

There is actually an updated version that's supposed to work with Win7

http://www.microsoft.com/en-us/download/details.aspx?id=38780

Right-clicking the vcdcontrolTool.exe file and choosing Run as administrator eliminates the "Cannot Open SCM: Access is denied" message, but VCdRom.sys is still not visible in %windir%\system32.

Apparently it's just not compatible with x64 versions... even if you run it elevated and try to load the copy of the driver file left in the unzip subdir (which is found with no problem), the message "Driver has been blocked from loading." results. Possibly whatever MVP re/wrote it either forgot about kernel mode code signing or doesn't want to pay the ($400?) annual fee to MS for signing x64 drivers.

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

54 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-10-05T20:07:47+00:00

    Basith M, 

    I would suggest that you stop avoiding the issue, and if you have nothing useful to say, then ****.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-09-08T21:07:49+00:00

    You said, "would make" and I infer that you haven't actually tested this approach. Assuming someone tried it and it worked, I would then agree it is an answer. However, end users shouldn't have to do this and Microsoft should take this small step to fix the problem. Shame on them for releasing code that isn't properly signed.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-09-08T20:51:34+00:00

    I don't know why that post was marked as the answer.

    Ignoring the 'unsigned driver' message and installing that version, then signing the .sys file yourself (as I mentioned in my 01 September 2014 post on page 2 of this thread), would make that version run just fine in Win7 x64.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-09-07T21:13:01+00:00

    Does anything from Microsoft ever work correctly as stated? even software they design to work with their currently released stuff?

    >>>>>>>That is why Apple leads and others follow.<<<<<<<<

    Was this answer helpful?

    0 comments No comments