Rob[atSound-Rehab]
Nevermind. I gave it a go and everything is fine. VS-700R and VS-700C installed on all systems with win10 #1607 without any issues (well, the issue was to get 1607 itself installed because one machine just wouldn't want to). So contrary to what is out there somewhere on the web it did not make a difference whether you come from a clean build or an in place upgrade.

Glad it all worked out for you, Rob.  It was hard for me to imagine that there'd be a significant different in OS features between a clean build and an upgrade... but you can never be certain these days on anything anymore.  Again, I really appreciate you coming through for me in such a huge way.  Glad you are up and running.

Hi I managed to get the drivers reinstalled, but when I add a control surface in Sonar Platinum the VS-700 doesn't show up as a control surface type. Do I need to reinstall something else?

synthnl
Hi I managed to get the drivers reinstalled, but when I add a control surface in Sonar Platinum the VS-700 doesn't show up as a control surface type. Do I need to reinstall something else?

Yes, there's a .dll that needs to be installed. I forget which post mentioned where to get it, but it's in here somewhere...

Well...I've finally joined the "it works in Windows 10" club for the VS700C console in standalone mode! Kudos to everyone here for their insights, persistence, and willingness to help.
 
I never had any luck until forcing the driver update, as mentioned in post #236 - the computer kept being stuck in the uninstall/reinstall infinite loop, regardless of how often I turned off driver signing, rebooted, etc. I think this may have happened for two reasons. First, Windows was in the middle of a big update, and second, I don't think I was patient enough when plugging in the controller. I saw the posts where people said it would take around 10 minutes, but when it got longer than that I bailed and rebooted - probably leaving little driver pieces scattered around that the uninstall didn't touch.
 
Also, I needed to delete the VS-700 control surface and create a new one in Preferences. No big deal, but things didn't work until I did. It did not need to emulate a Mackie' it worked fine with the V700C dll, and functions properly as a Mackie control with other software.
 
It was important to get this working because I've been planning to sell it for months due to lack of space, and also, I have a big touch screen that takes care of a lot of the VS-700C's switched functions anyway. However I didn't feel I could sell it until I verified its full functionality with Windows 10, and also so I could give it a few hours of use to make sure everything worked properly. Thanks everyone!!!
 

I want to use my VS700R temporarily on my tablet pc, but it has 32bit windows 10.
Does anyone know the correct changes to make to the RDIF1089.INF file in the "vs700_w81d_v202/files/32bit" folder?
 
OK, 1 hour after asking the above question I managed to suss it myself, so I'll leave this here in case any one else is desperately holding on to their VS700R like myself and needs to use 32bit windows 10.
I compared the original and edited 64bit RDIF1089.INF files and made relatively the same changes to the 32 bit RDIF1089.INF file.
 
IMPORTANT, THIS IS FOR 32BIT WINDOWS 10 ONLY. FOR 64BIT WINDOWS GO TO THE FIRST POST IN THIS THREAD.
So the changes I made are highlighted in bold here :
 
[Manufacturer]
%MfgName%=Roland,NTx86.6.2,NTx86.10
;[ControlFlags]
;ExcludeFromSelect=*
[Roland]
;; Windows7 - Windows2000 or Windows9X / ME
;; not supported
[Roland.NTx86.10]
;; Windows8
%RDID0089DeviceDesc%=RDID0089Install, USB\VID_0582&PID_00FD ; VS-700
%RDID0090DeviceDesc%=RDID0090Install, USB\VID_0582&PID_00FE ; VS-700 M1
%RDID0091DeviceDesc%=RDID0091Install, USB\VID_0582&PID_00FF ; VS-700 M2
%RDID0089DeviceDesc2%=RDID0089Install, USB\VID_0582&PID_0100 ; VS-700
%RDID0091DeviceDesc2%=RDID0091Install, USB\VID_0582&PID_0101 ; VS-700 M2
[Roland.NTx86.6.2]
;; not supported
 
