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

Actually, you would have to uninstall Windows 10, 8.1, 8, 7, Vista - every version of Windows later than XP as Microsoft pushed this "update" retroactively to all OS's that had not been end-of-lifed by June of 2015 or thereabouts.

Once again, this is not about existing users - we don't count in Microsoft's estimation.  It is about corporate warfare with Rovi (the current incarnation of Macrovision, or at least ancestor / inheritor of Macrovision technology, patents, royalties etc.).  If you look, many of the cable and satellite set-top boxes in the western world and a good deal of south-east Asia run Rovi software which **** Microsoft off to no end.  It thwarted their ridiculous goal to be the monopolistic owner of the set-top-box and over-the-top content delivery mechanisms and systems.  The fact that ChromeTV and all the other content delivery devices / services have long since pre-empted that goal is lost on Microsoft, and out of pure spite they will do whatever it takes to make sure Windows users are precluded from access to products provided by its sworn corporate enemies (Rovi, Google, Apple to name a few).  And don't forget the game console wars.  In Micorosft's mind, if you want to play games, get an Xbox - your computer is no longer going to be allowed to play any game that is adware free, even if you did pay for a "perpetual license" on the Windows PC platform.

Hi everyone, here is a solution works for me.

1. Download SECDRV.SYS and dseo13b
2. Copy past SECDRV.SYS to windows\system32\drivers
3. Open dseo13b, enable test mode, then sign files, input path: C:\windows\system32\drivers\secdrv.sys
4. Run cmd as admin, enter "bcdedit /set testsigning on" (without quote)
5. Reboot

Do aware this method makes your system vulnerable to many viruses, please be cautious. Cheers!

A workaround like this should not be required to play games that are legally purchased, and would otherwise work perfectly fine.

In the Windows 10 Feedback Hub, I've posted about this. Title of the feedback is "Windows x64, SafeDisc/SecuROM Copy-protection (SecDrv.sys), and older games" without quotes. It also has a comment with a link that points to this post.

If we all provide feedback in the hub on that same thread, maybe we can convince them that this is actually important to a lot of people.

EDIT: Here's a link to the one I setup in feedback hub.

https://aka.ms/Ijucz6

I set it up in security, because Microsoft says it's a security concern.

Please post this thread in the Feedback hub AND share the link to this entry in the feedback hub

appropriate category apps and games > all other apps

Thanks

or comment and upvote on my submission:

https://aka.ms/Mr337x

None of these workarounds function any longer (at least since "Creator's Update"). 

Using dseo13 leads to a BSOD on reboot (after you disable your virus / firewall software because it will, if created by a "Microsoft Partner" block/quarantine/remove dseo as soon as you try to put it anywhere on your system.

The "bcdedit /set {bootmgr} displaybootmenu yes" method fails if you have a USB keyboard because the boot menu appears before the USB driver is loaded, and the keyboard input is thus not enabled.  Beat that F8 key all you want.  The boot menu times out and you get a normal boot.  At least this is try on UEFI systems.  I havn't dug out an old PS2 keyboard to see if that makes a difference.

However, I believe that MS saw these workarounds and pushed updates to defeat them, a practice they seemed to initiate when the initial suggestion was to revert to WIndows 8 or 7 (whereupon they pushed updates down to ALL supported previous windows OS's to block any workarounds whatsoever.)

As I mentioned ages ago, as soon as a workaround is posted, MS will push an update to defeat it.  You are going to buy that g@& d@#^ X-box if you ever want to play a "windows game" ever again!  At least that is the message MS is trying to send you.