After client machine have installed this update they are now being prompted for a Username and password when launching outlook. Setting up a fresh copy of outlook also prompts.

Is anyone else having this same issue?

Hi,

I haven't received any report about this issue yet. If possible, uninstall this kb on a client to test, check if this issue will be gone.

I also suggest you check some options in Outlook as mentioned in this article:

https://social.technet.microsoft.com/Forums/en-US/bcd2d9c2-1a1b-4446-bf32-69fee8cdf11b/why-does-outlook-keep-prompting-for-password?forum=outlook

Check whether Outlook is configured to prompt you for credentials, and configure Outlook to use NTLM Authentication especially.

For your reference:

https://support.microsoft.com/kb/2986204

Regards,

Melon Chen
TechNet Community Support

Hi

If we uninstall it the problem is resolved.

Following through the link everything is setup as it should be on both Outlook and Exchange.

This update has installed it self on the majority of machines.

Anything else we can check?

Yes, we found x86 Office running on x64 windows causes the same problem. Thought it was only with our Office 365 users. It appears to be more wide spread than that. We are also finding that if the users have not created a outlook profile on the machine before it refuses to create one for them on launch as well when the update has been applied. Have worked through several reports. Will be notifying Microsoft today. Expected we were not the only ones experiencing this but there has been no update to the KB.

We found that we have to uninstall the update 2 - 3 times before it is actually removed from the system and functionality returns.

Had exactly the same issue... we use office365.

We have set it to remove from all machines via WSUS.

I have it too, Office 365 users, I have exhausted all other options I started to remove outlook updates the first one I removed was KB2986204 and outlook is now functioning as it should.  I will pull the update from WSUS for now and remove from affected PC's.

Hi,

It seems the update has caused some issues, the temporary workaround is to uninstall the update and wait for the fix. As soon as there is a fix, I will let you know.

Regards,

Melon Chen
TechNet Community Support

I've had the same issue. Uninstalling that update resolves the credential prompt. Does anyone know if a fix has been released yet?

Watch out there is another one about with the same result KB2899504... I assume others are having an issue with this also?

How has this happened again???

Uninstalling this update aswell as KB2986204 resolved my issue. I hope Microsoft are aware of this issue. I've submitted a ticket request with them so I will pass on my findings.

Watch out there is another one about with the same result KB2899504... I assume others are having an issue with this also?

How has this happened again???

Same issue here! Pffff. Installed KB2899504 and same issue again. 

Is a fix available now (2 months later)?

Or is the only solution still to uninstall KB2986204 ?

I have exactly the same problem since early Dec. once in a while with different users. Very annoying!

Same here.  I've been waiting on a solution as well to install both KB2986204 and KB2899504.  Could we get an update from Microsoft?  Thanks.

Heads up there's another update causing a credential popup:

KB2956087

It was been install on our machines today. 12/02/2015

Confirmed the same issue here. We are blocking:

KB2986204
KB2899504
KB2956087

as these all cause password prompts to appear on domain joined PCs that should be using NTLM.

We are Exchange 2013 CU6 running a mix of x86 & x64 Win7 clients all on x86 Office 2013 SP1.

So looks like we have another one this time: KB2956170

Causing credential popup and stops as soon as this is uninstalled.

This is 4 now! what is going on MS??

Anyone else experienced this?

Having the same issue with the last 4 outlook updates including the latest  march 2015 (KB2956170)

Glad to see its not just us

• Edited by St.Clair 1 hour 25 minutes ago

Having the same issue with the last 4 outlook updates including the latest  march 2015 (KB2956170)

Glad to see its not just us

• Edited by St.Clair Friday, March 13, 2015 5:57 AM

Having the same issue with the last 4 outlook updates including the latest  march 2015 (KB2956170)

Glad to see its not just us

• Edited by St.Clair Friday, March 13, 2015 5:57 AM

Having the same issue with the last 4 outlook updates including the latest  march 2015 (KB2956170)

Glad to see its not just us

• Edited by St.Clair Friday, March 13, 2015 5:57 AM

Having the same issue with the last 4 outlook updates including the latest  march 2015 (KB2956170)

Glad to see its not just us

• Edited by St.Clair Friday, March 13, 2015 5:57 AM

Having the same issue with the last 4 outlook updates including the latest  march 2015 (KB2956170)

Glad to see its not just us

