Office 2019 Click-to-Run Error 0xc0000142

[Ballzy-x7]

I've created a package within SCCM for Office 2019 and it deploys and installs successfully but when running any of the Office applications, all users (including admins) get an error 'The application was unable to start correctly (0xc0000142).'

 

Looking at the logs I can see the following:

 

Microsoft-AppV-ServiceLog]2020-Dec-07 08:42:19.072 - Vfs: [4180].[7852]: ERROR: Failed to load VFS mappings. Error code: 2 [vfs_configuration_loader_helper::initialize_detokenizer; 300]

 

[0]1054.1EAC::2020-12-07 08:42:19.081184200 [Microsoft-AppV-ServiceLog]2020-Dec-07 08:42:19.072 - Vfs: [4180].[7852]: ERROR: Failed to load runtime configurations. Error code: 0x8F10252A-00000002 [vfs_runtime::start_runtime_internal; 103]

 

[0]1054.1EAC::2020-12-07 08:42:19.081197700 [Microsoft-AppV-ServiceLog]2020-Dec-07 08:42:19.072 - SubsystemController: [4180].[7852]: ERROR: start_runtime() failed on Virtual Filesystem subsystem. Error 10308780409369919490. [AppV::Client::Virtualization::VirtualEnvironment::start_runtimes; 105]

 

[0]1054.1EAC::2020-12-07 08:42:19.081201100 [Microsoft-AppV-Client]Process 9468 failed to start due to Virtual Filesystem subsystem failure. Package ID {9ac08e99-230b-47e8-9721-4577b7f124ea}. Version ID {1a8308c7-90d1-4200-b16e-646f163a08e8}. Error: 0x8F10252A-0x2

 

Error: 0x8F10252A-0x2 appears to imply a folder is missing (System Error Codes (0-499) (WinError.h) - Win32 apps | Microsoft Docs) but I cant work out where from.

Start Menu is re-directed but AppData is not and user profiles are all local with UEV enabled.

 

Any ideas?

[ITGuyNW]

Did you or anyone ever solve this? Done feature update from 1909 to 21H2 and every Office app now has the same 0xc0000142 error. Fresh installs of 21H2 are fine.

[MatthewL]

I've just looked in my notes had a similar issues although cannot remember the full details following an update and I have noted to run this in future:

 

“C:\Program Files\Microsoft Office 15\ClientX64\OfficeClickToRun.exe” scenario=Repair system=x64 culture=en-us RepairType=FullRepair DisplayLevel=True

[ITGuyNW]

For future reference what I did was...

 

log on the machine as admin

right click word and run as admin

change key (even if its existing key)

close word and reopen to prompt activation box

activate and should be all good

 

It seems the feature update from 1909 to 21H2 was causing Office to reactivate and it was getting stuck.