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 Office 365 updates error 0X87D00668 & BITS errors

  • Thread starter Thread starter edd080
  • Start date Start date
  • Replies Replies 5
  • Views Views 9K

edd080

Member
Messages
7
Reaction score
0
Points
1
Hello to all;
I have been trying to figure out the cause to my problem for a couple of days now but I cannot seem to find what the issue is.
So I am trying to push the Office 365 current channel update to our users (this works through an adr and previous updates where working as expected);
however since this particular update (current channel update 2302 16130.20218) a number of workstations are reporting error 0X87D00668 and some are also reporting BITS errors:
updatedeployment.jpg
bits_error.jpg
I am not sure if these errors might be related; and why is this happening? The update does not seem to get transfered to the client workstation; I can confirm that other updates are working fine (windows defender definition updates are being installed and windows 10 /11 updates)
I have checked wuahandler logs and could not find any errors, the same with cas logs.
I have also deleted the adr (including the downloaded office updates) and created the adr from scratch just to make sure I am getting a fresh start but the errors still crop up.
I am at quite a loss at what else I can troubleshoot to get this update to actually install properly.
Can anyone help me out please?
Thanks in advance.
 
Last edited:
On how many machines are you encountering this error?. Please try the following steps:
  1. Stop Windows Update service.
  2. Rename C:\Windows\SoftwareDistribution
  3. Rename C:\Windows\System32\GroupPolicy\Machine\registry.pol
  4. Restart Windows Update service.
 
It is happening on quite a number of machines; the error count is increasing everytime i have 40 compliant but around 120 under error out of around 300 clients. I tried the registry.pol fix; strangely enough the machine goes under compliant (the update is still not actually installed ) then is moved again under the error tab.
If i check for the office update manually on one of the client workstations, the update gets installed and it then appears under the compliant tab.
 
I think this is a common issue with sccm deploying office 365 patches as i see it happening on monthly basis. Microsoft must fix this once for all.
 
Back
Top