I think it is important for people to state whether their Windows 10 was a Fresh installation or Upgrade/s and how many iterations (upgrade since the original fresh one). I have been involved in testing Windows since NT 3.51, I was then working at a "very well known" chip company. At the time, Windows 3.1 was booting from Novell Netware on to minimum configuration clients... One would consider it great day if your computer suffered few crashes only. Usually, they happen in the middle of something important that you spent some time on. Compare this to the stability of Windows 7 or 8.1, it is a huge advance. Alas, over 2 decades.. I have a firm belief that if you upgrade from a Windows installation where the user had a number of applications installed, uninstalled or upgraded, a lot of loose strings stay behind uncleansed, as well as corrupt or wrong version files, which the Windows upgrade routine either leaves behind by design, for you to fix (in case they belong to one of the installed applications), or does the wrong thing where it gets deleted or corrupted. Add to that possibly erroneous registry or full of garbage!! It is important that Microsoft gets its act right; sorting out the upgrade routines. But it is important for the users to know if the problems they are facing are inherited from previous installations or issues inherent in the new Windows it self. I spent more than 12 hours (in total) fixing few issues with Windows 10, I would install Windows and all the applications a fresh, in less than that, and have a piece of mind. So, I would suggest when reporting an issue or requesting assistance, state the configuration of Windows with a brief installation/upgrade history, please. Thank you, Simple.
Lets take win 10 as a start, explain the exact problems that were inherent in a upgrade and weren't when that same version was clean installed. Seeing how methodical you are in your professional testing of systems, so as not to flood the thread with thousands of systematical flaws in design, only use 10525, 10532, 10547. Now everyone will be able to see the correlation between the upgrade/clean scenario which the errors where non existent in the nature of a clean install and will have a firm grasp of the reasoning behind your post. TY
I converted this to enterprise prior to install however has anyone one else noted that this version throws a blue screen error informing you that you can not right click on the desktop and choose display properties and personalization when you are log in under the admin account? 10240 does not do this but this bld does for me. The settings panel comes up after the blue warning which is just weird. Bug or deterrent? Regards
Neither. Right click works perfectly here. It is something you did or changed that is causing the problem there.
And you have enabled and logged on to the administrator account correct? It is only that account that thoughts this blue box. Regards
With the countless variations of setups and the interworkings between drivers/hardware/software, I don't think anyone can rule out that it isn't related to Windows 10. That's a pretty general statement that because others aren't seeing the issue that it doesn't affect a small percentage as a direct correlation to W10.