Jump to content

Recommended Posts

Posted
This is what I'd always configure your PDC as a local time server, either to one provided by the LA or a reputable external one. Time synchronisation is crucial in Windows domain environments.
Posted
This is what I'd always configure your PDC as a local time server, either to one provided by the LA or a reputable external one. Time synchronisation is crucial in Windows domain environments.

 

Time sync. appears to be fine:

 

C:\Users\admin>w32tm /query /status

Leap Indicator: 0(no warning)

Stratum: 5 (secondary reference - syncd by (S)NTP)

Precision: -6 (15.625ms per tick)

Root Delay: 0.0966034s

Root Dispersion: 7.9588069s

ReferenceId: 0x0A6B5D03 (source IP: 10.107.93.3)

Last Successful Sync Time: 20/07/2015 12:01:11

Source: DC03-V.curriculum.local

Poll Interval: 10 (1024s)

Posted

Event ID 1001:

 

 

Fault bucket , type 0

Event Name: WindowsUpdateFailure3

Response: Not available

Cab Id: 0

 

Problem signature:

P1: 7.9.9600.17729

P2: 80072f8f

P3: 00000000-0000-0000-0000-000000000000

P4: Scan

P5: 0

P6: 1

P7: 8024500b

P8: AutomaticUpdatesWuApp

P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}

P10: 0

 

Attached files:

 

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.9.9600.17729_582b7025d3b574e45152b0861b40c17aa98bd5aa_00000000_3e5e131e

 

Analysis symbol:

Rechecking for solution: 0

Report Id: a52f6755-2ed6-11e5-80d1-005056a0347d

Report Status: 4100

Hashed bucket:

Posted
You could also try resetting Windows Update. Stop the service "Windows Update" and rename c:\Windows\SoftwareDistribution to SoftwareDistribution_old then start Windows Update service again.
Posted
try

netsh winhttp import proxy source=ie

 

Then run windows update

Just had the same error myself, this fixed it :-)

Cheers

Mike

 

GENIUS!

 

How did you come across the fix??

 

Has worked on the first server I've had the error on - will test the others tomorrow

Posted
GENIUS!

 

How did you come across the fix??

 

Has worked on the first server I've had the error on - will test the others tomorrow

 

Used it before, sometimes servers that do work suddenly stop updating...its one of the many things I try to get updates working again

 

Mike

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...