WinBeta it's like Neowin, a reliable source that have always making a reliable articles, if you do not trust then provide evidence of its unreliability instead of use only words
Many years ago when Winbeta was just an IRC channel I was an op with them and if they say it's real, it's real. I know many of those people and the connections they have.
Also i have following them in more than one occasion, and i have never seen any incongruence or fake of any type, i think that tomorrow many will be disappointed (hope that wrong) by BUILD
Trying to upgrade a ThinkPad laptop (32-bit) that's currently running 10049 to 10061. The install runs for hours, hangs at 87% (Setting up a few more things 49%). If I kill the power and boot it again, it says it was interrupted and reverts back to 10049, finally displaying a useful error message telling me that it reverted back because of an unexpected shutdown (duh). It's done that a second time now, where to start looking for a clue of what's causing the hang? 0xC1900101 - 0x4000D The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation
I believe that we should wait for the BUILD Conference (beginning of May?) which is NEXT Week!! Oops!! 29. April to 1. May!! I think I read somewhere about 4./5. May would be some special day?!
I'm going to say that it is highly likely that we will see a new build tomorrow. 10074 has been in the External ring for a while now and usually, it doesn't take that long before a build gets released to Insiders if it is in that ring already. If they do say "in the coming days", it's just for the sake of waiting.
Just upgraded to this build, and for me, it's a complete dud. The upgrade process went smoothly, but the laptop now hangs at the lock screen upon power on. It then blue screens with this error message at the bottom: "DPC_WATCHDOG_VIOLATION" I am now trying to figure out what to do. Where can I download an ISO of this build and start from scratch? Also, the graphical environment for various recovery related tasks never comes up. Is Microsoft serious about not allowing "F8" to invoke safe mode? How stupid is this billion dollar company? The recovery screen never comes up. How do you get around this crap? MS can't rely on betting on this environment always popping up when a problem happens. There needs to be an F key to invoke to override their stupid architecture!
At this point i doubt that will be 10074, maybe it will be 101xx with all new changes to cortana and other.
I've heard that in Windows 8, turning off Fast Startup solves that problem, I mean, DPC_WATCHDOG_VIOLATION.
How do I turn off Fast Startup when I can't even get into the OS? The Recovery screen never even comes up. There needs to be an F key option, and brilliant brains at MS didn't provide this. Purely idiotic. This is why I run Linux.
How am I supposed to get into safe mode when MS eliminated the F8 option and the recovery GUI never comes up?