Windows XP was for Windows eXPerience, Windows NT was New Technology and Windows ME was Millenium Edition. Not that it leaves us any the wiser !
 
I have what would be called an aging Q6600 but beefed up with SSD for OS and other separate drives for samplea and projects, additional memory and 3 monitor video card and whilst it was good on Win 7 Pro 64-bit, since my Win 10 upgrade it is even snappier, and DPC latency has dropped too. So, I'm all for it.

The Kiosk Project
Windows XP was for Windows eXPerience, Windows NT was New Technology and Windows ME was Millenium Edition. Not that it leaves us any the wiser !
 
I have what would be called an aging Q6600 but beefed up with SSD for OS and other separate drives for samplea and projects, additional memory and 3 monitor video card and whilst it was good on Win 7 Pro 64-bit, since my Win 10 upgrade it is even snappier, and DPC latency has dropped too. So, I'm all for it.

 I've got a Q6600 running on W10. Despite it's lower clock @ 2.4 it's the architecture that makes it great.

Just updated to the updated version of Windows10. XLN decided I now have a new OS and wouldn't allow AD to start. I had to uninstall the computer from the XLN installer and install the "new" computer. I wonder if I have to jump through these hoops with other programs or VST's. Sonar itself didn't seem to mind.

Sonar 2015 is Windows 10 compatible. We may need to inform XLN that Win 10 compatibility is highly desirable. 

John
Sonar 2015 is Windows 10 compatible. We may need to inform XLN that Win 10 compatibility is highly desirable. 

What incompatibility?

They simply require reregistration when the OS changes, that's by design it appears. Whilst it might be a pain in the ass to do it for some, I don't see this as being unreasonable, esp as it's a one time operation with an OS upgrade. It's a pretty simple operation.

Doktor Avalanche

John
Sonar 2015 is Windows 10 compatible. We may need to inform XLN that Win 10 compatibility is highly desirable. 

What incompatibility?

They simply require reregistration when the OS changes, that's by design it appears. Whilst it might be a pain in the ass to do it for some, I don't see this as being unreasonable, esp as it's a one time operation with an OS upgrade. It's a pretty simple operation.

Yes, but if memory serves me, this one time operation has thus far had to be performed twice by some folk, if not all, at the initial change over to Win10, and now again, and who knows how many times in the future. I can't recall if I had to do it or not when I upgraded to Win10, and haven't had to do it this time around so far, as said update may not have reached me yet.

Doktor Avalanche

John
Sonar 2015 is Windows 10 compatible. We may need to inform XLN that Win 10 compatibility is highly desirable. 

What incompatibility?

They simply require reregistration when the OS changes, that's by design it appears. Whilst it might be a pain in the ass to do it for some, I don't see this as being unreasonable, esp as it's a one time operation with an OS upgrade. It's a pretty simple operation.

The OS hasn't changed. Its still Windows 10. Plus I know of no other program that has the same problem. BFD 3 doesn't. 

Then MS are sending major updates that are making it think it's a different OS or XLN have tightened up their code and are making people reregister again or there is some issue with the XLN code and they need to losen it up (if they are willing).

From this I would not state that AD2 is incompatible with windows 10 however. You can still use it.

I have fully upgraded / updated both my pc' s to Win 10, and I have near to no issues on both. Win 10 has been a win (win) situation for me so far. I did it more on a whim than anything else. All my plugs and Vsti works as they should on my end. My issues so far have been pilot errors...

Doktor Avalanche

John
Sonar 2015 is Windows 10 compatible. We may need to inform XLN that Win 10 compatibility is highly desirable. 

What incompatibility?

They simply require reregistration when the OS changes, that's by design it appears. Whilst it might be a pain in the ass to do it for some, I don't see this as being unreasonable, esp as it's a one time operation with an OS upgrade. It's a pretty simple operation.

 That is a flaw in XLN's authorization. I don't think anything else in W10 needs to be reauthorized.