As it seems, the EFF is still pressuring Microsoft into clearing up the privacy issues for their users. See this blog for more details on that, and keep in mind that some of the policies related to this aren’t supported in Windows 10 Pro version 1607 and later; see this TechNet article for the specifics.
Advertisement
Windows 10 users should also be aware that enabling Cortana, Microsoft’s virtual assistant, adds to even more data sent back to Microsoft. “Microsoft should come clean with its user community”.
Windows 10 users will now have to triage their installed apps again, removing any unwanted software in an effort to free-up some additional space.
After some analysis being done, it was concluded that changes to the video encoding systems caused such problems. We say “new” because, truth be told, it sounds a lot like Microsoft’s “OneClip” tool from previous year. No new Windows 10 Mobile phones break into the top 10, but AdDuplex was nice enough to explain where they fall: The Lumia 550 is inexplicably the most popular of the new devices, falling to #23.
A digital rights group has accused Microsoft of “blatantly” disregarding user choice and privacy in the launch of Windows 10.
“The fact remains that many users would much prefer not to use these features in exchange for maintaining their privacy”, said Kalia of the trade-offs between convenience – primarily Cortana – and privacy.
Less core fixes are for Xbox One media casting via cast to device, and a problem with nodes being disconnected from the Windows Cluster service “intermittently”. Microsoft also won’t say how long this data is retained, instead providing only general timeframes.
The Electronic Frontier Foundation labels this as “an unprecedented amount of usage data”.
One user on the Windows Dev Centre forum complained: “We have a working product running for years and millions of unhappy users that are unable to use it at all after this update …”
Advertisement
Meanwhile, Microsoft suggested that users remove the faulty update from a PowerShell prompt with administrative privileges, using the “wusa /uninstall /kb:3176934” command.
