Windows 10: office 2013 persistent error: OHub.exe

I have been running windows 10 with few functional problems although I have had persistent errors in the Event viewer, most of which seem harmless and related to connections to MS services that seem related to a) MS services themselves being down or b) a lag during the boot process where my internet connection doesn't come awake until the desktop is fully active/drawn.

However one error occurs ONCE daily -- but not all the time when I reboot. The listing is below.

My machine is a fairly powerful one: i74930k, 16 gb memory (Corsair), Samsung SSD 256k, Nvidia 680. I don't seem to have excessive memory usage etc.

Thanks in advance for any help.

The error:

C:\Program Files\WindowsApps\Microsoft.MicrosoftOfficeHub_17.6106.23501.0_x64__8wekyb3d8bbwe\OHub.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
c092c7f6-052b-45b7-a836-52d601d162df
Microsoft.MicrosoftOfficeHub_17.6106.23501.0_x64__8wekyb3d8bbwe
Microsoft.MicrosoftOfficeHub

:)

 

Ohub.exe pop up.

Have you ever run the Norton Removal Tool and/or the McAfee Consumer Products Removal Tool (i.e., before you installed AVG 2015
and before you upgraded to Win10)?

You're not alone! =>
https://goo.gl/WCix0I

FWIW, it would appear that OHub.exe is related to Office (2013).

 

Error 0x80070643 Getting windows update Error

The following are the errors I get with win 10 update of tuesday july 5

How can I fix ?

Thanking you in advance

Definition Update for Microsoft Office 2013 (KB3115260) 32-Bit Edition - Error 0x80070643

Update for Microsoft Office 2013 (KB3085565) 32-Bit Edition - Error 0x80070643

Update for Microsoft Office 2013 (KB3101503) 32-Bit Edition - Error 0x80070643

Update for Microsoft Office 2013 (KB3115253) 32-Bit Edition - Error 0x80070643

Update for Microsoft Office 2013 (KB3115255) 32-Bit Edition - Error 0x80070643

 

Do you have Office in Startup?

 

No, office is not in startup. But onedrive is. I wonder if the error is about onedrive and my local copy of office not conjugating???

 

It's possible. Disable OneDrive at Startup to see if it removes the error.

 

just did that. we'll see what happens.