BÄREN-Wiki · öffentliche Vorschau

Windows, Fehlercodes und Gerätewissen

Öffentlich sichtbar sind Fehlerquelle und Grundeinstufung. Vollständige Diagnosen, Hersteller- und Praxishinweise sowie Reparaturroutinen erhalten ausschließlich angemeldete Bären-EDV-Techniker.

Windows, Fehlercodes und Gerätewissen

Microsoft-Windows-Backup · Ereignis 738: Die Komponentenwiederherstellung "%1" wurde um %2 mit Fehlern abgeschlossen. Gemeldeter Fehler: "%3"(%4). Suchen Sie in den Ereignisdetails nach eine…

Microsoft-Windows-Backup · Ereignis 738: Die Komponentenwiederherstellung "%1" wurde um %2 mit Fehlern abgeschlossen. Gemeldeter Fehler: "%3"(%4). Suchen Sie in den Ereignisdetails nach eine…

Microsoft-Windows-Backup · Ereignis 756: Vom Sicherungsmoduldienst auf Blockebene wurde eine unbekannte Anforderung mit dem Code "%1" empfangen.

Microsoft-Windows-Backup · Ereignis 773: Die um %1 gestartete Wiederherstellung des Systemstatus wurde mit Fehlern abgeschlossen. Gemeldeter Fehler: "%2"(%3). Suchen Sie in den Ereignisdetai…

Microsoft-Windows-Backup · Ereignis 773: Die um %1 gestartete Wiederherstellung des Systemstatus wurde mit Fehlern abgeschlossen. Gemeldeter Fehler: "%2"(%3). Suchen Sie in den Ereignisdetai…

Microsoft-Windows-Backup · Ereignis 1027: Die Wiederherstellung von Hyper-V-Komponenten wurde mit Fehlern abgeschlossen. Mindestens eine Komponente wurde möglicherweise nicht ordnungsgemäß wi…

Microsoft-Windows-Backup · Ereignis 1041: Die Wiederherstellung von Hyper-V-Komponenten "%1" wurde um %2 mit Fehlern abgeschlossen. Fehler: "%3" ("%4"). Suchen Sie in den Ereignisdetails nach…

Microsoft-Windows-BitLocker-API · Ereignis 514: Failed to backup BitLocker Drive Encryption recovery information to Active Directory Domain Services. Errorcode: %2 Protector GUID: %1 Volume GUID: %3

Microsoft-Windows-BitLocker-API · Ereignis 518: The attempt to create a data recovery agent protector on the BitLocker volume failed. Errorcode: %1 Certificate thumbprint: %2 Volume GUID: %3

Microsoft-Windows-BitLocker-API · Ereignis 770: BitLocker decryption was started for volume %3.

Microsoft-Windows-BitLocker-API · Ereignis 771: BitLocker encryption was stopped for volume %3.

Microsoft-Windows-BitLocker-API · Ereignis 773: BitLocker was suspended for volume %3.

Microsoft-Windows-BitLocker-API · Ereignis 778: The BitLocker volume %3 was reverted to an unprotected state.

Microsoft-Windows-BitLocker-API · Ereignis 779: The BitLocker volume %3 was erased.

Microsoft-Windows-BitLocker-API · Ereignis 787: BitLocker free space wiping was stopped for volume %3.

Microsoft-Windows-BitLocker-API · Ereignis 793: BitLocker resealed boot settings to the TPM for volume %3.

Microsoft-Windows-BitLocker-API · Ereignis 797: Group Policy settings prevented BitLocker Drive Encryption from reverting to BitLocker software-based encryption. Volume %3 is not protected by BitLo…

Microsoft-Windows-BitLocker-API · Ereignis 798: BitLocker failed to initialize hardware encryption for volume %3. Drive is not provisioned for use with BitLocker hardware encryption: Hardware-based…

Microsoft-Windows-BitLocker-API · Ereignis 799: BitLocker failed to initialize hardware encryption for volume %3. Drive is not provisioned for use with BitLocker hardware encryption: The hardware-b…

Microsoft-Windows-BitLocker-API · Ereignis 800: BitLocker failed to initialize hardware encryption for volume %3. Drive is not provisioned for use with BitLocker hardware encryption: Hardware-based…

Microsoft-Windows-BitLocker-API · Ereignis 801: BitLocker failed to initialize hardware encryption for volume %3. Drive is not provisioned for use with BitLocker hardware encryption: Hardware-based…

