Error Code-895156191

Brijesh Singh 0 Reputation points
2026-02-28T05:05:58.7933333+00:00

Hi,

I am encountering error code 895156191 while signing in on a particular PC. However, I am able to log in successfully on other systems using the same credentials.

This issue appears to be device-specific. Kindly assist in identifying the root cause and provide the necessary resolution at the earliest.

Thanks

Brijesh

Microsoft 365 and Office | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-02-28T05:06:17.8+00:00

    Error code 895156191 indicates a sign-in failure that is specific to that device rather than to the account or service, since the same credentials work on other systems.

    Follow these steps on the problematic PC:

    1. Capture and share the status/error code with IT admin
      In Microsoft 365/Teams or other Microsoft apps, note the full error/status code shown at sign-in and share it with the organization’s IT admin. Many sign-in issues can only be resolved by the admin because they involve domain, device, or tenant configuration.
    2. Check device compliance and access policies
      If the organization enforces device-based access (for example via Microsoft Entra or Intune), the device may be:
      • Marked as disabled or deleted in Microsoft Entra ID.
      • Marked as not compliant with policy.
      The admin should:
      • Verify in Microsoft Entra admin center that the device is present and enabled. If it shows as disabled with errors like AADSTS135011: Device used during the authentication is disabled, the device must be re-enabled.
      • If logs show AADSTS50155: Device is not authenticated, perform device recovery as per the documented manual recovery steps (for example, using dsregcmd /status and dsregcmd /leave followed by a restart, depending on whether the device is Entra hybrid joined, Entra joined, or only has a work account added).
    3. Check for compliance errors on the device
      If a message such as “Device is not compliant” or “Try signing in another way” appears when accessing internal apps:
      • Ensure the device is properly joined to the organization’s network and domain as required by policy.
      • Sign in to Windows with the work or school account, connect to the corporate network (VPN/DirectAccess if remote), lock the device (Windows logo key+L), unlock with the same account, and retry access.
    4. If the error appears on a Microsoft cloud sign-in page (login.microsoftonline.com)
      For a browser-based sign-in error like “Sorry, but we’re having trouble signing you in” on that PC only:
      • Identify the detailed error code from the sign-in page source (search for HR= in the HTML as documented).
      • Provide that code to technical support or the IT admin so they can look it up in the known error codes list and apply the corresponding fix.
    5. Escalate to Microsoft support if device cannot be recovered
      If the device object cannot be re-enabled or recovered (for example, it was deleted and manual recovery fails), the admin should open a support request with Microsoft, providing:
      • The device details (name, join type, user, and sample error from Event Viewer or sign-in logs).
      • The exact error code and correlation IDs from the failing sign-in.

    These steps focus on validating that the affected PC is correctly registered, enabled, compliant, and trusted by Microsoft Entra ID and any conditional access policies, which is the typical root cause when sign-in works on other devices but fails on one specific machine.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.