Office Click-to-Run Updates May be Broken with Latest Version

Topic

New Reply

I was running Office 2019 click-to-run (same version for 365) V2405 17628.20164) from June 19.  It updated today to V2406 17726.20126 from June 26.  With the new 2406 I noticed A failure to check for updates giving

Something Went Wrong – error code of 30088-27

I tried an online repair which didn’t fix the issue.  I then completely deleted and reinstalled Office 2019 from my MS account.  After activating I was on V2405 17628.20144 from June 11.

Everything was working fine, and when I checked for updates it worked, and updated back to V2406 … and the update error 30088-27 came back!  So I did yet another reinstall and I’m staying on 2405 for now … unless it auto updates again and breaks.

I’ve seen a few posts on the web seeing the same thing using 365 and other click-to run on 2406 … but not many posts.  So I don’t know how widespread the issue is, but something may be breaking the update service in the current Office V 2406.

Anyone else seeing this?

Moderator Note: Topic relocated to more appropriate forum from original location

 

3 users thanked author for this post.

LH, IronTechmonkey, lmacri

Reply | Quote

Replies

My advice is to just sit tight and let Microsoft fix this.

Receiving “Something went wrong” Error 30088-27 AND “You’re up to date” when updating.. – Microsoft Community Hub

As you can see it has happened in the past and it takes Microsoft to fix it.  They are getting telemetry on the issue.

Susan Bradley Patch Lady/Prudent patcher

5 users thanked author for this post.

IronTechmonkey, snissen, pmbinc, lmacri, Brocktoon

Reply | Quote

Exactly the reason I have my O365 set to Semi-Annual Enterprise Channel. Gives MS time to fix this kind of thing. I certainly don’t need the latest monthly features until they are actual features.

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

3 users thanked author for this post.

pmbinc, windbg, Brocktoon

Reply | Quote

Yep … I think patience would have been the better solution compared to the 2 reinstalls I spent my Saturday afternoon on.  I’ve now turned off auto update for MS office in the update options.

Thanks again for the responses!

Reply | Quote

Brocktoon wrote:

Anyone else seeing this?

I’m an Office 365 subscriber and the recent click-to-run updates were without errors here.  My apps are working normally.

Desktop mobo Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

Reply | Quote

But what patching channel are you on? Monthly?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Hi Brocktoon:

Thanks for posting about this.

I’m currently using Microsoft Office Home and Business 2019 C2R Version 2406 / Build 17726.20126 (Current Channel, rel. 26-Jun-2024). I normally just let my MS Office 2019 C2R update automatically but after reading your post I tried a manual update at File | Office Account | Update Options | Update Now and got the same error 30088-27.

Per Susan’s suggestion I’ll just sit tight for now and wait for Microsoft to (hopefully) fix this on their back end.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v127.0.2 * Microsoft Defender v4.18.24050.7-1.1.24050.5 * Malwarebytes Premium v5.1.5.116-1.0.1252 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2406 / Build 17726.20126

Reply | Quote

Brocktoon,

I have exactly the same issue as you described!
I also did on online and an offline repair, and even an unistall/re-install of my MS Office 365.
But all with the same outcome: after manually updating to the latest Version 2406 (build 17726.20126), and after that again manually searching for updates, the “Something went wrong – error 30088-27” showed up.
Now, after re-installing MS Office, I am on the last-latest Version 2405 (build 17628.20144), and I also disabled Automatic Updating so to wait for a fix.
Thanks for posting your issue, I couldn’t find anything recent regarding this issue, that makes me thought I am the only person in the world having this problem.
Now I know there are more people seeing this, I wil sleep at least a bit better!
Let’s hope this error will be fixed soon by MS.

Best reagrds,

Wim.

Reply | Quote

Same issue here.

 

Microsoft 365 Apps for Business

Version 2406 (17726.20126 Klick-uns-Los)

Aktueller Kanal

 

 

Reply | Quote

Susan Bradley wrote:

But what patching channel are you on? Monthly?

Yes, monthly.  Admittedly I’ve never had any issues so I never really thought about it.

Desktop mobo Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

Reply | Quote

Same problem here (Germany) with MS-Office 2019 H & B.

We discovered the problem because we have an office update command in the autostart folder of every client PC.  On the morning of 27. June 2024, the daily office updates worked fine – as usual. But minutes after that, every further (manual) update attempt failed with error code 30088-27. Nevertheless the office programs themselves (such as Word) still start and work.

