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-Privacy-Auditing · Ereignis 1040: Der MCP-Wert für ClientID: %6 ServerID: %7 Vorgang: %8 Ressource: %9 Benutzer: %5 konnte nicht in %4 geändert werden. Fehler: %10

Microsoft-Windows-Privacy-Auditing · Ereignis 1042: MCP-Wert für ClientID: %3 ServerID: %4 Vorgang: %5 Ressource: %6 Benutzer: %2 konnte nicht wie %1 erstellt werden. Fehler: %7

Microsoft-Windows-Privacy-Auditing-Activity-History-Privacy-Settings · Ereignis 1: Der Genehmigungswert für die Cloud-Synchronisierung wurde geändert, Einstellung %12, fehlgeschlagen

Microsoft-Windows-Privacy-Auditing-Activity-History-Privacy-Settings · Ereignis 3: Der Genehmigungswert für die Verlaufssammlung wurde geändert, Einstellung %12, fehlgeschlagen

Microsoft-Windows-Privacy-Auditing-Activity-History-Privacy-Settings · Ereignis 5: Aktivitätsverlauf löschen, Einstellung %12, fehlgeschlagen

Microsoft-Windows-Privacy-Auditing-Activity-History-Privacy-Settings · Ereignis 7: Der Wert für den Kontofilter wurde geändert, Einstellung %12, fehlgeschlagen

Microsoft-Windows-Privacy-Auditing-CPSS · Ereignis 1001: %2 failed to change the System Setting {(%9) (%10) (%11)} owned by %8. Justification: %12.

Microsoft-Windows-Privacy-Auditing-CPSS · Ereignis 1003: %2 failed to change the User Setting {(%9) (%10) (%11)} for user %6 owned by %8. Justification: %12.

Microsoft-Windows-Privacy-Auditing-CPSS · Ereignis 1005: %2 failed to create the System Setting {(%8) (%9) (%10)} owned by %7. Source: %11

Microsoft-Windows-Privacy-Auditing-CPSS · Ereignis 1007: %2 failed to create the User Setting {(%8) (%9) (%10)} owned by %7 for user %5. Source: %11

Microsoft-Windows-Privacy-Auditing-CPSS · Ereignis 1009: %2 failed to remove the User Setting {(%7) (%8) (%9)} owned by %6 for user %5. Justification: %11

Microsoft-Windows-Privacy-Auditing-CPSS · Ereignis 1011: %2 failed to remove the System Setting {(%7) (%8) (%9)} owned by %6. Justification: %11

Microsoft-Windows-Program-Compatibility-Assistant · Ereignis 202: Der Dienst "Programmkompatibilitäts-Assistent" konnte nicht initialisiert werden.

Microsoft-Windows-Program-Compatibility-Assistant · Ereignis 203: Der Dienst "Programmkompatibilitäts-Assistent" konnte nicht gestartet werden.

Microsoft-Windows-Program-Compatibility-Assistant · Ereignis 204: Der Dienst "Programmkompatibilitäts-Assistent" konnte nicht beendet werden.

Microsoft-Windows-Program-Compatibility-Assistant · Ereignis 205: Der Dienst "Programmkompatibilitäts-Assistent" konnte Phase 2 nicht ausführen.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 12: ProvXML category '%1' failed with '%2' at CSP node '%3'. %4

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 22: Package '%1' failed with '%2'.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 42: InitiateSystemShutdownEx failed. HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 45: InitiateSystemShutdownEx failed. HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 62: AddPackage failed. HRESULT = %1

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 65: RemovePackage failed. HRESULT = %1, package id = %2, at stage = %3

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 67: RemovePackageMetadata failed. HRESULT = %1, package id = %2, at stage = %3

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 69: RemoveResourceManagerPackageMetadataForCsp failed. HRESULT = %1, package id = %2

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 72: ApplyKnownPackages failed. turn = %1, HRESULT = %2

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 73: PublishDeviceProvisioningLogs failed. HRESULT = %1

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 75: CleanupOOBEProvisioningLogs failed. HRESULT = %1

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 81: GetLastProvisioningResultsAsync failed. HRESULT = %1

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 83: GetLastProvisioningCommandResultsAsync. HRESULT = %1

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 92: RegisterForCspAlerts Failed. HResult = %1, EnrollmentId = %2.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 94: UpdatePendingResultInternal Failed. HResult = %1, PackageId = %2.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 102: AutoPilotGetPolicyDwordByName error: policy name = %2; HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 104: AutoPilotGetPolicyStringByName error: policy name = %2; HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 106: AutoPilotDisable error: HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 108: AutoPilotIsDisabled error: HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 110: AutoPilotGetOobeSettingsOverride error: OOBE setting = %2; HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 112: AutoPilotRetrieveSettings error: HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 113: AutoPilot reported the DLL was unloaded while there were %1 outstanding calls.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 115: Autopilot discovery failed to find a valid MDM. Confirm that the AAD tenant is properly provisioned and licensed for exactly one MDM. HRESULT = %1

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 154: AutoPilotManager failed to start MSA service. HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 155: AutoPilotManager failed to start TPM task. HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 156: AutoPilotManager reported that MSA TPM is not configured for hardware TPM attestation even though the profile indicates it is required. AutoPilot can…

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 171: AutoPilotManager failed to set TPM identity confirmed. HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 172: AutoPilotManager failed to set AutoPilot profile as available. HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 173: AutoPilotManager failed to register for network availability. HRESULT = %1.

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 174: AutoPilotManager failed to register for device identity availability. HRESULT = %1

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 175: AutoPilotManager failed to register for device identity task update. HRESULT = %1

Microsoft-Windows-Provisioning-Diagnostics-Provider · Ereignis 180: AutoPilotManager failed during device enrollment phase %1. HRESULT = %2