I'd kill for that error.

At least it would be getting somewhere. I'm stuck with something that appears to be port related and the corp firewall, it say no.

I'm guessing here, but my money's on the voice 'n video side. Looking at what this wants, it needs a right shedload of open ports. I reckon that the older versions (8.5 and lower) just used to accept that they were closed, disable the cruft and get on with the real job at hand that you installed the sodding thing for in the first place. The new versions sit in a corner and sulk. Can't for the life of me figure out why they'd make this change though, assuming that I'm on the right track (although sheer blind stupidity's got to be a prime suspect).

@Mighty Error Code Number !

While I agree with the sentiment, only the low 16 bits are used for the error code. The high 16 bits are used to identify the source and provide other classification info:

http://msdn.microsoft.com/en-us/library/ms819773.aspx

So if it's a genuine windows error, it's code 0x1D (29).

Re: Skype

I think that even Microsoft users have levels to which they will not stoop.