Hi,

I've created an outlook rule that moves any email received from @abc.com domain into ABC folder. The problem I am running into is that the rule only works for group inboxes instead of personal.

So group.inbox@abc.com will be moved correctly,

while carole.baskin@abc.com will not be moved into ABC folder even though it should work as well.

Please anybody know of this issue? I am using a corporate email and a global address book.

I have multiple calendars. I am trying to make calendar invitations to a particular calendar, however, I receive an error message and the appointment/meeting does not get calendared, or sent to the people I "invite" to the meeting/appointment. 

When I type in all the information and send I receive the following error message: "This meeting is not in the Calendar folder for this account. Responses to this meeting will not be tallied. Do you want yo send anyway?" 

I have been instructed from Microsoft support that I am supposed to make an appointment/meeting through the default calendar assigned to that email and copy it over to the other calendar I initially want it on. However, this does not make any sense, because I am able to do so on another desktop that has the email set up on a work computer with no issues. Doing it this way seems inefficient and not practical as well. 

Please advise. 

We have seen our community members ask questions about Outlook keeps prompting for credentials many times. This issue could be caused by numerous reasons. Below is a list of the most common reasons for this problem:

• Outlook is configured to prompt you for credentials
• Incorrect password cached in credential storage
• Required Authentication Settings for outgoing server and incoming server
• Outlook Anywhere is not configured to use NTLM Authentication
• Corrupt Outlook profile
• Slow or unstable network connection
• Antivirus programs
• Shared calendars

Outlook is configured to prompt you for credentials

If you are using an Exchange account, there is a setting in your Outlook profile to always prompt for logon credentials. To find the setting, please follow:

1. In Outlook 213, go to File tab > Info>Account Settings> Account Settings…

2. Highlight your Exchange account and click Change button.

3. Click on More Settings button.

4. Select the Security tab.

5. Under the User Identification, make sure the “Always prompt for logon credentials” option is not selected.

If you are using other types of email, please make sure you have ticked the option “Remember password”.

Incorrect credential cached in Credential Manager

Your Windows system stores user credentials on your computer. If the cached credentials are incorrect, you will be prompted for password. This issue usually happens after the password for your domain user account is changed. Before your password changed, you saved your credentials. The stored credentials are not overwritten when Outlook triggers the authentication prompt even if you enable the Remember my credentials option.

To fix this issue, you need to remove the corrupted credentials, follow these steps:

1. Click Start, click Control Panel, and then click Credential Manager.

Note If View by is set to Category, click User Accounts first, and then click Credential Manager.

2. Locate  the set of credentials that has Outlook in the name.

3. Click the name to expand the set of credentials, and then click Remove from Vault.

Repeat step 3 for any additional sets of credentials that have the word Outlook in the name.

Required Authentication Settings for outgoing server and incoming server

Different email provider may need different authentication settings. Please make sure you have set the server settings correctly. You can contact your email provider to gather the information.

In general, we select the “My outgoing server (SMTP) requires authentication” option and the first bullet “Use same settings as my incoming mail server”.

In addition, click on the Advanced tab and check if you have enter the correct Server Port Number and select the correct encrypt type. Below is a screenshot for an IMAP account:

Outlook Anywhere is not configured to use NTLM Authentication

The Outlook Anywhere feature allows you to access your Exchange account remotely from the Internet when you are working outside your organization's firewall.

When using Outlook Anywhere to connect to your Exchange server, we need to choosethe authentication method among Basic Authentication, NTLM Authentication and Negotiate Authentication. The difference among them is the way that the passwords are sent when connecting to the server. With Basic Authentication, the password is sent in clear text. Using NTLM Authenticationcan significantly reduce the number of password prompts.

To check the authentication setting, please go to File > Account Settings > Account Settings,select the Exchange account, and then clickChange. In the Change Account wizard, click More Settings, and then click the Connection tab. Click the Exchange Proxy Settings button and now, you can see the settings underProxy authentication settings. Try to change the authentication toNTLM Authentication and then check the issue again.

Slow or unstable network connection

If your network connection is slow or unstable, Outlook may lose connection to the mail server. When Outlook try to reconnect, it will prompt for the credentials. To verify this, please switch to a stable network environment and then check if this issue persists.

Corrupt Outlook Profile

Corrupt profile may cause Outlook to no longer remember your password. Please try to create a new mail profile in Control Panel and reconfigure your email account in the new profile to fix the issue. To create a new mail profile, you can refer:

http://support.microsoft.com/kb/829918

Antivirus software

Antivirus software usually integrates into your Outlook and it may cause some conflicts. Try to temporarily turn off your antivirus software to check if the issue will be gone.

Shared Calendar

Shared calendars can impact the user credentials, this issue may also occur if you have shared calendars opened in Outlook. You can try to unselect the shared calendar to check the result. It’s recommended to not open the shared calendar unless you want to view them.

If you have any comments, welcome to post in the forum. Thank you.

Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi,

