Vdi 2 Troubleshooting

@@ -12,7 +12,7 @@ author: officedocspr5 ms.author: odocspr manager: jtremper ms.topic: article-ms.date: 2026-07-28T00:00:00.0000000Z+ms.date: 2026-11-05T00:00:00.0000000Z ms.service: msteams ms.subservice: msteams-admin audience: admin@@ -115,8 +115,9 @@ The code logged here needs to be mapped using this table: | Standard Error Code | loadErrc or deployErrc | Definition | Notes |
 | --- | --- | --- | --- |
 | 0 | 0 | OK | Not an error. 'SlimCore Connected' success, user is properly optimized |
-| 2 | 19 | ERROR\_FILE\_NOT\_FOUND | A file required for SlimCore deployment or startup couldn't be found. Check the endpoint's Event Viewer AppXDeployment-Server/Operational logs to identify the missing file and failing operation. If the error occurs during package registration or startup, verify that the required SlimCore Host and Framework packages are present and registered for the affected user. Check whether an endpoint cleanup script or security product removed the package or its files. An initial registration attempt can return this error before the plugin downloads and stages the package; if subsequent deployment and optimization succeed, no remediation is required for that initial failure. |
+| 2 | 19 | ERROR\_FILE\_NOT\_FOUND | A file required for SlimCore deployment or startup couldn't be found. Check the endpoint's Event Viewer AppXDeployment-Server/Operational logs to identify the missing file and failing operation. If the error occurs during package registration or startup, verify that the required SlimCore Host and Framework packages are present and registered for the affected user. Check whether an endpoint cleanup script or security product removed the package or its files. An initial registration attempt can return this error before the plugin downloads and stages the package; if subsequent deployment and optimization succeed, no remediation is required for that initial failure. Please upgrade your plugin to 2026.29.1.4 or higher, which contains a fix for this issue. |
 | 5 | 43 | ERROR\_ACCESS\_DENIED | MsTeamsVdi.exe process failed at startup. BlockNonAdminUserInstall being enabled could cause this error. Or the endpoint could be busy registering multiple MSIX packages after a user logon and AppX service didn't finish registering SlimCoreVdi. |
+| 6 | 51 | ERROR\_INVALID\_HANDLE | Windows returned 'the handle is invalid' during SlimCore download, deployment or start-up operation. Review the Microsoft-Windows-Bits-Client\Operational Event Viewer log on the endpoint. For MSIX package deployment failures, check AppXDeployment-Server/Operational Event Viewer log on the endpoint. The underlying Windows OS error might appear as 0x80070006. HP and DELL devices that have a RAM Disk Manager where environmental variables TEMP/TMP are pointing to a RAM Disk (for example, Z:) can experience this error. For a workaround, check the same link as in Error 4390 below - 'Thin Clients with RAM Disks' |
 | 32 | 259 | ERROR\_SHARING\_VIOLATION | A file required for SlimCore deployment or startup is in use by another process, and the requested access conflicts with the existing file handle. Check the endpoint's logs and AppXDeployment-Server/Operational event log to identify the affected file and operation. Allow any ongoing package installation or update to complete, then retry optimization. If the issue persists, use Process Explorer to identify the process holding the file open. Coordinate any process restart with the user's status to avoid interrupting active calls. |
 | 104 | 835 | BG\_E\_BLOCKED\_BY\_BATTERY\_SAVER | Windows Background Intelligent Transfer Service (BITS) paused the SlimCore MSIX download because the endpoint is in Battery Saver mode. Connect the endpoint to AC power or turn off Battery Saver/Energy saver, then retry optimization if it doesn't recover automatically. Confirm HRESULT 0x80200068 in the endpoint's AppXDeployment-Server/Operational logs. This is a power-management restriction, not necessarily a network or CDN failure. |
 | 110 |  | ERROR\_OPEN\_FAILED | Windows Background Access policies blocking BITS ('BG\_E\_BLOCKED\_BY\_BACKGROUND\_ACCESS\_POLICY'), which prevents SlimCore downloads during optimization. For AVD/W365 users, the Windows App might not have [Background app permission->'Let this app run in background' set to 'Always'](https://support.microsoft.com/Windows/Experience/Performance-Optimization/manage-background-activity-for-apps-in-windows) on Windows Settings/Apps/Installed apps/Windows App. If this option is not visible, check if GlobalUserDisabled is set to 1 and change it to 0, under HKCU\Software\Microsoft\Windows\CurrentVersion\BackgroundAccessApplications |