ComputerBase Menü
Aktuelles

WSUS 2016 Anbindung Windows 10 Clients

F

florian_1994

Cadet 2nd Year
Registriert
Juni 2017
Beiträge
24
Guten Tag zusammen,

wir haben einen neuen WSUS Server 2016 Standard (Version: 10.0.14393.0) in unserer Umgebung als virtuelle Maschine bereitgestellt.

Dieser wurde komplett mit dem etwas älteren Windows Server 2008 R2 synchronisiert.

Es wurde ein Zertifikat eingespielt, sodass die Verbindung zwischen Server und Clients über https (POrt 8531) stattfindet.

Die Gruppenrichtlinie wurde bereits angepasst.

Windows 10 LTSB 2016 Clients (Version 1607) erhalten beim Suchen nach Updates folgenden Fehlercode:
Beim Installieren von Updates sind Probleme aufgetreten. Wir versuchen es allerdings später noch einmal. Falls dieser Fehler weiterhin auftritt und Sie Informationen im Web suchen oder sich an den Support wenden möchten, kann dieser Fehlercode hilfreich sein: (0x80245006).
Zum Vergrößern anklicken....

Windows 10 LTSB 2015 Clients (Version 1507) erhalten beim Suchen nach Updates folgenden Fehlercode:
0x800705b4
Zum Vergrößern anklicken....

Ich habe folgenden Lösungsvorschlag schon an den Clients probiert:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
Zum Vergrößern anklicken....

Leider hat dies die beiden oben genannten Fehlermeldungen nicht beeinflusst.

Aus dem Windows Update Log wird folgendes ersichtlich:

