Microsoft is taking to Skynet for its fight against malware, cyberattacks, and viruses - with the upcoming Fall Creators Update for Window 10 using all internet-connected Windows 10 computers along with machine learning to fight off threats like WannaCry.
The global malware hits with WannaCry and Petya have woken Microsoft to a new world of attacks, prompting them to push the Windows Defender Advanced Threat Protection system that uses machine learning powered by the massive 400 million Windows 10 PCs throughout the world. Director of Program Management Enterprise and Security said: "If Word were to start allocating memory in big chunks, when it never does, we would be able to detect that. We built the machine learning models around common applications like Word".
This new initiative will reportedly stop viruses from spreading as fast as they currently do, with enterprise customers being the first to receive this new feature. The consumer version of Windows will receive it sometime in the future, hopefully not too long from now... until you remember that Microsoft is using every Windows 10 user to make this happen. Will we be able to disable it?
Update: After this article went live, I was pointed in the direction of an update to the story from Andy, the administrator of Beta Archive. He posted on the forum saying:
The Register article https://www.theregister.co.uk/2017/06/2 ... s_10_leak/ has got BetaArchive a fair amount of attention this evening. They claim, and I quote "32TB of Windows 10 internal builds, core source code leak online".
First of all let us clear up a few facts. The "Shared Source Kit" folder did exist on the FTP until this article came to light. We have removed it from our FTP and listings pending further review just in case we missed something in our initial release. We currently have no plans to restore it until a full review of its contents is carried out and it is deemed acceptable under our rules.
The folder itself was 1.2GB in size, contained 12 releases each being 100MB. This is far from the claimed "32TB" as stated in The Register's article, and cannot possibly cover "core source code" as it would be simply too small, not to mention it is against our rules to store such data.
At this time all we can deduct is that The Register refers to the large Windows 10 release we had on March 24th which included a lot of Windows releases provided to us, sourced from various forum members, Windows Insider members, and Microsoft Connect members. All of these we deemed safe for release to BetaArchive as they are all beta releases and defunct builds superseded by newer ones, and they were covered under our rules.
If any of this should change we will remove these builds from the FTP and we will happily comply with any instructions to do so by Microsoft.
With regards to the BBC article http://www.bbc.co.uk/news/technology-40366823 about two Britons that have been arrested following an alleged Microsoft hack, we don't believe there is any connection with this alleged "Windows 10 core source code leak".
Microsoft is experiencing a massive leak in its security, with files leaked that relate to Microsoft's USB, storage, and Wi-Fi drivers for Windows 10 posted to Beta Archive last week. Beta Archive, if you didn't already know, is an enthusiast website that tracks Windows releases, and asks its members to donate money or contribute something Windows-related after accessing a private FTP full of archived Windows builds.
In an email to The Verge, a Microsoft spokesperson said: "Our review confirms that these files are actually a portion of the source code from the Shared Source Initiative and is used by OEMs and partners". The Register is claiming that 32TB of data was leaked, including unreleased Windows builds - something The Verge reports that "most of the collection has been available for months, or even years".
Inside the latest Windows 10 build, we are starting to see Microsoft provide mixed reality developers with support for MR headsets, inside of Windows 10 build 15048.
The latest build provides Mixed Reality developer kit owners to check out a simulation of the demo, but not an actual mixed reality experience. It's also not available easily, as you'll need to enable "Developers Mode" on Windows 10 that will enabled the "Mixed Reality Portal" that includes the demo.
If you've got the latest Windows 10 build, you can run the simulation - but without a mixed reality headset, it's kind of useless right now. Interestingly enough, the new "Windows Mixed Reality" portal app removes any reference to HoloLens.
We've been hearing so much about Apple's new iPhone X that Google has been kind of overshadowed, and while the Pixel and Pixel XL have been selling well (I love my Pixel) - Android 8.0 has been kind of quiet - until now.
Android 8.0 is being teased as Oreo, after Nougat was used for Android 7.0, with the Oreo tease coming from a Google employee over Twitter. Hiroshi Lockheimer, the SVP of Android, Chrome OS and Play teased a picture of an Oreo cake. I think that's a big enough hint of what letter dessert we'd get for 'O'.
What do you think Android 8.0 will be called? How many desserts start with an o?
Microsoft has been working on a major design refresh of Windows 10, and has now shown off its 'Project NEON' refresh during a presentation at its Windows Developer Day event.
In the image above, you can see that there was a slide shown off during the presentation, with the UI refresh featuring a new 'Acrylic' component that will be a tweaked version of what Aero represented in the much-discussed Windows Vista, which will blur UI elements and background apps.
Microsoft will reportedly usher in Project NEON with its upcoming codenamde Redstone 3 release for Windows 10 later this year.
Microsoft is working on a new all-cloud operating system, something unearthed by Brad Sams on Thurrott, with the new OS referred to as Windows Cloud.
Windows Cloud looks identical to Windows 10, except that it works completely differently - as it is capable of running UWP apps only. This means that non-UWP apps do not work at all, and an error message will display that says 'The app you're trying to run isn't designed for this version of Windows'.
Inside, the new all-cloud OS is going to be an interesting future for Microsoft - as it will be exclusive to UWP applications. Sams got Windows Cloud from a "third-party and not directly from Microsoft" - adding that it "is possible that this is a hacked together build but we won't know until we get our hands-on an official release".
Microsoft has been making some very stupid changes to Windows 10, with their latest update breaking triple-monitor gaming for both AMD and NVIDIA gamers.
Their latest update doesn't sound so bad, with the latest builds of Windows 10 including something the company called Dynamic Lock - which Microsoft reportedly refers to as "Windows Goodbye" internally, reports Windows Central. Microsoft uses special Windows Hello-capable cameras that let Windows 10 owners log into their PCs with facial recognition.
Instead of quickly locking your PC with pressing the Windows key and 'L' at the same time, the new Dynamic Lock will do it automatically - at least for some users. We don't yet know how Microsoft will know that users have walked away from their PCs, but they could leverage their Windows Hello feature - by using the camera to constantly detect your face in front of the PC, and when you walk away it would lock it.
Microsoft has just released its new Cumulative Update for Windows 10 (KB3213986) which has broken multi-screen gaming, with the company noting that there are "known issues".
This means gamers that are running triple-display setups with AMD EyeFinity and NVIDIA Surround Sound will experiencing stuttering or clipped screens when running a game, but it should be fine in 2D applications. There's a workaround for this issue, with Microsoft adding that gamers can run their 3D apps in non-fullscreen mode - either in window-maximized, or just windowed modes.
But it gets better. Microsoft suggests that gamers disconnect their other displays, leaving just a single display connected to the PC for the game to work. Because, you know - that's why you spend thousands of dollars for the bleeding edge of high-end gaming, to disconnect those expensive LCDs.
Microsoft notes in the change log for KB3213986: "Users may experience delayed or clipped screens while running 3D rendering apps (such as games) on systems with more than one monitor. To work around this issue please consider the following options: 1. Running the application in Windows mode (not full screen), or 2. Starting the application with only one monitor connected".
CyanogenMod is shutting down, bringing an end to an era of Android operating system goodness. For those who don't know what or who CyanogenMod is, it's an aftermarket custom ROM that had everything Android had to offer, but some great improvements and tweaks.
Unfortunately, the company has been going through troubles - with its CEO being booted, its original founder leaving, and different choices that have led CyanogenMod to close down on December 31, 2016. The company explains: "As part of the ongoing consolidation of Cyanogen, all services and Cyanogen-supported nightly builds will be discontinued no later than 12/31/16. The open source project and source code will remain available for anyone who wants to build CyanogenMod personally".
Keeping the OS in open source is a nice touch, so developers can grab the latest version of CyanogenMod code, and keep developing it personally if they wanted to. Nothing much from there, which is sad to see over the holidays.
Apple's iOS 10, launched back in September, was mainly praised, but with the recent release of the 10.1.1 update, many users reported issues with battery life. The main point of the 10.1.1 update was to fix some of the camera issues that users were experiencing with the new iPhone 7 Plus dual camera.
The iPhone users who installed 10.1.1 update are reporting that the battery life of their devices lasts much shorter and even that their phones are shutting down with at least 30-50% charge left.
Some users have tried going back to 10.1 version, but according to the reports, that doesn't fix the problem.