SIMS Summer 2025 loads of failed installed

[gshaw]

13 hours ago, Sheridan said:

We've had the ports defined by a gpo for a long time. I tried a fresh download as well but no luck

 

Just built a domained machine from our previous image (moving these devices to Entra Joined \ InTune this summer) and SOLUS deployed the Summer 2025 update fine from there. 

 

Appears to be either firewall or AV then hmmm

[Sheridan]

I'm not sure if the firewall is an issue here as it uses 52965 and 52966 for the Solus service to perform the update and 8739 to connect to the UI

 

We know 8739 is open when a user is logged in otherwise it isn't. The other two are open all the time and that's why the update seems to begin (and actually complete) but something is hanging or not closing hence the timeout error

 

We're looking at rolling out the next update by a simple copy script instead via sccm

[gshaw]

Good news for my issue, all working now

• downloaded the SIMS Summer update and SOLUS Agent update again in SOLUS manager
• cleared C:\ProgramData\Capita\Deployments\Package on the affected client
• reinstalled the latest version of SOLUS Agent 3.12.86.1 (instead of previous 3.12.72.1)
• deployment now working on the InTune devices

Very strange one, especially as the older client was working on the domained devices but not arguing with a fix that works (!)

[mdrabble]

17 minutes ago, gshaw said:

Good news for my issue, all working now

• downloaded the SIMS Summer update and SOLUS Agent update again in SOLUS manager
• cleared C:\ProgramData\Capita\Deployments\Package on the affected client
• reinstalled the latest version of SOLUS Agent 3.12.86.1 (instead of previous 3.12.72.1)
• deployment now working on the InTune devices

Very strange one, especially as the older client was working on the domained devices but not arguing with a fix that works (!)

 

Would you mind sharing how you have created your Intune deployment packages for SIMS and Solus please.

[gshaw]

4 hours ago, mdrabble said:

 

Would you mind sharing how you have created your Intune deployment packages for SIMS and Solus please.

 

It's basically following this well-written guide How to deploy SIMS.net to Entra Joined Devices - Tech Blog, News, How To's and More. though with the issues I had this week make sure you get the freshest MSI files by running a re-Download & Extract of the SOLUS Agent from the server console

[AGA]

Think we're seeing the same issue trying to deploy the SIMS summer update.

All the PCs that we pushed the update to have returned with 'Deployment timed out' in the SOLUS upgrade deployment logs.
The PCs now report as being on the latest SIMS version (7.224.27), but when testing a handful we found that it's only functional on some of them. On others, when trying to launch SIMS it can't find the connect.ini
 

In the SOLUS systemlog file on each PC affected, the line that stands out is:
Info|Sent ProgressUpdateType: DeploymentJobId:70dffa0d-280f-4df3-9d6a-e72805280786 PackageId:e8fd29b0-20b5-4625-89fc-8abdabdfd746 TaskId:00000000-0000-0000-0000-000000000000 ActionType:General ProgressType:Finish Message:'One or more errors occurred.' MoreInfo:'System.AggregateException: One or more errors occurred. ---> Sims.Solus3.Agent.PackageDeployer.PackageException: Package failed. Rollback was executed. ---> Sims.Solus3.Agent.PackageDeployer.TaskException: Execution of task 2b05c745-cf87-46db-9615-a9bf15631d3e failed. ---> System.InvalidOperationException: Process must exit before requested information can be determined.

 

And the other error message we're seeing returned in the solus agent logs is:
'Decompiling of the package SIMS Summer 2025 Full Release (7.224.27) (SIMS Workstation) failed'

Solus version on all our PCs is 3.12.86.1

Had no issues installing the spring update.

 

Has anyone had anything useful back from Support they can share?

[gshaw]

24 minutes ago, AGA said:

Has anyone had anything useful back from Support they can share?

 

Fairly standard steps but it did work in the end for me, with an added step of also Download / Extract SOLUS for a clean install (mine were freshly built machines)

 

Please attempt the following fixes

1. Restart the SOLUS3 deployment service from the SOLUS 3 Server. 
2. On the affected workstation restart the SOLUS 3 Agent Service.
3. Re-download the Update in question.
4. On the affected workstation delete the package from C:\ProgramData\Capita\Deployments\Package
5. Deploy the update in question to the affected workstation to resolve the issue.
6. If this does not resolve the issue the SOLUS 3 agent on the workstation will have to be removed and reinstalled.

Edited August 6, 2025 by gshaw

[AGA]

7 minutes ago, gshaw said:

 

Fairly standard steps but it did work in the end for me, with an added step of also Download / Extract SOLUS for a clean install (mine were freshly built machines)

 

