Correct. With the reboot command. I did get a warning upon doing from SSH, as you see in the code above. It did reboot, though. I don't see where the update was executed. It appears to have been downloaded, then expanded.

On second look, it appears the update was downloaded, but not executed. Could you please let me know how that is done?

I'm not too comfortable with SSH, yet, but here is the output from Putty. It appeared to work, though upon restart it's still using 4.0.0-build 10 23/02/2016). Thanks. # /recalbox/scripts/recalbox-upgrade.sh --2016-03-19 17:52:29--  http://XXXXX.recalbox.com/4/rpi2/stable/last/boot.tar.xz Resolving XXXXX.recalbox.com... 37.187.92.30 Connecting to XXXXX.recalbox.com|37.187.92.30|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 5342084 (5.1M) [application/octet-stream] Saving to: '/recalbox/share/system/upgrade/boot.tar.xz.part'   /recalbox/share/sys 100%[===================>]   5.09M  65.6KB/s    in 28s   2016-03-19 17:52:57 (189 KB/s) - '/recalbox/share/system/upgrade/boot.tar.xz.part' saved [5342084/5342084]   --2016-03-19 17:52:59--  http://XXXXX/4/rpi2/stable/last/root.tar.xz Resolving XXXXX.recalbox.com... 37.187.92.30 Connecting to XXXXrecalbox.com|37.187.92.30|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 194676292 (186M) [application/octet-stream] Saving to: '/recalbox/share/system/upgrade/root.tar.xz.part'   /recalbox/share/sys 100%[===================>] 185.66M  3.52MB/s    in 2m 18s   2016-03-19 17:55:18 (1.34 MB/s) - '/recalbox/share/system/upgrade/root.tar.xz.part' saved [194676292/194676292]   # reboot WARNING: could not determine runlevel - doing soft reboot _  (it's better to use shutdown instead of reboot from the command line)_   Broadcast message from root@RECALBOX (pts/0) (Sat Mar 19 17:56:45 2016):   The system is going down for reboot NOW! #

When I try doing a system update from ES/Recalbox (4.0.0 build 10 23/02/2016 20:10) from Wi-Fi, I get the "working" icon and then a pop-up for a "Network Connection Needed" prompt. Yet, I have connected, working Wi-Fi according to ES. Any ideas? Do I need to do a fresh install with the latest beta? Try an Ethernet cable? I hate to lose the settings/saves I've done the past few weeks. Both ES and the splash screen at startup acknowledge I'm on 4.0.0-build 10 23/02/2016 20:10). I have Auto Update set to "OFF" and Overclock at 900 mHz (so, no overclock). Regards, Bryan