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
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

54 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2016-02-05T02:19:41+00:00

    "We will be happy to assist you with any issue with Windows Operating System." is what you said almost 1 year ago, Basith.  This is a problem with the Windows Operating System and you have done NOTHING since then.

    We're still waiting for you to keep your word.  How do you even have a job?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-02-05T08:23:16+00:00

    This thread is getting quite funny.

    It has been noted quite early in the thread that this product is not supported by Microsoft beyond XP.

    Unfortunately, a hapless MS person initially the mistake of trying to support it, at least until it became apparent the problem was not in XP.

    Given his reasonable suggestion of starting  a new thread was not taken up, the MS person rightly decided to get on with the rest of his life. 

    In spite of this, several people - who, like me, are at least one synapse smarter than any MVP because we refuse to pay M$ to put MVP against our names - several  us have offered alternatives that might work under W7-64.

    Now I hate Microsoft for good reasons,  but ignoring trolls (I'm being kind)  is not one of them.

    If Microsoft tells you in advance a product is not supported by Microsoft for the OS you are using, why the **** are you wasting your time trying to get them to support that product?

    Are you really that stupid?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-02-13T17:12:06+00:00

    Darr247 is correct in that it's a signing issue. For what it's worth, likely the only way to utilize this solution is to disable signature checking and put Windows into test mode (https://www.raymond.cc/blog/loading-unsigned-drivers-in-windows-7-and-vista-64-bit-x64/). Not worth it for me, I'd just go with one of the other solutions.

    https://www.raymond.cc/blog/10-free-software-to-mount-cd-or-dvd-iso-image-file-as-virtual-drives/2/

    Daemon tools has been a staple for years for this type of thing. Sad that Microsoft can't support this functionality properly.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-02-28T06:24:12+00:00

    Just passing by to say that I've the same problem on Windows 7 64bit. :)

    Was this answer helpful?

    0 comments