It will be a shock from Win 7

Mark

I am fully aware of how different it will be.  😊 

I hated Windows 8, and was very vocal about it. As for Win 10, because of the return of the "Start" button, and many other enhancements, I think I will like this one. I know it looks a lot like Win 8, but they have some big differences. With Win 8, I resented that they refused to listen to users. It was either my way or the highway,c completely neglecting the mouse interface.

First thing I noticed is that on my Dell laptop, it does not turn the speakers off when you plug in the headphones.

Mark

dThe second thing that I noticed is that when running Cubase, VEP or anything that needed the eLiencer, I got a message saying that the eLicencer has to be upgraded.  The programs loaded, but you may not be able to run the eLicencer without upgrading it.

Mark

Next thing, when I ran Cubase 5.5.3 (64-bit) and started an empty project, I was informed that a new project folder cound not be opened.  Could not save to Steinberg folder and it was suggested I save to "Mark Folder"  instead. Ivory Steiway plugin appears to work.  VEP plugin appears to work.

Hi,

for Cubase users, post on Steinberg's website :

"While many Steinberg products have successfully been tested under Windows 10, such as WaveLab, our VST instruments and our audio interfaces running in ASIO mode, others, unfortunately, still cause problems when run on the new operating system by Microsoft. We recommend users notably of our DAWs, Cubase and Nuendo, not to update for the time being as this may lead to an increase in audio drop-outs and MIDI timing issues. We also have recognized incompatibilities when using Apple QuickTime and the Steinberg EuCon adapter, and audio interfaces won’t operate reliably in WDM audio mode either. Our engineers are examining the problems and evaluating possible solutions for affected customers. We shall immediately inform you as soon as we know more.

We’ve published a Knowledge Base article that gives a daily updated overview of Steinberg products that run smoothly under Windows. Please check the article’s included chart for current information on product compatibility."

Best.

Philippe

So I upgraded to Windows 10, and my whole experience has been a nightmare. I list them below.

1. The upgrade HOSED my computer -- it did not succeed. I was left with a totally unbootable computer.

      Solution: I created a bootable USB with Microsof Media Creation Tool using my wife's laptop.

      Next problem: Computer would not boot from USB.

      Solution: Change bios settings (turn on UEFI).

      Next problem: Would not install to my new SSD as it could not recognize the partition (even though it was there).          

         Solution: I had to delete the partition, recreate it, and finally reformat the hard drive. FYI, this was for a newly bought SSD.

Win 10 successfully installed...

Upgrade is still going on... My Cubase 8 Pro has not been fully migrated.

Ya know, I don't understand this desire some people have of constantly wanting to have the newest freshest gadget, software, or OS to come down the pike😕  Just because it's new doesn't mean you need it and you have to have it.

One of my motos has always been "If it ain't broke don't fix it."  I still use a system from 2007 that has XP.  After all these years, it still works fine and I use it almost daily.  However, my new system is a Windows 8 and it's been like pulling teeth to get that thing to cooperate.

For example, I plugged an external harddrive into the machine and W8 wouldn't read it.  I tried all of the USB ports and still would not let me open the files on the drive.  W8 aknowledged that there was, in fact, an external storage device plugged in but It refused to let me access the files.  I ended up having to manually assign a drive letter to the external device because W8 has been programmed to assume that any large external device is partitioned and therefore won't assign a drive letter.  The problem is, I have to do this everytime I plug that device into the machine😕

What a pain in the $crotum sack😠😤😠😤

I did not like W7 and I hate W8 if Microsoft continues it's current trajectory, by W10 I'll seriously consider switching to a Mac.  But that would be contigent upon me getting over Apple's arrogant business practices and overpriced products.

@jasensmith said:

I did not like W7 and I hate W8 if Microsoft continues it's current trajectory, by W10 I'll seriously consider switching to a Mac.

The snag is that Windows is becoming more and more like OSX so it could be a frying pan/fire situation... 😠

DG

Well, I had Win 7 and never upgraded to Win 8 or Win 8.1. I hated Win 8 with a passion.

With Win 10, I really like it, and combine the fact that my computer was getting bloated, I realised I needed a fresh install of the OS, sooner or later, so I took the dive --  I wasn't gonna do a fresh install of Win 7.

So now I have a fresh install of Win 10, and to be honest, I am thrilled. Why? Because of this upgrade process, I managed to get my projects from 10 years ago opening up and all plugins properly resolving. I never did this with Win 7 as there were problems with some of them under JBridge.

Just to see my super old projects opening up with no missing plugins or issues, was awesome! I was in 7th heaven last night. 😇

There are some few quirks here and there, but I can wait.

@nektarios said:

So now I have a fresh install of Win 10, and to be honest, I am thrilled.

Okay, this is definately encouraging and thank you for posting this report. 

Like you, I have older material that I would like to reexplore with my new toys so, again, thanks for the report.

All of my 2005 projects opened just fine. I was never able to do this under Win 7, because JBridge was not interpreting some plugins correctly -- but now it was under Win 10. It may be because I was forced to regenerate the bridge files from scratch with a new version of JBridge. 

Be warned: Even though I am able to open my old projects, I still haven't managed to open any of my VSL projects. Seems to be an issue with the eLicenser -- looks like it can't have two applications accessing it at once. 

So I managed to fix the eLicenser issue: You need to install it as an administrator. Right Click->Properties go to Compatibility Tab, and select: Run as Administrator at the bottom.

Despite solving this, smy VE Pro still won't connect with my Cubase. It's not even visible.

Just to let everyone know, my VE PRO projects under Windows 10 open fine now.