---
title: Troubleshooting
slug: ps/help/en_us/ics/25x/vadep/troubleshooting
createdAt: 2026-09-21T05:29:32.780Z
---

- [Host does not support Native Key Provider](docId:6Lp2-pRVtXO2Q2QMiNO-q)
- [Secure boot is disabled](docId:6Lp2-pRVtXO2Q2QMiNO-q)
- [TPM/vTPM is in lockout mode](docId:6Lp2-pRVtXO2Q2QMiNO-q)
- [TPM is not attached](docId:6Lp2-pRVtXO2Q2QMiNO-q)
- [Virtual ICS does not boot due to signature failure](docId:6Lp2-pRVtXO2Q2QMiNO-q)
- [Booting stops with error "System Integrity verification failed"](docId:6Lp2-pRVtXO2Q2QMiNO-q)
- [Booting stops with error "Rootfs manifest validation related files do not exist”](docId:6Lp2-pRVtXO2Q2QMiNO-q)
- [Booting stops with error "Root file system signature verification failed"](docId:6Lp2-pRVtXO2Q2QMiNO-q)
- [Booting stops with error "No file entries found in the manifest"](docId:6Lp2-pRVtXO2Q2QMiNO-q)
- [Upgrade aborts with error “ADM23397: This appliance cannot be upgraded to 22.8R2”](docId:6Lp2-pRVtXO2Q2QMiNO-q)

### Host does not support Native Key Provider

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/eSFUlJIZW6yt_MO62MPOt_trblshoot8.png" position="flex-start" size="80" width="1021" height="72" initialPath="img/trblshoot_8.png" githubPath="img/trblshoot_8.png" darkWidth="1021" darkHeight="72" showCaption="false"}

**Cause**: Key Management is not enabled.

**Solution**: Enable Key Management in the Vcenter server. For details, see [Configuring and Managing vSphere Native Key Provider](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-security/configuring-and-managing-vsphere-native-key-provider.html).

### Secure boot is disabled

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/XEUUdbcsrlG505yypdWxG_trblshoot5.png" position="flex-start" size="80" width="819" height="49" initialPath="img/trblshoot_5.png" githubPath="img/trblshoot_5.png" darkWidth="819" darkHeight="49" showCaption="false"}

**Solution**: Secure boot is mandatory for virtual ICS. Enable secure boot for better security.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/lkiwSqpNcl8Ju6Bi_pDso_trblshoot6365x373.png" position="flex-start" size="37" width="365" height="373" initialPath="img/trblshoot_6_365x373.png" githubPath="img/trblshoot_6_365x373.png" darkWidth="365" darkHeight="373" showCaption="false"}

### TPM/vTPM is in lockout mode

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/cSs6hQ1YoBfzx7ZHMGAjM_trblshoot7.png" position="flex-start" size="75" width="751" height="48" initialPath="img/trblshoot_7.png" githubPath="img/trblshoot_7.png" darkWidth="751" darkHeight="48" showCaption="false"}

**Cause**: It could be due to too many consecutive ungraceful shutdowns.

**Solution**: Once TPM is in lockout state, it will remain inaccessible until the recovery time has elapsed. After 1000 secs, system boots and comes up.

### TPM is not attached

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/RZRNievixR73zu8qISDTb_trblshoot3.png" position="flex-start" size="80" width="990" height="81" initialPath="img/trblshoot_3.png" githubPath="img/trblshoot_3.png" darkWidth="990" darkHeight="81" showCaption="false"}

**Solution**: Attach TPM for better security.

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/S_P9JMH0S8FBAtrcX7rjz_trblshoot4781x225.png" position="flex-start" size="78" width="781" height="225" initialPath="img/trblshoot_4_781x225.png" githubPath="img/trblshoot_4_781x225.png" darkWidth="781" darkHeight="225" showCaption="false"}

### Virtual ICS does not boot due to signature failure

:inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/TX9fBNEwrtUBxz37buMRD_trblshoot1527x136.png" alt caption size="53" width="527" height="136"} :inlineImage[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/2rjLtzoTXOyQm8VmKNGWr_trblshoot2.png" alt caption size="52" width="522" height="133"}

**Cause**: The primary reason for virtual ICS not booting could be that ExtraConfigs are disabled.

**Solution**: Enable ExtraConfigs in your VMware settings. For details, see [Specifying Advanced Virtual Machine Settings with ExtraConfig Elements](https://techdocs.broadcom.com/us/en/vmware-cis/cloud-director/vmware-cloud-director/10-6/-vcloud-api-programming-guide-for-service-providers-10-6/deploying-and-operating-vapps-api/using-metadata-to-control-virtual-machine-placement-api.html).

### Booting stops with error "System Integrity verification failed"

::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/v5GbLKvLGbDwe6eQ3RCIW_trblshoot9.png" position="flex-start" size="80" width="817" height="109" initialPath="img/trblshoot_9.png" githubPath="img/trblshoot_9.png" darkWidth="817" darkHeight="109" showCaption="false"}

**Cause**: If any new files get created or existing files get modified as part of ICS system, these will be detected and prevent booting.

**Solution**: Securing InitramFS and RootFS feature prevents unauthorized files creation in ICS system. Select “d” to dump diagnostics to see which files are created/modified and Contact Ivanti Support for error. Perform Rollback - option “r” if available or perform Factory Reset – option “f” for clean installation from recovery options provided. All configs will be lost after performing Factory Reset.

### Booting stops with error "Rootfs manifest validation related files do not exist”

**Cause**: If Securing InitramFS and RootFS feature dependent files are missing, the system is interrupted due to failure in validation of required files.

**Solution**: Contact Ivanti Support for error. Perform Rollback - option “r” if available or perform Factory Reset – option “f” for clean installation from recovery options provided. All configs will be lost after performing Factory Reset.

### Booting stops with error "Root file system signature verification failed"

**Cause**: If Securing InitramFS and RootFS feature dependent file contents are modified, the system is interrupted due to failure in signature verification of required files.

**Solution**: Contact Ivanti Support for error. Perform Rollback - option “r” if available or perform Factory Reset – option “f” for clean installation from recovery options provided. All configs will be lost after performing Factory Reset.

### Booting stops with error "No file entries found in the manifest"

**Cause**: If Securing InitramFS and RootFS feature dependent files don’t have any content, the system is interrupted due to failure in validation of required files.

**Solution**: Contact Ivanti Support for error. Perform Rollback - option “r” if available or perform Factory Reset – option “f” for clean installation from recovery options provided. All configs will be lost after performing Factory Reset.

### Upgrade aborts with error “ADM23397: This appliance cannot be upgraded to 22.8R2”

**Cause**: This error indicates that the upgrade cannot proceed due to insufficient disk space in the boot partition and Factory Reset version is very old.

**Solution**: Contact Ivanti Support for error.