Microsoft Office ProPlus 365 is installed in one of the user machine (Dell Latitude 5285). Windows 10 64 bit Enterprise edition is installed.

Outlook works in Office network and in VPN connection. But it hangs frequently when not connected in VPN at home or hotel. 

I have performed the below. 

1.Checked that Cached mode is enabled Outlook
2.No PST files are mapped
3.Updated Office 365. Now version of Outlook is 16.0.9226.2114
4.Enabled “"Disable hardware graphics acceleration"  in outlook which resolves many of the issues

Issue 1 : How to resolve the Outlook hanging issue which happens at public network (Without connected in VPN)

Issue 2 : How to resolve frequent password prompt

Regards,

Boopathi

Regards, Boopathi

Hi

I exported my Outlook PST from my old machine, selecting all the items (the top root item). I copied it to my new machine. Imported it into my new outlook. And now new Outlook is not updating or syncing any emails. 

The outlook on old machine is working fine and updating inbox and other folders as usual. 

Kindly help me with my issue as am sure outlook client has some issue and needs some fix. 

I HAVE REVIEWED OTHER QUESTIONS AND ADVICE ABOUT THIS ERROR. 

We are seeing a send/receive error in Outlook 2013, details are "Unknown error 0x80040600".  The problem is preventing send and receive of email to certain accounts, while permitting it to other accounts.

Virtually all questions and all advice found so far relates to earlier versions of Outlook, and the advice for dealing with the error cannot be followed here.  For example, the SCANPST.EXE program does not appear to be on the affected system, so we can't repair the PST file as advised.  If a new PST file is created and made default, we cannot import messages from the old file as advised... Outlook will appear to be working for hours on updating it when we mount it and try to open it, but will not display any items in it.

Yesterday, it did this on one of about ten email accounts managed by this Outlook client, the others continued to send/receive just fine.  We eventually restored a backup of the PST file and lost a couple of days of email, but everything worked fine again.  Minutes ago, Outlook began reporting the same error with a different account.

Help please!  Thanks for any advice or ideas.