Online and offline repair attempts via Programs & Features did not resolve the issue; to be more precise: the online repair option made the update mechanism work again – but only for a single time. Following update attempts led to error code 30088-27 again. – Dead end!

I wonder how MS will fix it. How will there be an “update for the update” without a working update mechanism. It seems MS-Office can’t find the right update server or can’t connect to them. Or maybe something is messed up in the registry.

Unfortunately, not the first time that MS has a problem with its update management. Sad!

Reply | Quote

Hey MarKo,

the Office Online Repair Tool failed and uninstalled everything.

Reinstall works and the Update fails right away. No one time working for me.

There are also 2 errors in the event viewer:

Microsoft Office 16 Alerts ID300

Failed to parse element: VersionOverrides

Id=***************DisplayName=Vorgeschlagene Ereignisse, Provider=Microsoft, StoreType=Unknown, StoreId=(null)

P1: Apps for Office

P2: 16.0.17726.20078

P4: New Document

Failed to parse element: VersionOverrides

Id=******************, DisplayName=Bing Maps, Provider=Microsoft, StoreType=Unknown, StoreId=(null)

P1: Apps for Office
P2: 16.0.17726.20078
P3: 0x8004323E
P4: New Document

Reply | Quote

Interesting! I’ve been looking all over the joint for the past 4 hours and…….nope, not a peep (except here).

I finally figured out (I’m kinda slow) that it MUST be on their end since I have two machines with 365 and they both exhibit exactly the same behavior.

Having written that, it sure would be nice if MSFT stopped this nonsense. I mean, we’re paying a recurring subscription fee so we don’t have issues such as these, right?

Jeez!

1 user thanked author for this post.

Brocktoon

Reply | Quote

And now I’ve talked with a friend who had their Office 365 auto-update to  V2406 and now seeing the same thing.  I’m seeing some more posts pop up on the MS support and other forums, but so far nothing from MS themselves.

As others have mentioned, how do you patch or fix if the update system isn’t working?

Reply | Quote

Brocktoon wrote:

how do you patch or fix if the update system isn’t working?

Hi Brocktoon:

According to the release history <here> for retail editions of MS Office 2016 / 2019 C2R (Current Channel)  our Version 2406 / Build 17726.20126 (rel. 26-Jun-2024) is the latest release so there’s nothing to worry about for now. At this point the best thing to do is wait to see if Microsoft can fix the problem on their backend servers.

In a worst case scenario where Microsoft can’t fix the problem from their end and they start releasing new builds with critical security fixes we can easily roll back to an earlier version of MS Office where manual updates were working (e.g., Version 2405 / Build 17628.20164 *** released 19-Jun-2024) as instructed in Diane Poremski’s Uninstall Updates in Office ‘Click to Run’ on their slipstick.com site and then see if the update runs.  There’s no point trying this now because you’ll just update back to the buggy Version 2406 / Build 17726.20126.

Keep in mind that for now we know that manual updates aren’t working for some of us in Version 2406 / Build 17726.20126, but that doesn’t necessarily mean that a Click-to-Run update won’t be automatically delivered in the background when the next build is posted.
__________________________

***  Note: You would enter the command

"C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.17628.20164

in an elevated command prompt to roll back C2R editions of Outlook 2016, 2019, or M365 to Version 2405 / Build 17628.20164.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v127.0.2 * Microsoft Defender v4.18.24050.7-1.1.24050.5 * Malwarebytes Premium v5.1.6.117-1.0.1270 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2406 / Build 17726.20126

1 user thanked author for this post.

IronTechmonkey

Reply | Quote

Check for updates on Version 2406 (Build 17726.20126) works OK for me.

Which antivirus is in use for people who get “error 30088-27”?

Reply | Quote

b wrote:

Which antivirus is in use for people who get “error 30088-27”?

Hi b:

I use Microsoft Defender as my primary antivirus and run Malwarebytes Premium in real-time protection mode for secondary protection.

I completely disabled Malwarebytes (i.e., I changed Settings | General | Windows Startup | Launch Malwarebytes in the Background When Windows Starts to OFF and re-booted) but that didn’t fix the 30088-27 error I see when I run a manual update at File | Office Account | Update Options | Update Now in my MS Office 2019 C2R Version 2406 / Build 17726.20126.
————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v127.0.2 * Microsoft Defender v4.18.24050.7-1.1.24050.5 * Malwarebytes Premium v5.1.6.117-1.0.1270 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2406 / Build 17726.20126

1 user thanked author for this post.

b

Reply | Quote

The results so far:

