Watermark?  

Edwin said:

Nonsense!
Anyone running an Insider Build knows exactly what they have.
It's just a trademark boast!

And if you should sell a used machine that just happens to have an Insider build on it? The watermark lets "everyone" know that a trial not full retail OS is what is on especially for those not in the program itself and familiar with which is what. MS is protecting their own interests by having that information displayed in full view which gets into legal issues.

The exception being the TH2 and RS1 builds which suddenly didn't have one since there would only be minor changes between build numbers before the final release was out. With the rearm showing 1001 on each of the RS1 Insider build any could be run for a long time much longer then the typical 6 month expiration date for the regular "BETA" type "Developer" builds where a watermark doesn't seem to ever bother regular testers. The option to stop receiving Insider builds is still there for those worried about how that looks with their wallpapers.

Personally the 14901 was the perfect opt to put the Recovery option to the test on one machine here which rolled backwards as smooth as silk indicating MS has made some serious progress in that area. Two VMs now running the 905 while another runs the 901. If the Redstone 1 Anniversary gets buggy on the main then I either drop the next available build on or repair/clean install 10 on it.

Actually had a favorite canine around here for 14yrs. that unfortunately had to be put down due to failing health issue. So I keep track more on the OS health issues as far as the question: "To Be or To Not Be BUGGY"!

Night Hawk said:

Once it's done you mean. Explorer type errors are the most common. Often when something else is freezing up on you an explorer error pops up. The error code or number is always the best troubleshooting information to have however for researching a particular problem.

Yes once lol.

I think one of the most common to see would be the "Not responding" type errors that not only come up with explorer windows but just about anything you can run! Browsers, small apps, etc. will suddenly hang and you end up needing the Task Manager to end process if not forced on some occasions into a hard boot which in most cases trying to avoid when possible. But if you should see that repeat itself which it could at any time be sure to catch a glimpse of the error info.