I wanted to test deployment of WIn 10 20H2 so in WSUS we approved it just for our IT computers OU. Through the manual windows update mechanism it did show up and install. So we know the binaries are downloaded fully on our WSUS server, I wanted to see if I could use the Update manager wizard in Patch Manger to push this update out to a specific computer. I walk through the wizard and I monitor the active task until it goes away. I check task history and there are two line items for this update Download Success Successfully downloaded 10/29/2020 10:19:35 Install Failed Install failed. The installer requires more data to be downloaded HRESULT: 0x8024200D 10/29/2020 10:20:06 Any idea how to push this through? I think 1809 turns pumpkin in November and would like to push out the newest build to the handful of machines we have on it behind the scenes without asking the user to take over and remote control on and do an interactive windows 10 install.

This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Test deployment of Win 10 20H2 - fails The installer requires more data to be downloaded

kjstech over 3 years ago

I wanted to test deployment of WIn 10 20H2 so in WSUS we approved it just for our IT computers OU. Through the manual windows update mechanism it did show up and install.

So we know the binaries are downloaded fully on our WSUS server, I wanted to see if I could use the Update manager wizard in Patch Manger to push this update out to a specific computer. I walk through the wizard and I monitor the active task until it goes away. I check task history and there are two line items for this update

Download	Success	Successfully downloaded	10/29/2020 10:19:35
Install	Failed	Install failed. The installer requires more data to be downloaded HRESULT: 0x8024200D	10/29/2020 10:20:06

Any idea how to push this through? I think 1809 turns pumpkin in November and would like to push out the newest build to the handful of machines we have on it behind the scenes without asking the user to take over and remote control on and do an interactive windows 10 install.

Top Replies

jhuffman7 over 3 years ago +2

We ended up scripting the upgrade using the media creation tool. Here's the powershell code, and I used PSExec to execute it remotely. ## Downloads the latest Windows 10 Upgrade Assistant $dir …

Parents

0 jhuffman7 over 3 years ago

We ended up scripting the upgrade using the media creation tool.

Here's the powershell code, and I used PSExec to execute it remotely.

## Downloads the latest Windows 10 Upgrade Assistant

$dir = "C:\Install\Win10Upgrade20H2"
mkdir $dir
$webClient = New-Object System.Net.WebClient
$url = "https://go.microsoft.com/fwlink/?LinkID=799445"
$file = "$($dir)\Win10Upgrade.exe"
$webClient.DownloadFile($url,$file)
Start-Process -FilePath $file -ArgumentList "/passiveinstall /skipeula /auto upgrade /copylogs $dir" -verb runas

0 shocko over 3 years ago in reply to jhuffman7

So I found that if I set the option on the PM task 'Force download' the 2nd time I run the task it downloads the ESD file from our WSUS server.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 shocko over 3 years ago in reply to jhuffman7

So I found that if I set the option on the PM task 'Force download' the 2nd time I run the task it downloads the ESD file from our WSUS server.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data