I fail to use the following fixlet to deploy Office 2024 patch to the office computers. It is a volume license
Office 2024 Version 16.0.17932.20638 Available - Perpetual Channel - Office 2024 Volume Licensed
Below message is extracted from the log
Not Relevant - Office 2024 Version 16.0.17932.20638 Available - Perpetual Channel - Office 2024 Volume Licensed (fixlet:505843)http://sync.bigfix.com/cgi-bin/bfgather/bessecurity )
This log snippet starts after the problem, you would need to look a bit before this
Below is the full log with link and IP are removed, thanks
Current Date: January 23, 2026
At 10:20:16 +0800 -BESClient_Download_FastHashVerify enabled: Off .xxx.xxx.xxx.xx_0&AdapterIpv6=c0-25-a5-9d-64-79%5efe80%3a%3ad40f%3a1bc4%3a3039%3a2519%2f64_0'
This line indicates the command line that was executed...
Command started - waithidden "C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /update user updatepromptuser=False displaylevel=False updatetoversion=16.0.17932.20638 (action:505843)
This line indicates the command claims to run successfully (the 'Exit Code=0' indicates the program return a 0 exit code, which should indicate Success)
At 10:23:23 +0800 - actionsite (xxxx://xxxxxxxxxxxxxxxxx:52311/cgi-bin/bfgather.exe/actionsite)
Command succeeded (Exit Code=0) waithidden "C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /update user updatepromptuser=False displaylevel=False updatetoversion=16.0.17932.20638 (action:505843)
Command succeeded parameter "timeout" = "Fri, 23 Jan 2026 10:23:23 +0800" (action:505843)
One common issue I've seen is that Office Click2Run updates generally require a user account to be logged on at the time. You may need to either set a requirement to run only when user is logged on, or you may need to have the action 'Reapply while Relevant' until it runs with a logged-on user.
Try to verify that, though. I've not patched Office myself in several years. Try running the same action while logged on to the endpoint and see if the update applies successfully in that case.
2 Likes
It seems download the update from the Internet. How to change it to update from local drive ?
I think you'd have to write your own custom fixlet to do that? But I may not be clear on what you're asking.
Sorry that my question is not clear. I want to download the update from the internet to a PC and then distribute the update to the local drives of other PCs in the office. Then use a fixlet to update from the local drives of PCs.
gus
January 30, 2026, 3:42pm
8
Hi @wsd_administrator , BigFix users can use the task:
#565056 - Configure the Update Source of Office 365 - Office 2024#365074 - Configure the Update Source of Office 365 - Office 2021#365076 - Configure the Update Source of Office 365 - Office 365#365056 - Configure the Update Source of Office 365 - Office 2019#365055 - Configure the Update Source of Office 365 - Office 2016
To choose the update source of Office Click-to-Run product updates.
Through the web [from the Microsoft Content Delivery Network (CDN)]
From an on-premises location. This method requires setting up a network share location from which updates can be downloaded. Throughout this document, 'network share' or 'network share location' refers to this method.
Through the use of the BigFix architecture, wherein the entire binary is downloaded to the client cache folder.
Please review the following documentation for more details:
1 Like
You can use the Office deployment tool to download the files, save them to a network share, use the configure update source to point to that share.(Give machines access to that share) You would need to use ODT monthly to get the patches. But you run setup.exe /download and the xml config file.