Read more.Quote:
Result: higher satisfaction, fewer known issues, lower support call volumes.
Printable View
Read more.Quote:
Result: higher satisfaction, fewer known issues, lower support call volumes.
Not trying to be facetious but there were some pretty glaring issues that were missed like compatibility with Microsofts own hardware and Intels storage mediums xD
But fewer issue, means lower support call volumes and higher satisfaction numbers, I'm not quite sure how AI is a major factor in that, they don't say anything about the AI writing the code or bug fixing or even QA testing.Quote:
with the latest update, there are higher satisfaction numbers, fewer known issues, and lower support call volumes compared to previous Windows 10 releases.
Reading more into it, looks like they use the AI to regulate who gets the update when, targeting people with the least potential issues (or least likely to complain) first to give the coders more time to focus on bug fixes.
Also as the general trend of support calls in that graph is downward, I suspect that removing AI from the equation would of had little difference and what it did potentially do was to boost early numbers for the roll out.
It smacks of internal politics, doing the easy jobs first to make it look like the team are ahead of schedule and using the current buzzterm AI
Well the numlock, capslock and scroll-lock lights still don't work!
That seems harsh. It shouldn't be hard for MS to eg monitor that a box has taken the update and then not checked back in afterwards implying they bricked it. But filtering through the sheer quantity of data that MS has and making sense of it is an ideal job for an AI to do. I'm normally pretty anti-Microsoft, but I have to say well done on this one it is an interesting tool in the face of an untestable platform thanks to all the various cards out there.Quote:
Originally Posted by Pob255
Now if they could un-mess my local garage's networking so they can bill customers, that would be nice too. Sounds like the removal of home networking stuffed what was a working setup.
When I initially installed Win10 I had issues with the onboard audio cutting out which were fixed,and now this updated has brought that bug back so I need to use my DAC and headphone amp,for normal usage.
So far this update has been meh for me!
"intelligently selects devices that our feedback data indicate would have a great update experience..." Yep, pick the ones who are less likely to complain first! Not sure how "AI" that is. My experience, with a number of PCs(I volunteer for RNIB Tech Support, UK) is that Build 1803 disables or even "hides" critical software, such as older Radeon drivers (graphics cards and anything that uses them won't work), Accessibility software like screenreaders etc. Thus an update has had to be issued for the April Update! All taking some 50 to 90 minutes per machine. Speaks volumes about the "wrinkles" which had to be ironed out of Build 1803.