I mentioned before in post number 153 in this thread that it takes 5 to 10 minutes to install the drivers and it looks like it is doing nothing with only the option to press cancel.
It was the same here and it did actually take just over 10 minutes.
But, if you open device manager, all of the VS700r inputs and outputs show in device manager/audio inputs and outputs after only a minute or two, so you have to wait for 8 minutes before it says finishing installation.
 
 

I am still using Win 7 PRO.  I've thought about going to WIN 10 PRO but I don't know what benefit if any I would derive. I have such a weird system, but it works. I have a 700 Rack and Console but I really am using the rack only for midi input. I bought a Lynx Hilo USB when they first came out. In personal A:B listening, the HILO conversion simply smoked the Roland 700 rack.  So, I use the V700 console for a controller, the rack for midi input, and the HILO for conversion. I've got a ADL stereo tube pre for going in. If I need more inputs at one time, I can use the rack pre's sending to the HILO via the ADAT outs to the HILO ADAT in. I use a Roland TDK30SX as a drum controller with various samples. This works pretty well as you can use the internal TDK sounds for in ears no latency drum monitoring. I guess that I am in the "if it ain't broke, don't mess with it".  Someone tried to tell me that Win 7 is no longer supported and has been discontinued. Actually, that is only partially correct.  WIN7 PRO is still being sold and installed in business application machines, DAWS, etc. 
The two lessons that I came away with out of the V Studio 700 Cakewalk by Roland episode is a firm promise to never make another purchase of a Roland product and never under any circumstance buy a hardware product that can be used by only one music software application. 
I also run Pro Tools12, Harrison Mixbuss, and Cubase.  The controller is basically a "doorstop" when using these.  I guess as long as WIN 7PRO works,  I don't see much reason to change.

stevee9c6
I am still using Win 7 PRO.  I've thought about going to WIN 10 PRO but I don't know what benefit if any I would derive. I have such a weird system, but it works.

 
you're right. I felt like that for a long time, then took the plunge in the last minute when win10 was still free to upgrade ... so now everything looks much more pretty and apart from that is the same ... expect the growing fear of every win10 update, especially since the last ones really temporarily broke things ...
 

stevee9c6
I have a 700 Rack and Console but I really am using the rack only for midi input.

 
that would be way too noisy for me - i've grown to really despise that fan noise. there is a 20$ replacement for that (e.g. ESI MIDI MATE USB cable) with even less MIDI jitter ...
 

stevee9c6
The two lessons that I came away with out of the V Studio 700 Cakewalk by Roland episode is a firm promise to never make another purchase of a Roland product and never under any circumstance buy a hardware product that can be used by only one music software application. 

 
very true. and if you print t-shirts with that on it, I will buy the first 10 !!!
 
BTW, still owning the rack and the console. the console I would not want to part with, the rack is only installed as the backup (or in case I need the fantom or ARX boards) ... meanwhile gone MOTU, not seen a proper Sonar crash since
 

Ok.. so Windows 10 64 bit just forced an update on me and this trick is no longer working. Now when I try to update the driver, Windows is complaining that:
 
"the hash for the file is not present in the specified catalog file. the file is likely corrupt or the victim of tampering". 
 
/sigh.
 
Does anyone know how to get around this. I'm really hating roland right now. 

Ok nevermind. Evidently when windows updated, it enabled driver signing again. Going through that process again, fixed it. 
 
Cheers!

Okay, so I've got a strange one here. Hopefully someone can help me suss it out.
 
I've successfully done the whole unsigned driver thing a long time ago in Win10, and it's been running great. I've had to redo it a few times when I get an OS upgrade that overwrites it, but no real issues.
 
The other day, I went into Sonar Platinum and noticed that my VS-700c wasn't working. The USB light is on, it's being recognized under "Devices", but not under "Control Surfaces". I tried reinstalling the driver (which worked), but still no dice on getting it as an option under Control Surfaces.
 
Any ideas? If I can't get it to come up, is the ACT xml data available somewhere that I could just import it?