Microsoft surprised, Apple disappointed me. Better a touch screen as one touch bar= Gimmick with dubious benefits. Microsoft is the new Apple. Microsofts All-in-One-PC Surface Studio will be my next.
Just wanted to report an interesting issue at least to me. After I got around to upgrading to 14955 yesterday evening from 14951, if I had crossfire enabled it would freeze any 3d app just on the screen. So no games, benchmarks etc. Not a hard lock or driver crash just would freeze on that screen. Multi monitor set up. First thought it was the last AMD driver, started nuking amd drivers and reinstalling earlier one and each did the exact same thing. I could ctrl-alt-del to log out or restart on top of the frozen screen. My other monitors continued working fine. I rolled back to build 15951 and crossfire now works again like normal. Not sure if this affects Nvidia in SLI. Reported as bug.
Well, with this build it seemed like they finally solved the "just a moment" bug. I was happy to see the screen asking me for a username and I said to myself that I was finally going to be able to test this build. But I guess I spoke too soon. After I entered a username I was greeted with a black screen, and nothing else. Mouse cursor was still active, hard drive showed occasional activity, and I could even do a clean shutdown using the power button or the power key on the keyboard. But booting back only brought me back to the same black screen. Nothing I did enable me to go any further. This is the fourth consecutive build I am unable to install and test. Even with the early Windows 10 betas back in the day, even if most of them were basically unusable, I could always at least eventually get to a working desktop one way or another. Guess it's virtual machine again to test this new build. And wait for the next one.
I also got the black screen in the final stages (the mouse is present and moving and the hard disk is churning away), where it goes for sometime and nothing is happening. A forced restart seems to bring it into the login screen where it continues into welcoming the user and successfully performing desktop and applications setup.. Minimizing the connected/attached hardware seems to affect this issue!! For Virtual Machine, I had to enable 3D, other wise it will crash at boot (if in Full screen mode).
The issue reported above is on real computers not a virtual machine. How can you change the resolution before finishing installation? Did you change monitors? However, If you are using VirtualBox, enable 3D and 2D, it will sort the crashing issue. You can increase the Video memory to 256Mb if you wish..
1700 is normal compile time. How many Builds get compiled at 0127 1:27 am. Why would MSFT be working till 1:27 am to compile a Build ?