Problem description Hello, there is a technical issue I am encountering while attempting to utilize MSN Messenger 4.6 with the Escargot patcher. Despite having successfully patched MSN Messenger 4.6, I am unable to log in. Upon entering my email address and password, the application remains stuck on the “Signing in” page. I have simplified my password, yet the issue persists. Currently, I am testing MSN Messenger version 3.6.
I would greatly appreciate your assistance in resolving this matter. Thank you for your attention to this issue.
Error code/error message: There are no errors involved in this progress.
Furthermore, the preferences indicate that the account is logged in. However, once logged in, the sign-in page continuously loops without successfully proceeding to the next stage, which is the MSN Messenger’s main menu progress.
How does MSN Messenger 2.2 works when logging in? It has the “provided by” option which says “hotmail.com”. Is there something to put in the messenger in order to login?
MSN messenger version 1.0 to 2.2 only support login on hotmail.com, just simply enter your username without escargot.chat and ignore the hotmail.com part.
Despite the successful transition from hotmail.com to escargot.chat, the login process remains in a continuous loop. Upon examining the “Accounts” page within the preferences, it is observed that the username has been automatically entered without any complications, similar to MSN Messenger versions 3.6 and 4.6. However, when disregarding this and opting to retain the default “hotmail.com” option, the system indicates an incorrect password.
@SuperMarioWar1 Hello, the issue may not be with Windows 2000, but rather with the primary Escargot account. It is possible that the flash profile picture is causing the problem. If there is a way to delete all the data from Windows Live Messenger 2009, I would greatly appreciate it. There is evidence that MSN Messenger 2.2 functions properly, and I have successfully logged in with a different account that works without any issues. Therefore, it appears that the problem is specifically associated with the main Escargot account.