OfficeBackgroundTaskHandlerRegistration flashes a window every hour

Anonymous
2017-04-15T05:19:15+00:00

Is there a really, really good reason that the "OfficeBackgroundTaskHandlerRegistration" task (see it in Task Scheduler, Microsoft, Office) must run every hour?  This is what it says that it does: "This task initiates Office Background Task Handler, which updates relevant Office data."

I ask, because it runs officebackgroundtaskhandler.exe in such a way that it flashes a window (itself) on the screen. Only instantaneously to be sure, but it's noticeable, especially once you catch onto what's happening. You can run the task manually if you want to see it without waiting.

Why doesn't the task use one of the many tricks to hide a window from displaying?

Insider Fast on Win10.

Microsoft 365 Insider | Install, activate, and update | Windows

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.

0 comments No comments
Answer accepted by question author
Anonymous
2017-05-30T14:37:13+00:00

( Update 6/7/17 - PaulSey... )

The fix is now available in mainstream builds 16.8210.2075 released on 6/6/17

This issue is fixed starting with build 16.0.8201.2025 which is now available as the latest update for those participating in the Office Insiders Slow program. It will be included in a future update for those not participating in Insiders.

For more information on joining Office Insiders see the Office Insider page.

Thank you everyone for reporting this issue!

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments

165 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-05-31T13:39:20+00:00

    And it's even worse for Office, since the production ring receives updates monthly, increasing the risk that some bug, like this one, will reach production.

    You are right on with that!  I'm on a production version of Office Home and Student 2016 which was just updated to Version 1704 - 8067.2115.  Now I suddenly have this problem.

    Before finding this thread, I posted this.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-05-31T11:59:26+00:00

    This issue is fixed starting with build 16.0.8201.2025 which is now available as the latest update for those participating in the Office Insiders Slow program. It will be included in a future update for those not participating in Insiders.

    For more information on joining Office Insiders see the Office Insider page.

    Thank you everyone for reporting this issue!

    Microsoft seems to ignore Insider feedback and insists on using the production ring as beta testers as well. That's also the reason I left the Windows insider program last summer. Insider feedback being ignored for months and bugs being released to production even after countless insider complaints.

    And it's even worse for Office, since the production ring receives updates monthly, increasing the risk that some bug, like this one, will reach production. So, I decided to switched to the Office deferred channel (Current Branch for Business), like I already did for Windows. This way I will receive better tested Office updates every 4 months, instead of monthly.

    Doing that for Windows is easy, you just enable the flag in Windows Update settings to defer feature updates.

    But it's way more complicated for Office. First you need to install some custom policy templates from here: https://www.microsoft.com/en-us/download/details.aspx?id=49030

    Of course, the installer doesn't install the templates, that would be too easy. It just unpacks them somewhere, and you have to manually copy the admx files to C:\Windows\PolicyDefinitions. Then you need to use gpedit.exe -> Computer Configuration -> Administrative Templates -> Microsoft Office 2016 (Machine) -> Updates -> Update Channel -> Double Click -> Check "Enabled", Set "Channel identifier" to "Deferred" -> OK.

    As a gamer, being able to play my full screen multiplayer games in peace, without popups, automatic reboots and other annoyances is getting harder and harder. I also had to use group policies to prevent automatic reboots. And it's a good thing I'm not paranoid about privacy, and I'm fine with sending telemetry to Microsoft, because completely controlling that seems just as difficult.

    It's sad that now gamers almost need some Windows Administrator training to be able to control what their PCs do.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-05-31T10:20:36+00:00

    Yes, that's also a useful technique to add to my toolbox for the future..  At first I thought that this was a virus/malware but getting no alerts... I wasn't seeing it regularly enough to see a pattern (i.e. hourly) so didn't think task scheduler.  Your method cuts through all that and scoops up "all" relevant data events allowing the offending one to be captured...

    Many thanks...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-05-31T09:58:19+00:00

    I used Process Monitor. Set the filter to only record "Process Start", "Process Exit" and "Process Create" events, minimize the Process Monitor window, wait for the problematic process to pop up again, and then look at the last entries.

    Was this answer helpful?

    0 comments No comments