Jump to content

Recommended Posts

Posted

Good morning.

 

Seems like i got problems with my updates again....

 

I keep getting the error above when i'm "seaching" for updates. Googling it isnt really helping me with this...

 

Any ideas?

Posted
Is it a standalone machine or a machine which is on a network ?

 

Do you go through a proxy ?

 

Machine on the network and being pointed at a WSUS server and no proxy.

Posted
Install this update from here Microsoft Update Catalog

 

Reboot and try searching for updates again.

 

That update is not applicable to my computer... i'm sure ive installed novembers CU update.

 

Have you tried to use any Microsoft fixit tools ?

 

Tried that and still no difference..

Posted

 

I have solved this problem.

 

The error 0x8024500c occurs on Windows 10 1607 when some combination of GPO settings is enabled.

 

When one of these settings is enabled, the "Do not connect to any Windows Update Internet locations" setting must not be enabled:

- Do not include drivers with Windows Updates

- Select when Feature Updates are received

- Select when Quality Updates are received

 

Maybe some others, but I have tested only this.

 

Thank you for your help.

 

All of those is "not configured"

Posted
What should "Windows 10 Download mode" be on? I just changed it to 0 - HTTP and its looking for updates, showing them and then saying it cant connect..
Posted

if you are just using WSUS im sure i have seen somewhere that after a certain build of 10 the client still needs to contact MS Windows update.

id put in proxy information and proxy for winhttp and see if it continues to give you problems which will narrow down if it is a problem with the client dealing with the update directly or from your WSUS setup.

 

when i was testing w10 1607 i did come across niggles with updates and 1607 via wsus which i didnt really get to the bottom of

 

useful link?

https://arstechnica.com/civis/viewtopic.php?t=1325695&start=40

  • Thanks 1
Posted
if you are just using WSUS im sure i have seen somewhere that after a certain build of 10 the client still needs to contact MS Windows update.

id put in proxy information and proxy for winhttp and see if it continues to give you problems which will narrow down if it is a problem with the client dealing with the update directly or from your WSUS setup.

 

when i was testing w10 1607 i did come across niggles with updates and 1607 via wsus which i didnt really get to the bottom of

 

useful link?

https://arstechnica.com/civis/viewtopic.php?t=1325695&start=40

 

Problem is we dont use a proxy now. All done by our ISP (Exa) I will have a look at the link now and still what i'm missing.

Posted
if you are just using WSUS im sure i have seen somewhere that after a certain build of 10 the client still needs to contact MS Windows update.

id put in proxy information and proxy for winhttp and see if it continues to give you problems which will narrow down if it is a problem with the client dealing with the update directly or from your WSUS setup.

 

when i was testing w10 1607 i did come across niggles with updates and 1607 via wsus which i didnt really get to the bottom of

 

useful link?

https://arstechnica.com/civis/viewtopic.php?t=1325695&start=40

 

Problem is we dont use a proxy now. All done by our ISP (Exa) I will have a look at the link now and still what i'm missing.

 

Nope. Any updates needed are installed or not for my machine.

Posted

Ok, there have been many things funky with WSUS and Windows 10 in the start.

 

Two questions...

 

What version Server are you running with WSUS?

 

What version Windows 10 client build are you runing?

Posted
Ok, there have been many things funky with WSUS and Windows 10 in the start.

 

Two questions...

 

What version Server are you running with WSUS?

 

What version Windows 10 client build are you runing?

 

2016 server > Only built yesterday

Windows 10 1607 (after nov 16 update. Manual patched with the update that was ment to fix this....

Posted
Windows 10 1607 (after nov 16 update. Manual patched with the update that was meant to fix this....

Have you tried the March 2017 update?

 

https://support.microsoft.com/en-us/help/4013429

 

  • Addressed issue where adjusting the Windows Server Update Services settings using the Group Policy feature causes downloads to fail.
     
     
  • Addressed additional issues with updated time zone information, Internet Explorer, file server and clustering, wireless networking, Map apps, mobile upgrades for IoT, display rendering, USB 2.0 safe removal, multimedia, Direct3D, Microsoft Edge, enterprise security, Windows Server Update Services, storage networking, Remote Desktop, clustering, Windows Hyper-V, and Credential Guard.

Posted
I'll try that manualy on a another machine tomorrow and see what happens...

 

I got a feeling i've installed this on my machine and tired and still no luck... Watch this space.

 

Looking at that. they released another update to fix problems with the last one. I'll try the latest one..

  • 6 months later...
Posted

Have you reset the SoftwareDistribution folder?

Stop the windows update service, rename the folder C:\Windows\SoftwareDistribution then start windows update service and check for updates. I am not sure if wureset does that or not.

  • Thanks 1
Posted
Have you reset the SoftwareDistribution folder?

Stop the windows update service, rename the folder C:\Windows\SoftwareDistribution then start windows update service and check for updates. I am not sure if wureset does that or not.

 

tried that. :(

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...