Which are you currently using?
Once Windows boots up, reinstall the drivers using the manual method outlined in Step 1. 3. Configure the Correct COM Port
Expand the Ports (COM & LPT) or Universal Serial Bus controllers section.
Many users report that the device manager recognizes the iPROG and the drivers appear correctly installed. The software may even detect the programmer at the port level, but it will still refuse to operate, displaying the persistent "not connected" error. iprog programmer not connected new
Based on user experiences and technical analysis, the "Programmer not connected" error can stem from several root causes:
Go to Device Manager → Ports → iPROG universal programmer, right-click, go to Properties → Port Settings → Advanced, and set the COM port number to 4 or a lower number.
Most "Not Connected" errors stem from Windows automatically installing an incompatible driver. Which are you currently using
Many users report that iPROG programmers work better on Windows 7, particularly 32-bit systems, while Windows 10 can be problematic. Some users experience delays between operations, with the programmer appearing disconnected or taking a minute to respond to the next script command.
If you see any listed in your Device Manager
Is disabled if using Windows 10/11?
Without administrative privileges, the software might be blocked from opening the local COM ports required to communicate with the USB hardware. Right-click the iprog.exe executable file. Select . Go to the Compatibility tab.
Press Win + X and select Device Manager . Look for an item under Other devices or Universal Serial Bus controllers labeled "FT232R USB UART" or "iProg" with a yellow warning triangle.