I had not tried to use my UM-880 for a while - after I did an upgrade to the Sonar Platinum as I was just not seeing the location to see the patches. I emailed them and after a VERY long delay got a reply but did not have time to look at again for another VERY long time. When I went to try I found the UM880 not available.. and found this thread. I think at the start I had edited the definition file - but the key for me was to uninstall - and do the UNSIGNED Driver install on Windows 10. Then the installer installs with a big warning - but it installs and works otherwise it just declined to install at all - this is using the 8.1 driver from Roland. (I have a memory of editing the manufacturer definition file in the setups - but it literally was at least 7 months ago). The Shift-Click on Restart to get the special options and then telling the setup to disable signed driver check (Number 7 or F7) and that allowed the driver install.

Note of caution folks. The Windows 10 update (patch Tuesday) of 6.14.2017 seems to have broken the UM-880 driver install in a new and problematic way. I have a correctly modified .inf, and run the BCEdit turn driver signing off command. I have successfully reinstalled UM-880 drivers following previous Windows updates without issue.
I'll note I was under a time constraint this morning and didn't have time to investigate. I did see a Windows pop error about a file hash being wrong and possibly tampered with. I'll be trying again tonight or tomorrow.
For right now my DAW is totally crippled, so be cautious with the update.

Driver "signing" (one part of that, it checks to see if the driver has been hacked) has been enhanced in newer Win 10 builds.  I've seen other software/devices that will no longer work under Win 10.  Since the Roland/Edirol drivers need to be hacked, this MAY be an issue with driver signing.  
 
I had a PCR500 and it initially worked OK with the hack driver and Win 10 but the Anniversary upgrade caused problems and I finally gave up.  I sold the PCR500 to a person that is still on Win 7 and can use it.  

                 

Follow up on this is I did get the driver to load. Didn't really have to do anything differently. Disable integrity checks and driver signing, use the modified .inf for the installer. I did notice when restarting after disabling driver signing Windows was still saying 'Configuring Windows updates'. This PC had already booted multiple times during the update and had put me through the whole 'Hi we're setting a few things up' screens (or whatever that says), yet apparently I had not been patient enough.
There is nothing in the update that was worth the nuisance for usage as a DAW. And Microsoft decided to make it harder to get to Control Panel and a cmd prompt by removing them from right clicking on start, because I guess we needed that.
In the end I suppose the blame is still directed at Roland for refusing to just basically take the same driver they've got and getting it signed for Windows 10. For me, my MIDI setup is fairly complex, including some multi port drum maps, and there are over 350 projects to deal with. Converting that all over to a new interface is not a trivial task. I'd much rather be just creating music. I guess all the money I spend on Vdrums, SPD's, Fantom, Integra, etc., doesn't mean anything to Roland.
 

Here is a comment from a security expert on another forum:

 
The Patch Tuesday Windows updates are vitally important for your Windows computers' security. The Shadow Brokers have released more of the exploits stolen from the NSA and are prepping them for zero day attacks. Microsoft has responded by creating special patches to block the most prevalent methods of exploitation. Updates are even being offered to people running the out-of-support Windows XP and Server 2003.
 

Most of the Roland hardware, that is supported, now has Windows 10 "plug and play" drivers (built into Windows drivers).  The old products have to be hacked, if possible, to make them work in Win 10.

Yes, true enough, everybody security is beating their chest how dangerous the threat landscape is and how important they are to IT. I won't derail this important thread for Edirol/Win 10 users other than to note the first Ransomware exploit was predicated around an obscure exploit in SMB 1.0. Hardly an issue for Windows 10 users.
Nonetheless, Microsoft will likely be releasing a steady stream of exploit patches for the foreseeable future.
Hopefully by temporarily disabling integrity checks and driver signing those of us relying on the tips from this thread will continue to have usable Edirol devices (perfectly good hardware, just abandoned by the manufacturer).

I just want to share what I found joy the UM-880 again. I did take it out from the rack and just about to junk it, but my conscience doesn't clear why Roland make such junk. It should be a way to work. I get try and try again.
Here is How to make the Edirol UM-880 work with the w8.1 driver work. Download the latest driver from the Roland website. https://www.roland.com/global/support/by_product/um-880/updates_drivers/ > install it to your computer, >Plug and turn on your UM-880, >Restart your computer, >After your PC back, type UM-880 to the searching bar, >When it pop up, right click on the UM-880 icon and click "Run as Administrator" and restart your computer. After you PC on, make sure your system channel output must be flashing. It works again. I love it!
 
my PC: Intel (r) Core(TM) i7-4790 CPU @.6GHz

My findings for future reference.  Both the .INF update and disabling driver signing were necessary steps:
1. Uninstall broken driver / 'Unknown Device' from device manager if necessary.
2. Update [Manufacturer] section in the .INF file to add a Windows10 option:
;---------------------------------------------------------------;

[Manufacturer]
%MfgName%=Roland,NTamd64.6.2,NTamd64.10

;[ControlFlags]
;ExcludeFromSelect=*

[Roland]
;; Windows7 - Windows XP 64
;; not supported

[Roland.NTamd64.6.2]
;; Windows8
%RDID0015DeviceDesc%=RDID0015Install, USB\VID_0582&PID_0014 ; UM-880

[Roland.NTamd64.10]
;; Windows10
%RDID0015DeviceDesc%=RDID0015Install, USB\VID_0582&PID_0014 ; UM-880

;===============================================================;


3. [Shift] + restart Windows 10.  Buried at the end of the resulting page menu is an option to restart disabling driver signing... restart.
4.  Install driver as instructed allowing unsigned installation on resulting dialog.