inplace Upgrade Windows 10 from 1709 to 1809 faild

We have to Upgrade aprox 2000 client computers from Windows 10 1709 to 1809.

We want to Upgrade this computers with an inplace upgrade. I have downloaded the ISO image from Volume licensing; modify the install.wim file so it is suitable for us. This wim file works fine for me at the following scenarios.

• I can do a fresh (Bare-Metal-Provisioning) install Windows on a computer without any problems.
• If the installation of the Version 1709 is fresh, I can update to 1809 without any problems.

But when a user was working on the Computer or there are mutable Userprofiles with data are on the computer - Update is failing at about 84%-85% and it performs a rollback.



As an example: if I take two a computer from the same Model with Windows 10 1709 installed. The first Computer used by a user for a while. The second is fresh installed 1709 and I trie to Updated them.

The upgrade failed on both computers.

I have uninstalled the Virus Protection. Then the Upgrade on the fresh installed Windows 1709 Computer run thru without a Problem. On the same model witch was in use for a while.

• The upgrade failed.

Run "dism /online /cleanup-image /restorehealth" and "sfc /scannow"

• The upgrade failed

Updatde Drivers and Bios

• The upgrade failed

Unistall a bunch of Software

• The upgrade failed

I Run the SetupDiag tool and it always gives me these logs back



Firs Version:

Matching Profile found: FindRollbackFailure - 3A43C9B5-05B3-4F7C-A955-88F991BB5A48

SetupDiag version: 1.5.0.0

System Information:

Machine Name = Offline

Manufacturer = HP

Model = HP ZBook 15 G4

HostOSArchitecture = 1033

FirmwareType = UEFI

BiosReleaseDate = 20190430000000.000000+000

BiosVendor = P70 Ver. 01.28

BiosVersion = P70 Ver. 01.28

HostOSVersion =

HostOSBuildString = 16299.637.amd64fre.rs3_release_svc.180808-1748

TargetOSBuildString =

HostOSLanguageId =

HostOSEdition = Enterprise

RegisteredAV =

FilterDrivers = FileInfo

UpgradeStartTime = 05.07.2019 12:58:36

UpgradeEndTime = 05.07.2019 13:29:12

UpgradeElapsedTime = 00:30:36

CV = XRhZOSXnvUqCBvhK

ReportId =





Error: SetupDiag reports rollback failure found.

Last Phase = Pre OOBE Boot

Last Operation = OOBE boot apply

Error = 0x8007042B-0x4000D

LogEntry: 2019-07-05 13:29:12, Error SP Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]

LogEntry: 2019-07-05 13:29:12, Error SP Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]



Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.




Or Second Version


atching Profile found: FindRollbackFailure - 3A43C9B5-05B3-4F7C-A955-88F991BB5A48

SetupDiag version: 1.5.0.0

System Information:

Machine Name = Offline

Manufacturer = HP

Model = HP ZBook 15 G4

HostOSArchitecture = 1033

FirmwareType = UEFI

BiosReleaseDate = 20190430000000.000000+000

BiosVendor = P70 Ver. 01.28

BiosVersion = P70 Ver. 01.28

HostOSVersion = 10.0.16299

HostOSBuildString = 16299.637.amd64fre.rs3_release_svc.180808-1748

TargetOSBuildString = 10.0.17763.345 (rs5_release_svc_prod2.190213-1831)

HostOSLanguageId =

HostOSEdition = Enterprise

RegisteredAV =

FilterDrivers = FileInfo

UpgradeStartTime = 15.07.2019 08:42:53

UpgradeEndTime = 15.07.2019 09:14:54

UpgradeElapsedTime = 00:32:01

CV = 1qvGJs7pQUCDQU/D

ReportId =





Error: SetupDiag reports rollback failure found.

Last Phase = Pre OOBE Boot

Last Operation = OOBE boot apply

Error = 0xC1900101-0x4000D

LogEntry:

LogEntry:



I can provide more logs if necessary



I have tried this on differed HP Models but the behavior is always the same as I have descripted. I have also done many researches on this topic but I did not find a specific solution what exactly went wrong during the Update.



I have also opened a case by Microsoft, but they could not provide me a solution for this Problem so far.



My question about the issue is:

Is there a way to research in the logs to find out what exactiy the Problem is during the Upgrade like a Problem with this dll or with that registry entry or Software XY or etc….



Many thanks for any Help.



Thomas Odermatt

Weiterlesen...