This was observed in a Hameg HMO2524 setup: Pulseview does not remember settings for TCP connected devices (see #882). Pulseview does remember settings for USB connected devices. Upon close and re-start, the previous state of enabled channels and probes is retained. For the first connect to a USB attached HMO2524, the channels' state is determined via SCPI queries, but does not reflect in PulseView's probes dialog. Instead, all channels are enabled. After manual adjustment, the state is retained across invocations (see above, for USB, not TCP).
Turns out this is a hameg-hmo issue as the channel state isn't updated when querying the device state. Compare http://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/hameg-hmo/protocol.c#l449 with the drivers that don't show this bug: http://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/yokogawa-dlm/protocol.c#l447 http://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=src/hardware/rigol-ds/protocol.c#l795
*** Bug 1068 has been marked as a duplicate of this bug. ***
Fixed in bd70ec4b7325707a8b2f2fdf5ebf097051781c7b, thanks!