Can't get mikroprog to connect with PIC18F4620

[amfortas]

I must be missing something!

I re-installed Microprog Suite and purchased a new Microprog but cannot get connection to a PIC18F4620. Running new Windows10 64 bit. computer.
I purchased the new Microprog because of this problem.

Looking at the drivers I have USB 18F USB Communications Device (x64) installed and Device is Working Properly.

I run Mikroprog Suite and select PIC18F4620 but fails to read contents. Try Reading Voltages and get Cannot communicate with hardware message.

Microprog loads .hex file O.K.

The one thing I cannot undertstand is that the Microprocessor Pinout is shown as 40(36) when the actual device is 44pin TQFP. The connection to the .pdf file shows the correct device data
I am using both 5pin and 10 pin access correctly wired and successful for about a decade.

I have re-installed after extracting the .zip file.

I only use PIC18F4620 devices in all my products so I cannot test device pinout error theory.

A very unexpected problem which started with new computer installation.

Any ideas ?

Amfortas

[amfortas]

Added detailes 1) Show devices does not detect Microprog.
2) Yellow and Green LEDS lit.

[amfortas]

Work completely at a standstill. I have reloaded Mikroprog Suite and Mikro prog drivers many times and still cannot find MikroProg.
Initially felt MikroProg might have been faulty but new device shows identical refusal to communicate and drivers appear to be working and showing programmer in Device Manager.
Nil response from the forum suggests no obvious answer which is why I can't sort it out . Help!

Thanks,
Amfortas

[amfortas]

Tried Loading MikroProg Suite and Drivers into my laptop Win10 and everything works fine !
Seems my main computer is causing problems. It works with all other USB devices so it does not like MikroProg. A great pity because I do !
Anyone experienced this sort of problem with a computer ?

Many thanks,
Amfortas

[amfortas]

Concluding this thread, Mikroprog ran fine in my main computer after opening as administrator. The mystery remaining is simply why my Win10 installation required administrator authority to secure proper USB communications for Mikroprog Suite.
That could be up to many topics within my installation and use of WIN10.

An unexpected but interesting problem.

Amfortas