New
#290
Oh? I have a PHD in real-life situations. Like with $multi-k building contracts. When something went wrong or wasn't working out properly, I wanted to know why so I could correct the situation in order to make profit instead of losing my arse. I should think it would be the same with testing software. Sure, I wouldn't be able to correct the code for I'm not a coder, nor do I know the source code, but at least I could get some insight about it.
I'm not expecting a reason for every nitpicky bug that comes along, but a major one like the AMD block I surely do think we deserve at least some kind of reason for it. After all, isn't that why they called it the "Insider" program and not the "Outsider"?
BTW, UUPtoISO and the UUP Dump methods are great in case we have to clean install after an update failure, but I should think MS would rather have us attempt the upgrade via WU first so they get the telemetry needed to correct or improve that method.