Windows 10

Microsoft Patched the KRACK Vulnerability Last Week

Last week, Microsoft released an update Windows 10 Cumulative Update KB4041676. Guess what was also included within this… Yup! The Patch for the Krack Vulnerability.  At this time the KRACK vulnerability that was not publicly disclosed, until Monday, October 16 2017.

Very slick move on the part of Microsoft slipping this in to protect its customers against such a threat.  For those who dig deep into the updates notes would have arrived at Microsoft’s Security TechCenter post which reads.

“A spoofing vulnerability exists in the Windows implementation of wireless networking. An attacker who successfully exploited this vulnerability could potentially replay broadcast and/or multicast traffic to hosts on a WPA or WPA 2-protected wireless network.”

For the post and affected Microsoft products:
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-13080

 

Windows 10 Cumulative Update KB4041676 Fixed

On Tuesday, October 10, 2017 Microsoft released KB4041676 as an update that includes quality improvements. What many started to notice was that it was accompanied by an issue included systems unable to boot and those cause in boot-loops.

 

Jump to quick fix: for those of you who already installed this

In the cmd line of the advanced repair options type:

Dism /Image:C:\ /Get-Packages (could be any drive, had it on D, F, and E.)
Dism /Image:C:\ /Remove-Package /PackageName:package_ for_###
(no space between package_ and for)

Remove every update that’s pending – There are 3 updates that are causing the issue they are:

  • Rollupfix_wrapper~31bf3856ad364e35~amd64~14393.1770.1.6
  • Rollupfix~31bf3856ad364e35~amd64~14393.1770.1.6
  • Rollupfix~31bf3856ad364e35~amd64~14393.1715. 1.10

 

Microsoft explained in a support article that this has been caused by what it describes as a “publishing issue,”

““We have corrected the publishing issue as of the afternoon of October 10th and have validated the cumulative security updates. We recommend all customers take these cumulative security updates,”.

 

At the office and in the lab:

I have taken steps to flush the update from my WSUS environments as a precaution and to allow for the corrected package to be downloaded.

 

ref:

https://support.microsoft.com/en-ca/help/4049094/windows-devices-may-fail-to-boot-after-installing-october-10-version-o

Docker hv-sock proxy (vsudd) is not reachable, Windows 10

Yes, I am playing (or trying to) with Docker.  My first step is to install Docker and get it up and running. So far I am confident that I have all the prerequisites, however Docker fails to properly start with the following error:

Docker hv-sock proxy (vsudd) is not reachable
at Docker.Backend.ContainerEngine.Linux.ConnectToVsud(TaskCompletionSource`1 vmId) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 267
at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 251
at Docker.Backend.ContainerEngine.Linux.Start(Settings settings) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 123
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.<Register>b__0(Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 47
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145

Currently I am researching possible solutions to fix, however non of the suggestions has worked for me. If you have suggestions please feel free to comment and let me know.

Here is a systeminfo of the system I am testing with:

OS Name: Microsoft Windows 10 Enterprise
OS Version: 10.0.15063 N/A Build 15063
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation

System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
[01]: Intel64 Family 6 Model 30 Stepping 5 GenuineIntel ~2926 Mhz
[02]: Intel64 Family 6 Model 30 Stepping 5 GenuineIntel ~2926 Mhz

Total Physical Memory: 4,096 MB
Available Physical Memory: 2,755 MB
Virtual Memory: Max Size: 4,800 MB
Virtual Memory: Available: 3,167 MB
Virtual Memory: In Use: 1,633 MB

Ubuntu Linux for Windows 10 Released On Windows App Store

We can now get Ubuntu Linux for Windows 10 from the Windows App Store. Hows that for an amazing new feature. Simply open the Windows store and search for “Ubuntu”. I would be remiss if i didn’t mention that Windows Insiders Members get first go at this new application.

Also to note that this is not a full version of the Linux Operating System “Ubuntu”. This application is mainly utilizing terminal via bash with included gui-less utilities such as  ssh, git, apt, etc…

  • Navigate to Control Panel > Program and Features
  • Select Turn Windows features on or off
  • Select Windows Subsystems for Linux and Click OK
  • Reboot

 

 

 

Exchange Remote PowerShell Broken in Windows 10 Anniversary Update

So you updated to Windows 10 Anniversary and now have found yourself unable to connect to a remote PowerShell sessions. I noticed this in my management of Exchange Online in Office 365 after upgrading to Windows 10 version 1607 aka Anniversary Edition.

In my attempts to connect, as I have done in the past: http://jermsmit.com/azure-active-directory-module-for-windows-powershell-how-to-connect/ I encountered a error message:

 

Later comparing this with my down-level installs of Windows 10 and Server 2012 R2 this issue does not exist. So what changed?

It seems that the version of PowerShell which was updated may have something to do with this issue. This is when I attempted to run PowerShell in a down-level mode.

This is done by issuing the following command in an elevated command prompt (Run As Administrator): PowerShell.exe -Version 2.0

From this point we can now connect without issue.

Hope this helps