xinso, I think you gave everyone the impression, Non Insiders that is OK to install this build over there RTM build and stay activated permanently, hope your right
If I access my M$ account to get Insider Builds, will my Local account be changed to M$ account, or just used to get Insider Builds?
questions. watermark on this version? timebomb on this version? does it show up for VL license without being insider?
About the new title bar color feature: I can't actually find a color that doesn't look horrible. Why is this so difficult? I thought one of the dark ones would be less offensive than all the candy-colored ones (the vast majority of them), but this also affects a lot more than the title bar. In Firefox, for example, it colorizes the tab bar too. Other programs ignore the color completely. This is no solution to a real problem.
Yes watermark is back. Windows 10 build 10525 expire on 16 july 2016. You can check licence with command slmgr /dlv in command prompt.
I never complained about the Grey Title Bar but I love the change to Personalization. I'm using a Light Blue Color right now
This is a Windows Insider build only, install it if you are not insider, lose permanent activation, management needs to say on thread these are windows insiders builds.
IMO, any color can't be worse than the forced white. Fortunately, the theme tweak enabled colorization back in RTM, so I never had to use Windows 10 with white title bars, and I'm glad they are reintroducing the feature instead of messing it up even more. What I still don't like is that it seems inactive title bars will still be white, while I'd prefer a medium gray color, just like it was in Windows 8/8.1. But let's wait and see what the final result will be. Note: The colorization doesn't apply to universal apps, they still choose their own color (prominent example the Settings app). I guess Firefox can resolve the issue with another update, the current release is tweaked to expect enforced white title bars. As for other programs that ignore the color: Well, if the developers/designers decided to perform their own custom rendering of the window chrome, it's their choice, most of the time there's nothing you can do about it. And don't forget: Breaking the theme and releasing it in this state to the public was no solution to a real problem in the first place.
Looks great and all but I won't install over my RTM and lose permanent activation. I'd use a VM, another drive or wait until it's generally available.