2017.07.11 10:14:59.6430846 1156 11876 ComApi * START * Init Search ClientId = UpdateOrchestrator
2017.07.11 10:14:59.6430874 1156 11876 ComApi * START * Search ClientId = UpdateOrchestrator
2017.07.11 10:14:59.6479182 1156 11876 Agent * START * Queueing Finding updates [CallerId = UpdateOrchestrator Id = 3]
2017.07.11 10:14:59.6479213 1156 11876 Agent Removing service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 from sequential scan list
2017.07.11 10:14:59.6479239 1156 11876 Agent Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is not in sequential scan list
2017.07.11 10:14:59.6479265 1156 11876 Agent Added service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 to sequential scan list
2017.07.11 10:14:59.6479367 1156 11876 ComApi Search ClientId = UpdateOrchestrator
2017.07.11 10:14:59.6480140 1156 3644 Agent Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is in sequential scan list
2017.07.11 10:14:59.6490703 1156 7368 Agent * END * Queueing Finding updates [CallerId = UpdateOrchestrator Id = 3]
2017.07.11 10:14:59.6499926 1156 7368 Agent * START * Finding updates CallerId = UpdateOrchestrator Id = 3
2017.07.11 10:14:59.6499932 1156 7368 Agent Online = Yes; AllowCachedResults = No; Ignore download priority = No
2017.07.11 10:14:59.6499937 1156 7368 Agent Criteria = IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1""
2017.07.11 10:14:59.6499963 1156 7368 Agent ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2017.07.11 10:14:59.6499966 1156 7368 Agent Search Scope = {Machine}
2017.07.11 10:14:59.6499983 1156 7368 Agent Caller SID for Applicability: S-1-5-21-894068800-755652548-4051164869-6687
2017.07.11 10:14:59.6499986 1156 7368 Agent ProcessDriverDeferrals is set
2017.07.11 10:14:59.6499989 1156 7368 Agent RegisterService is set
2017.07.11 10:14:59.6504031 1156 7368 Agent Blocking Windows content for WUfB
2017.07.11 10:14:59.6506760 1156 7368 Misc Got WSUS Client/Server URL: https://wsus.kleiner.de:8531/ClientWebService/client.asmx""
2017.07.11 10:14:59.9733691 1156 7368 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://wsus.kleiner.de:8531/ClientWebService/client.asmx
2017.07.11 10:14:59.9735652 1156 7368 ProtocolTalker OK to reuse existing configuration
2017.07.11 10:14:59.9735678 1156 7368 ProtocolTalker Existing cookie is valid, just use it
2017.07.11 10:14:59.9735687 1156 7368 ProtocolTalker PTInfo: Server requested registration
2017.07.11 10:14:59.9885349 1156 7368 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.11 10:15:00.3875928 1156 7368 WebServices Auto proxy settings for this web service call.
2017.07.11 10:15:00.4430256 1156 7368 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.11 10:15:00.4840773 1156 7368 ProtocolTalker PTInfo: syncing with server using normal query
2017.07.11 10:15:00.4955224 1156 7368 ProtocolTalker SyncUpdates round trips: 2
2017.07.11 10:15:00.5130891 1156 7368 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.11 10:15:00.5270226 1156 7368 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.11 10:15:01.0884386 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:01.2647838 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:01.4237253 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:02.0905786 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:03.3163322 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:03.4019731 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:04.3787332 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:04.4642934 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:04.7815656 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:05.2725130 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:05.4305139 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:05.5612991 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:06.5356301 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:06.9558013 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:07.9309886 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:08.1832447 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:08.2451380 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:08.4524505 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:08.5385510 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:09.6122772 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:09.6596393 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:10.6382700 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:10.6687318 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:11.6488801 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:11.7590675 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:11.8428114 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:11.8523980 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:12.0025554 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:12.1623675 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:13.1518523 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:14.3109366 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:14.4443824 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:15.4291106 1156 7368 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.11 10:15:15.5923950 1156 7368 Agent Found 0 updates and 87 categories in search; evaluated appl. rules of 5000 out of 9283 deployed entities
2017.07.11 10:15:15.5983627 1156 7368 Agent * END * Finding updates CallerId = UpdateOrchestrator Id = 3
2017.07.11 10:15:15.6045968 1156 1916 ComApi *RESUMED* Search ClientId = UpdateOrchestrator
2017.07.11 10:15:15.6048503 1156 1916 ComApi Updates found = 0
2017.07.11 10:15:15.6048506 1156 1916 ComApi * END * Search ClientId = UpdateOrchestrator
2017.07.11 10:15:15.6051368 1156 11876 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
2017.07.11 10:15:15.6497711 1156 11876 ComApi * START * Init Search ClientId = UpdateOrchestrator
2017.07.11 10:15:15.6497734 1156 11876 ComApi * START * Search ClientId = UpdateOrchestrator
2017.07.11 10:15:15.6524653 1156 11876 Agent * START * Queueing Finding updates [CallerId = UpdateOrchestrator Id = 4]
2017.07.11 10:15:15.6524681 1156 11876 Agent Removing service 9482F4B4-E343-43B6-B170-9A65BC822C77 from sequential scan list
2017.07.11 10:15:15.6524704 1156 11876 Agent Service 9482F4B4-E343-43B6-B170-9A65BC822C77 is not in sequential scan list
2017.07.11 10:15:15.6524730 1156 11876 Agent Added service 9482F4B4-E343-43B6-B170-9A65BC822C77 to sequential scan list
2017.07.11 10:15:15.6524818 1156 11876 ComApi Search ClientId = UpdateOrchestrator
2017.07.11 10:15:15.6525497 1156 3644 Agent Service 9482F4B4-E343-43B6-B170-9A65BC822C77 is in sequential scan list
2017.07.11 10:15:15.6536915 1156 11760 Agent * END * Queueing Finding updates [CallerId = UpdateOrchestrator Id = 4]
2017.07.11 10:15:15.6545480 1156 11760 Agent * START * Finding updates CallerId = UpdateOrchestrator Id = 4
2017.07.11 10:15:15.6545485 1156 11760 Agent Online = Yes; AllowCachedResults = No; Ignore download priority = No
2017.07.11 10:15:15.6545488 1156 11760 Agent Criteria = IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1""
2017.07.11 10:15:15.6545508 1156 11760 Agent ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2017.07.11 10:15:15.6545511 1156 11760 Agent Search Scope = {Machine}
2017.07.11 10:15:15.6545528 1156 11760 Agent Caller SID for Applicability: S-1-5-21-894068800-755652548-4051164869-6687
2017.07.11 10:15:15.6545531 1156 11760 Agent ProcessDriverDeferrals is set
2017.07.11 10:15:15.6545534 1156 11760 Agent RegisterService is set
1601.01.01 01:00:00.0000000 1156 11760 Unknown( 38): GUID=adf11b8c-baac-3d44-1059-4f8c843b025a (No Format Information found).
2017.07.11 10:15:15.6552137 1156 11760 SLS Retrieving SLS response from server...
2017.07.11 10:15:15.6555401 1156 11760 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/10.0.14393.0/0?CH=171&L=de-DE&P=&PT=0x7d&WUA=10.0.14393.1358
2017.07.11 10:15:16.7280215 1156 11760 WebServices Certificate failed SSL intermediate CA check.
2017.07.11 10:15:16.7320113 1156 11760 SLS *** Potential Failover Scenario ***
2017.07.11 10:15:16.7373344 1156 11760 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\sls.cab with dwProvFlags 0x00000080:
2017.07.11 10:15:16.7494841 1156 11760 Misc Microsoft signed: NA
2017.07.11 10:15:16.7496782 1156 11760 Misc Infrastructure signed: Yes
2017.07.11 10:15:16.7580158 1156 11760 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\TMP9BD9.tmp with dwProvFlags 0x00000080:
2017.07.11 10:15:16.7684674 1156 11760 Misc Microsoft signed: NA
2017.07.11 10:15:16.7686521 1156 11760 Misc Infrastructure signed: Yes
2017.07.11 10:15:16.7709472 1156 11760 SLS SLS Response was invalid for service 9482F4B4-E343-43B6-B170-9A65BC822C77 - HTTPStatusCode[200]
2017.07.11 10:15:16.7709520 1156 11760 Misc EP: error: 0x80245006 : - failed to get SLS data
2017.07.11 10:15:16.7709555 1156 11760 Misc Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL, error = 0x80245006
2017.07.11 10:15:16.7709580 1156 11760 Agent Failed to obtain the authorization cab URL for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, hr=0
2017.07.11 10:15:16.7709586 1156 11760 Agent Caller Service Recovery failed to opt in to service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, hr=0X80245006
1601.01.01 01:00:00.0000000 1156 11760 Unknown( 38): GUID=adf11b8c-baac-3d44-1059-4f8c843b025a (No Format Information found).
2017.07.11 10:15:16.7717979 1156 11760 SLS Retrieving SLS response from server...
2017.07.11 10:15:16.7721318 1156 11760 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/10.0.14393.0/0?CH=171&L=de-DE&P=&PT=0x7d&WUA=10.0.14393.1358
2017.07.11 10:15:17.8265839 1156 11760 WebServices Certificate failed SSL intermediate CA check.
2017.07.11 10:15:17.8293229 1156 11760 SLS *** Potential Failover Scenario ***
2017.07.11 10:15:17.8328077 1156 11760 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\sls.cab with dwProvFlags 0x00000080:
2017.07.11 10:15:17.8404633 1156 11760 Misc Microsoft signed: NA
2017.07.11 10:15:17.8405993 1156 11760 Misc Infrastructure signed: Yes
2017.07.11 10:15:17.8460156 1156 11760 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\TMPA020.tmp with dwProvFlags 0x00000080:
2017.07.11 10:15:17.8512715 1156 11760 Misc Microsoft signed: NA
2017.07.11 10:15:17.8513385 1156 11760 Misc Infrastructure signed: Yes
2017.07.11 10:15:17.8518540 1156 11760 SLS SLS Response was invalid for service 9482F4B4-E343-43B6-B170-9A65BC822C77 - HTTPStatusCode[200]
2017.07.11 10:15:17.8518568 1156 11760 Misc EP: error: 0x80245006 : - failed to get SLS data
2017.07.11 10:15:17.8518600 1156 11760 Misc Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL, error = 0x80245006
2017.07.11 10:15:17.8518614 1156 11760 ProtocolTalker PTError: 0x80245006
2017.07.11 10:15:17.8518657 1156 11760 ProtocolTalker Initialization failed for Protocol Talker Context 0x80245006
2017.07.11 10:15:17.8641331 1156 11760 Agent Exit code = 0x80245006
2017.07.11 10:15:17.8641336 1156 11760 Agent * END * Finding updates CallerId = UpdateOrchestrator Id = 4
2017.07.11 10:15:17.8795435 1156 1916 ComApi *RESUMED* Search ClientId = UpdateOrchestrator
2017.07.11 10:15:17.8798388 1156 1916 ComApi Updates found = 0
2017.07.11 10:15:17.8798391 1156 1916 ComApi Exit code = 0x00000000, Result code = 0x80245006
2017.07.11 10:15:17.8798394 1156 1916 ComApi * END * Search ClientId = UpdateOrchestrator
2017.07.11 10:15:17.8800826 1156 11876 ComApi ISusInternal:: DisconnectCall failed, hr=8024000C
Zum Vergrößern anklicken....
 
