Microsoft has announced a new edition of Windows 10, Windows 10 Pro for Workstations. This is targeted for the higher end workstations that can include multiple server grade CPU’s, large amounts of RAM, and multiple HDD’s in a RAID configuration. So, naturally, it includes some home hobbyists! This is great news for those in various industries that require an OS that can take advantage of the much higher powered systems they are required to use. The new edition of Windows is expected to be released as part of the Fall Creators Update this fall.
Performance is a very important requirement in this new world of fast paced innovation and we will continue to invest on Windows 10 Pro for Workstations to enable Windows power users to maximize every aspect of their high-performance device. Windows 10 Pro for Workstations utilizes significant investments, that Windows has made in recent releases, for scaling up across a high number of logical processors and large amounts of memory. Our architectural changes in the Windows kernel take full advantage of high-end processors families, such as Intel Xeon or AMD Opteron, that package a high number of cores in single or multi-processor configurations.
A recent Consumer Reports report has slammed the Microsoft Surface line and removed them from their recommended devices and putting them into the “not recommended” list, stating upwards of a 25% failure rate. Panos Panay has responded with Microsoft’s own statistics and disagreement with Consumer Reports.
This will be an interesting story to follow, seeing both companies bring data to back up each others claims. While I am a Microsoft fan, if something has problems – it has problems. Being a fan of Microsoft, if reliability is a concern, it needs to be called out so it can be remedied and the next model be a higher quality. In the past, Panos has been very receptive to criticism and eager to fix the issues, typically with great results.
This is why today’s Consumer Reports survey is disappointing. While we respect Consumer Reports, we disagree with their findings. Surface has had quite a journey over the last few years, and we’ve learned a lot. In the Surface team we track quality constantly, using metrics that include failure and return rates – both our predicted 1-2-year failure and actual return rates for Surface Pro 4 and Surface Book are significantly lower than 25%. Additionally, we track other indicators of quality such as incidents per unit (IPU), which have improved from generation to generation and are now at record lows of well below 1%.
Yesterday was Microsoft’s monthly Patch Tuesday. This time, they come with fixes for 48 vulnerabilities, with 27 that could result in remote code execution exploits. The problems exist within Windows, IE, Edge, Sharepoint, SQL Server, Hyper-V, the Windows Subsystem for Linux, and the Windows Kernel itself.
Experts are recommending prioritizing CVE-2017-8620, which is a vulnerability within Windows Search.
Make sure to get your systems patched and update and stay safe out there!
“This is by far the most critical bug for this month,” says Dustin Childs at the Zero Day Initiative, which reports CVE-2017-8620 is “under active attack.” A previous Search flaw also allowed a malicious SMB request to execute code on target machines.
“As with the previous Search flaw, within an enterprise, an attacker could remotely trigger the vulnerability through an SMB connection and then take control of a target computer,” he adds. “That’s pretty close to wormable and just the sort of thing malware writers look for in a bug.”
The Windows Server Insiders Team has released a new build for those running the new Windows Server Insider Preview. The Windows Subsystem for Linux has been released on the Server build, which is a great addition. Check out the blog post for more.
What’s New in Build 16257 for Windows Server
Windows Subsystem for Linux (WSL) is available on Windows Server
Windows Subsystem for Linux (WSL) is now available on Windows Server along with a compliment of Linux distributions.
Test WSL on Windows Server. WSL runs unmodified Linux (ELF64) binaries natively. With the additions of WSL you can run node.js, Ruby, Python, Perl, Bash scripts or other tools that expect Linux behaviors, environment, or filesystem-layout, the ability to install and run Linux with WSL expands the tools at your disposal on Windows Server.
At this time, WSL does not support persistent Linux services (such as daemons and jobs) as background tasks. To enable WSL and install a Linux distribution, see Enable the Windows Subsystem for Linux and Install a Linux distribution in the Windows Server 2016 Installation Guide on GitHub.
As always, make sure and read the known issues before upgrading. You might find a show stopper in your case. Many times, it’s an issue that is just annoying or doesn’t affect you at all.
Known issues for PC
If you installed Builds 16226-16237 and upgrade to this build, Storage Spaces will not work correctly. While Build 16241 contained a fix for the general reported issue with Storage Spaces in that build range, we discovered that the fix only applies for computers not already in the bad state, and need to do some extra work to return those already impacted to the good state. Special thanks to the Insiders that have helped us investigate this!
Trying to use the dictation hotkey (WIN + H) in UWP apps won’t work – you’ll see the UI come up and immediately dismiss. If you’d still like to use dictation, the microphone in the touch keyboard will work. You can right-click the Taskbar for an option to show the touch keyboard button if it’s not already visible.
We’re investigating your reports that after upgrading to the latest Insider Preview builds, some network settings are lost and revert to default settings. Static IP address configuration is reverted to DHCP. Networks which were marked as private are reverted to public. After the upgrade you will need to manually readjust your network settings back to your preferred settings.
Start, Action Center and notification toasts may at times have a background that is 100% transparent. A fix will be available in later flight – for now, if you encounter this issue, try ending ShellExperienceHost.exe via Task Manager or rebooting to resolve the issue.
Connecting to a VPN using a solution downloaded from the Windows Store may result in a system crash.
The battery flyout might show unexpected text for the % charged (specifically “%1!s!%2!s!% until fully charged”).
Microsoft has announced the Windows Bounty Program for computer security professionals (or those that enjoy looking for security vulnerabilities). The target areas are the Windows Insider slow builds of Windows 10, Hyper-V, Microsoft Edge, Windows Defender Application Guard and the mitigation bypass and bounty for defense. The payouts for finding an exploitable vulnerability range from $500 – $250,000.
The overall program highlights:
Any critical or important class remote code execution, elevation of privilege, or design flaws that compromises a customer’s privacy and security will receive a bounty
The bounty program is sustained and will continue indefinitely at Microsoft’s discretion
Bounty payouts will range from $500 USD to $250,000 USD
If a researcher reports a qualifying vulnerability already found internally by Microsoft, a payment will be made to the first finder at a maximum of 10% of the highest amount they could’ve received (example: $1,500 for a RCE in Edge, $25,000 for RCE in Hyper-V)
The Windows Insider team has released the first Windows Server Insider build – build 16237. This is great for those IT professionals wanting to be on the bleeding edge and learn the new capabilities of the Windows Server OS. In a non-production environment, of course (although, what’s that saying? All environments are dev if you’re brave enough. 🙂 ).
As always, make sure to read the release notes to see if there are any issues that might affect you directly.
The Insider team has released new builds for PC (16241) and for Mobile (15230) today. And, the upcoming and final Bug Bash for the Fall Creators Update. With the Bug Bash also comes a couple Mixer (formally Beam) webcasts. If you see MSTechpages there, be sure to say hi!
We’re really excited to do our 2nd (and final) Bug Bash for the Windows 10 Fall Creators Update! The Bug Bash will start at 12am (Pacific Time) on Friday July 14th and will run a full week ending at 11:59 pm (Pacific Time) on Sunday July 23rd. This build will be our Bug Bash build. As usual, we will be publishing new quests so be sure to open Feedback Hub and complete as many quests as you can!
And we’ll also be doing Mixer webcasts at the following dates and times for the Bug Bash:
Tuesday July 18th: 1:30pm – 3:00pm (Pacific Time)
Friday July 21st: 10:00am – 11:30am (Pacific Time)
This Patch Tuesday from Microsoft includes patches for Windows that affects all Windows OS’s released since 2007. Swati Khandelwal has a post about the new vulnerabilities and how they could be exploited. Make sure you run Windows Update to grab the latest updates and protect yourself from these vulnerabilities.
Researchers at behavioral firewall specialist Preempt discovered two zero-day vulnerabilities in Windows NTLM security protocols, both of which allow attackers to create a new domain administrator account and get control of the entire domain.
NT LAN Manager (NTLM) is an old authentication protocol used on networks that include systems running the Windows operating system and stand-alone systems.
Although NTLM was replaced by Kerberos in Windows 2000 that adds greater security to systems on a network, NTLM is still supported by Microsoft and continues to be used widely.
Good news for those in the Fast Ring for the Windows Insider program on the desktop. A new build, 16237, has been released. Also, starting July 14th, a new Bug Bash begins! These are fun, a lot of quests to learn more about the new updates and features in the OS, as well as provide feedback and bug reports on those features. It’s always fun! A lot of new improvements this build, too.
Upcoming Bug Bash
We’re really excited to do our 2nd (and final) Bug Bash for the Windows 10 Fall Creators Update! The Bug Bash will start at 12am (Pacific Time) on Friday July 14th and will run a full week ending at 11:59 pm (Pacific Time) on Sunday July 23rd. As usual, we will be publishing new quests and will be doing some Mixer webcasts. So be sure to open Feedback Hub and complete as many quests as you can! More details to come early next week!