The issue evolved with an update released on 26.June 2024 which is definitely the culprit: since the update to version 2406 (Build 17726.20126) further update attempts fail with error code 30088-27. MS-Office 2019 seems to be affected as well as the Office 365 app. A similar problem had occured in June 2022 and was resolved by MS with an update weeks later.

According to internet researches, the error code in question is usually shown when Office files are disrupted. But un- and re-installing Office or starting the online repair via Programs & Features, as suggested by MS, cannot resolve the issue as all these attempts finally end up with the buggy version / build named above.

Further recommendations associated with error code 30088-27: disabling firewall and/or antivirus program; performing a disk-cleanup; performing the “sfc /scannow” command; deleting the “Updates” folder in “C:\Program Files (x86)\Microsoft Office”; changing the update channel from “current” to “semi-annual”; changing the network environment or the DNS IP address; finally: wait & pray. None of these tips helped (at least not for us).

Meanwhile, more and more people are addressing this issue – here on askwoody as well as in other forums.

While writing these lines, I remember a similar problem from December 2017 (not with Office, but with Windows 7) when system updates failed because a file called authorization.xml (as part of authcab.cab) had a wrong expiry date:
https://superuser.com/questions/1274342/why-does-windows-update-fail-with-error-code-0x80248015-for-windows-7

Maybe it’s quite similar here: an out-dated certificate or a wrong expiry date somewhere or a wrong update server (CDN)URL in the registry? Any ideas?

P.S.: @qwertz-man: There are no Office-related errors or warnings logged in our event viewer.
P.P.S.: @b: We use Avira Prime.

1 user thanked author for this post.

IronTechmonkey

Reply | Quote

Running Norton 360 on my system

1 user thanked author for this post.

b

Reply | Quote

I’m running Microsoft 365 Apps for Enterprise current channel version 2406 Build 17726.20126. I’ve checked for updates multiple times without a problem.

--Joe

1 user thanked author for this post.

TechTango

Reply | Quote

Running Windows Defender on my system.

 

Reply | Quote

FWIW, Windows Security (Defender) here and seriously doubt that’s the issue.

I suppose I’ll just drop this and forget about it entirely unless a new update is released and I can’t get it as a result of this error.

I also would find it hard to believe that MS would allow that to happen and let this go unaddressed and unresolved. There are probably countless thousands of folks who have this issue but have not reported it because they have not even noticed it at this point.

Reply | Quote

They know, but Office is still operational, there may be other things going on that we are not aware of. I also doubt that it’s antivirus related.

 

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

lmacri

Reply | Quote

Susan Bradley wrote:

My advice is to just sit tight and let Microsoft fix this. Receiving “Something went wrong” Error 30088-27 AND “You’re up to date” when updating.. – Microsoft Community Hub As you can see it has happened in the past and it takes Microsoft to fix it. They are getting telemetry on the issue.

Affected users might also want to subscribe to Prius 04’s 02-Jul-2024 topic Microsoft 365 Update Error 30088-27 in the Microsoft 365 and Office board of the Microsoft Answers forum. I’m hoping that Jonathan Z – MSFT (Microsoft Community Support Specialist) will post another update in that topic once Microsoft has a fix.
————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v127.0.2 * Microsoft Defender v4.18.24050.7-1.1.24050.5 * Malwarebytes Premium v5.1.6.117-1.0.1270 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2406 / Build 17726.20126

1 user thanked author for this post.

Brocktoon

Reply | Quote

It does look like it’s got MS’ attention as they replied:

“Currently, we have received numerous reports from users experiencing error code 30088-27 upon updating to the version 2406 (build 17726.20126) of Excel. Your issue falls into this category, which has recently become a prevalent concern. We are actively gathering information about this problem and working diligently towards finding a resolution.”

I would correct them in that it’s not just Excel, but it sounds like they’re on the right path

Reply | Quote

We, too, doubt that the issue is related to antivirus. Thus, we have dug a little deeper and found these articles:

1. A troubel-shooting advice published in 2015 according to which some registry settings should be checked, namely those in HKLM\SOFTWARE\Microsoft\Office\15.0\ClickToRun\Configuration (replace “15.0” with “16.0”). Ok, the article refers to Office 365 ProPlus and is bit older, but it might be useful:

https://deploywindows.com/2015/04/10/hitting-error-code-2-28-and-30088-27-with-office-365-proplus-updates/

2. An article from April 2023 on the German blog “borncity.com” (with English translation) according to which some users and admins have reported that their Office-2016/2019 installations – against their will and without any annoucements by MS – have been “upgraded” to Office 365. Maybe now, in June/July 2024, MS made another attempt to push users towards Office 365 – and by trying so caused error code 30088-27.

