| MCMR-36787 | Zebra FX 7500 devices did not reconnect to SOTI MobiControl after a reboot. |
| MCMR-40251 | SOTI MobiControl upgrades failed due to a post-installation error. |
| MCMR-42020 | On some Android devices, profiles remained stuck in the Removal Pending state and could not be revoked or installed. |
| MCMR-42307 | Zebra firmware upgrade actions could not be canceled, affecting assigned Android devices that remained stuck in a Scheduled state. |
| MCMR-42828 | After upgrading SOTI MobiControl, Windows CE packages with scripts remained stuck in the Pending Install state in the SOTI MobiControl console. |
| MCMR-42843 | When sending an action to multiple devices, pressing Enter did not select the filtered action. |
| MCMR-42883 | After upgrading SOTI MobiControl, existing Android Lockdown profiles were missing their respective configurations. |
| MCMR-43183 | Text could not be highlighted and copied from the device list after an upgrade of SOTI MobiControl. |
| MCMR-43216 | Licensed applications on Apple TV devices were uninstalled on devices that did not check in for extended periods of time. |
| MCMR-43463 | Deployment Server logs in System Health intermittently caused the browser tab to freeze and run out of memory. |
| MCMR-43590 | Anonymous user logout activity was incorrectly recorded in SOTI MobiControl user logs. |
| MCMR-43718 | Samsung Knox E-FOTA policies incorrectly showed zero targeted devices for assignment and could not be assigned to Samsung devices in device groups. |
| MCMR-43866 | Signal policies did not trigger on Zebra Android Enterprise device enrollment until a manual check-in or file sync occurred. |
| MCMR-44052 | On Windows Modern devices, the session inactivity timeout from Microsoft Security Baselines was applied incorrectly. |
| MCMR-44084 | iOS and iPadOS devices received operating system updates before the configured deferral period expired. |
| MCMR-44121 | Profiles and packages for a device loaded indefinitely after upgrading SOTI MobiControl. |
| MCMR-44191 | Signal policies did not trigger after user-based iOS enrollment in SOTI MobiControl. |
| MCMR-44235 | Japanese text could not be entered correctly into the Send Message field under Device Actions. |
| MCMR-44277 | Single sign-on users in SOTI MobiControl sometimes had incorrect permissions and could not perform allowed profile actions. |
| MCMR-44354 | Partially enrolled Android Enterprise Dedicated devices could not be deleted from the SOTI MobiControl console. |
| MCMR-44482 | Windows Classic devices configured with Lockdown auto-login no longer logged in automatically after the SOTI MobiControl agent was upgraded from an earlier version. |
| MCMR-44488 | API users remained logged in after token expiry or logout, increasing the length of Management Service user sessions. |
| MCMR-44771 | Some device groups showed an internal server error in the SOTI MobiControl web console after an upgrade. |
| MCMR-44772 | An error during cloning prevented certain profiles with Wi-Fi configurations from being cloned. |
| MCMR-44779 | The managed app configuration editor became unusable when editing some Android Enterprise app configurations. |
| MCMR-44822 | Managed macOS devices did not reconnect to Deployment Servers after upgrading SOTI MobiControl. |
| MCMR-44900 | Wi-Fi profiles reverted the proxy setting to None after saving Automatic Proxy Configuration settings. |
| MCMR-44932 | After upgrading SOTI MobiControl, lockdown profiles could not be saved if menu items contained URLs longer than 256 characters. |
| MCMR-44981 | File Sync did not immediately download files to online Android devices when Sync Online Device Now was enabled. |
| MCMR-45076 | Device Relocation policy assignments were not displayed when the SOTI MobiControl web console language was set to German. |
| MCMR-45143 | After upgrading SOTI MobiControl, the web console failed to load on workstations using Forcepoint or Websense. |
| MCMR-45162 | After upgrading SOTI MobiControl, the Lockdown authentication page remained stuck in the loading state for users without Global Settings access. |
| MCMR-45230 | Device enrollment requests requiring approval remained stuck in the Pending Approval state and did not appear for administrator review. |
| MCMR-45241 | The SOTI MobiControl Management Service crashed during usage statistics cleanup when the database table became excessively large. |
| MCMR-45395 | After upgrading SOTI MobiControl, profile deployment schedules showed different times in the Overview and Edit views. |
| MCMR-45418 | Audit logs showed the wrong time unit for Delete Offline Devices settings configured in months. |
| MCMR-45429 | Devices did not appear on the Profile Assignment page when viewing assigned profiles or using search filters. |
| MCMR-45446 | Profile filters using custom attributes displayed an invalid filter error when saved or assigned. |
| MCMR-45473 | Previously selected device groups were unexpectedly deselected when editing profile assignments in SOTI MobiControl. |
| MCMR-45504 | Windows devices became non-compliant after being moved to another device group, preventing policy and profile updates. |
| MCMR-45535 | Data Collection policy assignments were not visible when the SOTI MobiControl console used a non-English language. |
| MCMR-45609 | Device assignment target counts were incorrect when string custom attribute filters used “is not” conditions. |
| MCMR-45706 | The SOTI MobiControl installation stopped during the database stage when upgrading the server. |
| MCMR-45733 | Scheduled report logs did not display report history older than two to three days. |
| MCMR-45743 | Profile configurations were missing, and profiles could not be edited after an upgrade of SOTI MobiControl. |
| MCMR-45752 | Decommissioned XTreme Hub devices could not be deleted from SOTI MobiControl. |
| MCMR-45779 | Japanese text entered with Microsoft IME into text fields in the SOTI MobiControl web console appeared incorrectly during composition. |
| MCMR-45825 | The SOTI MobiControl Deployment Server took several minutes to start after an upgrade. |
| MCMR-45843 | After upgrading SOTI MobiControl, the web console and Remote Control intermittently displayed Internal Server Error and Bad Request messages. |
| MCMR-45858 | Upgrades failed during database deployment when Content Library data was present. |
| MCMR-45864 | Search synchronization could fail to complete, making SOTI MobiControl web console search unusable. |
| MCMR-45866 | Data Collection records in the SOTI MobiControl web console displayed the date of the previous day. |
| MCMR-45872 | The Application Data Usage report returned no data after a Telecom Expense Management policy was assigned to device groups. |
| MCMR-45924 | Profiles with scheduled Play Media could not be assigned from a SOTI MobiControl console that used the Japanese language, and Weekly or Interval media playback did not work. |
| MCMR-45931 | Database maintenance alerts were incorrectly triggered after nightly maintenance, even though no database issue existed. |
| MCMR-45978 | SOTI MobiControl Agent installation on Windows devices sometimes required an unexpected device restart to complete. |
| MCMR-45995 | After upgrading SOTI MobiControl, assigned packages did not load in the Packages tab for some profiles. |
| MCMR-46027 | The SOTI MobiControl web console showed an internal server error when selecting View All Devices. |
| MCMR-46084 | The Enrollment Policy agent download list showed duplicate Android Enterprise entries, and one of the entries opened an XML error page. |
| MCMR-46111 | Enterprise applications in a configured App Policy failed to download on Android devices when custom HTTPS listener ports were used. |
| MCMR-46201 | Managed Google Play app policies did not show all available release track options for some private Android Enterprise apps. |
| MCMR-46209 | Search integrity in SOTI MobiControl consistently dropped to approximately 85% after synchronization. |
| MCMR-46224 | Windows Desktop Classic devices prompted users for the enrollment password on every reconnect, reboot, or agent restart. |
| MCMR-46252 | System Health displayed an incorrect 10 GB database limit for SQL Server Express 2025. |
| MCMR-46261 | After upgrading SOTI MobiControl, geofence email notifications displayed a geofence reference ID instead of the geofence name. |
| MCMR-46366 | Signal policy activation and deactivation times reset to 12:00 AM when edited in SOTI MobiControl web console using the Japanese language. |
| MCMR-46419 | Scheduled actions, reporting, logs and device time were offset by one hour in British Columbia and Alberta after the daylight saving time transition in November. |
| MCMR-46447 | Shared device users were intermittently unable to log in or log out, leaving Android devices unusable. |
| MCMR-46457 | After upgrading SOTI MobiControl, the Deployment Server and SQL Server used excessive CPU when devices reconnected. |
| MCMR-46549 | After upgrading SOTI MobiControl, M3Mobile M3SM20 devices unexpectedly restarted or entered boot loops. |
| MCMR-46792 | The SOTI Signal service restarted automatically at 00:00 UTC every day. |
| MCMR-46804 | Manual synchronization on the Microsoft Integration page failed and incorrectly marked the integration as inactive. |
| MCMR-46861 | On the Android Enterprise platform, the managed App configuration for some enterprise apps uploaded in SOTI MobiControl appeared blank. |
| MCMR-46919 | Downloading a Devices view CSV returned only the header row when the Target OS Version column was included for devices without firmware upgrade data. |