• Edited by St.Clair Friday, March 13, 2015 5:57 AM

Having the same issue with the last 4 outlook updates including the latest  march 2015 (KB2956170)

Glad to see its not just us

• Edited by St.Clair Friday, March 13, 2015 5:57 AM

We are also having the same issue... Unbelievable that it can go on for so long without resolution.

Our users are actually asking to be switched back to Office 2010. I am not even joking.

I've been struggling with the same issue for months, and resolved it today.  To fix the problem, here at least, I had to enable Digest Authentication for the Autodiscover entry under Default Web Site on my Exchange Servers' IIS.  I was then able to create a profile on a patched machine and access email.  Old profiles on machines broken by the patches had to be recreated, then they also worked.

Jerod 

For anyone still watching this issue, we're now up to 5 updates that cause this behaviour, we're having to block these on WSUS to prevent our customers being prompted for passwords on domain joined machines using NTLM.

KB2986204
KB2899504
KB2956087
KB2956170
KB2965270

Further progress since my last post in February. We upgraded to CU7 and now CU8 and the problem remains, but we think we have tracked the issue and have a case open with MS. If anyone else is able to test and confirm our findings it would be helpful to know, below are the key aspects to look for:

- Outlook 2013 has one of the above updates installed.
- The UserPrincipalName (abc123@domain.com) is different to the PrimarySMTPAddress (a.b.carey@domain.com) of the mailbox.
- The computer is domain joined.
- Mapi/HTTP is configured in the Exchange 2013 organisation.
- NTLM/Negotiate is used as the authentication mechanism.

If all of the above aspects are true for your configuration and you are able to re-produce the password prompting try altering the Mailbox PrimarySMTPAddress so that it's the same as the UserPrincipalName.

In our testing the issue went away when the UserPrincipalName and PrimarySMTPAddress matched, not that it gives us a solution as our customers are quite attached to their vanity email addresses, but it does highlight a specific type of behaviour under specific circumstances.

Ukjone:

I can confirm we have the exact same as you have tested it and it does go away if I change the primary address to UserPrincipalName!

Have Microsoft given you any sort of solution yet?? Please let me know if they do im getting fed up of these updates causing issues.

It appears this has now been resolved, at least for us anyway!

After installing KB3039799 password prompts have stopped and all seems to be working as advertised.

OK so I look to have been a little premature, this has not resolved it for us just some machines seemed to stop asking for credentials but are now back to asking again.

Finally, after many days of emails to and fro with MS Support I have some information worthy of an update.

Firstly I can confirm as Derik128 mentions that KB3039799 exhibits the same behaviours as previous updates. I've listed all the KBs below for completeness.

We've literally thrown hundreds hours at this problem to try to pin it down even further and again thanks to Derik128 for testing our scenario from the 23rd April.

Here's where we find ourselves - looking for further testers to confirm. Microsoft Support have suggested that we try the following Registry Key.

Key: HKEY_CURRENT_USER\Software\Microsoft\Exchange

Value: MsoAuthDisabled

Type: DWORD

Value: 1

For us this is like a switch. A scratch install of Win7, Office 2013 with KB3039799 installed prompts for a password. Add the registry key and the password prompts disappear, delete the registry key and back they come.

Any advance on this experience from others?

At this stage it's back to MS. This is a workaround, but not really a clean solution so we'll see what they come back with.

Here's the list of updates we are currently blocking on our WSUS Server. 

KB2986204
KB2899504
KB2956087
KB2956170
KB2965270
KB3039799

• Edited by ukjonE 10 hours 17 minutes ago

Finally, after many days of emails to and fro with MS Support I have some information worthy of an update.

Firstly I can confirm as Derik128 mentions that KB3039799 exhibits the same behaviours as previous updates. I've listed all the KBs below for completeness.

We've literally thrown hundreds hours at this problem to try to pin it down even further and again thanks to Derik128 for testing our scenario from the 23rd April.

Here's where we find ourselves - looking for further testers to confirm. Microsoft Support have suggested that we try the following Registry Key.

Key: HKEY_CURRENT_USER\Software\Microsoft\Exchange

Value: MsoAuthDisabled

Type: DWORD

Value: 1

For us this is like a switch. A scratch install of Win7, Office 2013 with KB3039799 installed prompts for a password. Add the registry key and the password prompts disappear, delete the registry key and back they come.

Any advance on this experience from others?