https://borncity.com/win/2023/04/18/microsoft-is-upgrading-parts-of-office-2016-2019-to-office-365/

3. A couple of weeks ago, we discovered a new executable in Sysinternal’s Process Explorer. It’s a child process of word.exe and is called ai.exe. It is part of MS’s latest efforts to implant artificial inteligence agents in every MS software product. First in Bing – now in Office (aka Co-Pilot). As we mistrust the current AI hype, we removed all the ai-associated files from our Windows systems and deactivated Co-Pilot in the gpedit settings. Is that why the updates failed?

Reply | Quote

AI.exe is not new.  It’s not copilot either.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I know it’s not new, but I thought it is implemented in Windows/Office 365 only. Thus, I was surprised to find in our Office 2019 C2R installation.

Reply | Quote

Hi @all,

 

any news on that?

Reply | Quote

Just hang tight.  Clearly Microsoft is investigating.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

For any of you that are interested I’ve written a powershell program that allows you to change the update channel. Personally, I prefer the Semi-Annual Enterprise channel as it gives MS time to sort out problems like this.

You can download the Change-MSOffice-UpdateChannel.zip program here.

Just unzip the 2 files (one is an .ico file) to a directory and then run the program from that directory. You’ll get a dialog box select the desired channel and click the Execute button.

Once you do that you can close the PS session and watch the messages from MS on your progress. It does re-download the appropriate version so you’ll completely regress to that version.

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

2 users thanked author for this post.

pmbinc, abbodi86

Reply | Quote

If Powershell isn’t your thing…

https://www.askwoody.com/forums/topic/7000001-changing-microsoft-365-click-to-run-to-slower-patching-channel/

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

abbodi86, pmbinc

Reply | Quote

RetiredGeek wrote:

For any of you that are interested I’ve written a powershell program that allows you to change the update channel. Personally, I prefer the Semi-Annual Enterprise channel as it gives MS time to sort out problems like this.

Hi RetiredGeek:

Do you use a  Microsoft 365 product on a subscription model, and have you tested your PowerShell script with retail (perpetual) versions of MS Office 2016 / 2019 / 2021 Click-to-Run (C2R)?

Susan Bradely’s 7000001 Changing Microsoft 365 click to run to slower patching channel notes the commands in that tutorial for changing to the Semi-Annual Channel “is not for Office Home and Student or any of the perpetual versions. It’s only for the Microsoft 365 subscription versions.”
————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4529 * Firefox v127.0.2 * Microsoft Defender v4.18.24050.7-1.1.24050.5 * Malwarebytes Premium v5.1.6.117-1.0.1270 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2406 / Build 17726.20126

Reply | Quote

Imacri,

Yes I subscribe to MS 365 Family and use it on 4 of my personal machines and share it with my Wife, Brother, and Sister-in-law.

I’ve tested it on the following machines:
My Main Driver MinisForum Venus UN970Pro (AMD Ryzen 9 9740)
My Canary Machine DellXPS8920 (Intel i-7 7700)
My Laptop Dell Inspiron 137000 (Intel i-5-1500U)

All except the laptop are running Win 11 Pro, the laptop is running Win 10 Pro.

The retail versions (perpetual license) do not have channels, what you buy is what you get as far as I can tell.

HTH

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

1 user thanked author for this post.

lmacri

Reply | Quote

Tested on a system with Volume License Office 2019 C2R, it updated to Version 1808 (Build 10412.20006 Click-To-Run) successfully and I have not seen those errors.

Reply | Quote

On 09. July 2024, a new Office update was released (Build 17726.20160):
https://learn.microsoft.com/en-us/officeupdates/update-history-office-2019

Here in our office (with Office 2019 C2R H & B), however, the update installation was only partially successful. We opened a administrative command prompt and typed in the following command:

“C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe” /update user updatetoversion=16.0.17726.20160

The update was installed properly, but – again – no new updates are possible since: error code 80033-27. I.e., the problem in question persists on a higher build level

Reply | Quote

Same experience as Marko on two Windows 10 machines. Entered:

“C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe” /update user updatetoversion=16.0.17726.20160

Office is now updated to the latest version but I’m still getting the 30088-27 error when I try to do an update. MSFT needs to fix this issue; it’s on their end.

Reply | Quote

Brocktoon wrote:

how do you patch or fix if the update system isn’t working?

Hi Brocktoon:

