| Previous | Next |
| ERROR_INSTALL_OPTIONAL_PACKAGE_REQUIRES_MAIN_PACKAGE_FULLTRUST_CAPABILITY | ERROR_PROVISION_OPTIONAL_PACKAGE_REQUIRES_MAIN_PACKAGE_PROVISIONED |
ERROR_DEPLOYMENT_BLOCKED_BY_USER_LOG_OFF
Per-user deployment lost the user session it was updating
ERROR_DEPLOYMENT_BLOCKED_BY_USER_LOG_OFF occurs when a package operation that requires an active target-user context overlaps logoff. Registration, application-data migration, and user-specific state cannot always be completed after that session is torn down.
Record the target user SID and deployment activity, then retry after the user signs in and the profile is fully available. For device management, schedule per-user operations within a reliable user session or use provisioning when the goal is installation for future users. Do not redirect the operation to another logged-on account because package registration is user-specific.
What to inspect
- Confirm which user SID the operation targeted.
- Correlate failure time with logoff and profile-service events.
- Choose provisioning for device-wide future-user deployment.
References
- Microsoft: per-user versus all-user package management
- Microsoft: provisioning packages for future users
- Microsoft: deployment logs and user context
Looking for a different code? Search another status or error code.