This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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.
I disliked Windows 8 so much I just wouldn't buy another computer and limped along until HP came out with the Windows 7 fall back option. Then I discovered programs that would make windows 8 or 10 resemble a Windows 7 model. That made me happy
Now they ruined my favorite Microsoft game.
Microsoft send a patch to allow Conquerors to play again!!!
This might have to be done anew for every regional setting Windows supports, as my (Dutch) Windows 10 doesn't find any entries searching for secdrv as K Heinz is obviously on a German, Austrian, Swiss or other German-language Windows 10, even though Heinz Ketchup is actually from Pittsburg, Pensylvania originally... ;)
This might have to be done anew for every regional setting Windows supports, as my (Dutch) Windows 10 doesn't find any entries searching for secdrv as K Heinz is obviously on a German, Austrian, Swiss or other German-language Windows 10, even though Heinz Ketchup is actually from Pittsburg, Pensylvania originally... ;)
Are u saying you can run these games (like Civ 4) on Windows 10 in Holland?
This might have to be done anew for every regional setting Windows supports, as my (Dutch) Windows 10 doesn't find any entries searching for secdrv as K Heinz is obviously on a German, Austrian, Swiss or other German-language Windows 10, even though Heinz Ketchup is actually from Pittsburg, Pensylvania originally... ;)
Dank u wel for your confirmation Eric!
Based on the feedback within the Windows 10 Feeback app I already had the idea there is regional splitup like it is also present in Steam. Very unfortunately though.
I think you are right that the secdrv.sys issue has to be reposted on the feedback app for and in every single language / regional settings Windows supports.
It might be also a good idea to promote so upvote this issue on the Windows 10 reddit channel.
Afaik MS is also reading it. But this would be more optional in addition to the feedback app.
Have no ketchup in my veins, coming from Germany. ;)
Red stuff nonetheless I hope, or is it blue in your case :D
Well they're reading this thread, too. I'm pretty sure of it.
The whole SECDRV discussion within Microsoft imho would off course be whether to include and (allow people to) enable a piece of code that is rated unsafe, knowing that a single weak link can break an otherwise good (even a perfect) cable. The way I look at it is that disabling and removing it is the responsible thing to do from a security perspective.
That said, I might have to read back the whole thread figuring out whether the sign and enable TESTSIGNING boot mode as mentioned by Adam Bise on August 17 still works, whether it has to be re-enabled and/or the driver re-signed before every boot to work to start games, or that the whole procedure has been forced to not work by making sure the service for SECDRV.SYS doesn't start regardless of the drivers signed status or TESTSIGNING boot mode status?
In the case SECDRV won't load whatever is attempted, dual booting an older SKU is the way to go indeed. Regardless of the above, this has the additional benefit of having only security holes in an OS that is only used to play games. That would help isolating possible security issues with SECDRV. Note that if there is a viable security breach anywhere, there's really no telling how it can be exploited, so this might not be safe anyhow if there are other computers on the network, or you use e.g. any passwords that you also use elsewhere.
That isolating this issue isn't as easy as might seem, even on a separate OS, serves to defend Microsofts apparent position to choose to eliminate SECDRV from Windows 10 all together.
