[BUG] denuvo 88500005

[WolfGames156]

Prerequisites

• I have searched existing issues and confirmed this has not been reported.
• I am using the latest build version from the releases page.

Steam client version

stabel 1780352834

Windows version

win 11

Describe the bug

I created a Lua script using an extracted ticket for Denuvo-protected games.

I'm sure the ticket is correct. It worked with Pragmata, but it did not work with 007 First Light or Crimson Desert.

I also checked the registry, and both the AppTicket and eTicket appear to be written correctly.

I tried multiple different tickets, but it still didn't work.

I shared the error below.

Also, this is unrelated to the topic, but I think you should improve OnlineFix much more. It doesn't work in some games—in fact, it hardly works in almost any of them. If this feature actually worked properly, it would be excellent.

Steps to reproduce

Place the required DLL files in the Steam root directory.
Configure the Lua script with the target AppID and extracted ticket.
Set both AppTicket and eTicket using setAppTicket() and setETicket().
Launch Steam and start the game.
Observe that Denuvo authentication fails with error code 88500005.

Expected behavior

The game should launch successfully after setting a valid AppTicket and eTicket. Since the same method and ticket extraction process worked with Pragmata, I expected 007 First Light and Crimson Desert to accept the ticket and proceed normally without returning a Denuvo error.

Actual behavior

The game fails during the Denuvo authentication stage and returns error code 88500005. The AppTicket and eTicket appear to be written correctly in the registry, and multiple extracted tickets were tested, but the result remains the same. The issue only occurs with certain Denuvo-protected games, while others (such as Pragmata) work correctly using the same setup.

Log files

winhttp.log
achievement.log
decryptionkey.log
ipc.log
keyvalue.log
main.log
manifest.log
misc.log
netpacket.log
onlinefix.log
package.log
pics.log
richpresence.log
steamui.log

Lua configuration (if relevant)

addappid(3768760)
addappid(3950810)
addappid(3950820)
addappid(3950830)
addappid(3950850)
addappid(3950870)
addappid(3950880)
addappid(3950900)
addappid(3950910)
addappid(3950930)
addappid(3954230)
addappid(3954250)
addappid(3954260)
addappid(3986520)
addappid(4521800)
addappid(4521810)
addappid(4521820)
addappid(4521830)
addappid(4521840)
addappid(4601250)
addappid(4626160)
addappid(4707780)
addappid(3768761,0,"8284c5e8921ec5acbe53f4d45af0260905841dc698ca179dd218ce5a2657ef09")


setAppTicket(3768760, "xxx")

setETicket(3768760, "yyy")

Additional context

[Temlpe]

It’s possible that the account you used to obtain the license no longer has any available slots, as Denuvo limits each account to five slots.

Additionally, the Ticket you provided in Lua is xxx, yyy, which is clearly not a valid Ticket.

[WolfGames156]

I’m aware of the daily limit of 5 devices, and there are currently fewer than 5 devices associated with the account. As far as I remember, the error message shown when the 5-device limit is reached is different. If there are any other restrictions besides the 5-device limit, could you explain them in a bit more detail?
Also, I used "xxx" and "yyy" because I preferred not to share the actual ticket details.

[OpenSteam001]

Thank you for the detailed issue report. Please set the log level to debug in opensteamtool.toml, then reproduce the issue and upload the new logs.

[WolfGames156]

I updated the log files

[WolfGames156]

I also tried it without the DLCs, and it still didn't work.

[OpenSteam001]

Thanks for the report.

Based on the logs you provided, the eTicket itself looks fine and appears to be written correctly. I don’t currently see an obvious issue on the OpenSteamTool side with the ticket handling.

Do you know whether the eTicket was used within Denuvo’s validity window? As far as I know, Denuvo has a roughly 30-minute time window for the generated eTicket. If the ticket is older than that, Denuvo authentication may fail with error 88500005, even if the AppTicket/eTicket data itself is correct.

Could you try again with a freshly generated eTicket and make sure it is used immediately after extraction?

[WolfGames156]

I know, yes, that's why I recreated the ticket and tried many times, and the same error occurred again. I think there's a different problem.

[WolfGames156]

Perhaps the game is giving an error because the Steam ID in the ticket doesn't match the Steam ID of the account currently active on Steam?

[OpenSteam001]

Perhaps the game is giving an error because the Steam ID in the ticket doesn't match the Steam ID of the account currently active on Steam?

The spoofed SteamID from the registry is 76561198711743417, located at:

HKCU\Software\Valve\Steam\Apps\3768760\SteamID

Is the SteamID inside the extracted eTicket the same as this one?

[WolfGames156]

Perhaps the game is giving an error because the Steam ID in the ticket doesn't match the Steam ID of the account currently active on Steam?

The spoofed SteamID from the registry is 76561198711743417, located at:

HKCU\Software\Valve\Steam\Apps\3768760\SteamID

Is the SteamID inside the extracted eTicket the same as this one?

There was no value named SteamID in the place you mentioned. When I created one and entered it, a different problem occurred. It says "Try again in 24 hours, a problem occurred." It might be because I sent too many requests. I'll try again later.

[OpenSteam001]

@WolfGames156
Sorry, I may not have described it clearly.

I don’t mean that there should be a registry key/path named:

HKCU\Software\Valve\Steam\Apps\3768760\SteamID

What I mean is:

Registry key/path:

HKCU\Software\Valve\Steam\Apps\3768760

Value name under that key:

SteamID

Value type:

REG_SZ

Value data:

76561198711743417

According to your log, OpenSteamTool read this SteamID value successfully:

GetSpoofSteamID for AppId 3768760: SteamID REG_SZ -> 0x11000012CCAA3B9(76561198711743417)

So I want to confirm: is the SteamID inside the extracted eTicket also 76561198711743417? In other words, was the eTicket extracted from the same Steam account?

[Temlpe]

For example, the account SteamID for extracting Ticket is 76561198711743417, and you need to write this value into the corresponding registry.

[WolfGames156]

yea 76561198711743417 this id same with extracted ticket steam account

[JackRipper-Rips]

the 00005 is usually when a ticket has become invalid, this is often caused by things like windows updates, game updates, bios changes or even sometimes force closing the game.