Like many, I've struggled with URC CCP USB drivers. After a bunch of trial/error, here's the quite simple process I use every time. I have only used x64 versions of Windows, so I don't know if the x32 versions work differently, but it's likely there is zero difference.

This has worked on Win 7, Win 8, Win 8.1, and Win 10 (all releases)

Notes:
Note 1: Use a USB 2.0 port, although my PC works with USB 3 as well. Why? Your PC/Laptop may use a different chip (Intel, ASMedia...) for different USB ports. This is why you often see people say to try different ports. Also, some ports may be getting more/less power. So... if if you find a port that works, remember which one you used and stick with it to get the remote programmed. Try others later or if the one you picked doesn't work. You may have to install the driver again for different ports. You'll know this happens because you'll see an Unknown Device in Device Manager and you know you just fixed that problem. Oh, avoid USB hubs and save yourself some potential headache (they may work just fine for you but YMMV).

Note 2: Just because you got the Unknown Device item in Device Manager to go away by installing a driver Windows didn't reject, it doesn't mean your remote will up/download. You'll have to open CCP and try a download to the remote. I never had to reboot during this process (unless you need to use an unsigned driver - see Note 7 below).

Note 3: I didn't have to use any compatibility mode settings or run as administrator for the program (icon or shortcut icon). I am a local admin and I keep User Account Control at the lowest setting out of practice.  SOME posts said UAC got in the way if it wasn't at the lowest (off) setting.  If you like it on, set it to the lowest setting for the install and push it back up after.

Note 4: All the files are under your CCP base/root directory and NO additional downloads were required if only using URC drivers.  The Windows Mobile approach did need additional installs.

Note 5: Allow CCP to run through all its updates if they are needed first.

Note 6: Don't go hunting for 'better' or newer drivers. If you get one working, just be happy and get actual work done;).

Note 7: If you need to install a driver that isn't digitally signed (like the one I had used), Google instructions on how to disable driver signing checks. The quick way is to hold the Shift key while you select Restart in later versions of Windows.

In Win 8 onward, hold Shift key and select restart, next screen-Troubleshoot, next screen-Advanced, next screen-Startup Options, next screen-Reboot button (lower right). After reboot, press F7 (not "7") and your PC will reboot and you shouldn't see any messages or changes to the UI.  It will allow you to install an unsigned driver. This mode only lasts for one boot. Once you reboot, driver signing is automatically re-enabled so you don't have to worry about something being left off.

Note 8: Don't worry if you're on a version of Windows newer than Vista and you only find a Vista driver folder. URC isn't on the cutting edge of driver tech, so the old stuff still works in my testing from Win 7 through Win 10.

Initial Prep:
1. I always install the latest Intel Chipset INF files using the .exe version (less to think about). If you haven't done this in a while, it's a good practice and can't hurt (afaik). This link works today, but search for Intel Chipset INF Utiliity to get the latest version. Intel has a good practice of putting the word (latest) somewhere on the page (ex. Version: 10.0.27 (Latest)

[Link: downloadcenter.intel.com]

2. From reading many, many posts, I saw folks say installing the following were necessary. For me, I did NOT have to do this to use only the URC drivers. If you're going to try the Windows Mobile Device driver approach, they are likely needed. There should be zero downside to your computer except installing software MS abandoned a while ago.

• Install (as admin if you can) USB\drvupdate-amd64.exe
  • NOT FOR MX-880 (see post below).  
• Install (as adminif you can) MX-880\Drivers\devinst64.exe

Note: The drvupdate-amd64.exe file is the EXACT same file you'll get if you go and download the "Microsoft Windows Mobile Device Center 6.1 for Windows Vista".

[Link: microsoft.com]

I couldn't find a more recent version than 6.1 and it's dated 2012.  This is why it's likely included in the CCP install b/c it hasn't changed. Some people reported they were able to get their remote to work with only the MDC drivers installed. I never tried because I know the URC USB drivers work for my setup (multiple PCs and laptops).


Driver Install:

1. I used the "have disk" method. This is described all over the internet, but here's the quick steps:

• Double click on the Unknown Driver or the device that isn't working
• Go to the Driver tab
• Click the Update Driver button
• Press the bottom option "Browse my computer..."
• Press the bottom option "Let me pick from a list..."
• Press the "Have Disk" button to get the browse window. If you don't see a Have Disk button but just a list, just press Next and you'll get the browse window.
• HUGE NOTE: If you see "This driver is not digitally signed" at any point, see Note 7 above to turn off digital signing to allow you to install it. Turn off signing and start this section again.
• Pick the .inf file and press Open. The .inf file is a text file that describes the driver(s) it relates to. Feel free to open it and have a look if you're curious. This is why you don't see a .sys (actual driver file in most cases) in the pick list. Windows wants the .inf to figure out if the associated driver files will install (notice I don't say "work")
• The driver is installed, now test. If that driver didn't work, keep on trying until you find one that works.

Note: The only remotes that have their own Drivers folder are: MX-980, MX-880, MX-6000, MX-5000, MSC-400. I just did a simple folder name search for this. IF you have a different remote that doesn't have its own Drivers folder, you'll have to trial/error with the drivers in the USB folder.

2. The driver I found that worked is located here:

• [Your CCP root directory name]\MX-880\Drivers\Windows Vista\64-bits
• I used "URC_USB_Sync_FW1.inf"

3. Unknown Device in Device Manager will disappear!

4. ​Connect your remote and test with a download.  Windows picked URC_USB_SYNC_FW.sys.

• Win 10 put the device under Universal Serial Bus Controllers section
• The device name is URC USB Sync FW1
• To see the actual driver file, connect your remote to see it in Device Manager, double-cllck on the device (URC USB Sync FW1), Driver tab, Driver Details button. The version reported is 2000.416.2008.0.

I only have MX-880 remotes, so I suspect you'll likely have to go through trial/error with the drivers in the USB folder if you don't have a version with a Drivers folder.

This was painful for me to get all the trial/error done, hopefully this helps for you!!!