So, I had a deep think about this issue. And the one bit of info that keeps coming back up in my mind is that this is happening on two machines simultaneously. Correct???
This definitely implies that it is unlikely to be a strange configuration problem, hard disk issue, or permissions problem – those are all fairly rare things – and it would be unlikely (although not impossible) for two machines to experience identical issues at the same time.
This leads me to think that it is more likely something that is common to both machines and the error message is just a red herring.
So… we can do one more brainstorming session on this to see if we can think of anything anomalous that might prevent updates.
What is common between the machines?
- do you have any shared networked drives/backups/etc?
- did you restore both machines from the same backup?
- is there anything else that they share?
- do they both run any type of virus/malware checker?
- have you done anything “special” to both machines? (like reformatting with case-sensitivity enabled – this is something Linux users and developers sometimes like to do).
And lastly, how is your network configured? Is there anything “interesting” about it?
- do you use a proxy server?
- do you have a firewall?
- do you use any network reporting tools like Little Snitch to block app network access?
- parental filtering router? dns-cache-poisoning (Disney Circle)?
OK, that’s about all I can think of at this point. If none of those yield anything I think it’s probably just up to @simon or another RW dev to trace out any other possible mechanisms that exist to generate that error message.