Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steam installscript.vdf checking other keys for EA App #31

Open
4 tasks done
Fractal147 opened this issue Dec 14, 2023 · 2 comments
Open
4 tasks done

Steam installscript.vdf checking other keys for EA App #31

Fractal147 opened this issue Dec 14, 2023 · 2 comments

Comments

@Fractal147
Copy link

Checklist

  • I ensured I'm running the latest version of the patch, and that the issue is present in it if applicable
  • I have read the entirety of the FAQ section in the readme, and my question was not answered there, or was not answered sufficiently
  • I have ran general troubleshooting steps (if applicable), such as restarting the PC/reinstalling Origin/whatever else is described in the FAQ, and they didn't help
  • I have checked existing issues (including closed ones), and there wasn't an existing issue pertaining to my problem (with possible solutions in the comments)

Your issue

Reinstalling today (proton 7 fwiw), Mass Effect Legendary repeatedly runs installscript.vdf, despite the "Pretend EA App is installed" checkbox.

Turns out Steam is checking a new key: and adding it in manually 'fixes' it.

"HasRunStringKey"               "HKEY_LOCAL_MACHINE\\SOFTWARE\\Electronic Arts\\EA Desktop\\InstallSuccessful"
"HasRunStringValue"             "true"
@p0358
Copy link
Owner

p0358 commented Dec 14, 2023

Hmm, thing is, the HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Electronic Arts\EA Desktop\InstallSuccessful in README is 64-bit registry, which corresponds to HKEY_LOCAL_MACHINE\SOFTWARE\Electronic Arts\EA Desktop\InstallSuccessful in 32-bit registry, and Steam was generally checking the 32-bit one. I wonder where's the disparity now then...

The installer should create that key if checkbox is ticked (in HKLM, meaning HKEY_LOCAL_MACHINE in 32-bit registry):

Root: HKLM32; Subkey: "SOFTWARE\Electronic Arts\EA Desktop"; ValueType: string; ValueName: "InstallSuccessful"; ValueData: "true"; Flags: createvalueifdoesntexist; Check: IsEAAppCheckBoxChecked

Can you upload the full installScript.vdf of that game? I'll also need to check later if perhaps EA App would now create the keys in both places, if it doesn't, then the issue may be laying somewhere else...

@Fractal147
Copy link
Author

Certainly, though from what you've said it's probably not an issue with the FOEAA patch.
installScript.vdf.txt

Perhaps some wine/proton/protontricks issue where somehow the the 64-bit keys are not getting duplicated to the 32-bit land? But dunno - it certainly used to work with no issue on 2023-08 ish. No obvious changes to installscript or game since 2023-01. Hm!

Checked again right now with freshly validated game install, and new Proton Experimental prefix - same issue, installscript.vdf being run even after FOEAA patch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants