Constant 'Additional log on information may be required' pop-up

[UnderBoac]

@Windude

that only hide's the problem imo

 

[TomChicago]

I agree with Urthboundmisfit -- I have isolated the problem to the same update, No. KB2750841. Removing this update by way of Control Panel / Programs and Features / View Installed Updates, eliminates the pop-up balloon problem.

I am running two computers on a home network, one with Windows 7 Home Premium, and the other with Windows 7 Ultimate. The "Home Premium" computer is where I first detected this problem. I am now doing the same update on the "Ultimate" computer to see if I get the same result.

Concerning Windude99's suggestion to hide the network icon -- that, of course, will make the problem invisible, but I'm not sure this solution is advisable. It seems comparable to a patient running a fever, but rather than give him an aspirin, you change the numbers on the thermometer.

Sorry to hear that Mijcar was charged $103 for Help Desk services from Microsoft. But now that this information is available, the decision is whether to "hide" the update, or make the Registry change. I guess I'll try both options, one per computer, and see if there is any difference in performance. However, I will say this: I have hidden Windows Updates in the past (especially when running Vista -- I hid SEVERAL) and encountered no problems.

 

[uhanif100]

It cost me $103, but MS fixed it.

This involves a change in a registry key. Don't do this if you are not familiar with such changes. Always backup your registry first.

Open regedit and navigate as follows:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NlaSvc\Parameters\Internet

Double-click on EnableActiveProbing

Change value to 0.

Best Wishes,
Michael

yup registry fix working for me , using OpenDns and pop up message is gone

 

[charlieo]

In OpenDNS control panel . . . uncheck NXDOMAIN redirect. Reset EnableActiveProbing in registry to 1 and flush DNS. Reboot.

Works flawlessly now. Not sure yet what we lose without NXDOMAIN redirect, but OpenDNS seems to be working correctly (blocking, etc.). Waiting to hear what OpenDNS support says or if they can just fix by including the resolution for the sites that currently don't resolve.

 

[gilloz]

THIS IS RESPONSE FROM OPEN DNS.

Sorry to hear that you're having issues. I just read through both forum posts, and while somebody did post a registry fix in the Seven Forums thread, I'm wondering if a setting in your OpenDNS account is causing the issue. So far, it's sounding like this problem may be caused by the NXDOMAIN redirection setting being enabled for your network.

In order to resolve this, please log into the Dashboard and select Settings. After that, select your network, and then choose "Customization" in the left-hand menu. You will be brought to a page that you will allow you to toggle the "Enabled NX Domain Redirection" option. Please disable that option.

After that, flush your DNS resolver cache and web browser cache on each device to ensure that your new DNS configuration settings take effect immediately. Instructions to clear your DNS resolver cache can be found here: http://www.opendns.com/support/article/68, and instructions to clear your web browser cache can be found here: http://www.opendns.com/support/article/67.

Once you do that, please see if the Additional Logon balloon disappears. Will you let me know how it goes?

 

[brianzion]

THIS IS RESPONSE FROM OPEN DNS.

Sorry to hear that you're having issues. I just read through both forum posts, and while somebody did post a registry fix in the Seven Forums thread, I'm wondering if a setting in your OpenDNS account is causing the issue. So far, it's sounding like this problem may be caused by the NXDOMAIN redirection setting being enabled for your network.

In order to resolve this, please log into the Dashboard and select Settings. After that, select your network, and then choose "Customization" in the left-hand menu. You will be brought to a page that you will allow you to toggle the "Enabled NX Domain Redirection" option. Please disable that option.

After that, flush your DNS resolver cache and web browser cache on each device to ensure that your new DNS configuration settings take effect immediately. Instructions to clear your DNS resolver cache can be found here: http://www.opendns.com/support/article/68, and instructions to clear your web browser cache can be found here: http://www.opendns.com/support/article/67.

Once you do that, please see if the Additional Logon balloon disappears. Will you let me know how it goes?

this has worked for me opendns working fine and no pop up (i put the reg key back to 1 in this method being used.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NlaSvc\Parameters\Internet EnableActiveProbing)

 

[icecoldbier]

I just ran the Nov 13, 2012 updates for Windows 7 Home Premium 64bit and I'm getting the balloon popup Additional log on information may be required. However, I am not using OpenDNS. I think this problem goes deeper than just OpenDNS.

I used the registry change that someone posted and it works but will this change cause a problem somewhere down the line.

 

[myarmor]

I can't see why there is a reason to show that popup every 5 seconds or so.

