Resolved: Feature update to Windows 10, version 1709 – Error 0x80242006

Working with some of my team mates this week, I was hearing about multiple machines failing the Fall Creators Update (FCU) 1709 with a Windows Update error of ” Feature update to Windows 10, version 1709 – Error 0x80242006 ” .  Looking around the internet I see a lot of people hitting the common solutions but no real success.

Common Solution (doesn’t always work)

  1. Run the Windows Update Troubleshooter
    1. Open the Windows Settings – Formerly known as the Control Panel
    2. Select Update & Security – Last option
    3. Select Troubleshoot – 4th one down left side
    4. Click on Windows Update under Windows.
    5. Click on Advanced on the Windows update dialog box and click on Run as administrator (Enter the credentials if required).
    6. Click on Next and follow onscreen instruction complete the Windows Update troubleshooter
  2. Deleting the %windir%\SoftwareDistribution folder (requires you to stop several services)

The two steps above only partially fixes the issue.  Solution is below!

Windows Update Log File

  1. Create the Windows Update Log file: Get-WindowsUpdateLog
    1. PowerShell Source: https://blogs.technet.microsoft.com/mniehaus/2017/10/10/improved-windows-update-log-formatting-with-windows-10-1709/
  2. Open the log file
    1. I still use cmtrace.exe as my primary log file viewer
      1. https://www.microsoft.com/en-us/download/details.aspx?id=50012
    2. I have found Glogg is much faster but less formatting
      1. http://glogg.bonnefon.org/download.html

Root Cause

You have at least two issues

  1. Partial download in the Software Distribution folder may be corrupted (someone rebooted for a reason)
  2. Real: You windows update agent registered a download but can’t clear it out

Solution

You need to stop services remove/rename two folders then restart services.  Please be aware cryptSvc will try to restart so do the following quick.

  1. Press Windows Key + X on the keyboard and then select “Command Prompt (Admin)” or “Windows PowerShell (Admin)” from the menu.
  2. Stop the following services in order Windows Update Services, Cryptographic, Background Intelligent Transfer Service (BITS), and MSI Installer.  The following command lines will work just fine.
net stop wuauserv
net stop cryptSvc
net Stop DoSvc
net stop bits
net stop msiserver

3. Rename the SoftwareDistribution and Catroot2 folders.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old

4. Now, let’s restart the BITS, Cryptographic, MSI Installer and the Windows Update Services.

net start msiserver
net start bits
net start DoSvc
net start cryptSvc
net start wuauserv

5. Rerun Windows Update to install FCU 1709

Notes

Media Creation Tool Fails

Media creation tool did not work in this environment because all clients are configured to be controlled via Microsoft System Center Configuration Manager (SCCM or ConfigMgr)

PowerShell

How to stop and start services

Get-Service BITS | Where {$_.status –eq 'Stopped'} |  Start-Service

Get-Service BITS | Where {$_.status –eq 'Running'} |  Stop-Service

How to rename a folder

Rename-Item -path 'C:\Windows\SoftwareDistribution' -NewName 'C:\Windows\SoftwareDistribution.old'

Rename-Item -path 'C:\Windows\catroot2' -NewName 'C:\Windows\catroot2.old'

 

 

Advertisements

Windows Insider MVP: 2018

Congratulations! Thank you for your continued contributions to the Windows community, we are excited to re-award you as a Windows Insider MVP. This award is a token of our appreciation, your leadership and passion help make Windows the best yet. We look forward to our on-going collaboration with you and all of our Windows Insider MVPs as we continue to strengthen the Windows Insider MVP (WI MVP) Program.

A nice way to start 2018!  Thanks to all that I have had the pleasure of learning from.  I look forward to getting better together and sharing it!

 

 

Fixed: Task Manager Replaced by Sysinternals Process Explorer

I frequently benefit from Microsoft Sysinternals tools like Process Explorer (ProcExp64.exe).  One of the features is the ability to replace the Task Manager Default with Process explorer.

Process Explorer x64

However, I found a bug.  If you use the x64 version of Process Explorer to change the default you can’t change it back!?!?

Solution: You have to open the x86 version of the application.  Set the application again then a tiny check box appears.  Once you have the check box you can undo the default value.

Process Explorer x64 Check

X86 = ProceExp.exe (no 64 in the name)

