Anyone else having issues upgrading to 20H2?

[ExhaustedTech]

For some reason, I am having a very difficult time getting any devices to upgrade via BP anymore. More often than not, BP reports it back as successful but it isn’t.
If I run the setup.exe directly from the PC, it works fine but running the same setup.exe with the auto upgrade and quiet just doesn’t install for most devices. I’m at about a 15% success rate and cannot figure out why.

[doug]

What version of BP are you using?

So you’ve tried both methods described at this link, and neither works? ( https://batchpatch.com/remotely-deploying-windows-feature-update-version-20h2-the-october-2020-update-to-numerous-computers ) And both methods report successful despite not actually being successful? And you are definitely rebooting the target computer after applying the update, and then letting the target computer perform the install and reboot as many times as it needs to in order for it to complete the process?

I would suggest starting by looking at this: https://batchpatch.com/troubleshooting-windows-feature-update-upgrade-errors

I will note that in version 20201029 of BP, there was a fix for the built-in method (the method that uses the Windows Update feature in BP, not the deployment setup.exe /auto upgrade /quiet method), where if your target OS was a business edition, it would report success despite not being successful:

20201029
-Fixed issue where Windows 10 feature update preparation step was not running after download of ‘Feature update to Windows 10 (business editions)’, so upon reboot the installation would not be automatically triggered at the target computer

And in the most recent 20210827 release of BP we published a fix for the built-in method (the method that uses the Windows Update feature in BP, not the deployment setup.exe /auto upgrade /quiet method) where if your target OS is a non-English version, it would sometimes report success even though it wouldn’t install.

20210827
-Fixed issue where Windows 10 feature updates for non-English versions of Windows would sometimes not get installed despite BatchPatch reporting ‘Installation Result: Succeeded’

However, it doesn’t sound like either of these would affect you because you’re using the deployment setup.exe /auto upgrade /quiet method. I would, as a start, make sure that you are following the deployment method instructions *exactly* as described at the link at the top of this page. Are you missing the “copy entire directory” and/or “leave entire directory” checkboxes? Is your deployment command identical to the command shown in that tutorial?

[ExhaustedTech]

Perhaps I should get clarification on something first- Does method two only work when not using a SUS for regular updates? I have SCCM that is used for regular updates but I use BP for upgrades.

Version is 2021.8.27.12.28
I actually have been copying the ISO contents to a BP folder locally on each machine and running from there as a remote command since my success rate doing it as a deployment was only about 7%.
I’ve been working on this for about 2 weeks now and have been letting the job sit for 6-12 hours sometimes, just to make sure they have enough time to finish so I don’t think that’s the issue. And since it is working on a few devices, I assume my parameters and everything else is correct.

Maybe I’m incorrect but I thought running the built-in method would not work since we have a SUS, is that right?

I’ve done upgrades in the past without any issues and the only major thing that has changed since then is we’ve gone from WSUS to SCCM SUS.

[doug]

Third party tools like BP are not compatible with SCCM or with the WSUS/SUS that is controlled by SCCM.

However, the built-in method would/should work if you change your BP server selection (Tools > Settings > Windows Update > Server Selection) to ‘Windows Update’ or ‘Microsoft Update’.

Yeah, if you’re using the same command/deployment on multiple machines, and it’s working on some but not all, then the method is prob not the issue. I would suggest reviewing the link I posted about about how to troubleshoot feature update issues. I’d also consider which OS build is running on the targets before the upgrade attempt. Are they all the same or are the working ones not the same OS build as the non-working ones? And also consider the hardware of the target systems, which could potentially play a roll. I know you said if you run the setup manually at a machine it always works, but I’m a bit skeptical that that could be true in all cases. Something doesn’t sound right. Running the command remotely or doing it locally/manually really shouldn’t have an impact in this case. Also we have never had any similar reports. We have many people using these methods without any issues, so I’m struggling to guess what could be happening in your case. Though like I said, please start with reviewing the troubleshooting link I posted and see if helps you identify any issues. Let me know what you discover, if anything.

[ExhaustedTech]

We basically only have two different computers, one model for desktop and one for laptop. They’re all on 1909.
The ones that do actually give an error code are ones that are running low on space or something like an incompatible driver but there are very few. The rest show zero signs of error in either BP or the Windows Updates logs so I don’t know how to investigate. I’ll keep trying though.

[ExhaustedTech]

I killed the grid, deleted the deployments and queues and started from scratch. I was using the same deployments from previously and just changed names/paths. It didn’t like something or something was just corrupt. Once I started fresh, it’s working as expected

[doug]

Very strange. Glad you figured it out!! Thanks for reporting back.

[Author]

Posts