[beluczywo]

I just finished testing with dot net 3.5 and symptoms were exactly the same.
Regarding gguru's comments about "recently":
So if I've never tethered/logged in on this pc because of the firewall issue, it has never seen a successful login and therefore will always exit BuildOS.

The credential issue is exactly what I would expect and I hope overtyping the default actually works -- you might double-check the code to make sure that it truly uses overtyped login info (no place that I know of in BuildOS, but even Updater doesn't work with overtyped credentials -- might be a clue of where the problem is). Any way to have BuildOS prompt for login like Updater does so it is more explicit as to what is occurring?

I can also easily believe that dot net and proxy is, to use your word, "complicated". If there is a choice, using the "internet connection" information seems the MOST global within windows (but not the only for sure). If there is a selection box of where to look in the API, that would probably be the most robust for the most users as opposed to assuming SOCKS or something else.

It sounds like if I tether/login (might not be possible, I don't get good phone signal at my desk), I could login once and then potentially use BuildOS for "a while". I hesitate to ask and I'll understand if your answer was deliberately vague, but it seems to beg the question -- how long is "recently"? Feel free to say "that's need to know".

Probably the next step if you are willing, is to try the little app you mentioned and give you more detailed trouble-shooting info. If not, I guess I'm just doing things at home or taking new kitchens and whacking them to work with old BuildOS code.

Thanks for the continued help and suggestions. Have we ruled out a temporary work-around pending debugging?