Share via

unable to log in to facebook on microsoft edge after clearing browsing history for instagram problem

Anonymous
2025-03-22T10:23:35+00:00

unable to log in to facebook on microsoft edge after clearing browsing history for instagram problem, i can log in with chrome, i have tried all the recommended online things, clearing history, reinstalling edge etc etc etc, now I am not an expert in windows stuff, so i could be screwing stuff up, but still can't find an answer

Microsoft Edge | Website issues | Windows 11

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.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2025-03-23T06:56:45+00:00

    Hi, SJHH67 S

    Welcome to the Microsoft community.

    Did you encounter any error messages when trying to log in to Facebook? Try accessing Facebook in InPrivate Mode (Ctrl+Shift+N) and logging in to see if it works.

    If it works in InPrivate Mode, create a new Edge profile, sign out of your account from the old profile, log in to the new Edge profile, sync your data, and try again.

    edge://settings/profiles

    If InPrivate Mode does not work, try switching to a different version of Edge to check if the issue is specific to a particular Edge version.

    Become a Microsoft Edge Insider | Microsoft Edge

    If it is a version-specific issue, please report the problem you encountered to the developers using Alt+Shift+I. In the meantime, you can temporarily use the Insider version of Edge.

    Best regards

    Tommy Jin | Microsoft Community Support Specialist

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-03-25T08:08:58+00:00

    I get this error with logging in: The email you entered isn’t connected to an account. Find your account and log in.

    trying to log in under in private mode results in same error message.

    the beta version of edge results in the same error message.

    what's next?

    0 comments No comments