Windows Warning

Last night when I shut down my computer, Windows said it had some updates to install. I figured they were general security fixes. I let windows update my machine. The next day I turned on the computer. After the bootup, Sonar would not come up and I could not reinstall it. As I investigated this problem further I found that Addictive drums needed to be reauthorized. A few other programs that depend on internet authorization needed to be reauthorized as well. After doing these steps I still could not get sonar to run or install on the computer.
 
After a little digging I found that microsoft installed a whole new build on my system and that is why things were not working. All my software appeared to be running on a new system and it did not recognize any previous authorizations. So I had to go back to the older build and just like magic, Sonar started working again.
 
For the record I am still using Sonar Platinum. I like everything Bandlabs is doing, but I have yet to install it on my recording computer because I am in the middle of a huge project that contains 60 songs. After I am done I will upgrade to the bandlab version. I have installed the bandlab's version on my laptop so that I can play with it and see the differences. This only effected Sonar Platinum.
 
I only made this post to serve as a warning. Windows did not tell me I was updating to a new build that would appear as a totally different operating system for all my software. Be very careful about any update Microsoft wants to install unless you have the Bandlab version of Sonar. I am really supprised because in my opinion, it really did not take long for Sonar Platinum to become obsolete.
 
If this happens to you then you need to go back to the older build of windows and then turn off microsoft updates. Shout out to Bandlabs, Thank you for keeping Sonar relevant! 

Which update number? I had a couple last night, nothing broke.

This sounds like the Windows 'Spring Update 1803'? Some chaos being reported, eg:
https://www.techradar.com...ears-to-break-some-pcs
Another site is indicating the trouble is caused by the presence of anti-malware programs clashing with the W10 update.
 
1803 hasn't rolled my way (UK) yet, but things don't look good. Like others, I always have to do the re-authorise for XLN Drums when Microsoft makes my PC become a different PC, i.e. every major Windows upgrade, but the failure of Sonar Platinum reported above is scary.

I have read of people having problems after updating to 1804, but I updated the other day and have had no issues yet... apart from the XLN activation which I have had after updates in the past.

Don't you just love how Microsoft does this stuff?  I particularly like when they change your settings without asking you first, or telling you that they did.
 
Thanks for the heads up, and glad you got sorted out.

Some serious drama and overreaction going on here... Update to the latest Windows 10 build, reactivate a couple of plugins, Sonar Plat. works the same  as before. Starting to think people complain about Windows 10 updates just to complain. 

looneymusic
Some serious drama and overreaction going on here... Update to the latest Windows 10 build, reactivate a couple of plugins, Sonar Plat. works the same  as before. Starting to think people complain about Windows 10 updates just to complain. 

This was not an overreaction as you put it. It was a warning to wait. If Sonar does not work due to an update for me, then chances are it will not work for others too. I have too many projects in the works for a microsoft update to tie everything up. It was update version 1803 and now the build number is higher. Maybe they addressed the issue, or maybe not. They were having many problems with this and it was evident just by reading through their forums.
 
The whole point in the post is to hold off and wait until they work the bugs out. Not sure if they did, but I am not going to take that chance right now. Not only did it effect Sonar, but I could not reinstall it. The computer would freeze everytime I tried. This update also had hardware issues too. It may be that something conflicted with my hardware. When I rolled back the update then the problem was solved. I could install Sonar again and everything worked. I spent my whole morning trying to fix this. That is why I gave a warning. So that otherscould avoid what I went through.
 
If Sonar works the same for you then fine. What is the number in your update? It may be higher than the one I had.

That’s one of the issues with not keeping up to date. As MS evolves CbB’s development will also evolve taking into account any OS changes. This has been borne out historically as update release notes often would mention updates underdertaken to ensure continued OS compatibility.