Same issue here. Same setup. Win7 and OpenDNS.

Ditto.

Same here. Open DNS setup on router (WNDR3700v1). Installed today's updates on two systems - one hard-wired to the router and another that connects via WiFi.

After the updates, the annoying and inexplicable "Additional log on ..." message kept popping up.

Switched DNS setting on router to "auto retrieve from provider" and messages magically disappeared. Bizarre. Hope there is a fix soon!

Haven't tried it yet ... but I am curious if I went back and now re-entered the OpenDNS info on the router, if the problem would return (or if resetting somehow clears something out). Will try that experiment later when the family isn't online.

This may have something to do with Windows 7's (along with 2008R2 from my testing) Network Connectivity Status Indicator service:

http://blog.superuser.com/2011/05/16/windows-7-network-awareness/

It seems that when your machine tries to connect to either dns.msftncsi.com or www.msftncsi.com upon start-up and detects something in the way (like a paywall, captive portal, proxy, etc.), it throws up that "additional logon..." balloon. Something with one of today's patches changed something and somehow gets affected by users behind OpenDNS (this doesn't happen to me using Google's public DNS servers or my IPSs DNS servers).

Using that page above, I temporarily disabled the "EnableActiveProbing" key, rebooted and did not receive that annoying bubble while still safely using OpenDNS's systems. There is a gotcha though and your machine may not think it's connected to the Internet at all after disabling that probe, YMMV. Either way, while I do not recommend anyone change their registry because of the possible damage to one's PC taking such measures, I was able to use OpenDNS's servers after this update without that annoying pop-up making that registry change. Naturally, after this is fixed, I'll be re-enabling the probe to return my PC to it's native functionality.

Thanks gotroot for the article/hack. But, I have 5 systems running Win 7 or 8 and really do not want to have to change the registry setting on each system (and then remember to revert!).

I submitted a ticket to OpenDNS. I have not seen anything about this yet on MS forums. This is pretty strange ...

Some Win7 guys have stumbled opon it.
http://www.sevenforums.com/general-discussion/264221-constant-additional-log-information-may-required-pop-up.html

And that KB2750841 update is the culprit.
http://support.microsoft.com/kb/2750841

zelus ... can you comment on my posting above, which is an email I received from one of your techs in response to my ticket. Thanks.

It looks like the patch adds IPv6 support to the Microsoft Network Connectivity Status Indicator (NCSI). I'm assuming that the error is in regards to the IPv6 trying to probe the network connection and failing.

The patch adds a key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet for ActiveWebProbHostV6, ActiveWebProbePathV6, ActiveWebProbeContentV6 etc..

Unticking the NXDOMAIN redirection in the control panel does IN FACT solve the problem (i.e. the pop-ups stop). Re-enabled EnableActiveProbing in the registry, etc. Flushed DNS and re-booted.

So, what are we now missing by NOT using NXDOMAIN redirection? Should we care?

Thanks!

Charlie

Seems more like a band-aid not a resolution. Why limit our functionality? I'm waiting for a fix from the gurus here at OpenDNS!

I do not have this setting under customization. Is this a paid user thing? What do I do> Use something else?

Thank you. I hope we are notified by email when this is fixed?

The problem with unchecking "Enable type correction (and NX Domain redirection)" is that is also disables the web content filtering. So if you want to filter out certain categories of web sites (like adware or porn) you can no longer have OpenDNS do so. That is one of the main reasons that I use OpenDNS. Hopefully this is just a bandaid and OpenDNS will fix it correctly so Content filtering does not need to be disabled.

I have the same issue. Windows 7, OpenDNS, Windows XP Virtual PC installed.

You can also suppress the notification balloons by pressing the "show hidden icons" arrow on the left end of the Windows system tray, clicking on "Customize", then setting the "Network" icon to "Hide icon and notifications". This avoids messing with the registry and, as far as I can tell, does not affect OpenDNS features.

daled: I do have a paid account (OpenDNS VIP). When I unchecked "NXDomain," I had no warnings. Only the "Guide Page" options were greyed out. I did email tech support with your question. I will post here when I hear back.

uscjnet: Thanks. On my screen, NXDomain and typo correction are the same check box. I just have the free home account.

kb2750841 is the update that causes opendns users to see that pop up. I have uninstalled it, or in computers that haven't yet been updated I am hiding the update until they get this sorted out. What a PITA.

I hope this gets fixed faster than Eset's problem their having with an update in Sept. from Microsoft that is messing with their program too which hasn't even been resolved yet. Haven't seen such problems like this before from hotfixes it's getting very frustrating.

There's a lot of users of OpenDNS that don't use an account and can't change those settings. I hope that OpenDNS will take care of this problem for those users also.

Until now I never had any problems with using OpenDNS with no IP associated to account. Neither did any of my friends.
Is there any official information that OpenDNS servers should be used with accounts only?

By logic basic Domain name resolving should work without accounts.

Uninstalling update KB2750841 worked for me to fix it.

I just reinstalled the windows update on this win7 64 computer and not getting the pop ups. I didn't mess with the nxdomain redirection, so everything else is the same.

I installed updates on system in Vitualbox and both of my computers and I don't get the popup any more.