Zuletzt bearbeitet:
Zuletzt bearbeitet:
Aktuell folgende Fehlermeldung:

2017.07.25 09:57:34.8197501 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:35.5479573 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:36.0876255 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:36.5961584 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:36.7299944 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:37.4545087 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:38.4207798 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:39.0401568 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:39.6477225 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:40.6719267 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:41.4155824 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:41.6590030 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:41.8373054 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:41.9041018 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:41.9169499 1072 15168 ProtocolTalker PTInfo: syncing with server using normal query
2017.07.25 09:57:41.9416556 1072 15168 ProtocolTalker SyncUpdates round trips: 83
2017.07.25 09:57:41.9460767 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:41.9543162 1072 15168 Agent Update filtered by policy: 6964AAB4-C5B5-43BD-A17D-FFB4346A8E1D.100
2017.07.25 09:57:42.0847719 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:42.4802776 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:42.5331249 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:42.9332287 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:43.0926943 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:43.4879628 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:43.5066986 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:43.9222693 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:43.9767333 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:44.0195909 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:44.0259380 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:44.2662681 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:44.4566190 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
2017.07.25 09:57:44.8683412 1072 15168 EEHandler DeterminePatchSequence succeeded but status indicated an error 0x00000000
Zum Vergrößern anklicken....
 
