Windows Device Check Failures — How to Fix

If you were blocked from signing in to a Samsara application, your Windows device did not pass one of our security checks. Find your check below and follow the steps.

Contents

1. Windows Version Is Not Up to Date
2. Required Samsara Device Certificate Is Missing
3. Device Has Not Checked In to Intune in the Last 7 Days
4. Device Is Not Joined to Samsara's Microsoft Entra ID
5. TPM Was Not Detected
6. Disk Is Not Encrypted (BitLocker)
7. Device Is Not Part of the Samsara Windows 365 Cloud PC Environment
8. CrowdStrike Falcon Sensor Is Not Installed or Not Running
9. Chrome Browser Is Not Up to Date
10. Chrome Browser Is Not Signed In with a Samsara Account
11. Chrome Cannot Verify Your Device's Security Chip

Before you start: to find your device name and serial number, open the Company Portal app, select Devices, and click your computer.

1. Windows Version Is Not Up to Date

Why is this a problem?

Your device must run a supported version of Windows with the latest required security updates installed. Keeping Windows current protects Samsara data, your account, and the device itself from known security flaws.

This check supports both Windows 10 and Windows 11, but your device must be on an approved major version and have recent security patches installed.

How do I fix this?

Try this first:

1. Connect your device to the internet.
2. Open Settings.
3. Go to Windows Update:
   • Windows 11: select Windows Update.
   • Windows 10: select Update & Security, then Windows Update.
4. Select Check for updates.
5. Install all available updates.
6. Restart your device if prompted.
7. After restarting, return to Windows Update and check again — sometimes new updates appear only after the first round installs. Install anything remaining and restart again.
8. Wait 5–10 minutes, then try signing in to the application again.

Still not working?

Post in the #help-biztech Slack channel and include:

• Device name (from the Company Portal app)
• Operating system: Windows 10 or Windows 11
• Check name: Windows – Require Supported OS Version and Latest Security Patch
• Source: Okta Device Assurance
• When the problem started
• Anything that changed recently (returning from time away, a Windows update, a restart)

2. Required Samsara Device Certificate Is Missing

Why is this a problem?

Your device must have a valid Samsara security certificate installed. The certificate is a digital ID that proves the device is trusted, managed by Samsara, and tied to the correct hardware.

This check fails if the certificate is missing, expired, invalid, was created incorrectly, or does not match your device's serial number.

How do I fix this?

The certificate is normally issued automatically to managed Windows devices. Syncing with Company Portal usually brings it down.

Sync your device:

1. Open the Start menu and search for Company Portal.
2. Open Company Portal.
3. Go to Settings.
4. Select Sync.
5. Wait for the sync to finish, then try signing in to the application again.

Still not working?

Post in the #help-biztech Slack channel and include:

• Device name (from the Company Portal app)
• Operating system: Windows 10 or Windows 11
• Check name: Windows – Require Samsara Device Certificate
• Source: Okta Device Assurance
• When the problem started
• Anything that changed recently

3. Device Has Not Checked In to Intune in the Last 7 Days

Why is this a problem?

Your device must check in regularly with Microsoft Intune, Samsara's Windows device management system. Each check-in confirms your device is still managed, healthy, and receiving required security settings.

This check fails if your device has not checked in to Intune with your Samsara account in the last 7 days.

How do I fix this?

Your device needs to reconnect to Intune and complete a check-in.

Sync your device:

1. Open the Start menu and search for Company Portal.
2. Open Company Portal.
3. Go to Settings.
4. Select Sync.
5. Wait for the sync to finish, then try signing in to the application again.

Still not working?

Post in the #help-biztech Slack channel and include:

• Device name (from the Company Portal app)
• Operating system: Windows 10 or Windows 11
• Check name: Windows – Require Recent Intune Check-In
• Source: Okta Device Assurance
• When the problem started
• Anything that changed recently

4. Device Is Not Joined to Samsara's Microsoft Entra ID

Why is this a problem?

Your device must be joined to Samsara's Microsoft identity system, Entra ID. This confirms the device belongs to Samsara and is connected to the correct company identity environment.

This check fails if the device was never properly joined, was reset, was removed from management, or is signed in with the wrong work account.

How do I fix this?

In most cases this needs help from IT, but start by checking your connection.

