Stuck on first attempt using MPLAB X (PICkit4)

[Demon]

Thanks for the ideas. You got me started playing with the command window directly, noticed differences by playing with parameter syntax.

I've removed the ".X" suffix on the folder as well as replace a SPACE for an UNDERSCORE; just to be sure. I get identical results from the powershell window and MCS+5.

I've also added the -W option; my PIC is not powered. It's on the MeLabs 8-40 pin ZIF adapter PCB.

C:\MPLABX\v6.05\mplab_platform\mplab_ipe\ipecmd.exe -TSBUR223673449 -P16F877 -FK:\Project_v2\PBP\Test_1_16F877_Blinky\Blinky_16F877.HEX -E -M -OB -OL -OV -W -Y

DFP Version Used : PIC16Fxxx_DFP,1.3.42,Microchip
Selected Programming Tool Sno: 
BUR223673449
*****************************************************
Transmission on endpoint 2 failed (err = -109)
A communication error with the debug tool has occurred. The tool will attempt to recover momentarily. A log of the error was created at C:\Users\Papa\queuelogs\debugtool
Connection Failed.
Transmission on endpoint 2 failed (err = -109)
*****************************************************
Transmission on endpoint 2 failed (err = -109)
A communication error with the debug tool has occurred. The tool will attempt to recover momentarily. A log of the error was created at C:\Users\Papa\queuelogs\debugtool
Connection Failed.
Transmission on endpoint 2 failed (err = -109)
Erase Target Failed.

I'm including a PDF of the log file.

debugtool.pdf

NOTE FOR THE NEXT PERSON: look at CommandLineReadmes.htm in C:\MPLABX\v6.05\docs; the very first item is IPECMD.EXE, and it states that it supports PK4. The ReadMe has a detailed list of command line options available for IPECMD.EXE.