A: they were, but they seem to have stopped at or around 14-Oct last year and i cant see an obvious cause unless a windows update (on the wsus server) has botched it.

B: cant say since they are not reporting.165419-wsus-server-updates.log

thanks, will try that today for one of the affected machines. but i find it odd that the bulk of the fleet are now unable to contact (status report) all on the same date, especially with the error from wsus event viewer.

the machine is still not reporting and exhibits the same error message when attempting to check for updates

hi Rita, still working through this and testing Adam's suggestion while investigating the error event from wsus (Jan-17th post)

Hi Rita, thankyou for this. i can successfully resolve that url from a test 1803 machine and it attempts to download the aforementioned CAB file.

Hi Rita, I am back at work today and will be able to provide responses and updates on this issue shortly. thankyou for staying on it as well.

thanks for replying, my problem is i dont know how to append the time and date to the filename. when trying it stuffs up and changes the extension,.

that code was as far as i got that successfully downloaded the file but without any file modifications

thanks for the details and script suggestions. also for some reason when i submitted it seemed to have omitted my c:\ entries in the filepath not sure why.

i will gladly test this when i am off work today