Check your connection:

1. Open Settings → Accounts → Access work or school.
2. Look near the top for a line that reads "Connected to Samsara's Azure AD" or "Connected to Samsara Entra ID".

What to do next:

• If the line is present: restart your device, sign in, wait 5 minutes, then try again.
• If the line is missing or shows an error: do not try to add the account back yourself. Contact #help-biztech on Slack instead with the details below.

Still not working?

Post in the #help-biztech Slack channel and include:

• Device name (from the Company Portal app)
• Operating system: Windows 10 or Windows 11
• Check name: Windows – Require Samsara Entra ID Join
• Source: Okta Device Assurance
• When the problem started
• Anything that changed recently

5. TPM Was Not Detected

Why is this a problem?

Your device must have a Trusted Platform Module (TPM). TPM is a built-in security chip that protects encryption keys, sign-in information, and other sensitive security data on the device. This check makes sure company data is protected by modern, hardware-backed security.

How do I fix this?

TPM is a hardware feature, so this usually cannot be fixed on your own. Most Samsara-managed Windows devices already meet this requirement.

Try this first:

1. Restart your device.
2. Confirm you are using a Samsara-managed Windows device.
3. Sign in and try the application again.

Note: personal devices, older devices, and recently repaired devices may not meet Samsara's secure hardware requirements.

Still not working?

Post in the #help-biztech Slack channel and include:

• Device name (from the Company Portal app)
• Operating system: Windows 10 or Windows 11
• Check name: Windows Desktop – Require Secure Hardware
• Source: Okta Device Assurance
• When the problem started
• Anything that changed recently

6. Disk Is Not Encrypted (BitLocker)

Why is this a problem?

All internal drives on your device must be encrypted. Samsara uses BitLocker on Windows to protect company data if a device is lost, stolen, or accessed without permission.

This check fails if one or more internal drives are not encrypted.

How do I fix this?

BitLocker is normally turned on automatically on Samsara-managed devices, but you can enable it yourself if it is currently off.

1. Open the Start menu.
2. Search for Manage BitLocker and open it.
3. Check the status shown next to your internal drive (usually the C: drive):
   • If it shows "Encrypting" with a percentage: encryption is already in progress. Wait until it reaches 100% — the check will not pass before then. Keep your device powered on and plugged in. You can skip the remaining steps.
   • If BitLocker is off: continue to step 4.
4. Select Turn on BitLocker.
   • If Turn on BitLocker is greyed out or asks for an administrator password, stop here and contact #help-biztech on Slack.
5. Follow the prompts to choose where to back up your recovery key. Saving it to your Azure AD / cloud account is recommended.
6. Finish the setup wizard to start encrypting the drive.
7. Keep your device powered on and plugged in while it encrypts.
8. Once encryption is complete, try signing in to the application again.

Important: once BitLocker is active, do not disable, reset, or reconfigure it on your own.

Still not working?

If BitLocker shows an error, is paused, or the check still fails, post in the #help-biztech Slack channel and include:

• Device name (from the Company Portal app)
• Operating system: Windows 10 or Windows 11
• Check name: Windows Desktop – Require Disk Encryption
• Source: Okta Device Assurance
• BitLocker status (for example, off, paused, or "needs attention")
• When the problem started
• Anything that changed recently

7. Device Is Not Part of the Samsara Windows 365 Cloud PC Environment

Why is this a problem?

This check applies only to virtual Windows desktops — a Windows computer that runs in the cloud rather than on the laptop in front of you. Your session must be running on an approved Windows 365 Cloud PC.

This makes sure access from virtual Windows devices is limited to Samsara-managed Cloud PCs, not unmanaged or unsupported virtual machines.

How do I fix this?

Access the application from your Samsara-provided Windows 365 Cloud PC.

Note: if you are using a personal virtual machine or a non-Samsara virtual desktop, this check will fail because the device is not an approved Windows 365 Cloud PC.

Still not working?

Post in the #help-biztech Slack channel and include:

• Device name (from the Company Portal app)
• Operating system: Windows VDI or Windows 365 Cloud PC
• Check name: Windows VDI – Require Windows 365 Cloud PC Environment
• Source: Okta Device Assurance
• When the problem started
• Environment details (for example, whether you are on a Samsara Windows 365 Cloud PC, a local Windows device, or another virtual desktop)
• Anything that changed recently