Just an FYI that Prius 04 posted on 14-Jul-2024 in their topic Microsoft 365 Update Error 30088-27 and confirmed that running the command:

"C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.17726.20160

from an elevated command prompt with Administrator rights as instructed in Diane Poremsky’s slipstick.com article Uninstall Updates in Office ‘Click to Run’ updated their MS Office C2R to the latest Version 2406 / Build 17726.20160 (rel. 09-Jul-2024). Unfortunately, that forced update did not fix the 30088-27 error they see when they try to run a manual update check at File | Office Account | Update Options | Update Now.

I’m going to wait a bit longer to see if Microsoft can fix the 3008-27 error from their own end and/or that an automatic background update will eventually patch me to the latest build. However, I’m not willing to wait too long since the current Version 2406 / Build 17726.20160 includes security updates for the CVEs listed <here>.
————
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4651 * Firefox v128.0.0 * Microsoft Defender v4.18.24050.7-1.1.24060.5 * Malwarebytes Premium v5.1.6.117-1.0.1280 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2406 / Build 17726.20126

1 user thanked author for this post.

IronTechmonkey

Reply | Quote

I’m not willing to wait too long since the current Version 2406 / Build 17726.20160 includes security updates for the CVEs listed <here>.

 

I fully concur with Imacri; the security updates are important and we can’t wait forever for MSFT to fix this, which is why I used that upgrade path.

Reply | Quote

Thanks for sharing this; it is occurring on my computers a well. On 2 Win 10 machines running MS Office Pro 2021, on which MS Office is updated manually (but often) this morning:

The computer in which MS Office Pro was was updated recently (within days) yielded the Error Code: 30088-27 upon attempt to manually update MS Office.

The computer on which MS Office had not been updated for over 2 weeks first received an update successfully then upon another attempt yielded the same Error Code 30088-27.

I’m not sure how MS will update a broken updater but for now will leave it set to auto update.

Reply | Quote

Hi Brocktoon:

Just an FYI that there might be a connection between these 30088-27 update errors and the privacy settings in MS Office C2R.

After I enabled all 5 privacy settings in my MS Office 2019 C2R at File | Office Account | Privacy Settings | Manage Settings (i.e., all optional data collection, Connected Experiences, and personalized offers options) and restarted my computer (the system restart is important) my manual check for updates at File | Office Account | Update Options | Update Now ran to completion and I was updated from Version 2406 / Build 17726.20126 (rel. 26-Jun-2024) to Version 2406 / Build 17726.20160 (rel. 09-Jul-2024).

See my 30-Jul-2024 post today on page 4 of Prius04’s Microsoft 365 Update Error 30088-27 in the MS Answers forum for details, and note my advice there to disable the Fast Startup power option in Windows 10 and 11.

Kudos to Lauriejm56 for posting this workaround in Prius04’s topic.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4651 * Firefox v128.0.3 * Microsoft Defender v4.18.24060.7-1.1.24060.5 * Malwarebytes Premium v5.1.7.121-1.0.1293 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2406 / Build 17726.20160

Reply | Quote

I went to file > account > account privacy > manage setting > privacy settings and then checked anything that was unchecked.  I rebooted (fast startup is disabled), and the update error is still present.

I have One Drive disabled and have never used it.  I also don’t want to enable One Drive, so if for some reason One Drive is the issue, then MS will need to figure that out as I want nothing to do with it.

It was worth a shot, but checking the privacy settings didn’t fix my error.

Reply | Quote

I’m using Microsoft 365 Click-to-Run – can anyone advise if it’s safe to attempt an update yet?

Currently on Version 2406 Build 17726.20078

 

Reply | Quote

Just adding to all of the above. Until today I hadn’t heard of error code 30088-27.  Last month’s MS 365 update ran normally. Today (following Susan’s OK) I ran my usual schedule, firstly to update MS 365, then Windows.  (I am on Windows 10 Pro 22H2.)

I got my first 30088-27 as soon as I tried to run the Office update (normally disabled during the month).  Tried Quick Repair, rebooted, to no avail.  As Office was still working OK, I skipped through and did the Windows updates – all OK.

After rebooting, tried the Office update again – still NG.  Eventually downloaded 365 again on top of my existing version.  This succeeded and downloaded v2407 (17830.20138) which I assume is the latest version.

Just for fun, I tried the Download Now button again – still got the same error.  That’s when I came here and found this thread.  So I will leave things as they are now until MS fixes the problem and/or a permanent solution is published on this site.

Cheers,