Du musst dich einloggen oder registrieren, um hier zu antworten.

Ähnliche Themen

nospherato
Windows 10 Pro (1709) Windows Update nicht mehr möglich
Antworten
9
Aufrufe
4.866
nospherato
nospherato
T
Windows Update spinnt mal wieder
Antworten
14
Aufrufe
2.211
Volume Z
V
Zurück
Oben

Willkommen auf ComputerBase!

Mit Werbung weiterlesen

Besuche ComputerBase wie gewohnt mit Werbung und Tracking. Die Zustimmung ist jederzeit widerrufbar.

Details im Privacy Center und in der Liste unserer Partner. Ein Widerruf ist möglich in der Datenschutzerklärung.

… oder ComputerBase Pro bestellen

Nutze ComputerBase ohne Werbebanner, Video-Ads und Werbetracking schon für 4 €/Monat oder 36 €/Jahr.

Mehr zu ComputerBase Pro

Bereits Pro-Nutzer? Hier anmelden.

Tracking: Wir und unsere 165 Partner verarbeiten personenbezogene Daten, indem wir mit auf Ihrem Gerät gespeicherten Informationen (z. B. eindeutige Kennungen in Cookies) ein Nutzungsprofil erstellen, um z. B. Anzeigen zu personalisieren. Verarbeitungszwecke: Genaue Standortdaten und Abfrage von Geräteeigenschaften zur Identifikation, Informationen auf einem Gerät speichern und/oder abrufen, Personalisierte Anzeigen und Inhalte, Anzeigen- und Inhaltsmessungen, Erkenntnisse über Zielgruppen und Produktentwicklungen.

Impressum Kontakt Datenschutz