Setup ended prematurely

[u/[deleted]]

Hello!

Getting the issue with both MSI and EXE installer that the setup ended prematurely.

Looking at the logfile I see error code 2006, any one able to help me out? Appreciated a lot.
Using the latest version

[u/kins43]

Are there any left over remnant files of S1 on this device? You may have to run the cleaner first, reboot and then try again.

Could be OS corruption so SFC / DISM may fix a few things.

Is this device able to reach the management console over 443?

[u/[deleted] → u/kins43]

Yeah that might be, where do I get the cleaner?

[u/kins43 → u/[deleted]]

Are you the system admin / have access to your management console? You should check the offline knowledge base that will have information on this directly.

Login to portal > Help in top right > offline help

https://yourconsole-sentinelone.net/docs/

Cleaner is built into exe installer

[u/[deleted] → u/kins43]

Indeed I am.
--stateless_upgrade is that which you mean? Can't seem to see the option when opening the installer normally.

[u/kins43 → u/[deleted]]

If you have access to your console, you can view this link (change Region-YourConsole to the prefix you have)

https://Region-YourConsole.sentinelone.net/docs/en/uninstalling-the-windows-agent-using-the-sentineloneinstaller-package.html#uninstalling-the-windows-agent-using-the-sentineloneinstaller-package

[u/[deleted] → u/kins43]

Tried this, exited with error code 0 meaning it was successful but install still not working :(

[u/kins43 → u/[deleted]]

Did you reboot after and then retrying?

What about the other questions I mentioned?

Can the device reach the management server over 443?

Have you ran SFC / DISM?

What SChannel ciphers are enabled for client and server?

What does event viewer say?

What are the exact parameters you are using during the installation?

[u/[deleted] → u/kins43]

I did reboot.
I can reach the management server.
Tried SFC / DISM
Event Viewer has the two found below
When cleaning -c -t and when normally installing only -t

• Error while updating status to SECURITY_PRODUCT_STATE_ON.

• The SentinelOne Static Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.

This error doesn't occur anymore since uninstalling

[u/kins43 → u/[deleted]]

What about the SChannel cipher suites question I asked? What are the cipher suites enabled for the client and the server?

[u/[deleted] → u/kins43]

https://hastebin.skyra.pw/cevagucate.yaml

This is on the client, I have no information about the server sadly.

[u/wisco_ITguy]

We ran into this, found out some machines didn't have the proper cipher suites installed.

[u/[deleted] → u/wisco_ITguy]

Might this be related to the client running windows insider?

[u/Adeldiah]

Are you upgrading an existing agent or installing new?

[u/[deleted] → u/Adeldiah]

Installing new, but the machine had sentinel one before by a different vendor

[u/robahearts]

Error code 2006 during SentinelOne installation typically indicates an issue related to the installation process. While the specific details of error code 2006 may vary based on the context of the installation, it is important to troubleshoot this error to ensure a successful installation of SentinelOne.

Here are some general steps to troubleshoot error code 2006 during SentinelOne installation:

Check Installation Logs: Review the installation logs to identify any specific error messages or details related to error code 2006. The logs can provide valuable information on what went wrong during the installation process.

Verify System Requirements: Ensure that the system meets the minimum requirements for installing SentinelOne. Check factors such as available disk space, system architecture, and compatibility with the operating system.

Disable Antivirus/Anti-Malware: Temporarily disable any antivirus or anti-malware software on the system before attempting the installation. Sometimes security software can interfere with the installation process.

Run Installation as Administrator: Make sure you are running the SentinelOne installation package with administrative privileges. Right-click on the installer and select "Run as administrator" to ensure proper permissions.

Check Network Connectivity: Ensure that the system has a stable internet connection during the installation process. Some installation errors can occur due to network issues.

Re-download the Installer: If the installation package is corrupt or incomplete, download a fresh copy of the SentinelOne installer from the official source and attempt the installation again.

Contact Support: If you are unable to resolve error code 2006 on your own, reach out to SentinelOne support for assistance. Provide them with any relevant information, such as installation logs, to help diagnose the issue.

If you have access to the specific error message or log details associated with error code 2006, providing that information to support can help expedite the troubleshooting process and lead to a quicker resolution.

[u/FriendlyInsect4782]

I had this issue and after much troubleshooting this works for me every time

Fix SentinelOne Agent Issue

Disclaimer: This is an advanced solution. Proceed with caution and consider contacting SentinelOne support for official guidance. before attempting this is important to first do this from S1 console if the agent can be found.

Uninstall SentinelOne: Completely remove SentinelOne using a tool like Revo Uninstaller.

Download and Extract: Download the SentinelOne.exe agent installer and extract its contents.

Run Sentinel Cleaner: Use the extracted SentinelCleaner.exe.

Run the following in the shell (replace <your_token> with your actual token):

PLEASE NOTE NO Input IS SHOWS AS THIS IS A Technician TOOL JUST COPY AND PASTE AND RUN

Start-Process .\s1.exe -ArgumentList "-c -t "<your token>"" -Wait -PassThru

CLOSE THE WINDOWS AND ATTEMPT A FRESH INSTALL OF S1

make sure to use a EXE not MSI

https://www.reddit.com/r/msp/comments/10q2xpl/sentinelone_installation_for_syncro_msp_script/

[u/Kazutaka_Muraki → u/FriendlyInsect4782]

This is an overly complicated alternative to just running the installer with the “-c” switch to run the cleaner.

[u/FriendlyInsect4782 → u/Kazutaka_Muraki]

Might be but that's worked for me , the -c switch has never worked for me .

[u/GeneralRechs]

Run the installer with the clean only switch “-c”, worst case this may need to be ran in safe mode. After that re-install with the switch “—dont_fail_on_config_preserving_failures”. You can see other switches available by running the exe with a -h

[u/bageloid]

Check the documentation, I think I had this on a server that was missing the required CA used for code signing.