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-RRAS · Ereignis 17002: %1

Microsoft-Windows-RRAS · Ereignis 18000: %1

Microsoft-Windows-RRAS · Ereignis 18002: %1

Microsoft-Windows-RRAS · Ereignis 19000: %1

Microsoft-Windows-RRAS · Ereignis 19002: %1

Microsoft-Windows-RRAS · Ereignis 20000: %1

Microsoft-Windows-RRAS · Ereignis 20002: %1

Microsoft-Windows-Runtime-Media · Ereignis 212: Microsoft Windows Runtime Capture Engine Error Received

Microsoft-Windows-Runtime-Networking · Ereignis 2: %1 at %2 failed to start. The error code is %3: %4

Microsoft-Windows-Runtime-Networking · Ereignis 4: %1 at %2 failed with error code %3: %4.

Microsoft-Windows-Runtime-Networking · Ereignis 12: Failed connect request to '%1' at port %2. The last error is %3: %4

Microsoft-Windows-Runtime-Networking · Ereignis 14: Failed open request to '%1'. The last error is %2: %3

Microsoft-Windows-Runtime-Networking · Ereignis 21: Failed to send entity body to request handle %1. The last error is %2: %3

Microsoft-Windows-Runtime-Networking · Ereignis 26: Failed to receive HTTP response from request handle %1. The last error is %2: %3

Microsoft-Windows-Runtime-Networking · Ereignis 32: HTTP request to '%1' completed. The error code is %2: %3

Microsoft-Windows-Runtime-Networking · Ereignis 33: %1 at %2 failed to process HTTP response '%3'. The error code is %4: %5

Microsoft-Windows-Runtime-Networking · Ereignis 36: %1::%2 failed with HRESULT %3: %4

Microsoft-Windows-Runtime-Networking · Ereignis 37: Win32 API %1 failed with error code %2: %3.

Microsoft-Windows-Runtime-Networking · Ereignis 40: DatagramSocket %1 failed to deliver event and stopped receiving due to error %2: %3.

Microsoft-Windows-Runtime-Networking · Ereignis 43: DatagramSocket %1 failed to start receiving. The HRESULT was %2: %3.

Microsoft-Windows-Runtime-Networking · Ereignis 54: MessageWebSocket %1 failed to start receiving. The HRESULT was %2: %3.

Microsoft-Windows-Runtime-Networking · Ereignis 55: MessageWebSocket %1 failed to deliver event and stopped receiving due to error %2: %3.

Microsoft-Windows-Runtime-Networking · Ereignis 71: Failed to flush reads and wait for pending I/O to complete with context %1. Error was %2: %3.

Microsoft-Windows-Runtime-Networking · Ereignis 76: Async operation %1 at %2 failed server custom validation.

Microsoft-Windows-Runtime-Networking-BackgroundTransfer · Ereignis 4: Operation %1: Error %3 [%2]

Microsoft-Windows-Runtime-Networking-BackgroundTransfer · Ereignis 5: General error: %2 [%1]

Microsoft-Windows-Runtime-Networking-BackgroundTransfer · Ereignis 8: Operation %2: Task instance %1: Error %4 [%3]

Microsoft-Windows-Runtime-Networking-BackgroundTransfer · Ereignis 12: Request for unconstrained transfers for process %1 failed: %2

Microsoft-Windows-Runtime-Networking-BackgroundTransfer · Ereignis 17: Group '%1': Error %3 [%2]

Microsoft-Windows-Runtime-Networking-BackgroundTransfer · Ereignis 20: Notification %1: Error %3 [%2]

Microsoft-Windows-Runtime-Networking-BackgroundTransfer · Ereignis 24: Completion group %1: Error %3 [%2]

Microsoft-Windows-Runtime-Networking-BackgroundTransfer · Ereignis 27: Completion group %1: Completion group trigger %2 signal returned %3 and activation status %4

Microsoft-Windows-Runtime-Networking-BackgroundTransfer · Ereignis 30: Completion group %1: Trigger %2 delete failed with %3

Microsoft-Windows-Runtime-Web-Http · Ereignis 6: Failed to connect to '%1' at port %2. The last error is %3: %4

Microsoft-Windows-Runtime-Web-Http · Ereignis 8: Failed to open request to '%1'. The last error is %2: %3

Microsoft-Windows-Runtime-Web-Http · Ereignis 15: Failed to send entity body to request handle %1. The last error is %2: %3

Microsoft-Windows-Runtime-Web-Http · Ereignis 20: Failed to receive HTTP response from request handle %1. The last error is %2: %3

Microsoft-Windows-Runtime-Web-Http · Ereignis 26: HTTP request to '%1' completed. The error code is %2: %3

Microsoft-Windows-Runtime-Web-Http · Ereignis 27: Async operation %1 at %2 failed to process HTTP response '%3'. The error code is %4: %5

Microsoft-Windows-Runtime-Web-Http · Ereignis 29: Async operation %1 at %2 failed to start. The error code is %3: %4

Microsoft-Windows-Runtime-Web-Http · Ereignis 31: Async operation %1 at %2 failed with error code %3: %4

Microsoft-Windows-Runtime-Web-Http · Ereignis 46: Async operation %1 at %2 failed server custom validation.

Microsoft-Windows-Runtime-WebAPI · Ereignis 2: Async operation %1 at %2 failed to start. The error code is %3: %4

Microsoft-Windows-Runtime-WebAPI · Ereignis 4: Async operation %1 at %2 failed with error code %3: %4.

Microsoft-Windows-Runtime-WebAPI · Ereignis 9: Async operation %1 at %2 failed to remove handler from GIT. The error code is %3: %4

Microsoft-Windows-Runtime-WebAPI · Ereignis 10: Async operation %1 at %2 failed to register handler at GIT. The error code is %3: %4

Microsoft-Windows-Runtime-WebAPI · Ereignis 11: Async operation %1 at %2 failed to retrieve handler from GIT. The error code is %3: %4

Microsoft-Windows-Runtime-WebAPI · Ereignis 17: Failed to connect to '%1' at port %2. The last error is %3: %4