Server 2016 and Click to Run Version 2412 (Build 18324.20168)

Anonymous
2025-01-09T21:53:18+00:00

I have two clients with Server 2016 Terminal Services using Office 365 Click to Run. When the server updated to Version 2412 (Build 18324.20168) all applications would crash. I rolled back to Version 2411 (Build 18227.20162) but over night it automatically updated. I have confirmed that the registry setting is correct. Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration - set 'UpdatesEnabled' to False

Office was deployed via ODT with Channel="Current" so only thing i can think of is to redeploy using Channel="MonthlyEnterprise"

Anybody else seeing this issue or have other ideas?

Windows Server Devices and deployment Set up upgrades and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

30 answers

Sort by: Most helpful
  1. Anonymous
    2025-01-10T02:48:55+00:00

    Yes, we have 3 servers that have caught this issue.

    Currently trying these steps to try and roll-back to v2411

    Rollback Microsoft Office to an Earlier Version After an Update | Windows OS Hub

    0 comments No comments
  2. Anonymous
    2025-01-10T03:05:48+00:00

    Yes the roll back worked for me but then the servers updated to 2412 again over night even with the registry setting...

    Thinking of using the firewall to block connectivity for C2R updates ;)

    0 comments No comments
  3. Anonymous
    2025-01-12T00:54:21+00:00

    We have a 2016 vm with this issue now too, it just updated this morning. Our windows 11 hosts are fine, but this is our only 2016 one. Doesn't seem like rolling back will do much good if it's still auto updating despite the registry. I will try and submit a support ticket with MIcrosoft, but not sure how timely I will get a response.

    0 comments No comments
  4. Anonymous
    2025-01-12T22:39:57+00:00

    Hi, We have several servers with this issue also. have you had any updates from Microsoft?

    0 comments No comments
  5. Anonymous
    2025-01-12T22:48:13+00:00

    Nothing useful. This is what I got!

    0 comments No comments