Update error code 30088-27 Office 2021 what to do to get corrected????

Dear Daniel

Welcome to Microsoft Community.

Hello, I'm Linn, here to help you solve your problem. According to the error message prompted by Office2021 in the question, I think this seems to be an error caused by a network problem.

It is recommended that you change the network settings to fix the problem:

• Try to change to another network environment, such as a network hotspot;
• Set the DNS server (remember to reset it to automatic after the problem is solved): press Windows+R and enter ncpa.cpl
• Click the name of the network you are currently connected to, open the Network Status window, click Properties, double-click Internet Protocol Version 4 (TCP / IPv4) in the Network Properties window, change Automatically obtain DNS to "4.2.2.1" and "4.2.2.2", and then click "OK".
• Reset network settings: Enter the following command in Windows PowerShell (Administrator), and then restart the device: netsh int ip reset netsh winsock reset

Please try the above preliminary network solutions. This is not a complete solution.

Please understand that our initial response may not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution. Being patient will be a factor in eventually solving the problem.

Sincerest greetings

Linn |Microsoft Community Support Specialist

All on-line UPDATE functions work, but Office and we are blaming IP settings, DNS, etc. We can update everything with no issues so clearly this is in your end.

We can set any DNS but if you are the one with DNS issues, we are wasting our time.

In any case, your suggestions did not make a dent. Issue persists

And, the most important thing: NOT ALL PCs in the LAN have the same problem.

I also see this 30088-27 error on Office 2016 and 2019.

It is introduced after the update to build 17726.20126

Restoring the previous build fixes the update error.

MS 365 here and same exact issue on 2 machines.

MSFT needs to provide a fix as all other suggestions and workarounds fail. I am loathe to revert to a previous build due to the prospect that I could wind up with the same result after that previous build is updated (again).

Please provide a fix for this issue, Microsoft. Also, spare us the useless suggestions since this is clearly something YOU need to rectify.