My computer updated overnight. This morning I cannot access Outlook. I have 3 email addresses (one outlook.com and two others related to my business. I keep getting the same error message that I need to repair files. I have done this five times already and it STILL will not let me open mail. I googled the problem and found various "fixes" but nothing worked. 

I need to set an automatic reply in outlook 2016, but it is giving an error:

An automatic reply has not been entered and will prevent automatic replies being sent. Automatic reply rules will work. 

Please help me to resolve this issue.

I am using the Outlook Import/Export option to import PST files into Outlook accounts.

The import works fine if I have less than 512 records in the PST file.  For larger files the import aborts with error message "Some items cannot be copied. They were either moved or deleted, or access was denied".  At this point 512 records are imported.

To import another 512 records I have to repeat the process with "Do not import duplicates" selected.

I have some large PST files with over 20K emails to import and this process will take forever.  

Can anyone tell me why the import is failing after 512 records and if this is something that can be corrected in the registry?

DCRA

Outlook2016 won't connect to exchange account

I have quite a few machines where after launching Outlook and trying to authenticate, they get a "something went wrong" error that Trusted Platform Module has malfunctioned, error code 80090016.  The server message is "Keyset does not exist Keyset does not exist".

If different users log in on the same computers, their Outlooks functions properly.  So I assume it's something just in those users' profiles, but I'd prefer not to delete the users' profiles if there is a fix that could be done to each instead.  Anyone know how to fix this without completely deleting the user profile off the machine?

Here's the output of dsregcmd /status from a profile with the TPM error

+----------------------------------------------------------------------+
| Device State                                                         |
+----------------------------------------------------------------------+
 
             AzureAdJoined : NO
          EnterpriseJoined : NO
              DomainJoined : YES
                DomainName : MyDomainIsHere
 
+----------------------------------------------------------------------+
| User State                                                           |
+----------------------------------------------------------------------+
 
                    NgcSet : NO
           WorkplaceJoined : NO
             WamDefaultSet : ERROR
 
+----------------------------------------------------------------------+
| SSO State                                                            |
+----------------------------------------------------------------------+
 
                AzureAdPrt : NO
       AzureAdPrtAuthority : NO
             EnterprisePrt : NO
    EnterprisePrtAuthority : NO
 
+----------------------------------------------------------------------+
| Diagnostic Data                                                      |
+----------------------------------------------------------------------+
 
             Diagnostics Reference : www.microsoft.com/aadjerrors
              User Context : SYSTEM
               Client Time : 2019-03-22 14:29:39.000 UTC
      AD Connectivity Test : PASS
     AD Configuration Test : FAIL [0x80070002]
        DRS Discovery Test : SKIPPED
     DRS Connectivity Test : SKIPPED
    Token acquisition Test : SKIPPED
     Fallback to Sync-Join : ENABLED
 
     Previous Registration : 2019-03-22 14:29:04.000 UTC
               Error Phase : discover
          Client ErrorCode : 0x801c001d
 
+----------------------------------------------------------------------+
| Ngc Prerequisite Check                                               |
+----------------------------------------------------------------------+
 
            IsDeviceJoined : NO
             IsUserAzureAD : NO
             PolicyEnabled : NO
          PostLogonEnabled : YES
            DeviceEligible : YES
        SessionIsNotRemote : YES
            CertEnrollment : none
              PreReqResult : WillNotProvision

But here is the output from the same machine but under a new user profile for another user (I put stars where there was data I didn't feel appropriate to share publicly)

+----------------------------------------------------------------------+
| Device State                                                         |
+----------------------------------------------------------------------+

             AzureAdJoined : NO
          EnterpriseJoined : NO
              DomainJoined : YES
                DomainName : MyDomainIsHere

+----------------------------------------------------------------------+
| User State                                                           |
+----------------------------------------------------------------------+

                    NgcSet : NO
           WorkplaceJoined : YES
          WorkAccountCount : 1
             WamDefaultSet : NO

+----------------------------------------------------------------------+
| SSO State                                                            |
+----------------------------------------------------------------------+

                AzureAdPrt : NO
       AzureAdPrtAuthority : NO
             EnterprisePrt : NO
    EnterprisePrtAuthority : NO

+----------------------------------------------------------------------+
| Work Account 1                                                       |
+----------------------------------------------------------------------+

         WorkplaceDeviceId : *****************************
       WorkplaceThumbprint : *****************************
              WorkplaceIdp : login.windows.net
         WorkplaceTenantId : *****************************
       WorkplaceTenantName : *****************************
           WorkplaceMdmUrl : https://wip.mam.manage.microsoft.com/Enroll
      WorkplaceSettingsUrl :
                    NgcSet : NO

We recently upgraded to Outlook 2013 (from Outlook 2010).

In 2010, I set up (some kind of?) shortcut that allowed me to move emails to another folder. Essentially, it was a short cut to the Move to Folder window, and all I had to do was press ALT + 1, which was a very simple combo for my left hand. 

Now that we've upgraded to 2013, I have absolutely no recollection of how I created this shortcut! I've looked into macros and Quick Steps and neither seems plausible.

Anyone have any idea how I created this ALT + 1 shortcut?

The title just about says it all: How do I import a .pst file for an email address that no longer exists?

I have Outlook 365 in a Windows 10 environment.

Hi all,

We have a client who's recently migrated to Exchange Online and now, they're shared folders automatically collapse upon restart of Outlook.

These shared folders are all AutoMapped.

Is this normal behaviour? Is there any way to change it so it remembers the folder state?

Thanks in advance

We are running Office professional 2016 x64 (msi installation) on Windows Pro 10 v1809 17763.1339.  After installing July 14th 2020 security and non-security patches - we are seeing Outlook crash when clients send a message.  Also Word, Excel crashes have increased.  Anyone else having this issue?

Application Error Event ID 1000 Outlook

Faulting application name: OUTLOOK.EXE, version: 16.0.5017.1000, time stamp: 0x5ebb2344

Faulting module name: OUTLOOK.EXE, version: 16.0.5017.1000, time stamp: 0x5ebb2344

Exception code: 0xc0000005

Fault offset: 0x0000000000037c4a

Faulting process id: 0x11b4

Faulting application start time: 0x01d65f574363c508

Faulting application path: C:\Program Files\Microsoft Office\Office16\OUTLOOK.EXE

Faulting module path: C:\Program Files\Microsoft Office\Office16\OUTLOOK.EXE

Report Id: 2c334d21-ff2a-4220-8d6b-86b139f5ae21

Faulting package full name:

Faulting package-relative application ID:

Word Application error Event id 1000

Faulting application name: WINWORD.EXE, version: 16.0.5017.1000, time stamp: 0x5ebb2406
Faulting module name: KERNELBASE.dll, version: 10.0.17763.1192, time stamp: 0x7889407f
Exception code: 0xe0434352 Fault offset: 0x0000000000039709
Faulting process id: 0x3084
Faulting application start time: 0x01d65c68e655ff29
Faulting application path: C:\Program Files\Microsoft Office\Office16\WINWORD.EXE
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: f5985243-67c8-41b7-982a-5b9dae20a1ad
Faulting package full name: Faulting package-relative application ID:

Excel Application error event id 1000 
Faulting application name: EXCEL.EXE, version: 16.0.5017.1000, time stamp: 0x5ebb1f39
Faulting module name: EXCEL.EXE, version: 16.0.5017.1000, time stamp: 0x5ebb1f39
Exception code: 0xc0000005
Fault offset: 0x000000000064ca0e
Faulting process id: 0x2d58
Faulting application start time: 0x01d65eb4c07d4cfa
Faulting application path: C:\Program Files\Microsoft Office\Office16\EXCEL.EXE
Faulting module path: C:\Program Files\Microsoft Office\Office16\EXCEL.EXE
Report Id: f267c154-627b-4d61-8259-cc50f58c189a
Faulting package full name:
Faulting package-relative application ID: