Now that is interesting. Did you try running the game first? The key shows up after the game is run.

I ran the game with CrysisLauncher.exe and that should invoke the 64-bit binary. But I wish we could get a Blue in here to check to see if it's installing any other part of SecuROM on the computer.

I tried running the two games with 32-bit binaries (Wars didn't have one). I tried searching for the key with the games running.

It never showed.

Okay I get it, thanks a lot for the explanation :)

Okay, from reading the comments here, it sounds like it doesn't actually install SecuROM, but instead just some empty folders and a couple of unused registry entries. Hopefully none of these are in that "undeletable" state where you need the SecuROM removal tool to get rid of them.

Can anyone give a full list of the SecuROM related files, folders and registry entries that this game creates? Just so that we can remove them all manually if they don't get removed on uninstallation?

This would be possible to check by downloading the manual installer from the Backups & Goodies tab and installing the game in a sandbox (via for example) along with [url=https://www.portablefreeware.com/index.php?id=1433]RegFromApp recording to check for created/modified Registry entries.

Edit: from the posts above it seems the registry entries are 'undeletable' in so much as they are re-added upon subsequent game launches. Would be preferable to have no such SecuROM references added but perhaps they're needed for the game itself. Someone from the GOG team can probably comment on this.

No, by "undeletable" I'm referring to SecuROM files and registry entries that are named such that they cannot be deleted normally. For instance the registry entries have special characters and trying to delete them only returns an error message. This is why the SecuROM Removal Tool has to be used. The ones mentioned here, though, suggest that they can be deleted, just that they get recreated each time the game is run. However, I'd prefer to get confirmation on this before I decide whether or not to buy it.

The original Crysis is creating the SecuROM entries in the Registry, but I still don't know if it is creating other SecuROM files on the computer. I was able to delete the Registry entries, but they are recreated if Crysis 1 is run again. Are the entries in the Registry just dummy files?

I've also tested Crysis: Warhead and found out that it creates no SecuROM entries in the Registry at all. So this seems like a weird bug in the original Crysis.

Do you have a folder at the below location (referring to your specific username):
C:\Users\<username>\AppData\Roaming\SecuROM\

My guess is it is just a bug creating dummy registry entries that are empty and do nothing, so not actually SecuROM, and not even an inert SecuROM, but I'd like to be sure.

Crysis Warhead does have an issue, though, in that the copy protection wasn't fully removed resulting in guns shooting out chickens instead of bullets. This only affects the 32-bit version and it got removed from the store, so only the 64-bit version of Warhead is now available.
https://www.gog.com/forum/crysis_series/notice_temporary_removal_of_crysis_warhead_32bit_version

There is nothing else to find..............because it isn't installing securom for anyone ( but warhead 32bit users.)
And gog will address that issue..well they sort of have by removing it :/
It's just a few leftover folders, that can be removed once the games uninstalled.

IF securom was installed you would see a bunch more folders eg...

Keys .
!Caution Never Delete.
License & Info + readme folders.
UserData.
WL.

You don't as it's not installing jack shit....btw the removal tool will still flag securom.
Why? because it found a obsolete folder...one folder :P

Edit - my typing sucks fluffy balls.


If you like to keep track of what installed with any game/software use a snapshot tool.
Useful for cleaning up after many applications as CCleaner and such don't always remove all entries.

Yeah, GOG said that Warhead 32-bit version had an issue, but from what I can tell the 64-bit version is fine. I still hope that Crysis 1 is only creating dummy files and nothing else.

Normally, I'd say "lesson learned: don't buy any more EA games here on launch day." Except... EA logic:
If we keep buying their titles on launch day, they'll think they can get away with stuff like this, or even forget to take out the DRM entirely.

If we don't, this isn't a viable place to sell anything.

My logic is "If I buy at a discount of less than 50%, I'm getting ripped off and, if I pay more than $5, I won't have enough money to buy every game I approve of, so, if the game never meets those terms on a DRM-free site, I'll just play one of the thousands of other games I own or ramp up my novel-collecting."

IsThereAnyDeal.com's waitlist notifications are good for adopting such an "out of sight, out of mind" policy.

Was it confirmed by GOG it's just a dummy folder?

Registry entries cannot be anything but dummy.

They are just data. They don't *do* anything.

Anyone who looked saw it was just two empty registry keys that you could indeed remove.

So far nobody's found any evidence of active DRM except for the chicken problem in 32-bit warhead. So what's there to confirm?

From what korell posted and others are looking to know, a couple things:

1. Does the game add un-deletable registry entries (not referring to the registry keys that for whatever reason are re-added upon game launch but keys which actually can't be deleted due to special characters).
2. Apart from the registry keys created are any other SecuROM leftovers added.

Considering the only real reason they're looking to buy the game on GOG is to have a clean, SecuROM-free version it's not that unreasonable for them to ask. Pretty sure no one is under the impression SecuROM itself is active, however.