Please check your network settings and try again [2604]. Solution:

Scheme I:

 Open your Internet Explorer browser and select Tools>Internet Options. In the Internet properties window, click Advanced, slide down to the security module category column, check ssl3.0, TLS1.0, 1.1, 1.2, and then apply and confirm

Scheme II:

 Open the Edge browser, click the three points in the upper right corner, Open More Tools and select Internet Options. In the Internet Properties window, click Advanced, slide down to the security module category column, check ssl3.0, TLS1.0, 1.1, 1.2, and then apply and confirm

Scheme III:

 Press the keyboard combination key Windows+R to pop up the operation Enter the command: inetcpl.cpl In the Internet Properties window, click Advanced, slide down to the security module category column, check ssl3.0, TLS1.0, 1.1, 1.2, and then apply and confirm

An error occurred. [1001] ：

Scheme 1:

In the first scheme, the error "An error occurred [1001]" is caused by the security software that affects the WAM plug-in (AAD. BrokerPlugin).

See this article for more details on how to mitigate the following actions:

Unable to sign in to Microsoft 365 desktop application

To provide temporary relief, the following steps may help:

Restarting the device usually helps alleviate the problem.

Run the following commandlet in user mode PowerShell to repair WAM. For more context, see the article Authentication Failure in Microsoft 365 Service.

 Add-AppxPackage -Register “$env:windir\SystemApps\Microsoft. AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml” -DisableDevelopmentMode -ForceApplicationShutdown Add-AppxPackage -Register   “$env:windir\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\Appxmanifest.xml” -DisableDevelopmentMode -ForceApplicationShutdown

Scheme 2:

The second case is the error "An error occurred [1001]" caused by the user profile management problem.

See this article for more details on how to mitigate the following actions:

Device identification and desktop virtualization

In this category of problems, we found that user profile data is roamed on both VDI and physical devices, which may cause the identity and authentication data components to be in an error state. Be sure to follow the guidelines in the above article to see if user profile management practices can cause this problem. This section is extracted from the article to emphasize its importance:

No data under roaming path% localappdata% is supported. If you choose to move content under% localappdata%, make sure that the contents of the following folders and registry keys never leave the device under any conditions. For example, the Profile Migration Tool must skip the following folders and keys:

 %localappdata%\Packages\Microsoft. AAD.BrokerPlugin_cw5n1h2txyewy  %localappdata%\Packages\Microsoft. Windows.CloudExperienceHost_cw5n1h2txyewy  %Localappdata%  Packages <any application package> AC  TokenBroker %localappdata%\Microsoft\TokenBroker  HKEY_CURRENT_USER\SOFTWARE\Microsoft\IdentityCRL  HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\AAD