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

293 answers

Sort by: Most helpful
  1. Anonymous
    2017-07-10T06:10:23+00:00

    I reckon Steam is at fault. Steam is no doubt well aware of the games DRM, and MS's blocking the secdrv.sys  driver,

    but can't be bothered.

    They only need to make and .exe for their download of the game act like a common noCD fix/hack and there

    would be no issue with SafeDisk.

    Other sites, such as Good Old Games 'remove' the DRM from all of their games. Steam cuts corners for bigger profits.

    If Steam had a shred of social conscious they would add a disclaimer regarding the game having SafeDisk DRM

    with the games system requirements.

    While not an excuse,  the Specifications section of Steams description of the game shows

    Windows compatibility only as far as Vista.

    Why Vista ? Probably because MS did not release the DRM Blocking Windows Security update for Vista.

    The game was released in '04 and should have no other issues with 7>10 once DRM  Blocking has been

    circumvented.

    Problem is - you bought the game from Steam, and there is a big risk using a noCD crack in your Steam Library.

    I would  request a refund, explaining I was not aware of the SafeDisk  DRM Blocking issue on Win10, and that as it

    is the only version of Windows in which you cannot use any other means to circumvent DRM Blocking than

    to use a noCD hack, the Steam Download version of the game not fit for purpose (which here in Oz entitles the

    purchaser to a full refund).

    .

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-07-09T20:59:28+00:00

    Many if the old classic games have surfaced on Steam or GoG or Origin.

    Some games I owned, Steam accepted my cd-key.

    Lots of games are in feature on Steam right now.

    However not all to the games on Steam have had the DRM removed.  During the summer sale this year, I got Settlers Heritage of Kings on sale, but it won't run.  Looking through the steam discussions, it turns out that it is in fact the missing safedisc driver that causes the problem.  Since the post is two years old, nevermind Microsoft, the fact its still on sale, and hasn't had the DRM stripped for steam distribution, makes me wonder why Ubisoft hasn't used their summer interns productively to do exactly that.  Not that I would expect them to get it done the first summer (2015), but by now it should have been done, knowing that safedisc is out of Windows 10.  I even looked into windows.old, but tricksy old Microsoft deleted the remnants of Windows 7, so no go there.

    Check with Ubisoft as they are the publisher

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-07-09T20:48:50+00:00

    Many if the old classic games have surfaced on Steam or GoG or Origin.

    Some games I owned, Steam accepted my cd-key.

    Lots of games are in feature on Steam right now.

    However not all to the games on Steam have had the DRM removed.  During the summer sale this year, I got Settlers Heritage of Kings on sale, but it won't run.  Looking through the steam discussions, it turns out that it is in fact the missing safedisc driver that causes the problem.  Since the post is two years old, nevermind Microsoft, the fact its still on sale, and hasn't had the DRM stripped for steam distribution, makes me wonder why Ubisoft hasn't used their summer interns productively to do exactly that.  Not that I would expect them to get it done the first summer (2015), but by now it should have been done, knowing that safedisc is out of Windows 10.  I even looked into windows.old, but tricksy old Microsoft deleted the remnants of Windows 7, so no go there.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-06-28T23:32:40+00:00

    You should be able to restore the factory default secure keys.

    But if these screenshots are correct, you should read more and do less the rest of your life.

    https://support.hp.com/us-en/document/c04784866

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2017-06-28T23:20:25+00:00

    Makecert definitely is in the Windows SDK. I never installed the WDK to get this to work.

    In Command Prompt you can do: SET PATH=%PATH%;<path to x86\makecert.exe>

    In PowerShell you can do: $env:Path = "$env:Path;<path to x86\makecert.exe>"

    But those aren't remembered, that's why you can figure out how to do it in System Properties instead of having to do this again ever.

    You can use any folder to do this in. Recommended to use a personal folder (under Documents or Downloads).

    The switches to Makecert specify the certificate is created in Cert:\LocalMachine\My i.e. the Personal folder in certlm.msc.

    Do not copy SECDRV.sys anywhere under C:\Windows unless you are figuring out why it doesn't work after going through all steps and you get say an error code after running sc start secdrv, especially if the code ends with 0002 or 0003.

    If you have to go in the BIOS setup screen, don't do what you can't revert. Disabling secure boot is a simple switch on/off, or disable/enable. You can also turn off UEFI boot, if supported. If you then can't boot, turn it on again and look for another way. Make a photo if you're a guppy.

    Was this answer helpful?

    0 comments No comments