| Previous | Next |
| WEP_E_NOT_PROVISIONED_ON_ALL_VOLUMES | WEP_E_HARDWARE_NOT_COMPLIANT |
WEP_E_FIXED_DATA_NOT_SUPPORTED
WEP_E_FIXED_DATA_NOT_SUPPORTED — 0x88010002
This code places the first failure in third-party provider support for fixed data volumes. Operationally, the installed encryption provider cannot protect one or more fixed data volumes that the compliance policy requires.
Where the failure sits
Windows Encryption Provider integration has separate gates for provider licensing, hardware readiness, volume support, provisioning, active protection, device-lock configuration, and EAS compliance. WEPHOSTSVC events should therefore be read alongside the third-party provider’s own inventory and logs, not as a replacement for them.
This is not merely an unprovisioned supported volume; the provider reports that the volume class itself is unsupported.
Facts to collect first
- Volume type, filesystem, partition style, bus, size, and provider capability report
- Which volumes are OS versus fixed data and their current protection state
- Provider version/license and documented support matrix
- EAS RequireEncryption evaluation and WEPHOSTSVC events
Change one variable at a time
- Test a supported filesystem/volume type with the same provider.
- Compare OS-volume support with fixed-data-volume support.
- Query provider capability before attempting provisioning.
Verification after correction
The corrective action should be narrow: Upgrade/change the provider, change the storage layout to a supported design, or revise policy through the authorized authority.
Close the incident only when every in-scope fixed data volume is supported and encrypted, while an unsupported-volume control is reported before deployment.
Technical references
Use these sources for the formal contract, then combine them with evidence from the returning application or service for this condition:
Looking for a different code? Search another status or error code.