@theopolis thank you! That definitely serves as a workaround. Still troublesome for the average Joe user to have know a priori what extensions have been configured as auto-load to avoid a flurry of socket errors.