PICKIT3 requires adminstrative privilege - Page 1
Forum section: electronics / general

author: MIS42N
author_rank: Frequent Contributor
timestamp: November 04, 2021, 12:21:11 pm
content: *** SOLVED (sort of) - see my post #5 ***I write PIC assembler using MPLAB X V5.35 - the latest to support MPASM.A few days ago, my PICKIT3 programmer was "lost" to MPLAB. I run using Windows 10 and an account with only user privilege. In frustration I eventually reinstalled MPLAB but it still wouldn't see the PICKIT3. I then tried the same thing with a privileged account and it worked. So now it works in a privileged account but not in a user account.The PICkit is most likely a Chinese knock off, but it has worked flawlessly until now. And I can't see how using a privileged account v. unprivileged would change how the hardware works. It looks like a software problem. But what?The workaround is simple, use the privileged account. But I want to know why this happened. Anyone else experience this? Any idea where to look to fix it?

author: MarkF
author_rank: Super Contributor
timestamp: November 04, 2021, 03:59:34 pm
content: I just went down this rabbit hole on my Win10 and Win7 laptops.Neither machine could see my PicKit3 with newer versions on MPLAB X.Administrator privileges didn't work for me.The only way I was able to get my PicKit3 to work was by falling back to an older version of MPLAB X.I'm currently running version 3.65 on all my machines without any more issues (Win 10, 7 and XP).What can you do?

author: Dabbot
author_rank: Regular Contributor
timestamp: November 04, 2021, 08:04:51 pm
content: Did you try resetting the MPLAB X application data directories?1) Close MPLAB X2) Navigate to %AppData%\mplab_ide\dev (copy and paste to Windows Explorer)3) Rename the folder corresponding to the version giving you trouble. (E.g., change "v5.35" to "v5.35_old")4) Navigate to %LocalAppData%\mplab_ide\Cache\dev (copy and paste to Windows Explorer)5) Rename the folder corresponding to the version giving you trouble. (E.g., change "v5.35" to "v5.35_old")6) Open MPLAB X. You will need to configure the IDE again.

author: MarkF
author_rank: Super Contributor
timestamp: November 04, 2021, 08:59:01 pm
content: I totally uninstalled MPLAB X and every directory associated with it.Deleted the 'Program Files\MPLABX', '%AppData%\Local\mplab_ide' and '%AppData%\Roaming\mplab_ide' directories.Then, reinstalled a fresh copy of MPLAB.No joy.It would partially see the PicKit. But when you tried to use it, MPLAB saw a bogus USB Id and would fail.

author: rstofer
author_rank: Super Contributor
timestamp: November 04, 2021, 09:47:57 pm
content: Can you 'Run As Administrator' when you start MPLAB?Type MPLAB into the search box at the lower left of the desktop and then right-click on the application. Select 'Run As Administrator' and see what happens.

author: MIS42N
author_rank: Frequent Contributor
timestamp: November 04, 2021, 10:06:07 pm
content: Quote from: rstofer on November 04, 2021, 09:47:57 pmYes - I forgot to add that worked also.SOLVED (well - problem gone away). I deleted the directories '%AppData%\Local\mplab_ide' and '%AppData%\Roaming\mplab_ide'When I ran MPLAB it didn't know about any projects. So I navigated to the project and opened it. PICkit working.A note. Now when I start MPLAB, a little balloon appears [5 updates found]. I think a few days ago I clicked on the balloon and that's possibly the cause of my problems. It was several days before "the troubles" but I don't think I had stopped MPLAB after that. It was a few days later that I shut the machine down to move it to another room and the PICkit refused to work after the reboot. When I switched to the administrator account that balloon appeared again. In my non privileged account that balloon didn't appear.So maybe I should run MPLAB from the administrator account, do those updates, and see if it works after that. But guess what. It works now. If it ain't broke, don't fix it. I shall ignore that little balloon from now on.

author: Dabbot
author_rank: Regular Contributor
timestamp: November 04, 2021, 11:51:13 pm
content: Quote from: MarkF on November 04, 2021, 03:59:34 pmThat's a weird issue alright. It sounds like some funny business with the PICKit 3 itself. Do you know what firmware version is loaded?

author: MarkF
author_rank: Super Contributor
timestamp: November 07, 2021, 12:52:43 pm
content: If I'm not mistaken, MPLAB X installs the latest firmware version contained in the MPLAB install itself.But, the process I had to use was to install the PicKit 3 firmware via the 'PICkit3 Programmer Application v3.10' tool from Microchip (found on their archive site). After updating the PicKit firmware and switching back to MPLAB mode, the PicKit was found by MPLAB. Then during the programming the end MCU, MPLAB updates the PicKit firmware with the newest contained within the MPLAB version.Which is file 'PK3FW_014909.jam' for MPLAB X version 3.65.Not sure what the latest version is since I don't want to mess up my current MPLAB install.

author: Dabbot
author_rank: Regular Contributor
timestamp: November 07, 2021, 10:19:46 pm
content: Quote from: MarkF on November 07, 2021, 12:52:43 pmIt will tell you when you use it to program a chip. You don't even need a chip connected, as it checks the firmware loaded before going ahead.Look at thePICkit 3tab in theOutput. Mine, for example:Code:*****************************************************Connecting to MPLAB PICkit 3...Currently loaded firmware on PICkit 3Firmware Suite Version.....01.56.09Firmware type..............Enhanced Midrange