Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING SCCM ADR error code 0x800705b4

  • Thread starter Thread starter Hasl
  • Start date Start date
  • Replies Replies 5
  • Views Views 9K
  • Tags Tags
    adr

Hasl

New Member
Messages
2
Reaction score
0
Points
1
Hello guys,
We have an environment where we use ADR to update about 50 servers. For the last two months I've been trying to figure out why they don't work on most of them.
Most servers are WS2016, and WS2022. There's also few WS2019.
The May updates turned out to be that about 10 servers were installed, the remaining 40 were not.
Of the 10 successful ones, they were a mix of the 2016 and 2022 versions.
Yesterday I prepared a new ADR specifically for testing the June updates. I have picked 4 servers with different versions to try it out.
Here are my findings.

Settings of "old" ADRs is that servers have to install update without restart. Scheduled to do that in 1 day.
1718189705902.png1718189723353.png

On these servers i have managed to find GetUpdateInfo - failed to get targeted update, error = 0x87d00215 error in UpdatesDeployment.log
I have read different threads but wasnt able to fix the problem.
In SCCM in monitoring i can see this. 1718189319749.png

Error code 0x800705B4 i tried to fix with allowing clients to connect anonymously on my main DP. As i have seen here: https://www.prajwaldesai.com/fix-failed-to-install-update-error-0x800705b4

I have uploaded UpdatesHandler.log, UpdatesStore.log, WUAHandler.log and UpdatesDeployment.log.

Could anyone show me the way?
Thanks a lot!
Hasl
 

Attachments

The error code (0x800705b4) typically indicates a timeout issue or some other interference during the update process. The reasons can vary, but they often relate to software conflicts, corrupted update components, or even system file issues.
 
I
I have tried turn on allowing clients to connect anonymously on my main DP
I'm having the same issue with this month (Aug) windows updates to my client estate. I'm only get under 10% success rate with the following errors:
Failed to install updates - 0x800705b4 This operation returned because the timreout period expired.

Also

Failed to install update - 0x80004004 Operation aborted.

Only thing we noticed is the ADR for windows updates failed but was sucessfull after it was run again.
 
Hello guys,
We have an environment where we use ADR to update about 50 servers. For the last two months I've been trying to figure out why they don't work on most of them.
Most servers are WS2016, and WS2022. There's also few WS2019.
The May updates turned out to be that about 10 servers were installed, the remaining 40 were not.
Of the 10 successful ones, they were a mix of the 2016 and 2022 versions.
Yesterday I prepared a new ADR specifically for testing the June updates. I have picked 4 servers with different versions to try it out.
Here are my findings.

Settings of "old" ADRs is that servers have to install update without restart. Scheduled to do that in 1 day.
View attachment 6268View attachment 6269

On these servers i have managed to find GetUpdateInfo - failed to get targeted update, error = 0x87d00215 error in UpdatesDeployment.log
I have read different threads but wasnt able to fix the problem.
In SCCM in monitoring i can see this. View attachment 6267

Error code 0x800705B4 i tried to fix with allowing clients to connect anonymously on my main DP. As i have seen here: https://www.prajwaldesai.com/fix-failed-to-install-update-error-0x800705b4

I have uploaded UpdatesHandler.log, UpdatesStore.log, WUAHandler.log and UpdatesDeployment.log.

Could anyone show me the way?
Thanks a lot!
Hasl
I know it's a late response but hopefully will help someone else. We have a bunch of servers but same issue started on only 6 servers. All our DPs are HTTPS enabled. So I created a device collection and added those servers in it. Then searched for the adr in software update group and deployed it on the collection I created. And it worked. The updates started showing up on those 6 servers. Once done, I deleted the collection.
 
Back
Top