Advanced Control dead on local PC but OK on distant PC
Posted: Wed Apr 15, 2020 5:25 pm
Weird! On the local machine, the Advanced Control is like dead, does respond at all. I just could close it, and I can't launch it back. But it still works in the background (Task Manager dixit), the Web Control shows a normal progression, AND I can control it normally on another PC with a remote connection (within Advanced Control). Win 10 Pro 2004 Build 19041.207
EDIT: Had to reboot the machine. All is ok now on the local PC, but the remote access can't be reestablished (IP unchanged). I can establish a Remote Desktop Connection, though. 
EDIT2: As I was at it, I made a few (firmware) updates on the main PC (Win Pro 1909), with several reboots. And after that, All Clear. I'll assume it's part of the risks running an "Insider" version of Windows.
Code: Select all
14:30:33:WU01:FS02:0x22:************************************ System ************************************
14:30:33:WU01:FS02:0x22: CPU: Intel(R) Core(TM) i9-7940X CPU @ 3.10GHz
14:30:33:WU01:FS02:0x22: CPU ID: GenuineIntel Family 6 Model 85 Stepping 4
14:30:33:WU01:FS02:0x22: CPUs: 28
14:30:33:WU01:FS02:0x22: Memory: 31.70GiB
14:30:33:WU01:FS02:0x22:Free Memory: 24.64GiB
14:30:33:WU01:FS02:0x22: Threads: WINDOWS_THREADS
14:30:33:WU01:FS02:0x22: OS Version: 6.2
14:30:33:WU01:FS02:0x22:Has Battery: false
14:30:33:WU01:FS02:0x22: On Battery: false
14:30:33:WU01:FS02:0x22: UTC Offset: 2
14:30:33:WU01:FS02:0x22: PID: 15432
14:30:33:WU01:FS02:0x22: CWD: C:\Users\ajmch\AppData\Roaming\FAHClient\work
14:30:33:WU01:FS02:0x22: OS: Windows 10 Pro
14:30:33:WU01:FS02:0x22: OS Arch: AMD64
14:30:33:WU01:FS02:0x22:********************************************************************************
(...)
16:04:55:<config>
16:04:55: <!-- HTTP Server -->
16:04:55: <allow v='127.0.0.1 192.168.2.59'/>
16:04:55:
16:04:55: <!-- Network -->
16:04:55: <proxy v=':8080'/>
16:04:55:
16:04:55: <!-- Remote Command Server -->
16:04:55: <command-allow-no-pass v='127.0.0.1 192.168.2.59'/>
16:04:55: <password v=''/>
16:04:55:
16:04:55: <!-- Slot Control -->
16:04:55: <power v='full'/>
16:04:55:
16:04:55: <!-- User Information -->
16:04:55: <passkey v='********************************'/>
16:04:55: <team v='182116'/>
16:04:55: <user v='ajm'/>
16:04:55:
16:04:55: <!-- Folding Slots -->
16:04:55: <slot id='0' type='CPU'>
16:04:55: <cpus v='24'/>
16:04:55: </slot>
16:04:55: <slot id='1' type='GPU'/>
16:04:55: <slot id='2' type='GPU'/>
16:04:55:</config>EDIT2: As I was at it, I made a few (firmware) updates on the main PC (Win Pro 1909), with several reboots. And after that, All Clear. I'll assume it's part of the risks running an "Insider" version of Windows.