Uninstalled the update because as it is now, that update is useless and spamware (spamming balloon hints).

I use OpenDNS, and I prefer not to be logged in at OpenDNS all the time (I can't see what other way it would work as I have a dynamic ip address) just to turn off the annoying behavior MS introduced.

 

[brianzion]

Using Open DNS. Uninstalled Update for Windows 7 for x64-based Systems (KB2750841) and message stopped.

View attachment 241332

here is some info on the KB2750841 update from Microsoft

this article introduces the IPv6 readiness update for Windows 7 and for Windows Server 2008 R2.

This update improves the performance when you migrate from an IPv4 environment to an IPv6 environment.

Issues that are fixed in this update

Issue 1

When you assign a public IPv4 address in an environment, 6to4 addresses are automatically assigned to the servers and clients computers. This behavior is by default and occurs even when the computer does not have an E2E IPv6 connection or a 6to4 connection. Therefore, you may be unable to connect to IPv6 sites.

Note The expected behavior is that Windows clients do not assign 6to4 addresses unless the connection is confirmed.

This update enables Windows to check whether the relay can be reached before Windows adds a route to it. Windows deletes the route if the connection to the relay is unavailable. This behavior prevents Windows from trying to connect to an IPv6 address that cannot be reached through the relay.

Note The relay is the 6to4 public route that the 6to4 packet uses to reach its destination.

Issue 2

If you use many IPv6 address and IPv6 routes, the kernel memory is exhausted, and CPU usage reaches 100 percent.

This update limits the number of advertised prefixes and routes that each interface can process to 100.

Issue 3

If a computer has a public IPv4 address and if Internet Connection Sharing is enabled, the computer broadcasts a router advertisement (RA) message for the 6to4 address that is generated. Therefore, other computers are assigned IPv6 addresses. This behavior disconnects these computers if the computer that broadcasts the 6to4 RA does not have an E2E 6to4 connection.

Note Because of recommendations in the RFC 6343 document, you cannot disable 6to4 sharing.

After this update is installed, the automatic Connection Sharing 6to4 sharing functionality in Windows is disabled by default.

Issue 4

Assume that a computer is configured to use an IPv6 connection as the default connection. Additionally, assume that the computer does not have a connection to an IPv6 network. In this situation, it takes a long time for the computer to connect to an IPv6 site.

This issue occurs because Windows tries the IPv6 connection first. After the connection fails because of a time-out error, Windows tries the IPv4 connection.

After this update is installed, Windows uses the NCSI functionality to examine the Ipv6 connection. If the connection is broken, Windows uses IPv4 instead of IPv6.

An IPv6 readiness update is available for Windows 7 and for Windows Server 2008 R2

 

[myarmor]

@brianzion, if that was all it did, then I don't think anyone would've complained much.
However, that annoying balloon hint negates all that.
It's current behavior is similar to certain adware, but where the nagging is every 5 seconds.

Try doing something on your computer for a few hours while the balloon shows every 5 seconds.. I get annoyed with it rather quickly.

If I actually tried doing anything using a ipv6 connection, then I wouldn't mind it showing a few times (it would hopefully allow turning off that behavior though).
I think that adding a "Access type (partial: ipv4 only)" status to the network and sharing center + that ballon once or twice would be better.

 

[brianzion]

yeah i opted to put the reg file back to value 1 and i uninstalled the update now open dns is ok and no pop up in taskbar if it was a security update i would of left it.

 

[CraigK]

Uninstalling update KB2750841 worked for me to fix it.

 

[fireillusion]

Hello everyone.
I don'y know if Opendns fixed sth but yesterday i had the same problem, switched to google dns and today i switched back to opendns all options checked and there is no popup message.
Anyone else?

 

[charlieo]

Looks like it has been fixed. Re-enabled NXDOMAIN redirect on OpenDNS, waited 30 minutes, cleared DNS cache and rebooted. No popups..... EnableActiveProbing had been re-enabled (1) last night.

Anyone else seeing this as fixed??

 

[mijcar]

As a follow-up, MS decided to give me a refund. Score 1 point for MS!

Now when will the real fix come along from them?

 

[brianzion]

i reinstalled the windows update a while ago and am using opendns with no pop up

 

[dertiurt]

OpenDNS has resolved the problem by making exclusions for those domains:

OpenDNS Community > Forums > "Additional log on information may be required" pop up warning issue

 

[myarmor]

OpenDNS has resolved the problem by making exclusions for those domains:

OpenDNS Community > Forums > "Additional log on information may be required" pop up warning issue

Yup, it finally did away with the balloons.