Enlarge / This option is the best way of transitioning out of the Insider Program. (credit: Microsoft) The “official” release of the Windows 10 Creators Update , version 1703, won’t come until Patch Tuesday on April 11, but if you want to upgrade now—and don’t want to enroll your system in the potentially unstable Windows Insider Program—you can now do so. The Windows 10 Update Assistant will upgrade any Windows 10 Home or Pro system to the Creators Update; you’ll need to grab the latest version of the Assistant and then run it, but it should be straightforward enough. If you’re upgrading more than one machine or want to perform a clean install, the Media Creation Tool, available from the same link, is the better bet; the Media Creation Tool can fetch an ISO to burn a DVD or create a bootable USB drive, and that can be used for bare metal installs. The Creators Update itself is build 15063.0, but there will be a small Cumulative Update delivered on April 11. Previews of this patch have been rolled out to insiders, with the fast ring Insiders on 15063.14 and slow ring Insiders on 15063.13. Using the Update Assistant or Media Creation Tool appears to also update to 15063.13. This situation may well change by the actual release day next week. Read 2 remaining paragraphs | Comments
View original post here:
The Windows 10 Creators Update is now available for manual upgrading
			
An anonymous reader writes from a report via BleepingComputer: Last week, at the BlackHat Asia 2017 security conference, researchers from cyber-security firm Cylance disclosed two vulnerabilities in the firmware of Gigabyte BRIX small computing devices, which allow an attacker to write malicious content to the UEFI firmware. During their presentation, researchers installed a proof-of-concept UEFI ransomware, preventing the BRIX devices from booting, but researchers say the same flaws can be used to plant rootkits that allow attackers to persist malware for years. The two vulnerabilities discovered are CVE-2017-3197 and CVE-2017-3198. The first is a failure on Gigabyte’s part to implement write protection for its UEFI firmware. The second vulnerability is another lapse on Gigabyte’s side, who forgot to implement a system that cryptographically signs UEFI firmware files. Add to this the fact that Gigabyte uses an insecure firmware update process, which doesn’t check the validity of downloaded files using a checksum and uses HTTP instead of HTTPS. A CERT vulnerability note was published to warn users of the impending danger and the bugs’ ease of exploitation. Read more of this story at Slashdot.