8. CrowdStrike Falcon Sensor Is Not Installed or Not Running

Why is this a problem?

CrowdStrike Falcon is Samsara's endpoint protection software. It watches your device for malware, ransomware, and other threats in real time. Without it, your device is unprotected and puts Samsara's network and data at risk. This check fails if CrowdStrike is missing, has been stopped, or is misconfigured.

How do I fix this?

CrowdStrike should already be installed as part of Samsara's standard device setup. If this check is failing, it usually means CrowdStrike was never installed, was disabled by accident, or stopped working after an update. IT needs to reinstall or repair it.

Important: do not try to uninstall or disable CrowdStrike. It is required on all Samsara devices, and removing it on purpose may trigger a security investigation.

Post in the #help-biztech Slack channel and include:

• Device name (from the Company Portal app)
• Operating system: Windows 10 or Windows 11
• Check name: Windows – CrowdStrike Falcon Sensor
• Source: Okta Device Assurance
• When the problem started
• Anything that changed recently

9. Chrome Browser Is Not Up to Date

Why is this a problem?

Google Chrome must be updated to a supported version. Chrome releases frequent updates that fix security flaws attackers use to reach your device or steal information. Running an outdated Chrome puts both your data and Samsara's systems at risk. This check fails if your Chrome version is below Samsara's minimum.

How do I fix this?

Chrome updates itself automatically in the background on Samsara-managed devices. If you have not relaunched Chrome in a while, the update may be waiting for a restart.

1. Open Google Chrome.
2. Click the three-dot menu (⋮) in the top-right corner.
3. Go to Help → About Google Chrome.
4. Chrome checks for and downloads any available update automatically.
5. Click Relaunch to finish.

Still not working?

Post in the #help-biztech Slack channel and include:

• Device name (from the Company Portal app)
• Operating system: Windows 10 or Windows 11
• Check name: Windows – Chrome Browser Version
• Source: Okta Device Assurance
• When the problem started
• Anything that changed recently

10. Current Browser Is Not a Samsara Chrome Profile

Why is this a problem?

Samsara needs to confirm that the Chrome browser you're using belongs to you and is connected to Samsara. Chrome only shows this when you are signed in to a Chrome profile with your Samsara email address. This check fails if you are not signed in to Chrome at all, if you are signed in with a personal Google account instead, if you are using an Incognito window, or if you are using a different browser altogether (for example, Microsoft Edge or Firefox).

How do I fix this?

1. Open Google Chrome in a normal window — not an Incognito window, and not a different browser like Microsoft Edge or Firefox.
2. Click your profile picture or initial in the top-right corner.
3. If you see Sign in to Chrome, click it and sign in with your Samsara email address (for example, jane@samsara.com).
4. If you are already signed in with a personal Google account, click your profile picture, choose Add to create a new profile, and sign in to that profile with your Samsara email address instead.
5. Make sure the profile signed in with your Samsara email is the one you are using when you access Samsara applications.
6. Close and reopen Chrome, then try signing in again.

Still not working?

Post in the #help-biztech Slack channel and include:

• Device name (from the Company Portal app)
• Operating system: Windows 10 or Windows 11
• Check name: Windows – Chrome Enterprise Device Enrollment Domain
• Source: Okta Device Assurance
• When the problem started
• Anything that changed recently

11. Chrome Cannot Verify Your Device's Security Chip

Why is this a problem?

Your device has a built-in security chip, the TPM, that Chrome uses to prove it's running on a genuine, trusted Samsara device. This is a separate check from TPM Was Not Detected above — this one fails specifically when Chrome can't use the chip, even if the chip itself is working fine.

How do I fix this?

Try this first:

1. Restart your device.
2. Confirm the TPM check above is passing — Chrome depends on it.
3. Open Chrome and try signing in again.

If it still fails, this usually needs IT to reset Chrome's connection to the security chip on their end.

Still not working?

Post in the #help-biztech Slack channel and include:

• Device name (from the Company Portal app)
• Operating system: Windows 10 or Windows 11
• Check name: Windows – Chrome Enterprise Key Trust Level
• Source: Okta Device Assurance
• When the problem started
• Anything that changed recently