I have bought microsoft 365 but it is not letting me access the new log in i created instead its taking me to my other email.

Hi @Sefton Plumbing Services Ltd,

Thank you for the value information.

If you’re getting the “Something Went Wrong [1001]” Error in Microsoft when you try to sign into apps, the problem could be related to the Microsoft ecosystem on your computer.

You can try the following fixes to troubleshoot this issue:

Fix 1: Check internet connectivity

A poor or missing internet connection may be preventing you from signing in to Microsoft apps, causing the “Something Went Wrong [1001]” error. Check that other apps are connecting properly. If they are, the issue is elsewhere. If they’re not, check all your connections and/or run the Network Troubleshooter as follows:

Step 1. Go to Settings > System > Troubleshoot > Additional troubleshooters > Network Adapter.

Step 2. Run the troubleshooter.

Fix 2: Run system file checks

For this fix, please check the integrity of your computer’s system files.

Step 1. Type “cmd” into the Windows search box and select “Run as Administrator.”

Step 2. The Command Prompt window will open.

Step 3. Copy the command “sfc /scannow’, right click to paste it into Command Prompt, and then press Enter to run it.

Step 4. Repeat step 3 with the following command: DISM /Online /Cleanup-Image /RestoreHealth.

Fix 3: Repair the Web Account Manager (WAM) Plugin using PowerShell

If you’re still getting the “Something Went Wrong [1001]” error in Microsoft apps after those general fixes, the issue is something Microsoft-related

Particularly if you’re trying to sign into a Microsoft365 app, the issue may well be authentication failure due to missing Microsoft package information. Reinstalling the missing packages via PowerShell should resolve the issue.

Step 1. Right-click the Windows icon and select Windows PowerShell (Admin).

Step 2. If you’re presented with a User Account Control (UAC) window, click Yes to allow the app to open.

Step 3. In the PowerShell console that opens, right-click at the prompt and paste the following commands:

If your issue is with a work account:

if (-not (Get-AppxPackage Microsoft.AAD.BrokerPlugin)) { Add-AppxPackage -Register “$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml” -DisableDevelopmentMode -ForceApplicationShutdown } Get-AppxPackage Microsoft.AAD.BrokerPlugin

If your issue is with a personal account:

if (-not (Get-AppxPackage Microsoft.Windows.CloudExperienceHost)) { Add-AppxPackage -Register “$env:windir\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\Appxmanifest.xml” -DisableDevelopmentMode -ForceApplicationShutdown } Get-AppxPackage Microsoft.Windows.CloudExperienceHost

Step 4. Press Enter to run the command.

Step 5. Close PowerShell and try signing in to the problematic app again.

More information at: [Can't Sign In to Microsoft 365 Desktop Applications - Microsoft 365 Apps | Microsoft Learn](https://learn.microsoft.com/en-us/troubleshoot/microsoft-365-apps/activation/cannot-sign-in-microsoft-365-desktop-apps

Fix 4: If this is caused by user profile management issues. 

Please see this article for more details about how to mitigate: 

Device identity and desktop virtualization

In this category of issues, Microsoft 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. Make sure to follow the guidance in the article above to carefully review if user profile management practices could be causing the issue. This section is pulled from that article to emphasize its importance: 

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. For example: Profile migration tools must skip the following folders and keys:

%localappdata%\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy  %localappdata%\Packages<any app package>\AC\TokenBroker  %localappdata%\Microsoft\TokenBroker  HKEY_CURRENT_USER\SOFTWARE\Microsoft\IdentityCRL  HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\AAD  HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WorkplaceJoin

Roaming of the work account's device certificate is not supported. The certificate, issued by "MS-Organization-Access", is stored in the Personal (MY) certificate store of the current user and on the local machine.

More information about this error code can be found at: Error “Something Went Wrong [1001]” signing in to Microsoft 365 Desktop Applications - Microsoft Su…

I hope this helps you resolve the issue quickly. I’m glad to assist and truly hope the information provided has been useful. Please feel free to reach out anytime if you need further assistance.  

If you find my post helpful, kindly consider marking it as the accepted answer. Doing so can assist others in the community who may have similar questions in finding solutions more quickly.  

Thank you for your kindness and contributions to the forum. 

Note: To receive email notifications for updates on this thread, please follow the steps outlined in our documentation to enable email notifications.

Correlation Id: [Moderator note: personal info removed]

Timestamp: [Moderator note: personal info removed]

DPTI: [Moderator note: personal info removed]

Error

Something went wrong. [1001]

This all information I have when I try access account

Hi

I have attached image of error code.

thanks

Hi @Sefton Plumbing Services Ltd,

Good day and thank you for reaching out,

In order to assist you with more accuracy, can you please provide me with the error code and message you encountered?

For reference, below is an example of the type of error message you can share:

Once I have a clearer understanding of your current situation, I’ll be happy to assist you with greater accuracy. Please feel free to share any additional details you believe are relevant. Screenshots are especially helpful and much appreciated. 

Thank you for your patience and your understanding. If you have any additional questions, please feel free to reach out. 

I'm looking forward to your reply.