Symptoms

The Adaptiva OneSite Platform 9.3 release has received several updates but will soon be replaced by version 10.0.971.12, available on December 10, 2025. Adaptiva recommends that OneSite Patch customers upgrade to the latest build, however, we understand that not all customers can upgrade immediately.

To address known issues in the 9.3 release, we have provided this hotfix 9.3.970.17.

If you are experiencing any of the Client issues listed below, please update to the 9.6.970.17 hotfix or a later release. These issues may affect any version of 9.3 when using OneSite Patch.

• Administrators noticing the following failures with the monthly cumulative updates should upgrade. These errors will be recorded in the PatchingAdmin.log, SoftwareDeploymentManager.log, and WindowsPatching.log

INFO - Completion status for patch [1021071996], request [0MoNHt7iR7KQM8VVKr3Ztw]  
is [PatchDeploymentResult : patchID=1021071996, operation=1, 
softwareDeploymentOperationStatus=2, reasonCode=1, 
reasonMessage='Exception occurred: Error Message = Download operation failed: win32 error -1047526397 (0xc1900403), 
Error Code = -1047526397 (0xc1900403), Source Object = null', wuaRebootRequired=false]. 
- PatchingAdmin - TID=82, AdaptivaTimer - SoftwareDeploymentManager. ExecutingTask-SoftwareDeploymentManager$InstallationTimerTask

Error Codes may also include: -2145099774 (0x80246002), -2133843966 (0x80d02002), -2145116147 (0x8024200d)

• Administrators may be noticing patch failures with the Office 365 patches or they may see the Office 365 channel being changed inadvertently. For additional information on how to resolve Office 365 patching issues, please refer to this article: Office 365 Patch Deployment Improvements
• Administrators may notice sensor data is inaccurate for one or more devices in Business Unit or Group definitions. To resolve this, customers will also have to run a custom workflow on the impacted clients. See the attachment at the bottom of this article. This workflow should be deployed using a content push policy with a load balanced schedule to ensure all targeted clients are not updated at once. See Force Sensor Refresh Instructions below.
• Customers may experience high CPU or Memory usage during Feed processing.
• Administrators may notice the various Adaptiva logs no longer updating. This is due to a deadlock between the patch pre-staging runner and the patching policy update.
• Customers may notice an issue on servers where they are unable to log out due to the Windows System Event Notification Service (SENS) blocking the logout process.
• Client upgrades fail from a pre-9.3 build to 9.3 if the client has not received the risk assessment configuration policy object.
• Client upgrades fail from a pre-9.3 build to 9.3 where other versions of Java are installed and environment variables _JAVA_OPTIONS or JAVA_TOOL_OPTIONS exist.
• The Adaptiva client service will not start up for more than 90 minutes on devices with a network adapter on a non-routable network.
• The Adaptiva client will not connect to the on premises Adaptiva server when the macOS device is connected using a VPN connection.

Solution

Complete the following steps to resolve the above issues.

1. Download the latest 9.3.970.17 from here: Adaptiva_9.3.970.17.zip
2. Send email or create a ticket on the support portal to request the password from Adaptiva Support
3. Unzip the file on the Adaptiva Server
4. Run adaptiva-server-9.3.970.17-windows.exe
5. Select Quick Upgrade
6. All client devices will be upgraded based on the settings in the Client Upgrade page.
7. Please make sure all Central Office clients and RVPs are upgraded to ensure the above issues can be mitigated.

For more information on the latest releases, visit Product Releases – Adaptiva Support Portal.

Force Sensor Refresh Instructions

Complete the following steps to force targeted clients to update their sensor data. If you want to work with Customer Support to complete these steps, please open a ticket in the Adaptiva Support Portal. 

This requires the workflow ResetAllSensors to have already been imported. See the link at the bottom of this article. For more information about importing workflows see this article.

1. Create a group if targeting a specific subset of all clients.
2. Create a load balanced schedule.
   • Enter a Schedule name. For example: Reset Sensor with load balance.
   • Schedule Repeat should be ASAP. If you want the schedule to start at a specific time, select Not Recurring and enter the Start Time.
   • Toggle Additional Time Constraints to the right.
   • Enter the Load Leveling Duration. The total number of targeted clients will be evenly spread out across this time period. We recommend not processing more than 10 clients per minute initially. This can be increased as you review any impacts to server performance. For example, if you have 1000 devices, set the Load Leveling Duration to be 17 hours to ensure processing of no more than 10 clients per minute.
   • Click Save.
3. Create a Content Push policy to run the workflow on the targeted clients.
   • In the address bar enter https://<adaptivaservername>[:port]/content-push.
   • Click New to create a new policy.
   • Enter a name. For example: Reset Sensor.
   • In the Schedules section, click Browse and select the schedule that was created, then click OK.
   • In the Target Groups section, click Browse and select the group to target.
   • In the Intellistage and Push Settings section, turn off Enable IntelliStage (left).
   • Scroll to the bottom and select Advanced Settings.
   • Scroll to the bottom of the Advanced Settings page and click Browse next to Client Policy Execution Workflow.
   • Filter for ResetSensor and select it. Click OK.
   • Click OK and click Save.