LH.

 

Dell Precision 3630 w/32 GB RAM, 500 GB (C:), 1 TB (D:)
Window 10 Pro x64
Internet: FTTC (Fibre to the Kerb)

1 user thanked author for this post.

AusJohn

Reply | Quote

I appreciate the comprehensive reply; think I’ll lay low for a while longer.

Seem to have enough hassles one way and another, without going looking for any extras.

Office is still working OK, so I think it’s a case of “if it ain’t broke, don’t fix it!”.

 

Reply | Quote

AusJohn wrote:

Currently on Version 2406 Build 17726.20078

I’ve been using the automatic updates without any issues. I’m letting that sleeping dog lie for now.

Desktop mobo Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

1 user thanked author for this post.

AusJohn

Reply | Quote

See my reply to LH (above).

 

Reply | Quote

Again the same drama as on 09.07.2024:

MS has released another update for Office 2019 on 01. August 2024 (this time version 2407 – Build 17830.20138).
https://learn.microsoft.com/en-us/officeupdates/update-history-office-2019#retail-versions-of-office-2016-c2r-and-office-2019

And as at the beginning of July, the issue couldn’t be resolved. Opened the administrative command prompt again and this time entered the following command:
“C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe” /update user updatetoversion=16.0.17830.20138

Again the update was installed, but no further updates are possible since. Obviously the problem in question – error code 30088-27 – persists on a higher patch level

Disgraceful.

2 users thanked author for this post.

Brocktoon, AusJohn

Reply | Quote

Anyone checked the .log files in %temp% and %windir%\temp to see what cause the error exactly?

Reply | Quote

abbodi86 wrote:

Anyone checked the .log files in %temp% and %windir%\temp to see what cause the error exactly?

Hi abbodi86:

Which log file(s) are you referring to?

My C:\Windows\Temp and C:\Users\<myusername>\AppData\Local\Temp\ folders can accumulate over 600 files in the span of one week. I purged those folders today (I normally keep temp files created in the past 24 hours) and generated a new 30088-27 Office update error and I still can’t tell which file, if any, is logging these errors.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4651 * Firefox v128.0.3 * Microsoft Defender v4.18.24060.7-1.1.24060.5 * Malwarebytes Premium v5.1.7.121-1.0.1293 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2407 / Build 17830.20138

Reply | Quote

I think the logs in “%windir%\temp” would be more important (named as computer name + date)
they are the logs created by ClickToRunSvc service

Reply | Quote

Used the command prompt method to update … and it did work, but as many others report, the update error is still present in the new version.

Makes me wonder if MS’ eventual solution will just ask affected customers to run the command solution periodically

EDIT: Did MS support merge threads on this issue? … I can’t find the original support thread on this topic on MS’ forums

Reply | Quote

