Using Classic Outlook on Windows for personal email, calendar, and contact management
What antivirus software are you using ?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
We encounter an issue with M365 apps (Outlook, Work, Excel) on a specific environment ( Remote Desktop Service)
Sometime, when an user open his application (Outlook for instance) on a RDS, an authentification pop and ask for credentials. If the user enter his credentials, he encounter a 1001 error.
« We encountered an issue [1001] »
https://learn-attachment.microsoft.com/api/attachments/5a947921-955a-4688-ad93-acc305bf77c6?platform=QnA
We already try some step to resolve the issue that help in some case but not all the case, and not defintely for a same user ( Issue occur again) :
The main issue is that the error can occur again few day laterfor the same user.
We also generate some log from M365 apps client during the signin process with this link to help : https://learn.microsoft.com/en-us/office/troubleshoot/diagnostic-logs/how-to-enable-office-365-proplus-uls-logging
In the log I find the reference to the 1001 error but the log is a bit complex to understand or analyse.
0xa3e4 Microsoft Outlook Identity Authentication Client 48cmb Monitorable OneAuth log {"Message": "[MSAL:0004]\tERROR \tErrorInternalImpl:134\tCreated an error: 58tm1, StatusInternal::Unexpected, InternalEvent::None, Error Code 2147942403, Context '(pii)'", "IsError": true}
07/07/2023 09:04:21.440 OUTLOOK (0x8b30) 0xa3e4 Microsoft Outlook Identity Authentication Client 48cmb Monitorable OneAuth log {"Message": "[OneAuth:Error:58tm1:db6d7d6e-a557-4465-a968-a874c5e456e5] (Code:1001) An unexpected error occurred.", "IsError": true}
07/07/2023 09:04:21.440 OUTLOOK (0x8b30) 0xa3e4 Microsoft Outlook Identity Authentication Client 48cmb Monitorable OneAuth log {"Message": "[OneAuth:Error:9vdpp:db6d7d6e-a557-4465-a968-a874c5e456e5] Unexpected error code: 1001", "IsError": true}
Environment :
Using Classic Outlook on Windows for personal email, calendar, and contact management
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
What antivirus software are you using ?
This workaround is the best one that worked 2x times for us without any bad side.
Here are also 2 more things I have correlated to the 1001 error and this workaround.
We have Microsoft events of this kind : event 5961 : Microsoft/Windows/Apps
These event (error) are related to Microsoft.AAD.BrokerPlugin but also ShellExperience and Cortana depending on what application is triggering the issue.
Another fact is that I noticed related to ShellExperience and this error is that the Windows Menu and Search menu aren't working while this occurs.
This trigger the 5961 event each time the menu is tried to be accessed.
Deleting the registry mentionned above is automatically fixing Windows Menu, and Outloook Error 1001.
Until we have a final fix we will automated the cleaning of the registry once a day.
I hope this could help.
This was a working workaround for us, but this also seems to remove other Application settings like Outlook settings. Like if it is cleaning up the whole user profile. We rolled back on this registry.
Hi, Have had an update from Microsoft.
Problem should be resolved in the latest Office versions. Have to test it myself but thought t is worth sharing
As discussed, the below channels have rectified the Office login error 1001, kindly update and check the behavior.
https://learn-attachment.microsoft.com/api/attachments/fbe0e9ec-f32c-413e-84b9-1e24bc46c366?platform=QnA&fud_access=wJJIheezUklbAN2ppeDns8cDNpYs3nCYjgitr%2BfFBh2dqlqMuW7np3F6Utp%2FKMltnRRYFtVjOMO5tpbpW9UyRAwvLeec5emAPixgq9ta07Dgnp2aq5eJbnfd%2FU3qhn54uz6a7Elb9wzuuLVAO2As96jmgfhg0PGIhywXZSiMzB4AhT2aYHF8vQVT8jFgL75uK19w31UMnSRywTxSpIjFePbuTrDqwSizNAIwxJj%2FGEqNFFIdpifkIj123DYIhvYatmeXvOnVH51%2BKfyLyoee9qfOF%2F8a80gnXBSI3lQ%2FP5el8tbtDiMonFVsroGQjDphg38wz8c6hZrj%2BSXfkaggib7Hsao8utY0ths6K5E3n6N1C0zhxO7%2F4%2F0LIVh0JR8yUVqfXog%2FUaN5WK3BOAhohv20nXjf1piEqBmBlhDMAuo%3D
I've just been reading through the details on the Microsoft support article for this issue (link).
The details they give under Scenario 2 could be an issue if roaming of the %localappdata% folder is no longer supported:
Scenario 2:
In the second scenario the error "Something went wrong [1001]" is caused by user profile management issues.
In this category of issues, we find that on both VDI and physical devices the user profile data is being roamed and that can cause identity and authentication data components to be in a bad state.
Roaming any data under the path %localappdata% is not supported. If you choose to move content under %localappdata%, make sure that the content of the following folders and registry keys never leaves the device under any condition.
Roaming of the work account's device certificate is not supported.