problem with BR 80 drivers and windows 7

[Krasi]

I need help 

I'm trying to use my br 80 as an audio interface. Following all steps but every time I try to install the driver it says problem may have occurred, then asks me to run uninstall and try again. I do that several times with no effect. Same story repeats again and again. Downloaded the setup from their site as well thinking I may have had wrong file. No change I'm so frustrated and need any advice to help me with this issue. Thanks in advance!!

[Krasi]

Re:Cannot re-install new driver after uninstalling old driver. - December 26, 10 2:35 PM ( #3 )
I just spent hours trying to figure out how to uninstall/re-install the Win 7 drivers for the UA-25EX.  Using the Windows uninstaller did not work for me.  Prior to solving, I was seeing essentially the same error message:
UA-25EX Driver Ver.1.0.0

A problem may have occurred.

To install the driver, please execute Uninstal.exe (located in the same folder as Setup.exe), and then execute Setup.exe once again.
After trying the CleanAll.exe utility from Roland (which only runs in Win2000 compat mode and doesn't solve the problem) and a lot of manual registry hacking, I finally found the following solution for re-installing the drivers, based on the Microsoft web page titled Remove a Driver Package from the Driver Store

1) download the driver files to a local directory.    Specifically, in my case I downloaded the Win7 x64 drivers and unzipped them to a directory called ua25es_w764d_v100. 
2) run cmd.exe to open a command prompt, and "cd" to the directory ua25ex_w764d_v100.
3) Then cd to the subdirectory "Files"
4) There should be a single file with the .INF extension.  In my case, the file was called RDIF1079.INF
5) to install the driver, run the command:

   pnputil.exe -i -a  rdif1079.inf

That command reported that it successfully installed the driver.

After these steps, my Windows 7 laptop once again recognized my UA-25EX when I plugged it into one of the USB ports on the laptop.

p.s. I'm really pissed at either Microsoft or Cakewalk/Roland for creating this mess.  I just spent about 8 hours debugging this issue -  not how I planned to xmas afternoon.

I found this in a cakewalk forum so isn't just me with this issue. Apparently this guy blames either microsoft or roland for "creating this mess". I managed to sort my issue following exactly what the guy have said so anyone experiencing the same problem here is the solution.