1709 to 1803 fails

Hi guys,

Not sure if this is the appropriate place to ask about this but here is my issue. I'm attempting to update some of the laptops at my work. They are still running on 1709. I'm trying to upgrade them to 1803. I can't go any further than 1803 due to Checkpoint VPN restrictions that are out of my hands. I've downloaded the 1803 ISO from techbench and attempted the upgrade on several laptops. Quite a few of them fail around 50-56%. I've attached the setuperr.log from C:\$WINDOWS.~BT\Sources\Panther post install attempt.

Any support or guidance in the right direction would be appreciated.

Thank you,

 

You seem to have problems like this:
1. You do not have permission to update (you are not an administrator or not in administrator privileges)
2. The computers you are trying to upgrade are not OK, they are damaged.
3. The computers you are trying to upgrade have not been cleaned. It's probably there is many old Junk files and outdated registry keys.
Recommendations:
1. get or/and use administrator privileges or reset files and folder default permissions
2. before upgrading You must repair and clean up current version
There may be some more reasons, but these are not discoverable using given data.

 

Thank you.

How would I go about starting your recommendations? I am a local Administrator so how would I go about resetting default permissions?

 

I do not know other methods than just backup personal files and data, then disk full formatting (not Quick) and a completely new installation.
Maybe someone else knows other options.

 

I'm trying to avoid that, due to these being current users of mine laptops. I'm trying to keep the inconvenience of upgrading to a minimum for them. I know that's an option I may have to take if all else fails. Thanks again.

 

The log you provided doesn't have enough information. Post the full log or try removing whatever is using the offending cisco related DLL file that threw the error in the bit of the log you provided.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

/edit, nvm it failed

 

Question about: "I can't go any further than 1803 due to Checkpoint VPN restrictions" = Do you try to upgrade via Endpoint Remote Secure Access (that VPN)?

And what's about the running 1709: is that on Insider or with Digital License?

Finally: Did you have access to the physical computer at all?

Thanks.

 

You need to login to view this posts content.

 

This is supported since 1803, iirc, then the licensing things changed which enabled Pro to be able to upgrade all other home(sl)+ SKUs.

I have to do a new test (this was 2 years ago discovered) check but afaik WU also uses Pro for all upgrades for Enterprise and such by UUP.

 

You need to login to view this posts content.

 

Yeah, checked the log again and it seems to migrate, it's probably just the dynamic update feature that is not supported

Code:

2020-03-05 13:20:16, Info                  MOUPG  UpdateMedia: Media Edition [Enterprise] is not supported
2020-03-05 13:20:16, Info                  MOUPG  UpdateMedia: Scenario not supported for media update
2020-03-05 13:20:16, Info                  MOUPG  UpdateMedia:     Block reasons = [0x85]
2020-03-05 13:20:16, Info                  MOUPG  UpdateMedia: Leaving Execute Method

Anyway, OP should still get the all-editions ISO as it does not hurt to have - might prevent a few quirks when booting the upgrade media / being asked about product key
+ check free space before running setup
+ force delete C:\$WINDOWS.~BT before running setup
+ either update drivers (Dell lists way newer BIOS and drivers - specially storage-ralated) or revert the old ones installed to Microsoft ones (Intel storage for example) before running setup - it was mentioned in my first reply
+ use the launch options I suggested (the last log does not show them in use, and it errors on multiple steps with the recovery partition)
No joy? burn to dvd/iso and boot from media

edit: just remembered about having dism broken for wim (esd ok) due to a filter driver
op, can you post output from powershell as admin:
fltmc filters|select -skip 3|%{sc.exe qc ($_ -split ' ')[0]}

 

Yep, I have seen some members with failing upgrades reporting back that after a bios update all went fine

 

You need to login to view this posts content.

 

Also tried this. I got "The upgrade option isn't available if you start your computer using the Windows Installation media."

 

Any ideas?

 

Sorry, but You know for a month that there is only one way - to do a new clean installation. And in future hold Your computer in good health and should be updated regularly.