Most api-ms-win-core-path-l1-1-0.dll errors are related to missing or corrupt api-ms-win-core-path-l1-1-0.dll files.

More specifically, these api-ms-win-core-path-l1-1-0.dll errors can be caused by:

Invalid or corrupt api-ms-win-core-path-l1-1-0.dll registry entry.
Virus or malware infection which has corrupted the api-ms-win-core-path-l1-1-0.dll file.

Microsoft hardware failure, such as a bad hard drive, which has corrupted the api-ms-win-core-path-l1-1-0.dll file.

Another program overwrote the required version of api-ms-win-core-path-l1-1-0.dll.

Another program maliciously or mistakenly deleted the api-ms-win-core-path-l1-1-0.dll file.
Another program uninstalled the api-ms-win-core-path-l1-1-0.dll file.

In line with this, I would like to know more and I would appreciate if you can provide the following information:

Were there any changes you made before this issue occur?
What actions were you performing that resulted to this error message?
Do you have Lync add-on in Internet Explorer?

What are the troubleshooting steps you have done so far?

Moreover, we’ve got a few handy solutions for you to try:

* Use the System File Checker tool to repair missing or corrupted system files

* Create a test profile and see if the issue will occur. If not, this will give us an another angle to look at as it could be a corrupted profile.

... Can you find that and share it here?

it can be difficult to get files from the slot directory after a failure since they are all deleted the instant the task finishes. might be easier to instruct users how to run the app offline so that it's not deleted by BOINC when the task finishes

Those of you on Windows 7, when the app crashes, check the slot folder and post the contents of a file called "stderr_file"

I don't have any Windows 7 machines to test on, so this will be helpful in diagnosing the issue.

Stderr output
<core_client_version>8.0.4</core_client_version>
<![CDATA[
<message>
(unknown error) (87) - exit code 195 (0xc3)</message>
<stderr_txt>
23:27:36 (2892): wrapper (7.7.26016): starting
23:27:36 (2892): wrapper: running .\client-windows.exe ( --device config-001-hixorlo-fullinfo-rank100-genfix.npz 1500000 21668 input.npz)
23:27:40 (2892): .\client-windows.exe exited; CPU time 0.000000
23:27:40 (2892): app exit status: 0xffffffff
23:27:40 (2892): called boinc_finish(195)

</stderr_txt>
]]>

10/23/2021 14:25:43 | | [http] HTTP_OP::libcurl_exec(): ca-bundle set
10/23/2021 14:25:43 | minecrafthome | Scheduler request completed
10/23/2021 14:25:43 | minecrafthome | Server error: feeder not running
10/23/2021 14:25:43 | minecrafthome | Project requested delay of 3600 seconds

Program Host Status
Download server minecraftathome.com Running
Upload server minecraftathome.com Running
Scheduler minecrafthome Running
feeder minecrafthome Not Running
transitioner minecrafthome Not Running
file_deleter minecrafthome Not Running

Anybody been able to pull any of the new x86 One-Chunk tasks yet from the project?
Says unable to pull cpu work

It is not a beta project anymore correct?

This site can’t be reached
54.242.200.224 refused to connect.

Where's the Beef?

Application 	Unsent 	In progress 	Runtime of last 100 tasks in hours: average, min, max 	Users in last 24 hours
Multichunk population seed cactus stacking 	0 	433 	1.11 (0.25 - 15.76) 	181
Singlechunk population seed cactus stacking 	0 	20 	0.23 (0.21 - 0.25) 	2

Task data as of 18 Aug 2020, 0:17:49 UTC

Tasks ready to send	360
Tasks in progress	453

Computing status
Work
Tasks ready to send	360
Tasks in progress	4397
Workunits waiting for validation	0
Workunits waiting for assimilation	842
Workunits waiting for file deletion	0
Tasks waiting for file deletion	0
Transitioner backlog (hours)	0.00

Tasks by application
Application	Unsent	In progress	Runtime of last 100 tasks in hours: average, min, max	Users in last 24 hours
Multichunk population seed cactus stacking	0	3506	0.95 (0.13 - 24.81)	570
Singlechunk population seed cactus stacking	0	891	0.15 (0.04 - 2.04)	220