We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
I observed an access violation when running SDIO_x64_R817.exe in scripted/automated mode. Manual GUI-based download+install does NOT reproduce the problem.
Steps I took:
1. Generated an automatic script (attached as topgrade_sdio_script.txt) and ran SDIO with:
C:\Windows\System32\sudo.exe 'C:\Users\<user>\SDIO_x64_R817.exe' -script '...\\topgrade_sdio_script.txt'
(Topgrade invoked SDIO under the sudo wrapper; used_sudo = true.)
2. Result: process crashed with EXCEPTION_ACCESS_VIOLATION (0xC0000005). Topgrade captured .dmp files via procdump.
3. I also tried:
- invoking the same sudo wrapper directly (it returned RPC error 0x800706BE),
- running the EXE elevated directly (Start-Process -Verb runAs) — interactive manual GUI install does not reproduce the crash.
4. Artifacts attached: topgrade_sdio_artifacts.zip — contains the generated script, sdio_stdout/stderr, sd io_run_summary.json, the .dmp files in sdio_dumps, and analyzer logs.
Observations:
- Crash only seen when run via script/automation or via the wrapper; interactive GUI install succeeds on the same machine.
- The attached run summary shows exit_code = -1073741819 (0xC0000005) and used_sudo = true.
Requests:
- Can you confirm whether r817 contains a regression for scripted installations?
- Any immediate mitigation suggestions (e.g., avoid a specific script command such as `restorepoint`, or a recommended wrapper)?
Thank you — I can re-run with further instrumentation if needed.
I can't account for "sudo.exe" but I'd be interested in looking at the script and log files.
gist.github. com /niStee/a7900a329a3d3b78e2e21442b0ab2119
@nistee You need to move the call to "init" up the script, right after "logdir" say.
Edit: I've added checks to make sure the script engine is initialised.
Thanks