Hi, Frank Tomecek
Thanks for reaching out to Microsoft Q&A forum.
Sorry for this frustrating situation that you're encountering. What you’re seeing is consistent with Microsoft Office Click-to-Run (SxS) repeatedly “waking up” to do background work (updates, licensing checks, or component validation), and in your case it’s being triggered specifically when Outlook starts, which points to an Outlook-specific component, profile, or add-in interaction rather than Office in general.
Here are some suggestions you can try:
Reproduce in Outlook Safe Mode (fastest way to confirm add-in involvement)
Run: outlook.exe /safe
If the busy cursor stops in Safe Mode, it is almost always a COM add-in or integration loaded only by Outlook. From there, disable add-ins in normal Outlook (File > Options > Add-ins > COM Add-ins) and re-enable one at a time to identify the culprit.
Create a fresh Outlook profile (rules out a corrupted profile or OST-related loop)
Even when Office Quick Repair helps briefly, a damaged Outlook profile can immediately re-trigger background validation when Outlook initializes mail stores. Create a new profile and test before migrating everything. (This is often quicker and more reliable than another full Office reinstall when the symptom is Outlook-only.)
Clear the Office/Outlook local cache that can keep Click-to-Run “busy”
Several Click-to-Run performance loops are tied to corrupted local cache, and clearing the Office file cache is a common remediation path. A typical location referenced is the Office file cache under the user profile (for example, OfficeFileCache for the installed version).
Verify Click-to-Run is the genuine binary (quick sanity check)
In Task Manager, right-click the Click-to-Run process > Open file location. The legitimate path is commonly under C:\Program Files\Common Files\Microsoft Shared\ClickToRun. If it is not, treat it as suspicious and run a full malware scan.
Check whether “metered” networking is involved (surprisingly common with C2R loops)
There are documented cases where Click-to-Run behavior changes on metered connections and normalizes once metered is disabled. If these users are on VPN, mobile hotspot, or any metered policy, test with metered turned off.
As a controlled test, set Click-to-Run service to Manual (not Disabled)
This is not the long-term fix, but it’s a clean way to stop the constant cursor flipping while you isolate the Outlook trigger. Setting Microsoft Office Click-to-Run to Manual means it should start when needed rather than constantly in the background.
Hope this helps. Feel free to get back if you need further assistance.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment."
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.