Windows 10: Windows Office Update error code 0xc0000142 problem

Can anyone tell me how to fix this?

:)

 

error code 0xc0000142

Hi Sally,

The error code "0xc0000142" that you encountered when opening Microsoft Office applications can be caused by several factors including a recent update or corrupted data files on the system. For us to resolve your concern, kindly answer the questions below:

• Were there any recent changes made or updates installed prior to the issue occurring?
• What troubleshooting steps have you attempted?
• Which version of Microsoft Office do you have?
• Which version and build of Windows 10 is installed on your device?

As an initial recommendation, you can follow the steps on this
link to repair an Office application. The article provides a step-by-step guide for different versions of Windows and Microsoft Office.

We look forward to your response to our queries.

 

Office 365 programs: Application unable to start correctly 0xc0000142

Hi AK,

Glad to hear that you got your problem solved. In my case, the Office 365 error was related to my manual deletion of Windows.Old, so I had to do a Windows repair rather than an Office repair. But there could be multiple causes of the error code 0xC0000142.

Thanks

Brad

 

0xc0000142 error code 3 errors in total

left my computer on last night when i went to bed and when i got up today and tried to launch the sims 2 i received the following error code 0xc0000142 ing me the application cannot be started, it also happened when i tried to start any application such as notepad and i had to manually restart my pc to correct it, also in event viewer i keep getting a message regarding the usb device driver so ive uploaded a screenshot of that

and last but not least most of the time windows time and date changes on its own and cannot be updated from the internet it just says an error occurred while windows was synchronising with time.windows.com and in event viewer it says " The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized." (although i think the time thing maybe due to a low cmos battery even though my mobo is only a uear old )