New
#210
17063 is really slick..
- best Chrissie present so far..
I was sick as a dog for few days but managed to update just fine and make an ISO too.
Now I'm running into troubles. FF has no sound, it shows in the mixer as working but not a peep.
WD is showing caution triangle in tray only. Security center has no warnings. All is green, I run full scan and no problems reported.
Now comes worst part, every now and than I get a warning that my license is about to expire but when I run troubleshooting and go to my account at MS, there's nothing out of ordinary yet winver shows somewhat different than before ( org name that I don't remember being displayed ever before)
Some USB devices are not tolerated any more and are throwing GSODs every now and than. (KMODE........) USB memory was rejected and made GSOD twice when updating MR Rescue USB but passed third time and my security camera with USB digitizer also throws GSOD every few hours.
Other than those annoyances everything seems to work fine, even benchmark scores are up few %. Turning WD and security options off and on, doesn't make any significant difference.
Visual enhancements seem to be more pronounced now.
Agree 100%. They must have done something with audio and drivers in general that completely destroyed a ton of stuff. It's really weird when an audio card works on 17046 and it's useless with 17063, alongside webcams and Bluetooth headsets just to name a few.
A shame, because Timeline looks very promising but there will be time to use it. They better fix the issues this build created ASAP.
Audio issues ?? Except for the problem with FF I have none, all other browsers I have (Edge, IE, Vivaldy and Tor (also FF based) have sound as usual. Also most probably there's a problem with USB in general and not with individual devices.
PS.
I just found that Power saving was turned on for USB buss(es) so I turned it off as it did make some problems in the past and is of no use in desktop systems.
The point is that people on this forum seem to be experiencing a much higher level of issues on things that worked fine before, and it seems random to a degree. Sure we can expect new features to be buggy for sure, but it is a reasonable expectation that most existing things should work without falling over.
Microsoft added three known issues:
The first two I have not experienced and the third does not affect me because I only use Chrome and Edge, they are more than enough for me, the only problem I have in this build is with the sleep function but this problem along with the three mentioned above, I find them quite normal in a build of the fast ring.
Agree 100% with your above comment.....of course you will get moaners complaining that this doesn't or that doesn't work and why not.
What do they expect?....they should ask themselves "should they be an Insider".
M$ themselves are working like beavers to get new concepts to work and there are bound to be faults.....if they do not release a new flight all hell breaks loose in this forum, if they release a duff flight....critics abound.....they just cannot win.
Nice of them to acknowledge those problems, I reported last two as soon as I have found them. I'm also happy that it's not something unique to my system, specially part about license and activation as I couldn't find any fault with it. Except for that warning nothing seems to be out of order. Looks like Mozilla too is looking at sound problem with FF. Strange it's only one affected.
Just run few more benchmark tests and WD on or off does not make any difference. Security is not interfering with results at all.