Microsoft don't give a rat's ass about their users, they just care about making as much money as they can...
SECDRV.SYS Not Loading in Windows 10; this will break thousands of older games.
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.
293 answers
Sort by: Most helpful
-
Anonymous
2017-12-30T17:15:02+00:00 -
Anonymous
2017-11-26T23:10:58+00:00 I didnt want to get involved but are you guys serious? Windows 10 is pretty damn good, but i can see wanting to stay to windows 7. But Apple? Apple doesnt have any videogame support much and arent renowned for their backwards compatibility!
-
Anonymous
2015-09-15T12:36:15+00:00 I think you've missed the forest for the trees. Please tell me which step in the following logic chain is non-sequitur or incorrect.
The Logic for Eradicating SECDRV.SYS from Windows
Or, Why Microsoft’s Public Statements are Diametrically Opposed to their Public Actions
The only public statement From Microsoft on the banishment of SECDRV.SYS from its operating systems was made by public statement this issue was made by Microsoft’s (of Germany) Boris Schneider-Johne. He stated, “…. there are old games on CD-Rom that have DRM. This DRM stuff is also deeply embedded in your system, and that’s where Windows 10 says ‘sorry, we cannot allow that’…”. This is so stereotypically German – the caricature, “you vill (insert any act of subjugation here) undt you vill LIKE IT!”
This statement seems contradictory to facts, Microsoft’s own actions with respect to other “security threats” and indeed to SECDRV.SYS past problems. According Rovi (heir to Macrovision), “SafeDisc DRM hasn’t been supported for a few years now, and the driver has consequently not been updated for some time. Microsoft should have migrated the existing software since Windows 8. We don’t know if that’s still possible with Windows 10 or if they simply didn’t care about it.”
That statement, and the fact that Microsoft actually included SafeDisc drivers as part of their operating system through the initial releases of Windows 10 (well after the Rovi – Macrovision absorption was complete and SafeDisc was no longer a supported / protected product) seems to indicate that Microsoft actually had the intellectual property rights and source code ownership since before the release of Windows 7. There are indications also that Microsoft made updates to SafeDisc drivers on at least two occasions – Windows 7 and Windows 8 releases. Squeezing driver developers (and even applications developers) to give up intellectual property and source code rights to their products is a well-know Microsoft tactic that has been practiced since Bill Gates reportedly stole the rights to and / or source code for CP/M from Gary Kildall in the late 1980s.
So, when Microsoft tries to point the finger at Macrovision as the responsible party for not fixing security issues with SECDRV.SYS, people who have been in the IT industry for two or three decades simply say, “Yeah… right! And the moon is made of cheese – the Wallace and Gromit documentary, ‘A Grand Day Out’ told me so, and it is as factual as a Microsoft 'technical position'”.
What’s more, having been involved in IT since 1968 and a developer / user on IBM, DEC, Microsoft and the odd UNIX system, I have NEVER witnessed the outright EXPULSION of one file based on “security” or ANY considerations.
The additional act that puts the lie to Microsoft’s public statements regarding SECDRV, is that, BECAUSE MICROSOFT HAS PREVENTED EVEN TESTING THIS DRIVER ON WINDOWS, NO UPDATE CAN POSSIBLY BE MADE TO IT! That again is an UNPRECEDENTED OVERT ACT TO DENY ACCESS TO WINDOWS PLATFORMS FOR A SPECIFIC USER COMMUNITY. This ‘c@(&-block’ action must be money motivated. Microsoft is a big corporation, its only motivation is profit, and screwing users, other corporations, even governments in the name of profit has been their open-book history. So this is no different.
However, in this case, the hubris that caused Microsoft to essentially say “f#<& you” to users of DRM-protected optical media games, including many popular Microsoft titles, makes little economic sense, and should make Microsoft shareholdersconcerned: the amount of time and effort (i.e. MONEY) dedicated to banishing this one little 30 KB file from a Windows computer, retroactively to Windows 2000, (and it appears, the same ‘fix’ was applied to my ancient, supposedly non-supported Windows XP system when I turned it on the other day) would be far in excess of the time, effort and cost to fix any perceived vulnerabilities in a file that has for nearly a decade, been included in Windows (i.e. not necessary to purchase separately from a 3^rd^ party vendor).
Singling out this one file, while many other files, including other MS kernel modules, had and continue to suffer from security vulnerabilities (how does one think the Chinese have been able to steal intellectual property, medical data, government personnel data, defense secrets, even White House emails and strategy session notes for at least the last 15 years) yet have never been and are not now “banned” from even TESTING on Windows clearly shows that this is NOT ABOUT SECURITY.
There are many more files that have been identified as ‘vulnerable’, that are still being used by hackers, and yet are still allowed to load on Windows systems outright or at least for testing (either for update or for forensic analysis – ask any anti-virus or cyber-defense developer). So again, that begs the question. Why was SECDRV singled out for such UNPRECEDENTED DRACONIAN TREATMENT?
ANSWER: MONEY!
I have a number of dongle-protected applications that load manufacturer-specific security drivers which have been compromised by hackers, usually within weeks of their initial appearance, to offer cracked versions of these applications for little or no money. It is clear that these same security drivers / schemes could be hacked for “surreptitious” actions – the same type of “vulnerability” that is the supposed reason for such drastic action against SECDRV. But Microsoft has not banned these well-known, yet vulnerable drivers from their systems.
At the same time, Microsoft IS pushing its “online experience”: it gives precedence to signing in to Windows with a “Microsoft UID” as opposed to a local system UID; those who choose to sign in with a local system UID are still bombarded with Microsoft ‘news’ and marketing messages unless they physically disconnect the system from the internet; Microsoft is pushing its online Xbox and Media & TV apps as an additional way to keep users sucking from the Microsoft teat 24-7, thus increasing the income and value of Microsoft’s “online presence”.
But Rovi (the Macrovision heir), entered the online / IP media delivery space a while ago, and in Europe, is a non-trivial competitor to Microsoft in that market. Could the SECDRV scenario simply be a Microsoft marketing tactic to besmirch the Macrovision (Rovi) reputation as producers of flawed, hackable software (when in reality, there is no such thing as software or online services and / or security systems that can’t be hacked)? Is it an opening or ongoing salvo in a marketing war in which simple users of CD- / DVD-Rom games are “collateral damage”?
Logic suggests the answer is YES!
The natural inclination of engineers is to solve problems. Microsoft, having likely gained at least limited intellectual property rights and access to source code for the SafeDisc drivers, undoubtedly has an engineering staff capable of rewriting SECDRV.SYS to the point that it will allow any holder of a valid activation key / serial number to install and run any application dependent on SafeDisc protection.
But engineers are always subject to the whims of “Management” who, from the 1970s onward have been drawn almost exclusively from either finance or marketing. With “marketdroids” in control of Microsoft (a fact of their existence since the initial release of Windows as an MS-DOS application in the early 1980s) directed irrational expenditures of engineering time, effort and budget to “sock it to competitors” will take precedence over solving problems for (even decades-long) loyal users.
THEREFORE, YOU WILL NEVER BE ABLE TO PLAY DRM-PROTECTED OPTICAL MEDIA BASED GAMES IN WINDOWS OPERATING SYSTEMS EVER AGAIN.
Making comments / votes on the “feedback app” will do nothing but provide info (likely surreptitiously collected) that will allow Microsoft to further “insulate” your system from games / applications / modules / drivers of companies with which they choose to go to war.
Bottom line, there will never be a fix to this problem (unless someone hacks SafeDisc so users can strip its protection from their game discs). So…
GET THE F#<& OVER IT!!
And if you don't want Microsoft to seek / execute further retribution for your use of non-Microsoft DRM / security / online services, don't attempt to give them 'feedback' that allows them to analyze your system for the next 'market competitor' product to ban from Windows!
-
Anonymous
2015-09-13T13:41:53+00:00 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!!!
-
Anonymous
2015-08-13T23:58:20+00:00 well that's good to know. site I saw didn't mention was fixed. so why doesn't Microsoft respond?