Microsoft-Windows-BitLocker-API · Ereignis 802: BitLocker failed to initialize hardware encryption for volume %3. Drive is not provisioned for use with BitLocker hardware encryption: The key length…

Microsoft-Windows-BitLocker-API · Ereignis 803: BitLocker failed to initialize hardware encryption for volume %3. Drive is not provisioned for use with BitLocker hardware encryption: The key length…

Microsoft-Windows-BitLocker-API · Ereignis 806: BitLocker resealed boot settings to the TPM in the Windows Recovery Environment. Reseal time: %2

Microsoft-Windows-BitLocker-API · Ereignis 807: BitLocker free space wiping was canceled for volume %3.

Microsoft-Windows-BitLocker-API · Ereignis 808: BitLocker failed to initialize hardware encryption for volume %3. Drive is not provisioned for use with BitLocker hardware encryption: SID authority…

Microsoft-Windows-BitLocker-API · Ereignis 812: BitLocker cannot use Secure Boot for integrity because the UEFI variable '%1' could not be read. Error Message: %2

Microsoft-Windows-BitLocker-API · Ereignis 813: BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for variable '%1' is missing or invalid.

Microsoft-Windows-BitLocker-API · Ereignis 814: BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority is missing or invalid.

Microsoft-Windows-BitLocker-API · Ereignis 815: BitLocker cannot use Secure Boot for integrity because the expected TCG Log separator entry is missing or invalid.

Microsoft-Windows-BitLocker-API · Ereignis 816: BitLocker cannot use Secure Boot for integrity because the TCG Log for PCR [7] contains invalid entries.

Microsoft-Windows-BitLocker-API · Ereignis 818: BitLocker encountered a failure attempting to configure network unlock for volume %3.

Microsoft-Windows-BitLocker-API · Ereignis 830: The BitLocker Drive Encryption recovery information already exists in your Microsoft account.

Microsoft-Windows-BitLocker-API · Ereignis 832: TCG Log parsing failure. Error: %1.

Microsoft-Windows-BitLocker-API · Ereignis 833: BitLocker detected that custom Secure Boot policy is installed, and will seal to this configuration. Sealing to a custom policy may reduce the integr…

Microsoft-Windows-BitLocker-API · Ereignis 835: BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority has invalid structure. The event is exp…

Microsoft-Windows-BitLocker-API · Ereignis 836: BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority is invalid. The contents of the EFI_VAR…

Microsoft-Windows-BitLocker-API · Ereignis 837: BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority is invalid. The EFI_SIGNATURE_DATA stru…

Microsoft-Windows-BitLocker-API · Ereignis 838: BitLocker cannot use Secure Boot for integrity because the signature of the boot manager could not be validated as a Windows signature chained to a t…

Microsoft-Windows-BitLocker-API · Ereignis 839: BitLocker cannot use Secure Boot for integrity because the TCG Log entry for the OS Loader Authority is invalid. The signature contained in the EFI_S…

Microsoft-Windows-BitLocker-API · Ereignis 841: BitLocker was unable to update a key for volume %3 due to the following error: %4

Microsoft-Windows-BitLocker-API · Ereignis 843: BitLocker was suspended from within the Windows Recovery Environment. Suspend time: %2

Microsoft-Windows-BitLocker-API · Ereignis 867: Failed to delete BitLocker Drive Encryption recovery information for volume %1 from Entra ID. Protector GUID: %2. TraceId: %3

Microsoft-Windows-BitLocker-API · Ereignis 868: Failed while attempting to get BitLocker Drive Encryption recovery information from Entra ID. Error code: %1

Microsoft-Windows-BitLocker-API · Ereignis 877: Not all privileges requested are assigned to the caller.

Microsoft-Windows-BitLocker-API · Ereignis 880: BitLocker is unable to predict PCR7 value and will attempt to seal to current TPM PCR7 value as required by policy Policy PCR profile: %1.

Microsoft-Windows-BitLocker-API · Ereignis 882: BitLocker cannot use Secure Boot for integrity because hash of the boot manager for the TCG Log OS Loader Authority event could not be predicted.

Microsoft-Windows-BitLocker-API · Ereignis 883: BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for the OS Loader Authority is invalid. The EFI_SIGNATURE_DATA stru…