It was "just me".
Problem traced to a batch of Windows Updates installed this morning: Now running fine after having restored the system to an earlier point (yesterday).
But I thought I might leave my original post up in case this helps anyone else.
[Edited to add:] The culprit was KB833858.
Last edited by Globaliser; Jul 4, 2006 at 8:56 am