Found it:

1. Go to:

<…>\Cyberpunk 2077\r6\publishing\x64

2. Create a copy of the “GOG” subfolder next to the original one.

3. Rename the copy of the “GOG” folder to “null”

4. Go to:

<…>\Cyberpunk 2077\bin\x64

and delete the:

GameServicesGOG.dll"

https://www.gog.com/forum/cyberpunk_2077/a_fix_for_the_crashing/post70

Do you use the GOG version? If so, they changed something about the drm recently, you need to remove some files from the game directory. Then it’ll start working again. Let me check if I can find the reference to that…

Might be trying to delay the execution itself since there is a shortage of the “regular” injection they use because of embargoes?

Interesting points, I’ve definitely run into memory constraints which resulted in completely unresponsive hosts a few times over the years. But as the author said, I don’t see this changing within any another of time due to the large scale archetectural changes required… The author also mentioned “I’m tempted to abandon using Windows, macOS and Linux as the main platforms with which I interact.”. Does anyone know which “daily driver” compatible operating system the author could be referring to?

I’d be interested to know how they’re going to track this? They’d need to create some sort of fingerprint for each device, and store it together will all already installed games / software in some sort of database in perpetuity.

In the end it depends on your risk profile and adversary model. Usually it’s not a good idea though. Why not have an SSH tunnel to the network/machine and use port forwarding to forward the RDP connection? Or why not use SSH for remote access, period?

Might be for time synchronization in order to not have to rely on a public NTP server.