Forcing the Feature Update in Windows 10 in the Background

JasGot

We are going to be migrating almost 1100 workstations to a new domain in a month and I wanted to be sure all the Windows 10 PCs were on the latest version before we start.

This is what you will see (version may vary) if this is your situation.

We started this process last night, doing about 25 per day. Five per department at a time so they are not all affected at once. (Just a safeguard against potential Windows issues.)

Here is my working command and script to accomplish this.

Your execution may vary slightly. We run this from the BackStage window in ScreenConnect. This allows us to kick it off without interrupting the user and it is already an elevated Powershell Prompt. The PC will restart after hours.

We store the .ps1 script on the Deployment Share and we paste the command into the Powershell window of ScreenConnect Backstage.

This is the Script in the Deployment Share:

# Script Name: FUWindows.ps1
# Description: Trigger Windows 10 Feature Update and allow to restart after hours.

#Grab current Build Number and run the Update if we are behind.
$build = (Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion' CurrentBuild).CurrentBuild
if ($build -lt 19043)
{ 
# Setup the download location
$dir = "C:\FUWindows"
mkdir $dir

# Setup the Downloader
$webClient = New-Object System.Net.WebClient
$url = "https://go.microsoft.com/fwlink/?LinkID=799445"
$file = "$($dir)\Win10Upgrade.exe"

# Download the latest Feature Update
$webClient.DownloadFile($url,$file)

# Start the Feature Update Installer
Start-Process -FilePath $file -ArgumentList "/quietinstall /skipeula /auto upgrade /copylogs $dir"
}
else
{Write-Warning "Already at Desired Build"
}

This is the command we paste into the Powershell in Backstage(ScreenConnect):

Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process -Force; \\server\Deployment\FUWindows.ps1

The Feature Update runs quietly and there is no indication it is running unless you look at running processes. But, if you run the script again, you'll get a Pop-Up window telling you it is already running. You'll probably do this the first few times to be sure, but then you'll learn to trust it.

travisdh1

@jasgot said in Forcing the Feature Update in Windows 10 in the Background:

FUWindows.ps1

Best command name ever. Yes, I know what it actually means, doesn't make the alternative any less funny