PENDING In Place Upgrade rollback after 20 % Upgrading

[ramniwasyadav0]

Hi All,
i am trying to upgrade Win 10 1803 to 1903 via SCCM. downloading process completed and upgrading process is going on after that machine going restarted then upgrading process showing till 20 %. after that machine going restarted and showing undoing changes. after few mint roll backed not upgraded with new version 1903. machine model Dell Optiplex 380,390.
i am sharing setuperr.log with attachment and
setupact.log below

2019-10-31 11:19:13, Info SP Attempt to revert execution for operation 60
2019-10-31 11:19:13, Error SP Cannot revert execution of operation 60 (Cleanup source WIM file(s)). Execution queue is now compromised.[gle=0x00000012]
2019-10-31 11:19:13, Info SP Cannot revert execution in the queue, this is a fatal error.
2019-10-31 11:19:13, Error SP Operation execution failed: 6. hr = 0x8007001F[gle=0x00000012]
2019-10-31 11:19:13, Error SP ExecuteOperations: Failed execution phase Safe OS. Error: 0x8007001F[gle=0x00000012]
2019-10-31 11:19:13, Error SP CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x8007001F[gle=0x00000012]
2019-10-31 11:19:13, Info Persisting diagnostics data to D:\$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat
2019-10-31 11:19:13, Info Diagnostics data saved successfully
2019-10-31 11:19:13, Info SP Execution phase [Safe OS] exiting with HRESULT [0x8007001F]

 

[ramniwasyadav0]

hi All,
is any update regarding above issue.
i really appreciate your response.

 

[Prajwal Desai]

I see lot of errors and one of the error point to driver issue. I would like to take a look at Rollback logs.
Share Setuperr.log and Setupact.log named from
C:\$Windows.~BT\Sources\Rollback\
and
C:\$Windows.~BT\Sources\Panther

 

[ramniwasyadav0]

Hi Sir,
can i upgraded with win 10 1903 in dell optiplex 380,390 desktop.
Please find the below setupact.log .


2019-11-04 12:17:30, Info CBS CbsCoreFinalize: DpxUnload
2019-11-04 12:17:30, Info CBS CbsCoreFinalize: SrUnload
2019-11-04 12:17:30, Info CBS CbsCoreFinalize: CbsEsdUnload
2019-11-04 12:17:30, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2019-11-04 12:17:30, Info CBS CbsCoreFinalize: CbsEventUnregister
2019-11-04 12:17:30, Info CBS CbsCoreFinalize: AppContainerUnload
2019-11-04 12:17:30, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2019-11-04 12:17:30, Info DISM DISM Provider Store: PID=1576 TID=1600 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2019-11-04 12:17:30, Info DISM DISM Provider Store: PID=1576 TID=1600 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2019-11-04 12:17:30, Info DISM DISM Provider Store: PID=1576 TID=1600 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2019-11-04 12:17:31, Info DISM DISM OS Provider: PID=1576 TID=1600 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
2019-11-04 12:17:31, Info DISM DISM Provider Store: PID=1576 TID=1600 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2019-11-04 12:17:31, Info DISM DISM Manager: PID=1020 TID=1572 Closing session event handle 0x10e8 - CDISMManager::CleanupImageSessionEntry
2019-11-04 12:17:31, Info DISM DISM Provider Store: PID=1020 TID=1572 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-11-04 12:17:31, Info DISM DISM Provider Store: PID=1020 TID=1572 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2019-11-04 12:17:31, Info DISM DISM Provider Store: PID=1020 TID=1572 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2019-11-04 12:17:31, Info DISM DISM Provider Store: PID=1020 TID=1572 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2019-11-04 12:17:31, Info DISM DISM Provider Store: PID=1020 TID=1572 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2019-11-04 12:17:31, Info DISM DISM Provider Store: PID=1020 TID=1572 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=1572 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=284 Leave DismCloseSessionInternal - DismCloseSessionInternal
2019-11-04 12:17:31, Info MIG OC::COCDismAdapter::Release: DISM session closed succeessfully
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=284 Enter DismShutdownInternal - DismShutdownInternal
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=284 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=284 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=284 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=1568 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=1568 Successfully dequeued command object - CCommandThread:equeueCommandObject
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=1568 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=1568 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=1568 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=284 Deleted g_internalDismSession - DismShutdownInternal
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=284 Shutdown SessionTable - DismShutdownInternal
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=284 Leave DismShutdownInternal - DismShutdownInternal
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=284 DismApi.dll: - DismShutdownInternal
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=284 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2019-11-04 12:17:31, Info DISM API: PID=1020 TID=284 DismApi.dll: - DismShutdownInternal
2019-11-04 12:17:31, Info MIG DismShutdown hr = 0x0
2019-11-04 12:17:31, Error MIG OC Exception: [0x00000830]
2019-11-04 12:17:31, Error SP Could not restore OC status. Error: 0x8007001F
2019-11-04 12:17:31, Info SP SetupPlatform: Global progress: 20, Phase progress: 69
2019-11-04 12:17:31, Error SP Operation failed: Apply Optional Component status. Error: 0x8007001F[gle=0x000000b7]
2019-11-04 12:17:31, Info SP Operation can retry, we'll attempt to revert its execution.
2019-11-04 12:17:31, Info SP Attempt to revert execution for operation 25
2019-11-04 12:17:31, Info SP The current operation's changes could not be undone, we'll search for operations whose output might have been tainted
2019-11-04 12:17:31, Info SP Will have to revert execution for 35, as its output might have been tainted by the current operation
2019-11-04 12:17:31, Info SP Attempt to revert execution for operation 35
2019-11-04 12:19:39, Info SP Will revert execution for 60, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 114, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 49, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 50, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 51, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 52, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 53, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 66, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 110, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 38, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 24, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 48, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 117, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 117, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 117, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Will revert execution for 34, as it needed to be executed after the current operation
2019-11-04 12:19:39, Info SP Attempt to revert execution for operation 60
2019-11-04 12:19:39, Error SP Cannot revert execution of operation 60 (Cleanup source WIM file(s)). Execution queue is now compromised.[gle=0x00000012]
2019-11-04 12:19:39, Info SP Cannot revert execution in the queue, this is a fatal error.
2019-11-04 12:19:39, Error SP Operation execution failed: 6. hr = 0x8007001F[gle=0x00000012]
2019-11-04 12:19:39, Error SP ExecuteOperations: Failed execution phase Safe OS. Error: 0x8007001F[gle=0x00000012]
2019-11-04 12:19:39, Error SP CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x8007001F[gle=0x00000012]
2019-11-04 12:19:40, Info Persisting diagnostics data to D:\$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat
2019-11-04 12:19:40, Info Diagnostics data saved successfully
2019-11-04 12:19:40, Info SP Execution phase [Safe OS] exiting with HRESULT [0x8007001F]

 

[Jen]

Was this issue ever resolved? I'm seeing the same errors on an OptiPlex 7010 while testing a upgrade task sequence from 1903 to 1909.

 

[Jen]

I think the issue I was having was because the OptiPlex 7010 isn't officially supported for 1909. I was looking through Dell's documentation, and it doesn't look like the OptiPlex 380 or 390 are on the compatibility lists for any of the Win10 versions either. Here's the link to that contains tested/supported models by Win10 version:

Dell Computers Tested for Windows 10 2022 Update and Previous Versions of Windows 10 | Dell US