SECDRV.SYS Not Loading in Windows 10; this will break thousands of older games.

Anonymous
2015-08-01T20:13:40+00:00

Hello,

I have discovered an unfortunate problem with Windows 10.

Many games from the early-mid 2000's used Macrovision's SafeDisc (version 2) as a means of copy protection. At game startup, Windows loaded SECDRV.SYS to verify an original game disc was in the drive, after which the game would start.

When you try to run ANY game which uses this SafeDisc form of copy protection in Windows 10, the following happens:

 - You get an error window that tells you to log in with Administrator Privileges and to try again. This happens on any account, even those with Administrator access. The game fails to start.

 - If you then set "Run as Admin" compatibility mode on the game's startup file, the message disappears, but the game doesn't start.

 - Keeping a window open for C:\WINDOWS\SYSWOW64\DRIVERS shows SECDRV.SYS appearing at the moment you try to start the game. Based on its size, it appears to be the file that is present on the game disc (tested across several games), even though I see no disc activity and cannot find the file elsewhere on my system.

 - The Windows event log shows that SECDRV.SYS failed to load.

 - This happens both with an upgraded install (Windows 8.1 > Windows 10) and with a fresh Windows 10 install, with one of the games being installed immediately upon the fresh install completing.

 - On my Windows 64-bit 8.1 system, C:\WINDOWS\WINSXS has a folder called amd64_macrovision-protection-safedisc_31bf3856ad364e35_6.3.9600.16384_none_4e6b3758913c9240 with a SECDRV.SYS in it, presumably the one that ships with Windows. Windows 10 had such a folder in early builds, but it is missing from the release build. It appears SafeDisc support is missing entirely.

OTHER TESTING I HAVE DONE:

 - I updated one of the games to a version that no longer required the CD check, and it started immediately and ran perfectly once the check was removed. However, this is possible only with a very limited number of games, or resorting to fixes that violate the game's EULA or put the user's system security at risk.

 - I tried disabling driver signature verification and installing one of the games again; same problem.

 - Multiple compatibility modes; same problem. XP (Service Pack 3) mode and / or Run as Administrator mode make the error message go away, but the games still fail to launch.

SIGNIFICANCE:

Unless this is fixed in Windows 10, a massive catalog of older games will cease to function in Windows 10 for the simple reason that they cannot pass the SafeDisc copy protection check. I am accustomed to some games breaking with every new version of Windows as technology progresses (for example, the loss of the ability to run 16-bit programs in 64-bit Windows), but this seems to be an unnecessarily harsh change.

Windows for home | Windows 10 | Gaming

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

293 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-09-02T00:07:41+00:00

    I finally got everything running, and it successfully installed.

    Despite that, it still won't run. I made sure to place it in the Windows OS zone (both "SYSWOW" and "System32"). I also ensured that I used the SECDRV download version you told me to, in the code you listed. As you said, I already restarted my computer and have started it through the Power Shell.

    Even so, when I ran the busted games, they STILL won't come on.

    What am I doing wrong?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-08-31T21:45:33+00:00

    I there a work around for Taito Legends? And how might I go about doing this?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-08-26T17:55:32+00:00

    I attempted to input your commands into the Power Shell.

    This is what happened:

    That's a turtle on my desktop background, if you are wondering.

    If there's a way to do this on Command Prompt/DOS, I would much prefer that method. You gave me Command Prompt/DOS instructions earlier. As I actually understand Command Prompt/DOS (though I have no skill in it, I took college courses on its basic commands and networking commands), and I had already gotten the Path Variables to work.

    When you made the clarifications, you went back to the original post and changed everything to Power Shell. Was that neccesary? If so, I'll try again when I get a reply. Again, I am typing exactly what you tell me to, without any variation unless stated, so I obviously depend on you for answers.

    Thank you so much.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-08-26T08:55:03+00:00

    I'm sorry - it appears I oversimplified.

    I made a few changes to that post you're referring to which should correct the issue.

    The specific error you got can be remedied by using CN= at the start of the subject name.

    makecert -r -sr LocalMachine -ss My -n CN***=***Subject

    The second, consequently, is to use -Match instead of -EQ as the Subject isn't "Subject" anymore:

    dir Cert:\LocalMachine -Recurse | where Subject -Match Subject | select Thumbprint, Subject

    However, better go back to that post and follow the instructions which now use a proper string for the subject name - not just "Subject". I'm putting it in a PowerShell variable $Subject and that also clarifies which Subjects are property names and which are string values.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-08-26T03:32:43+00:00

    Okay, it's been months since I last tried it, and I figured out what I did wrong last time.

    I am trying the process again, and this time, I have successfully disabled Secure Boot. In addition, I successfully added the Windows Kit to the Path Variable system, so that I can use "MAKECERT" from the DOS/Command Line interface.

    I placed the copy of "SECDRV.SYS" in a path under "DOWNLOADS", alone in its own folder.

    However, when I begin the first step of certification, in which I entered the command ("makecert -r  -sr LocalMachine  -ss My -n Subject") exactly as you told me, I get this:

    I tried to see if the Subject or anything else was acting up, so I tried random combinations, all of which are seen above and below.

    Needless to say, I am totally stuck.

    What must I do?

    I've worked with computers for twenty years now, but hardware has always been my specialty, not software and CERTAINLY not Command Prompt/DOS.

    I thank you for helping me months ago. Would you be willing to help me again?

    -TURTLESHROOM

    Was this answer helpful?

    0 comments