Well, I've been running this build since it came out a while ago, and at first I was having lots of issues with Sonar (Ipswich update 1) stability. Lots of freezes, mostly, and terrible audio issues. That's life on the bleeding edge, right? I uninstalled and reinstalled the MOTU Firewire device drivers and I haven't had any issues with Sonar stability since then. This Windows 10 update just feels more solid, complete and generally well-performing than any one I've used so far. It's not clear to me how MS plans to roll out these changes to the user base running RTM, but the cumulative set of fixes and new features that is 10565 is just all good.
 
Keep in mind that these releases are full-on Windows 10 installs, complete with the "Hi, we're setting up a few things for you..." message when you log in after installation. This means that XLN (AD2) and NI (Guitar Rig et al) plugs end up having to be re-authorized, and I'm adding the reinstall of interface drivers to my list of Recommended Things To Do After a Windows 10 Upgrade. The only way I've found to successfully reauthorize Guitar Rig 5 is to uninstall, then reinstall, then go to Service Center and reenter the key. Pain, but it works.
 
Finally, I wanted to add that the Jamaica Plain update works absolutely wonderfully on 10565. If you've noticed any issues with 10565 and Sonar, post them here!
 
Live dangerously, my friends!
 
Kevin

...not in ANY hurry,
to deal with any of these issues.
 
still quite happy with XP,
and when i do update,
probably 8.1 will sit for quite a while.
maybe a year from now,
i MAY revisit w10,
 
but after reading post after post about issues,
i say why?
 

From the MS blog announcing 10565, they announced improvements to the Edge browser and Cortana, device installation issue fixes and new printer handling. See the blog here at:
http://blogs.windows.com/windowsexperience/2015/10/12/announcing-windows-10-insider-preview-build-10565/
 
For your convenience, here are a list of some additional fixes and some known issues:
 
Here are some things we have fixed:

• You should no longer see a warning message in the Settings app > Update & Security > Windows Update regarding changed ring settings for preview builds unless you actually change your ring settings.
• Background audio playback works again when apps like Groove are minimized.
• We fixed the issue where clicking on the system icons in the notification area quickly results in Windows Shell blocking the launch of fly-outs like Audio, Networking, etc.
• After Build 10525, we heard a lot of feedback that some context menus were too big for mouse. We’ve made adjustments to many of the context menus to make them smaller for using them with a mouse.
• You can now pin contacts to the Start menu from the People app.
• Certain apps won’t appear twice anymore when pinned to the taskbar.
• Hiding desktop icons via context menu on the desktop now works.
• Windows Store apps should now be updating automatically.

Known issues:

• The search box does not work if you are in a locale where Cortana is not available. We are currently investigating workarounds.
• The Xbox app for Windows 10 will consume gigabytes of memory on your PC if you have any Win32 games (non -Windows Store games) installed on your PC that have been identified as games or added by you in the Xbox app. Closing the Xbox app will release your PC’s memory.
• WebM and VP9 have been temporarily removed from the flight builds. We continue to develop a VP9 implementation that we intend to ship in Windows. Expect VP9 to return soon in a future release.
• Small form-factor devices, like the Dell Venue 8 Pro, that boot with rotation or virtual mode screen size set larger than the physical screen size will experience a bluescreen on upgrade and will roll back to the previous build.

batsbrew
...not in ANY hurry,
to deal with any of these issues.
 
still quite happy with XP,
and when i do update,
probably 8.1 will sit for quite a while.
maybe a year from now,
i MAY revisit w10,
 
but after reading post after post about issues,
i say why?

Some of us just like pain.
 
I live on the bleeding edge because I write software that uses the new W10 services, and my DAW machine and my development machine are one and the same. Not something I'd recommend for the average user, by the way, but I like it this way. So it very much depends on your situation as to whether or not Windows 10 is right for you, or whether or not you choose to participate in the Insider program.
 
Beyond that, Windows 10 brings more to the table for audio than MS has done in many, many years. Along with a streamlined set of API's for audio and MIDI that works across all devices (including phones), there are now services available for DAW writers to leverage that promise make DPC latency worries a thing of the past. 
 
Don't get me wrong, I'm not urging anyone to adopt Windows 10 if they don't see the value. I would be the first to tell them to stay away for a few years until all the blood-letting is over. So please don't think of these Insider Preview threads as any kind of Windows 10 advocacy thing, because they're not.
 
MS is finally focusing on the creative user market and they say they're working hard to achieve parity with Apple on the audio stack front. This effort is as welcome as it is long overdue, and now that we have their attention I feel compelled to help push that work forward in whatever small way that I can by using the latest stuff and reporting issues I find or sharing feedback as it occurs to me, and sharing that kind of activity with others here who feel the way that I do.
 
Hope that answers your question.
 
Kevin

all i know is,
when someone says 'windows 10',
and then follows it up with 'my stuff is no longer working',
that's all i need to know.
 

batsbrew
all i know is,
when someone says 'windows 10',
and then follows it up with 'my stuff is no longer working',
that's all i need to know.
 

 
Yeah, I've seen those posts too. However, in many cases if you scroll down a bit, you might well see something that says, 'I had that problem and here's what I did to fix it.'
 
I haven't done any kind of analysis of the issues people have had, but my sense (which I don't have much of, admittedly) is that most of the issues are driver problems and many of those have workarounds. The ones that don't have a resolution seem to mostly be because the person chose to roll back to the previous version without much in the way of troubleshooting. And that's what I'd do too if I were in their shoes.
 
To reiterate, though, I'm not interested in convincing you to adopt Windows 10 here. These Insider Preview threads are not shouting, "Windows 10 for everybody!" They are for people who want to understand and perhaps participate in MS's effort to build a more capable pro audio platform, particularly as it applies to Cakewalk and Sonar. If that doesn't interest you there are several threads wrapped up in debating whether or not Windows 10 is a worthwhile upgrade. I participate in them too!
 
Kevin
 

i'm just offering a different perspective, is all.
 
it is easy to get caught up in the 'rush'.....
i see it all the time.
 

I actually upgraded to Win10 from 8.1 Pro and very happy with it (more so than all the other versions). I did have an issue with my internet connection being intermittent and dropping out completely, but after doing a bit of searching, I found the solution - in Power Mgt.: uncheck the box that reads "Allow the computer to turn off this device to save power".
 
 
This resolved my one and only issue with Win10 (all my drivers are working very well). Like with any new version of any software, there's bound to be bugs/quirks that need to be sorted out. Now, if the problems were so many and it just hindered my day to day activities, then I'd definitely revert back to a more stable version.......quite the opposite experience with Win10.

Glad it's working well for you, Mersh!

batsbrew
i'm just offering a different perspective, is all.
 
it is easy to get caught up in the 'rush'.....
i see it all the time.

 
I get what you're saying and I respect your caution. I'm saying that by definition, this thread is for people who don't understand caution. :)