Please attempt the following fixes

1. Restart the SOLUS3 deployment service from the SOLUS 3 Server. 
2. On the affected workstation restart the SOLUS 3 Agent Service.
3. Re-download the Update in question.
4. On the affected workstation delete the package from C:\ProgramData\Capita\Deployments\Package
5. Deploy the update in question to the affected workstation to resolve the issue.
6. If this does not resolve the issue the SOLUS 3 agent on the workstation will have to be removed and reinstalled.

 

Thanks for the reply. I think we've tried everything except a complete reinstall of the SOLUS deployment service on the server. Is that what you're suggesting?

Have tried both restarting the service and rebooting the SIMS server.
Have tried deleted both the update package within 'D:\SIMSRoot\Repository' and the extracted copy inside 'D:\SIMSRoot\Repository\DoNotDeleteThisFolder', then redownloaded through SOLUS.

We're seeing the issue on both fresh installs, and on our existing PCs that were on the Spring update.
Uninstalling the solus agent and then deleting everything within these locations on the PCs and redeploying also hasn't helped:
C:\ProgramData\Capita
C:\ProgramData\Solus 3
C:\Program Files (x86)\SIMS
C:\Program Files\Solus3
 

We've found we can manually copy the 'C:\Program Files (x86)\SIMS\SIMS .net' folder over from a working PC and SIMS can be launched etc.
But solus is insistent on still trying to reinstall, so the agent will keep popping up trying again and again.
 

[gshaw]

7 hours ago, AGA said:

 

Thanks for the reply. I think we've tried everything except a complete reinstall of the SOLUS deployment service on the server. Is that what you're suggesting?

 

No it was just the Agent:

 

- from the Updates library find the Agent in the list

- Download button

- Extract button

- install onto a test machine using the freshly extracted files

 

What was really odd in my case was that a domained fresh machine was working on the older agent (think it was .72) but the new InTune builds only worked with the newer agent .86

[Sheridan]

I've shelved trying to fix this for now - support basically seem to think its the firewall and that I'm too 'stubborn' or 'inexperienced' to accept this 😄

 

I've proved its not the firewall so my plan is to ditch Solus completely and just use sccm to deploy sims in future

[SIMS_Customer_Support]

On 07/08/2025 at 07:58, Sheridan said:

I've shelved trying to fix this for now - support basically seem to think its the firewall and that I'm too 'stubborn' or 'inexperienced' to accept this 😄

 

I've proved its not the firewall so my plan is to ditch Solus completely and just use sccm to deploy sims in future

@Sheridan I’m sorry to hear about the repeated errors you’ve experienced — I understand how frustrating that must be. I’d really like to work with you to get the issue completely resolved. Can I ask one of our analysts to make direct contact with you? What is your preferred method of contact? I look forward to hearing from you? 

 

Many thanks

Sally

[5nowman]

Had chaos here with fresh installs of sims on Server 2025. I fear sims support might just blame the OS as it is not on their list of supported server operating sytems.

 

Server seems to hang on parts of simsinst and also crash when doing the migration "install server applications"

 

not related to your issues right?

 

5nowman

[SIMS_Customer_Support]

@5nowman I’m sorry to hear this. Can I ask one of our analysts to get in touch and help resolve the issues you are currently experiencing? What is your preferred method of contact? I look forward to hearing from you? 

 

Many thanks

Sally

[5nowman]

14 minutes ago, SIMS_Customer_Support said:

@5nowman I’m sorry to hear this. Can I ask one of our analysts to get in touch and help resolve the issues you are currently experiencing? What is your preferred method of contact? I look forward to hearing from you? 

 

Many thanks

Sally

Hi Sally,

 

Resolved. sophos was stopping simsinst.exe from finishing and migration from running.

 

Can you let me know what folder exclusions sophos should have for sims please?

 

5nowman

[SIMS_Customer_Support]

28 minutes ago, 5nowman said:

Hi Sally,

 

Resolved. sophos was stopping simsinst.exe from finishing and migration from running.

 

Can you let me know what folder exclusions sophos should have for sims please?

 

5nowman

Hi @5nowman

 

Great news you have resolved the issue. As requested, here are the details:

 

SOLUS 3 - Antivirus whitelisting/exceptions

 

 

Breakdown of which files and filepaths need to be whitelisted in my antivirus software in order to ensure SOLUS 3 works as expected?

