Project64: Difference between revisions
No edit summary |
Gabrielwoj (talk | contribs) →Malware and nagware: Added another way to get rid of the nagware screen that does not rely on patches and scripts. |
||
| Line 60: | Line 60: | ||
Version 2.4.0.1555 introduced a new method, with a per-machine ID that gets generated on the user side and requests a confirmation code associated with it. You can avoid it thanks to [https://github.com/Rosalie241/PJ64Launcher this script] by Rosalie241. | Version 2.4.0.1555 introduced a new method, with a per-machine ID that gets generated on the user side and requests a confirmation code associated with it. You can avoid it thanks to [https://github.com/Rosalie241/PJ64Launcher this script] by Rosalie241. | ||
Another way to do so is by using Regedit and removing the <code>user</code> REG_BINARY key from the HKEY_CURRENT_USER\SOFTWARE\Project64, then changing the permission from the Project64 folder (on Regedit) to deny Full Control and Read on the user you are currently signed in, [https://www.youtube.com/watch?v=Qg4L-bcLlxw as explained on this video]. Doing so will disallow Project64 from creating the key again, which is responsible for the nagware screen popup. | |||
===Windows 10 BSOD=== | ===Windows 10 BSOD=== | ||