Despite what I said recently in this thread (#2692594) I decided to try updating my C2R Office, and it all went smoothly as usual.

No error messages, and ended up with Version 2407 (Build 17830.20138 Click-to-Run) as hoped for.

abbodi86 wrote:

Anyone checked the .log files in %temp% and %windir%\temp to see what cause the error exactly?

Probably no point, given that all worked normally, but I have saved the log files in case they’re of interest to anyone.  If they are then let me know and I can make them available.

For what it’s worth:

1.  I’m on the “Current Channel”, and
2.  “Options, General, Privacy Settings, Turn on all connected experiences” is selected

 

Reply | Quote

I’m just interested to see the error details (corrupted files? wrong hash? delivery hicckups?…)
i won’t solve it of course

Reply | Quote

I need to poke around again and see if I can get any more word on an eta.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

The Thread on the Microsoft Website was cleared. o.O

https://answers.microsoft.com/en-us/msoffice/forum/all/microsoft-365-update-error-30088-27/108a3867-dae3-40d5-809e-41f016468b2e

Reply | Quote

This seems like it’s the “missing” thread; if not, it’s certainly got plenty of comments and complaints relating to the Office 365 error 30088-27 problem.

https://answers.microsoft.com/en-us/msoffice/forum/all/update-error-code-30088-27-office-2021-what-to-do/89ad2f55-bb1e-4809-bd2f-132c99b470c3

 

Reply | Quote

qwertz-man wrote:

The Thread on the Microsoft Website was cleared. o.O

Hi qwertz-man:

The topic Microsoft 365 Update Error 30088-27 was taken down from the MS Answers forum because the original poster’s account was suspended – see Moderator Don Varnau’s 04-Aug-2024 post today on page 5 of Moderation Requests to Moderators [Jul 30 – Aug 05].  The OP posted multiple replies in a short period of time and I suspect they were flagged by the automated spam bot as a possible spammer.

I’m hoping that topic will be taken out of moderation and visible again in a few days.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4651 * Firefox v128.0.3 * Microsoft Defender v4.18.24060.7-1.1.24060.5 * Malwarebytes Premium v5.1.7.121-1.0.1293 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2407 / Build 17830.20138

Reply | Quote

The thread and poster seem to have been reinstated now.

1 user thanked author for this post.

lmacri

Reply | Quote

Switch to the 365 Semi-Annual Enterprise Channel. The Current Channel and the Monthly Channel might as well be called the beta tester channels. In addition, Microsoft states “If needed, security updates for Semi-Annual Enterprise Channel are released on the second Tuesday of the month.” So, the Semi-Annual is the best choice for most organizations and individuals in my opinion.

SEE: https://www.fmsinc.com/microsoft-office/change-office-365-channel.html

Reply | Quote

Intrepid wrote:

Switch to the 365 Semi-Annual Enterprise Channel. The Current Channel and the Monthly Channel might as well be called the beta tester channels.

lmacri wrote:

Susan Bradely’s 7000001 Changing Microsoft 365 click to run to slower patching channel notes the commands in that tutorial for changing to the Semi-Annual Channel “is not for Office Home and Student or any of the perpetual versions. It’s only for the Microsoft 365 subscription versions.”

… but keep in mind that you can only change the update channel if you have a Microsoft 365 subscription. Many users posting in this topic, including the OP Brocktoon and myself, are using perpetual editions of MS Office 2016 / 2019 / 2021 C2R.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4651 * Firefox v129.0.0 * Microsoft Defender v4.18.24070.5-1.1.24070.3 * Malwarebytes Premium v5.1.6.117-1.0.1280 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2407 / Build 17830.20138

Reply | Quote

I have seen that when you disable:
File –> Options –> Save –>
“Show additional places for saving, even if sign-in may be required.”

 

and sometimes:
“AutoSave OneDrive and SharePoint Online files by default on Word”

once, that it then should be fine.

Reply | Quote

Hi Brian:

Thanks for the suggestion, but I launched my MS Word 2019 and DISABLED File | Options | Save | Show Additional Places for Saving, Even If Sign-in May Be Required and rebooted my computer and that did not fix my 30088-27 errors. Note to others: This setting does not exist in my MS Outlook 2019 options.

I might be looking in the wrong place (or it simply might not exist in my perpetual edition of MS Word 2019), but I could not see a setting named “AutoSave OneDrive and SharePoint Online Files by Default on Word” at File | Options | Save.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4651 * Firefox v129.0.1 * Microsoft Defender v4.18.24070.5-1.1.24070.3 * Malwarebytes Premium v5.1.7.121-1.0.5002 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2407 / Build 17830.20166

Reply | Quote

Hi Brocktoon:

Just an FYI that I updated my MS Office 2019 C2R to the latest Version 2407 / Build 17830.20166 (rel. 13-Aug-2024 – see the Current Channel release notes at https://learn.microsoft.com/en-us/officeupdates/current-channel) by copying and pasting the command below into an elevated command prompt with Administrator rights as shown in the attached image.  Unfortunately, build 17830.20166 has not fixed my 30088-27 update error. ***:

"C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.17830.20166

*** Note that I currently have my privacy setting at File | Office Account | Privacy Settings | Manage Settings | Connected Experiences | Turn On All Connected Experiences (as well as other optional privacy settings) DISABLED. If I had enabled that single setting and restarted my computer (the system restart is important) my manual check for updates at File | Office Account | Update Options | Update Now likely would have run to completion as it has in the past, but I didn’t even bother testing this time since I prefer to update using the command prompt method.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4651 * Firefox v129.0.1 * Microsoft Defender v4.18.24070.5-1.1.24070.3 * Malwarebytes Premium v5.1.7.121-1.0.5002 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2407 / Build 17830.20166

Reply | Quote

I’ve just updated my C2R Office, and it all went smoothly as usual.

No error messages, and ended up with Version 2408 (Build 17928.20066 Click-to-Run) as hoped for.

For what it’s worth:

1.  I’m on the “Current Channel”, and
2.  “Options, General, Privacy Settings, Turn on all connected experiences” is selected

Reply | Quote

Susan Bradley wrote:

My advice is to just sit tight and let Microsoft fix this.

Receiving “Something went wrong” Error 30088-27 AND “You’re up to date” when updating.. – Microsoft Community Hub

As you can see it has happened in the past and it takes Microsoft to fix it.  They are getting telemetry on the issue.

Any news on this?  Thank you!

Reply | Quote

I have identified a solution that address this specific issue, as this exact problem affected my environment starting with the June Office Updates.

It appears that Microsoft has changed the communication method for Office Click-to-Run. Previously, OfficeC2Rclient.exe used the WinInet proxy settings (Internet Settings) to connect to Microsoft’s cloud services. However, following the June update, OfficeC2Rclient.exe now utilizes the WinHTTP proxy (configured via NetSH) for communication.

Depending on your environment’s configuration, systems without a properly configured WinHTTP proxy will default to using the Default Gateway to access the internet. This could result in traffic being blocked by your Default Gateway Firewall, as such traffic typically routes through a proxy. In environments where a WinHTTP proxy is configured to use an actual proxy server, authenticated proxy rules may cause the traffic to fail with a 407 error, as the Windows WinHTTP proxy does not handle authentication well.

In our environment, we addressed this by reconfiguring our firewalls and proxies to allow the necessary communication. Given the risks associated with recent CVEs affecting Office products in the past couple months, I hope this information helps others who have been unable to update their Office installations, thereby reducing their exposure to potential vulnerabilities.

Reply | Quote

Is is possible that there is some commonality with certain home routers that may be triggering this as well?  Or perhaps ISPs?

Scratching my head on behalf of the consumer patchers in the group.

 

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Felix

Reply | Quote

I am also scratching my head.
I have two PCs (desktop & laptop) that each have Office Home and Student 2019.
Both are Win 10 22H2 with Norton 360. Both connect to the same ISP router via Wi-Fi.
Manually requesting Office updates using ‘Update Now’ used to work OK.
Then both PCs started giving the 30088-27 error message.
Earlier this week the desktop system stopped giving the 30088-27 error message and received an Office update to 16.0.17830.20166.
I just tried my laptop and it is still giving the 30088-27 error message and remains on version 16.0.17726.20160.
So I have two PCs with the same ISP router and firewall – one now works and the other still doesn’t.

Reply | Quote

Affected users should go to  File | Office Account | Update Options | Update Now and try another manual update.

I confirmed that all my optional privacy settings at File | Office Account | Privacy Settings | Manage Settings | Connected Experiences are DISABLED and my manual update seems to be working today after a system re-boot.

Kudos to Gunter Born for posting a heads up today on page 11 of Prius 04’s Microsoft 365 Update Error 30088-27 in the MS Answers forum. Here’s hoping Microsoft has released a permanent fix on their end that works for all MS Office C2R users.
———–
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4780 * Firefox v129.0.1 * Microsoft Defender v4.18.24070.5-1.1.24070.3 * Malwarebytes Premium v5.1.8.123-1.0.5007 * Macrium Reflect Free v8.0.7783 * Microsoft Office Home and Business 2019 C2R Version 2407 / Build 17830.20166

4 users thanked author for this post.

Brocktoon, Felix, EricW, b

Reply | Quote

I can confirm that when I tried the usual method of updating just now it went through without any error message!  It still did not work yesterday.

Thank you!

Hopefully now MS will address the WUshowhide issue here: https://www.askwoody.com/forums/topic/instructions-for-un-hiding-an-update-using-wushowhide/#post-2696736

Reply | Quote

Yup!!!  So MS finally fixed something in the background??  In any event updates are now working for me as well … without changing anything on my side

Reply | Quote

Same here for me: after enabling Automatic Updates (I had disabled it),
now my MS Word 2016 is automatically updated to Version 2407 Build 16.0.17830.20166.
And after “Update now” the window “You’re up to date” appears, and no longer
the Error 30088-27.
So this error is (finally!) fixed for me.

Wim.

Reply | Quote

After installing the latest updates we see this version in Word: Veriosn 2406 (Build 17726.20206).

Is there an option to update channel version to 2407?

 

 

Reply | Quote

Had issues updating MS Office Professional Plus 2021 from Version 2406 (Build 17726.201160 click to run) today. My update pattern is to have office updates disabled until I am ready to update. Since I did not have any issues when I updated in June and July, I thought I was free from this updating issue. Today when I enabled auto updates and selected update now I got the Update Error 30088.27.  Tried multiple times throughout the morning with same results. After restarting the PC and trying again, updating proceeded normally without errors and now I am at Version 2408 (Build 17928.20114 click to run)

Reply | Quote