At this stage it's back to MS. This is a workaround, but not really a clean solution so we'll see what they come back with.

Here's the list of updates we are currently blocking on our WSUS Server. 

KB2986204
KB2899504
KB2956087
KB2956170
KB2965270
KB3039799

• Edited by ukjonE Tuesday, May 19, 2015 9:16 PM
• Proposed as answer by ®win 11 hours 7 minutes ago

Finally, after many days of emails to and fro with MS Support I have some information worthy of an update.

Firstly I can confirm as Derik128 mentions that KB3039799 exhibits the same behaviours as previous updates. I've listed all the KBs below for completeness.

We've literally thrown hundreds hours at this problem to try to pin it down even further and again thanks to Derik128 for testing our scenario from the 23rd April.

Here's where we find ourselves - looking for further testers to confirm. Microsoft Support have suggested that we try the following Registry Key.

Key: HKEY_CURRENT_USER\Software\Microsoft\Exchange

Value: MsoAuthDisabled

Type: DWORD

Value: 1

For us this is like a switch. A scratch install of Win7, Office 2013 with KB3039799 installed prompts for a password. Add the registry key and the password prompts disappear, delete the registry key and back they come.

Any advance on this experience from others?

At this stage it's back to MS. This is a workaround, but not really a clean solution so we'll see what they come back with.

Here's the list of updates we are currently blocking on our WSUS Server. 

KB2986204
KB2899504
KB2956087
KB2956170
KB2965270
KB3039799

• Edited by ukjonE Tuesday, May 19, 2015 9:16 PM
• Proposed as answer by ®win Thursday, May 21, 2015 8:24 PM

Finally, after many days of emails to and fro with MS Support I have some information worthy of an update.

Firstly I can confirm as Derik128 mentions that KB3039799 exhibits the same behaviours as previous updates. I've listed all the KBs below for completeness.

We've literally thrown hundreds hours at this problem to try to pin it down even further and again thanks to Derik128 for testing our scenario from the 23rd April.

Here's where we find ourselves - looking for further testers to confirm. Microsoft Support have suggested that we try the following Registry Key.

Key: HKEY_CURRENT_USER\Software\Microsoft\Exchange

Value: MsoAuthDisabled

Type: DWORD

Value: 1

For us this is like a switch. A scratch install of Win7, Office 2013 with KB3039799 installed prompts for a password. Add the registry key and the password prompts disappear, delete the registry key and back they come.

Any advance on this experience from others?

At this stage it's back to MS. This is a workaround, but not really a clean solution so we'll see what they come back with.

Here's the list of updates we are currently blocking on our WSUS Server. 

KB2986204
KB2899504
KB2956087
KB2956170
KB2965270
KB3039799

• Edited by ukjonE Tuesday, May 19, 2015 9:16 PM
• Proposed as answer by ®win Thursday, May 21, 2015 8:24 PM

Thanks, ukjonE. You saved me hours of troubleshooting. This regkey fixed the credential popup for us without uninstalling any updates.

• Edited by ®win 11 hours 2 minutes ago typo

Thanks, ukjonE. You saved me hours of troubleshooting. This regkey fixed the credential popup for us without uninstalling any updates.

• Edited by ®win Thursday, May 21, 2015 8:29 PM typo

Thanks, ukjonE. You saved me hours of troubleshooting. This regkey fixed the credential popup for us without uninstalling any updates.

• Edited by ®win Thursday, May 21, 2015 8:29 PM typo

Good news is that after yet more testing with MS Support this issue has now been recognised as a bug and has been escalated to the Development Team. Current estimate is that an update should be out in June that will put this one to bed.

Hi,

Is either KB3054855 or KB3054853 the update we have been waiting for?

Please say yes!

Also if it is do you know at all can we install all previous dodgy updates? as some contain other fixes which we are missing out on.

Thanks.

Hi ,

any news ? I have the same issue and I use the Rgistry key workaround

Regards.

Yogev

Hi Yogev,

Since this is an old thread, if you need further assistance regarding this issue, I'd recommend you post a new question in the forum via:

https://social.technet.microsoft.com/Forums/office/en-US/home?forum=officeitpro

Thank you for your understanding and support.

Regards,

Steve Fan
TechNet Community Support

That's ridiculas... I for one am still watching this thread waiting for a "proper" fix.

We had success with the updates KB3054855 and KB3054853 it resolved it for us.