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-WiFiNetworkManager · Ereignis 2207: Profile Sharing Manager - Get Cred Sharing Opt In State failed, %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2209: Profile Sharing Manager - Set social network %2 in registry failed. State, %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2300: Profile Sharing Upload Manager - User is not opted in. Bailing on profile upload.

Microsoft-Windows-WiFiNetworkManager · Ereignis 2304: Profile Sharing Upload Manager - Upload failed, %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2306: Profile Sharing Upload Manager - Empty BSSID list. Skipping network.

Microsoft-Windows-WiFiNetworkManager · Ereignis 2307: Profile Sharing Upload Manager - Building Json payload completed with result %1, shared = %2

Microsoft-Windows-WiFiNetworkManager · Ereignis 2312: Profile Sharing Upload Manager - Failed to disable exchange state by location, %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2313: Profile Sharing Upload Manager - Failed to subscribe to location notifications.

Microsoft-Windows-WiFiNetworkManager · Ereignis 2314: Profile Sharing Upload Manager - Failed to set opt in status on location WNF change, %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2402: FeatureManager - Failed to subscribe to location notifications with result %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2403: FeatureManager - Failed to start social network sync schedule with result %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2404: FeatureManager - Failed to start sqm schedule with result %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2405: FeatureManager - Failed to subscribe to policy changed notifications with result %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2406: FeatureManager - EnableFeatureInternal failed with result %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2407: FeatureManager - DisableFeatureInternal failed with result %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2408: FeatureManager - Notifying NetworkManager of feature state change #%1 failed with result %2

Microsoft-Windows-WiFiNetworkManager · Ereignis 2409: FeatureManager - SetFeatureRegValue failed with result %1

Microsoft-Windows-WiFiNetworkManager · Ereignis 2410: FeatureManager - GetFeatureRegValue failed with result %1

Microsoft-Windows-WinHttp · Ereignis 804: Search for WPAD configuration file using DHCP failed: Interface=%2, ConfigurationURL=%4, Error=%5

Microsoft-Windows-WinHttp · Ereignis 804: Search for WPAD configuration file using DHCP failed: Interface=%2, ConfigurationURL=%4, Error=%5

Microsoft-Windows-WinHttp · Ereignis 807: Search for WPAD configuration file using DNS failed: DetectFlags=%1, Error=%2

Microsoft-Windows-WinHttp · Ereignis 808: Search for WPAD configruation file failed: Error=%1

Microsoft-Windows-WinHttp · Ereignis 811: Downloading the configuration file from the configuration URL failed: ConfigurationURL=%2, Error=%3

Microsoft-Windows-WinHttp · Ereignis 811: Downloading the configuration file from the configuration URL failed: ConfigurationURL=%2, Error=%3

Microsoft-Windows-WinHttp · Ereignis 812: The downloaded configuration file could not be used: ConfigurationURL=%2, MIMEType=%4, Error=%5

Microsoft-Windows-WinHttp · Ereignis 812: The downloaded configuration file could not be used: ConfigurationURL=%2, MIMEType=%4, Error=%5

Microsoft-Windows-WinHttp · Ereignis 815: Error locating proxy information for the URL: URL=%2, Error=%3

Microsoft-Windows-WinHttp · Ereignis 815: Error locating proxy information for the URL: URL=%2, Error=%3

Microsoft-Windows-WinINet · Ereignis 106: Failed to create handle: ParentHandle=%1, Error=%2

Microsoft-Windows-WinINet · Ereignis 107: Handle %1 failed to close: Error=%2

Microsoft-Windows-WinINet · Ereignis 202: HTTP request send failed: Handle=%1, Error=%2

Microsoft-Windows-WinINet · Ereignis 302: TCP connection to %2 for connection handle %3 failed: Error=%4

Microsoft-Windows-WinINet · Ereignis 306: DNS query for %2 hostname failed: Handle=%3 Error=%4

Microsoft-Windows-WinINet · Ereignis 703: SSL negotiation failed: RequestHandle=%1, Error=%2

Microsoft-Windows-WinINet · Ereignis 713: SSL renegotiation failed: RequestHandle=%1, Error=%2

Microsoft-Windows-WinINet · Ereignis 804: Search for WPAD configuration file using DHCP failed: Interface=%2, ConfigurationURL=%4, Error=%5

Microsoft-Windows-WinINet · Ereignis 804: Search for WPAD configuration file using DHCP failed: Interface=%2, ConfigurationURL=%4, Error=%5

Microsoft-Windows-WinINet · Ereignis 807: Search for WPAD configuration file using DNS failed: DetectFlags=%1, Error=%2

Microsoft-Windows-WinINet · Ereignis 808: Search for WPAD configruation file failed: Error=%1

Microsoft-Windows-WinINet · Ereignis 811: Downloading the configuration file from the configuration URL failed: ConfigurationURL=%2, Error=%3

Microsoft-Windows-WinINet · Ereignis 811: Downloading the configuration file from the configuration URL failed: ConfigurationURL=%2, Error=%3

Microsoft-Windows-WinINet · Ereignis 812: The downloaded configuration file could not be used: ConfigurationURL=%2, MIMEType=%4, Error=%5

Microsoft-Windows-WinINet · Ereignis 812: The downloaded configuration file could not be used: ConfigurationURL=%2, MIMEType=%4, Error=%5

Microsoft-Windows-WinINet · Ereignis 815: Error locating proxy information for the URL: URL=%2, Error=%3

Microsoft-Windows-WinINet · Ereignis 815: Error locating proxy information for the URL: URL=%2, Error=%3

Microsoft-Windows-WinRM · Ereignis 135: Die Anforderung wird aufgrund von ERROR_WINHTTP_CANNOT_CONNECT erneut gesendet. Dabei wird der nächste Proxy verwendet.

Microsoft-Windows-WinRM · Ereignis 136: Die Anforderung wird aufgrund von ERROR_WINHTTP_NAME_NOT_RESOLVED erneut gesendet. Dabei wird der nächste Proxy verwendet.

Microsoft-Windows-WinRM · Ereignis 137: Von der Vermittlungsschicht wurde "ERROR_WINHTTP_NAME_NOT_RESOLVED" zurückgegeben - Der Servername kann nicht aufgelöst werden. Der Vorgang wird abge…