Updated from 11102 too but after that I got strange behavior afterwards. No pages shown what so ever. Same thing happened @stable, @beta and also @dev-channel. Don't get it at all. Went back to 10586.71. Now everything works fine and as it should work. Well, maybe I just f***ed something up... ^^ Try again tomorrow!
Way too many bugs in this build, the new fast ring is a no go for me. I know we all wanted faster releases but these builds are definitely not for daily use for my needs. Using these builds requires a PC that is dedicated for beta testing only. I would rather have the old fast ring cadence than this.
So I'm curious....I did an update over 11102 and see no day to day issues that would affect my use of the OS. Majority of issues seem to be from clean installs. Was yours and update or clean install?
Maybe MS is delibrately screwing with people that are fresh installing since part of the testing process is to make sure it upgrades cleanly
Did an update. Issues with gpedit and services. After the update completed my system would boot to desktop and would lock up, I had to do a cold boot to get the computer to work. All in all this build for me seems to be very sluggish. I do not have any issues with chrome. A lot of issues related to the known memory management bug, IMO this is a big issue.
YES confirm,this is another crapy build from m$ ! No extra language pack and now bug whit LAV filters,o my GOD !!!
Going forward expect every Build to be just like this one. Before the "Faster Fast Ring" if a showstopper Bug was found it would more than likely not be released. Not so now. We could see 3 or 4 Builds a Month now. These Builds won't have as much testing time as before.
Yes. Right. After I clicked on Extended and Standard tabs, it started to display the services. Also I closed and re-opened services.msc and did not see that error again. Wondering...
not had a single issue with the build besides the install issue it's been great but you never had the best experience with windows 10 anyway
If you click the Extended tab you will see the script error again. It remembers the last tab clicked.