

4·
13 days agoAudio playback is such a low-demand process, surely a player (e.g.VLC) can spare a thread to line up playback of track 2, a few seconds before track 1 ends? It knows the exact length of the track, why can’t track 2 be initiated when the audio level in track 1 drops to zero (or minus infinity dB) in the last frame?
Ah yes, that’s a concern - but I have a job in Task Scheduler that re-writes my registry tweaks - mostly changing various tasks back to “disabled”. You can trigger it hourly, or on an event. As soon as a selected event - such as a telemetry switch-on - hits the event log, the “disable” script runs.
There’s other ways, like taking ownership of the executables and changing permissions to lock out the “SYSTEM” account.
And pihole blocks DNS resolution of the telemetry harvesters as well. Windows update won’t touch that. It’s not 100% effective, but I couldn’t be bothered to take it further.