Security Module 8016 Issue on Launch

[Shifty]

Fable 3 gives me a prompt saying that the Security Module has failed to activate.
I purchased the game off of Steam a while back before it got pulled and I have all the DLC for the game if this makes a difference.

I've tried running the game in compatibility mode for Windows 8, 7, Vista and XP but none have worked. I've also tried verifying steam cache, but I have all the files for it.

I'm running on Windows 8.1, so it shouldn't be a Windows 10 issue. Nobody seems to have a clear solution from looking around, so if somebody can think of something, that'd be awesome.

http://i.imgur.com/Zi3aux5.png - A link to an image of the prompt box I get on launch

[SilverFish]

Go into the installation directory and delete F3Secu.exe, Fable3.exe & FableLauncher.exe.

Path steam > steamapps > common > fable 3

Then after doing that right click on the game from the left hand side and select properties. Now click the Local Files tab and click Verify Integrity of Game Cache.

This forces the startup files to download again. Should work after doing this.

The Securom thing is actually from the disc version of the game where it activates with the key server. It does do it with the Steam version but should do everything automatically.

if it works then thx "iaincmet" who i copy pasted this from ^^

[Shifty]

Unfortunately this didn't work, still getting the security module popup :/
Know of anyway to bypass the securom by chance?

[Protonic Flux]

Same issue. What a load of ♥♥♥♥. Steam should stop selling this game.

[Shifty]

Steam doesn't sell it, they stopped in like... 2013? They ran out of keys for the game and them and Microsoft never resolved it.

[carrieshot ♣™]

any gfwl game seems to have the problem of the same 8016

[Nikki]

I understand it's a problem with some motherboards BIOS. I haven't ran into that issue yet, and my current motherboard is an ASUS TUF X299 Mark 1. I bought it in Aug/2017. Yes Fable 3 runs fine on it, but without a GFWL remover/emulator it gets stuck in an update loop for GFWL.