New
#11
Well that was my concern too but I would imagine they are pretty hot on security.
I thought I'd post illustrations of what I did:
Well that was my concern too but I would imagine they are pretty hot on security.
I thought I'd post illustrations of what I did:
As a footnote I tried reversing that setting and immediately a WU check failed with the same error code. I'll keep testing it from time to time.
I plan on doing just that next time I boot into 7. Must have been a DNS issue and ISP's couldn't reach MS servers as reports are showing up on their forums that it's now working OK anyway.
Thanks ;-)
Microsoft's changed DNS must have finally filtered through the world-wide web as I can now poll for updates without getting that error with my DNS set back to the default (Automatic).
So it appears that things are normalizing again.