what is even worse is that you can't disable the Xaml start menu anymore and are now stuck with the slow piece of s**t excuse of a start menu. First they took the start menu from us. Then in 10 they gave it back and now pretty much took it away again. No way I'm using this crap. That's even worse than the windows 8 start screen. Does anybody know if the registry hack to disable xaml start menu still worked in 10036 leaked build? I hope there'll be a way to disable cortana and the get back a real start menu in final Windows 10 but i very much doubt it.
Signing into apps separately with Microsoft Accounts while using Local Accounts seems to no longer work in build 10041. It worked when I upgraded to 10041. But not anymore after doing a clean install.
Anyone know how to decrease the width of the start menu in 10041? Though maybe it's just a bug from upgrading from 9926.
The problem with the new Start menu is not so much the implementation (XAML) but the design. If it would look and work more like the previous one, I think there would be not so much to complain about. But I'm actually more disappointed by the lack of progress to such a key part of the system within the last two months. As far as I can tell, it still has many of the issues of the previous build. The stuff on the left pane is pretty hard to distinguish, the All Apps view only supports alphabetical order, and when you unpin everything (no more tiles) you're left with a big blank space - but, hey, at least it got transparency now... and they really believe they will have a finished product by this summer? I'm not so sure what to think of it right now. At the moment, it looks and feels like a frankenbuild, a cross between Windows 7 and 8.x
I 100% agree, 9926 worked great for me, but this piece of garbage, oh boy, from hard lock ups to weird error messages, I went back to 8.1.1 today, my custom copy with no metro apps, lol,
The biggest problem with the Start Menu IMO, isn't so much that's its in alphabetical order. Its that it has the bloody letters there that do nothing, except making the menu twice as long as needs to be. If it let you jump to a particular letter (like on Windows Phone) then it could be useful as your program list gets longer. But at the moment its just pain to get to any program. I'm hearing this said a lot, but it doesn't match what I understand Microsoft are doing. Windows 10 won't be 'Finished' as in XP, Vista, or Seven were. Its more a case of it will be 'Done' (RTM) by Summer and 'Released' (GA) in the Fall. But from then on it will continue to be 'Updated' with features and addons as time goes by. e.g. You won't have to 'Up Grade' to Windows 11, it will be an 'Up Date' of Windows 10. Go back and watch the keynotes from Joe B and Terry M. They both clearly make a difference between 'Up Grades' and Up Dates' when talking about Windows 10. Yeah, I've just done a clean install of 10041. Because a few things were bugging me about the update. And just found the same thing, which is really annoying as I used one account for work e.g. Office and One Drive and another for play e.g. Xbox GT. This has worked fine since Windows 8.0, now it looks I'll have to have two logins on my own laptop. Plus the main bug I did the clean install to fix is still there Anyone else having issues with Metro Apps being to big for their windows, even when maximised ??? Another thing Microsoft has got to look into, is driver crud. My clean install took up 9.6GB leaving me 19.1GB on my 32GB eMMC drive. Which was really impressive and I guess was down to the new OS compression. But, after downloading and installing the new AMD GFX driver, Realtek Audio driver and one Defender Update through Windows Update my install was over 11GB
No option to logon/create Microsoft account during install. Build 9926 Enterprise x64 installs and works fine. build 10036 Enterprise x64 unable to create account during install, build 10041 Enterprise unable to create account during install. Upgrading from 9926 to 10041 viua fast_ring works fine. I've pulled out all of my hair on this one, doesn't make any since..
Just opening Process Monitor while the update is downloading and it tells you the exact folder where is the update. In my case for this build download was C:\RecoveryImage\install.esd
I also concluded that it was not possible to covert Local Account to Microsoft Account, it failed dozens of times for me. I ended up having to create a new Microsoft Account. Now, it's a flawless experience. As sad as that sounds. It is becoming more and more difficult to work with a Local Account. Less working features and more problems. The reality is, I don't want to have to rely on an email address to log into Windows. I've had so many issues in the past with Microsoft-related email addresses with password problems, dealing with security codes, having to manage a second (backup) email to even be able to use the primary email. Email is dated and a real pain these days and I have zero trust in that. However, it looks as though I am going to have to get used to that fact if I am going to use Windows 10. It would seem that Microsoft is steering this in a direction that does not necessarily reflect that of which our Insider Feedback consists of.