System Administrators are advised to ensure that the SOLUS 3 Agent service (and it's child/sub processes if given the option) is whitelisted in the Anti-Virus to ensure it doesn't stop the agent from finishing the installation. The deployment store for the agent should also be whitelisted. It has also been found that the following whitelisting will allow the SOLUS agent to work:

Global Exception List

Trusted Windows Program List

• S:\SIMS\Setups\SIMSAMPARKSetup.exe
• S:\SIMS\Setups\SIMSApplicationSetup.exe
• S:\SIMS\Setups\SIMSManualSetup.exe
• D:\SIMS\Sims\Setups\SIMSManualSetup.exe
• D:\SIMS\Sims\Setups\SIMSApplicationSetup.exe
• D:\SIMS\Sims\Setups\SIMSAMPARKSetup.exe
• C:\Program Files\Solus3\AgentService\Sims.Solus3.Agent.OfflineDeployer.exe
• C:\Program Files\Solus3\AgentService\Sims.Solus3.Agent.PackageDeployer.exe
• C:\Program Files\Solus3\AgentService\Sims.Solus3.Agent.UI.exe
• C:\Program Files\Solus3\AgentService\Sims.Solus3.Agent.AgentService.exe

Local Policy Level (Real-Time Scan ONLY Exclusions)

Folders

• C:\Program Files\Solus3
• C:\Program Files\sims\Sims .net
• C:\ProgramData\Capita
• C:\ProgramData\Solus 3

Files

• C:\Windows\sims.ini

Behaviour Monitoring approved program list

• C:\ProgramData\Capita\Solus3\Deployments\*
• D:\Sims\Sims\Setups\SIMSManualSetup.exe
• D:\Sims\Sims\Setups\SIMSApplicationSetup.exe
• D:\Sims\Sims\Setups\SIMSAMPARKSetup.exe
• S:\SIMS\Setups\SIMSManualSetup.exe
• S:\SIMS\Setups\SIMSApplicationSetup.exe
• S:\SIMS\Setups\SIMSAMPARKSetup.exe
• C:\Program Files\Solus3\AgentService\Sims.Solus3.Agent.OfflineDeployer.exe
• C:\Program Files\Solus3\AgentService\Sims.Solus3.Agent.PackageDeployer.exe
• C:\Program Files\Solus3\AgentService\Sims.Solus3.Agent.AgentService.exe
• C:\Program Files\Solus3\AgentService\Sims.Solus3.Agent.UI.exe
• C:\Program Files\Solus3\*
• C:\ProgramData\Capita\*

 

Many thanks

Sally 

[Sheridan]

We're still having issues - fresh client install (traces deleted)m and re-downloaded to the server several times. Runs through and shows the same 'one or more errors occurred ' but the error seems to be a different one now:

 

Sims.Solus3.Agent.PackageDeployer.PackageException: Failed to validate signature. ---> System.Security.SecurityException: Failed to validate signature.

 

This error was previously fixed by a full delete of the client but that isn't working now

 

 

[SIMS_Customer_Support]

3 hours ago, Sheridan said:

We're still having issues - fresh client install (traces deleted)m and re-downloaded to the server several times. Runs through and shows the same 'one or more errors occurred ' but the error seems to be a different one now:

 

Sims.Solus3.Agent.PackageDeployer.PackageException: Failed to validate signature. ---> System.Security.SecurityException: Failed to validate signature.

 

This error was previously fixed by a full delete of the client but that isn't working now

 

 

Hi @Sheridan

I am sorry to hear this, based on the error provided there is an assumption it is one machine that the error keeps happening on and all others are ok? Here are some steps that may help resolve this: 

1. Restart the SOLUS3 deployment service from the SOLUS 3 Server.
2. On the affected workstation, restart the SOLUS 3 Agent Service.
3. Re-download the update in question.
4. On the affected workstation, delete the package from `C:\ProgramData\Capita\Deployments\Package`.
5. Deploy the update in question to the affected workstation.
6. If the issue persists, the SOLUS 3 agent on the workstation may need to be removed and reinstalled.

Additionally, ensure that the SOLUS3 agent service on the Server is "Started". You can check this by going into `Services.msc`, scrolling down to find the SOLUS3 agent, and checking the status column. If this is blank, right-click on the line and select "Start".

 

Please do let me know if this resolves the issue. 

 

Many thanks

Sally 

 

[Sheridan]

8 minutes ago, SIMS_Customer_Support said:

Hi @Sheridan

I am sorry to hear this, based on the error provided there is an assumption it is one machine that the error keeps happening on and all others are ok? Here are some steps that may help resolve this: 

1. Restart the SOLUS3 deployment service from the SOLUS 3 Server.
2. On the affected workstation, restart the SOLUS 3 Agent Service.
3. Re-download the update in question.
4. On the affected workstation, delete the package from `C:\ProgramData\Capita\Deployments\Package`.
5. Deploy the update in question to the affected workstation.
6. If the issue persists, the SOLUS 3 agent on the workstation may need to be removed and reinstalled.

Additionally, ensure that the SOLUS3 agent service on the Server is "Started". You can check this by going into `Services.msc`, scrolling down to find the SOLUS3 agent, and checking the status column. If this is blank, right-click on the line and select "Start".

 

Please do let me know if this resolves the issue. 

 

Many thanks

Sally 

 

That’s basically everything I’d tried so far with this affected pc. I’m still getting the previous ‘errors have occured’ on other stations as well. This was a perfectly working system last when we last ran the Spring updates so I’m not sure why it’s become so problematic

 

As for this specific pc I ran the locally downloaded package manually and copied over the connect.ini file and it now works, so it’s not like the package has any issues or corruption. This isn’t really a good solution for the rest though!

[willtech]

What AV do you run, we have found an issue with Sophos and the Behaviour Monitoring Modal causing this issue. 

[Sheridan]

9 hours ago, willtech said:

What AV do you run, we have found an issue with Sophos and the Behaviour Monitoring Modal causing this issue. 

We do use Sophos, but there have global Exclusions in place since it was implemented (a few years ago) for the relevant Solus/SIMS folders

 

This does seem to just be an issue since the Summer 25 update - when we ran the Spring 25 update (same AV and settings, same client OS, same Solus 3 server) we had hardly any issues and they were just the usual random failed install (i.e solus not working on client pc, or pc not online etc)

 

There isn't a way to Deploy an update to single computer to test is there? Any deployment picks up all of the clients/server regardless of whether they're in the target list or no, and I don't want to keep trying a full deployment

Edited August 21, 2025 by Sheridan

[AGA]

We still haven't properly resolved this, and also have Sophos Central AV, so I did some tests.

Deployment works if we disable Real Time Scanning for Files in the Sophos Agent on the client.
We have Global Exclusions in place for all the known SIMS file paths and .EXEs.
We also can't see any Sophos Central logs to suggest it's taking any action? but it clearly is.

[willtech]

8 hours ago, AGA said:

We still haven't properly resolved this, and also have Sophos Central AV, so I did some tests.

Deployment works if we disable Real Time Scanning for Files in the Sophos Agent on the client.
We have Global Exclusions in place for all the known SIMS file paths and .EXEs.
We also can't see any Sophos Central logs to suggest it's taking any action? but it clearly is.

see this thread: 

 

[SIMS_Customer_Support]

21 hours ago, AGA said:

We still haven't properly resolved this, and also have Sophos Central AV, so I did some tests.

Deployment works if we disable Real Time Scanning for Files in the Sophos Agent on the client.
We have Global Exclusions in place for all the known SIMS file paths and .EXEs.
We also can't see any Sophos Central logs to suggest it's taking any action? but it clearly is.

Hi @AGA

 

You may find the following information helpful in resolving this issue: 

 

SOLUS 3 - 'Process must exit before requested information can be determined.'

 

Description of Issue

When attempting to deploy an update via SOLUS, the deployment will fail with the following error found in the agent deployment log:

'Process must exit before requested information can be determined'

Schools that have previously successfully deployed the update may see issues when deploying SIMS to newly added agents:

'Decompiling of the package SIMS Summer 2025 Full Release failed'

 

Cause

This issue at present appears to be caused by Sophos blocking the SOLUS Agent from finishing the SIMS Update, though this error may also show for other Anti-Virus software. 

 

Workaround

This issue occurs when an antivirus program blocks the SOLUS Agent from completing the SIMS Update.

We have recently observed an increased frequency of this issue for sites running Sophos.

We have confirmed via testing undertaken, where Sophos has been temporarily disabled/uninstalled from the affected workstations, that SOLUS works as expected.

 

Resolution

We have found that having the following exceptions in place will resolve the issue for most Schools; however, we would encourage affected users to consult with Sophos prior to making any changes to their application

AMSI Protection:

C:\ProgramData\Capita\Solus3\Deployments\
C:\ProgramData\Capita\Solus3 - Real-time only
 
Exploit Mitigation And Activity Monitoring:

C:\ProgramData\Capita\Solus3\Deployments\**

 

Please do let me know if the information provided resolves the issue, or if you need any further assistance.

 

Best wishes

Sally

 

[AGA]

Thanks both, that looks to have worked

[5nowman]

3 hours ago, AGA said:

Thanks both, that looks to have worked

Where are you doing this AMSI protection? or Exploit Mitigation and activity monitoring?

 

I cannot see it under any tampering sophos policy.

 

I cannot see it anywhere on the Sophos central management!

 

Any help would be good. thank you.