Enjoy

 

What’s new in Windows 10 Fall Creators Update, Redstone 3, 1709, 16299, etc

Hello all,

In the past month I have done 3 separate talks about the new release of Windows 10 FCU (1709).  The link below is the slides from the last talk:

CTSMUG201710 – Fall Creators Update 1709

The 5 links below are the most useful but I call out a lot of good data below.

Best

Windows Insider for Business (WIPfB) now with GPO control. Time to get a true pilot group in your enterprise

https://insider.windows.com/en-us/for-business-organization-admin/?utm_source=other&utm_medium=email&utm_campaign=201710-AdminAnnounce&utm_content=WIP_Body_OrgAdmin

 

You can now opt in people via GPO.

You can turn on Telemetry, Enable WIP, Select which build the machine gets.

You can view others submitted feedback from your company.  HOWEVER, you cannot edit or modify your companies submissions, yet.
I still say do a query of your enterprise to see who is already opted in.  Those who opted in over the past few years are your canary in a coal mine.

 

WAAS: Naming Structure Not-So-Secret Decoder Ring

In the past year we have had a lot of Nomenclature Changes for Windows As A Service (WAAS).  The following slide from Ignite 2017 really clears it up.  Just like designer MUD in a SPA.

WAAS Naming Alignment 01

How often Office and Windows updated?

WAAS Naming Alignment 02

What versions of Microsoft System Center Configuration Manager (ConfigMgr / SCCM) supports 1709 next week.

WAAS Naming Alignment 03

Windows 10 Fall Creators Update, 1709, Microsoft Windows [Version 10.0.16299.15], Redstone 3, RS3 release is Oct 17th 2017.  I know a lot of names for the same piece of software.

I am excited for next week.

Slide Source: https://view.officeapps.live.com/op/embed.aspx?src=https%3A%2F%2F8gportalvhdsf9v440s15hrt.blob.core.windows.net%2Fignite2017%2Fsession-presentations%2FBRK3075.PPTX

Windows 10 Fall Creators Update (1709) Deprecated Features – PowerShell 2.0 is EOL among others

Fall Created Update (2017 RS3 1709) will be removing some more security holes.  I wonder if some of these are in response to the SMB1 fiasco (WannaCry for example).

  • TLS RC4 ciphers.
  • The SCCM Windows Hello deployed feature which has been replaced with the Registration Authority of Active Directory Federation Services
  • SysKey.exe gone in favor of Bitlocker
  • Enhanced Mitigation Experience Toolkit (EMET) is being removed for Windows Defined Exploit Guard (WDEG) feature
  • PowerShell 2.0 is very security holey – Twitter Tears Shed – Jeffery Snover
    • For example you can invoke PoSH 2.0 if it is installed.  Since it lacks logging you will have no idea what happened.  Most companies I work with just remove it from 1703.

Posted July 20th 2017 a list of features that are being depreciated or Removed from 1709.

Deprecated

Windows PowerShell 2.0

Applications and components should be migrated to PowerShell 5.0+.

Microsoft Paint

Will be available through the Windows Store. Functionality integrated into Paint 3D.

RSA/AES Encryption for IIS

We recommend that users use CNG encryption provider.

System Image Backup (SIB) Solution

We recommend that users use full-disk backup solutions from other vendors.

TLS RC4 Ciphers

To be disabled by default. For more information, see the following Windows IT Center topic:

TLS (Schannel SSP) changes in Windows 10 and Windows Server 2016

Removed

Enhanced Mitigation Experience Toolkit (EMET)

Use will be blocked. Consider using the Exploit Protection feature of Windows Defender Exploit Guard as a replacement.

Syskey.exe

Removing this nonsecure security feature. We recommend that users use BitLocker instead. For more information, see the following Knowledge Base article:

4025993 Syskey.exe utility is no longer supported in Windows 10 RS3 and Windows Server 2016 RS3

TCP Offload Engine

Removing this legacy code. This functionality was previously transitioned to the Stack TCP Engine. For more information, see the following PFE Platform Blog article:

Why Are We Deprecating Network Performance Features (KB4014193)?

 

 

Full List Source: https://support.microsoft.com/en-us/help/4034825/features-that-are-removed-or-deprecated-in-windows-10-fall-creators-up