Try to upgrade 17672 to 17677/17682 but got 0x8007001f

setupact.log, from where I consider issues start:

2018-06-01 13:24:50, Info                  CSI    00000001 Shim considered [l:145]'\??\C:\$WINDOWS.~BT\NewOS\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17682.1000_none_af72f4b2be9d3dd4\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2018-06-01 13:24:50, Info                  CSI    00000002 Shim considered [l:142]'\??\C:\$WINDOWS.~BT\NewOS\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17682.1000_none_af72f4b2be9d3dd4\wcp.dll' : got STATUS_SUCCESS
2018-06-01 13:24:50, Info                  DISM   DISM Package Manager: PID=1956 TID=1940 Loaded servicing stack for offline use only. - CDISMPackageManager::CreateCbsSession
2018-06-01 13:24:50, Info                  CBS    Lazy store initialization mode
2018-06-01 13:24:50, Info                  CBS    Lazy store initialization mode, fully initialize.
2018-06-01 13:24:50, Info                  CBS    Offline image is writable
2018-06-01 13:24:50, Info                  CBS    Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SOFTWARE' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\SOFTWARE'.
2018-06-01 13:24:50, Info                  CBS    Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SYSTEM' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\SYSTEM'.
2018-06-01 13:24:50, Info                  CBS    Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SECURITY' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\SECURITY'.
2018-06-01 13:24:50, Info                  CBS    Loading offline registry hive: SAM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SAM' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\SAM'.
2018-06-01 13:24:50, Info                  CBS    Loading offline registry hive: COMPONENTS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/COMPONENTS' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\COMPONENTS'.
2018-06-01 13:24:50, Info                  CBS    Loading offline registry hive: DRIVERS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/DRIVERS' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\DRIVERS'.
2018-06-01 13:24:50, Info                  CBS    Loading offline registry hive: DEFAULT, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/DEFAULT' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\System32\config\DEFAULT'.
2018-06-01 13:24:50, Info                  CBS    Loading offline registry hive: ntuser.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Users/Default/ntuser.dat' from path '\\?\C:\$WINDOWS.~BT\NewOS\Users\Default\ntuser.dat'.
2018-06-01 13:24:50, Info                  CBS    Loading offline registry hive: schema.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/system32/smi/store/Machine/schema.dat' from path '\\?\C:\$WINDOWS.~BT\NewOS\Windows\system32\smi\store\Machine\schema.dat'.
2018-06-01 13:24:50, Info                  CSI    00000cf3 CSI Store 2476542714544 initialized
2018-06-01 13:24:50, Info                  CBS    Build: 17682.1000.amd64fre.rs_prerelease.180525-1616
2018-06-01 13:24:50, Info                  CBS    Session: 1956_746078 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Exit DismCheckImageHealthInternal - DismCheckImageHealthInternal
2018-06-01 13:24:50, Error                 MIG    OC::COCDismAdapter::EnableDisableOCs: Image is not serviceable; cannot proceed.[gle=0x0000007a]
2018-06-01 13:24:50, Error                 MIG    OC::CInstalledOCStore::ModifyOCsState: Failed to enable and disable OCs; hr = 0x800F0830[gle=0x0000007a]
2018-06-01 13:24:50, Error                 MIG    Failed to restore OC status; HRESULT = 0x800F0830[gle=0x0000007a]
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Enter DismCloseSessionInternal - DismCloseSessionInternal
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Input parameters: Session: 2 - DismCloseSessionInternal
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Refcount for DismSession= 2s 0 - CSessionTable::RemoveSession
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1976 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1976 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1976 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1976 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1956 TID=1940 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1956 TID=1940 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1956 TID=1940 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1956 TID=1940 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-06-01 13:24:50, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SOFTWARE
2018-06-01 13:24:50, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SYSTEM
2018-06-01 13:24:50, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SECURITY
2018-06-01 13:24:50, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SAM
2018-06-01 13:24:50, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/COMPONENTS
2018-06-01 13:24:50, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/DRIVERS
2018-06-01 13:24:50, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/DEFAULT
2018-06-01 13:24:50, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Users/Default/ntuser.dat
2018-06-01 13:24:50, Info                  CBS    Force unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/system32/smi/store/Machine/schema.dat
2018-06-01 13:24:50, Info                  DISM   DISM Package Manager: PID=1956 TID=1940 Finalizing CBS core. - CDISMPackageManager::Finalize
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2018-06-01 13:24:50, Info                  CBS    Execution Engine Finalize
2018-06-01 13:24:50, Info                  CBS    Execution Engine Finalize
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: GetPublicObjectMonitor::Audit
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: WcpUnload
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: DrupUnload
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: DpxUnload
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: SrUnload
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2018-06-01 13:24:50, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1956 TID=1940 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1956 TID=1940 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1956 TID=1940 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2018-06-01 13:24:50, Info                  DISM   DISM OS Provider: PID=1956 TID=1940 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1956 TID=1940 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-06-01 13:24:50, Info                  DISM   DISM Manager: PID=1384 TID=1976 Closing session event handle 0x974 - CDISMManager::CleanupImageSessionEntry
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1384 TID=1976 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1384 TID=1976 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1384 TID=1976 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1384 TID=1976 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1384 TID=1976 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1384 TID=1976 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-06-01 13:24:50, Info                  DISM   DISM Provider Store: PID=1384 TID=1976 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1976 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Leave DismCloseSessionInternal - DismCloseSessionInternal
2018-06-01 13:24:50, Info                  MIG    OC::COCDismAdapter::Release: DISM session closed succeessfully
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Enter DismShutdownInternal - DismShutdownInternal
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1984 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1984 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1984 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1984 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1984 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Deleted g_internalDismSession - DismShutdownInternal
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Shutdown SessionTable - DismShutdownInternal
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 Leave DismShutdownInternal - DismShutdownInternal
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 DismApi.dll:                                          - DismShutdownInternal
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2018-06-01 13:24:50, Info                  DISM   API: PID=1384 TID=1388 DismApi.dll:                                          - DismShutdownInternal
2018-06-01 13:24:50, Info                  MIG    DismShutdown hr = 0x0
2018-06-01 13:24:50, Error                 MIG    OC Exception:  [0x00000830]
2018-06-01 13:24:50, Error                 SP     Could not restore OC status. Error: 0x8007001F
2018-06-01 13:24:50, Info                  SP     SetupPlatform: Global progress: 23, Phase progress: 79
2018-06-01 13:24:50, Error                 SP     Operation failed: Apply Optional Component status. Error: 0x8007001F[gle=0x000000b7]
2018-06-01 13:24:50, Info                  SP     Operation can retry, we'll attempt to revert its execution.
2018-06-01 13:24:50, Info                  SP     Attempt to revert execution for operation 25
2018-06-01 13:24:50, Info                  SP     The current operation's changes could not be undone, we'll search for operations whose output might have been tainted
2018-06-01 13:24:50, Info                  SP     Will have to revert execution for 34, as its output might have been tainted by the current operation
2018-06-01 13:24:50, Info                  SP     Attempt to revert execution for operation 34
2018-06-01 13:25:07, Info                  SP     Will revert execution for 112, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 48, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 49, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 50, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 51, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 52, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 65, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 108, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 37, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 23, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 23, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 23, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 23, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 23, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 23, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 23, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 23, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 23, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 23, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 24, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 47, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 116, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 33, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Will revert execution for 33, as it needed to be executed after the current operation
2018-06-01 13:25:07, Info                  SP     Attempt to revert execution for operation 112
2018-06-01 13:25:07, Info                  SP     Attempt to revert execution for operation 48
2018-06-01 13:25:07, Info                  SP     Attempt to revert execution for operation 49
2018-06-01 13:25:07, Info                  SP     Attempt to revert execution for operation 50
2018-06-01 13:25:07, Info                  SP     Attempt to revert execution for operation 51
2018-06-01 13:25:07, Info                  SP     Attempt to revert execution for operation 52
2018-06-01 13:25:07, Info                  SP     Attempt to revert execution for operation 65
2018-06-01 13:25:07, Info                  SP     Attempt to revert execution for operation 108
2018-06-01 13:25:07, Info                  SP     The current operation's changes could not be undone, we'll search for operations whose output might have been tainted
2018-06-01 13:25:07, Info                  SP     Attempt to revert execution for operation 37
2018-06-01 13:25:07, Error                 SP     Cannot revert execution of operation 37 (Apply EAs for C:\$WINDOWS.~BT\NewOS). Execution queue is now compromised.[gle=0x00000012]
2018-06-01 13:25:07, Info                  SP     Cannot revert execution in the queue, this is a fatal error.
2018-06-01 13:25:07, Error                 SP     Operation execution failed: 6. hr = 0x8007001F[gle=0x00000012]
2018-06-01 13:25:07, Error                 SP     ExecuteOperations: Failed execution phase Safe OS. Error: 0x8007001F[gle=0x00000012]
2018-06-01 13:25:07, Error                 SP     CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x8007001F[gle=0x00000012]
2018-06-01 13:25:07, Info                         Persisting diagnostics data to C:\$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat
2018-06-01 13:25:07, Info                         Diagnostics data saved successfully

setuperr.log:

Hi Nero,

A quick look at the log yields at least this:

2018-06-01 12:51:21, Error                 CONX   Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514):   App Inventory returned duplicate file c:\program files (x86)\razer\razer services\gms\gamemanagerservice.exe.[gle=0x8007000d]
2018-06-01 12:51:22, Error                 CONX   Windows::Compat::Appraiser::WicaApplicationInventory::AddItemProperty (514):   App Inventory returned duplicate file c:\program files (x86)\razer\synapse3\service\razer synapse service.exe.[gle=0x8007000d]

Which seems to be related to the Razor mouse you (apparently |--) have and/or the software you installed for it. I would simply try

1) Uninstall that software (your mouse should still work) and try the upgrade again. If it succeeds you can try and reinstall that software. What happens then is anybodies guess but chances are that it will work. Then again, even if it does work then you can probably still expect the same issues on the next upgrade.

2) If 1) fails, disconnect the Mouse altogether during the upgrade.

Regards,

Stephen

Hi Stephen,

Then I did both, then failed again. It turns out to be the problem of Borderless Gaming.

I uninstalled it and consider Razer Synapse and Borderless Gaming was both startup apps, I disabled all startup. Then failed again.

In this time, seems like setuperr.log shows no third-party apps relevant to the failure, which I cannot make sure. I'll paste it below.

I temporarily switched Insider Channel to Slow so the log could be preserved. Any other info would be provided if necessary. Hope you can give a help. Thanks.

Nero

setuperr.log:

Hi Nero,

What a pity that it did not work but it was worth a try. So as to what is causing the failure remains.

Here are some common causes that regularly pop up:

1) You are running 3rd-party AV software.

2) You have some external hardware attached that causes issues

(simple remedy: unplug any non-essential USB and/or other hardware)

3) You have some internal hardware that causes issues

(often very hard to identify and/or fix, but I think it unlikely)

I can tell you now that it will probably come down to installing your machine scratch which is a lot of work but almost always the quickest route to get your system running properly. (i.e. doing a Clean Install). 

Switching to the Slow Ring is a good move, until 'we' decide what to do.

As to what to do, try a 'fix' or go for a Clean Install, is something I cannot answer until I know more about your system and indeed, your familiarity with doing such a procedure.

Assuming that 1)-3) are not causing the failure and that you're not to sure what a Clean Install actually is, I suggest you do a search (in this forum) on Clean Install. Plenty of posts about this and no need for me to repeat (it's rather a lot to explain).

Some remarks about your system would be helpful and also this:

Q) Anything 'special/remarkable/unusual' about your system? (As compared to an average PC)

Q) How good is your current system running?

Q) Do you know what's on your machine, that is, for example: How to install all that software that doesn't come out-of-the-box.? Do you know exactly where you stored that data-you-cannot-afford-too-lose?

Stephen.

Here's a tip for Clean Installers (Fast Ring): Try and wait with a Clean Install until the gap between the available ISO and 'your' latest available preview is small... -ish.

Hi Stephen,

Thank you for your advice. Actually I have no third-party AV software installed (just Defender), no external hard drive attached, and my internal hard drive is Intel-RST-Premiumed dual M.2 SSD that is in RAID0. It's dual Toshiba XG3 -- not the XG4 or XG5 series mentioned on reports that have compatibility issues with Windows 10 1803, besides.

Info about my system:

Aorus X3 V7

CPU: Intel Core i7-7820HK (overclocked, usually cancel overclock before upgrading to the new version)

Memory: Kingston Hyper-X 16GB x2 DDR4-2400

Hard Drive: Toshiba XG3 1TB x2 (Intel RST Premium RAID0)

Graphics Card: Mobile NVIDIA GeForce GTX 1060 6GB

For your question:

A1) This last clean install is about on 17063. To perform this install, I get original 17063 UUP files, convert to wim, then use DISM to extract wim. The next step is to backup all drivers from my current system (which is necessary because the lack of Intel Graphics driver would lead to hang on shutting down or wake up) and use DISM to import those drivers to extracted wim image. Then I may turn on some Windows Features (usually, all) then re-pack the wim.

I'll then head on to Aorus Recovery drive, backup original recovery image, then replace recovery image by repacked wim file. (Actyally there're bunch of .swm file and I know how to make it.)

Due to my habit, there's only one visible partition (C:). Other invisible partitions are like System Recovery, EFI. 

This PC is for some testing purpose on my work and was installed all windows features (through Turn Windows features on or off) and then unchecked follow components:

- Guarded Host

- Hyper-V

- Windows Hypervisor Platform

And in fact some sort of hypervisor is still running. This is also the PC for my personal use.

A2) Currently in 17672, Indexing Services and Defender usually drains CPU a lot, which sometimes impacts the system performance. The Shell sometimes runs slow.

I have almost all my personal data on OneDrive and for the data-backup purpose, I stored the whole Skyrim Special Edition folder on OneDrive (and it's a genuine copy, bought on steam) to keep my mods and edits of this game not losing by reinstalling the whole system. Too many small files cause OneDrive sometimes runs slow and drain too much system performance on indexing updating info.

A3) I usually manually install software that can be self-updated, such as Office 365, game platforms like Steam, Origin, uPlay and Battle.net; software from platforms such as Adobe Creative Cloud, Autodesk software; have self-updater such as Visual Studio; can check new update by itself such as IntelliJ IDEA.

For those who have no self-updater, I usually use Chocolatey to install almost all other components. I backed up my Chocolatey package list on OneDrive so I can recover them rapidly after the clean install. The Chocolatey package list can be provided if necessary.

I leave almost all my personal documents, music, photos on OneDrive, besides on OneDrive, it also placed some software installer (that the software itself would hardly update), some tools for work and gaming use, and I set the environment variable %HOME% as my OneDrive folder to keep many software preferences stored on OneDrive, such as Git, Vim, Ruby Gem and more.

My work folder is not in OneDrive (surely for some purposes and agreements) but most of my working sets is on some git repository.

That's all I've noticed now.

Due to my personal needs, I may stick on 17672 and try to upgrade to next 2-3 releases and see if it would succeed, or continue finding problem. If always fails, I'll surely do a clean install. Thanks.

Nero.

Hi Nero,

Please don't mention it. Oh, you already did... |--)

My guess would be that chances of the issue resolving itself are slim, but there is a another good reason to postpone that Clean Install:

Here's a tip for Clean Installers (Fast Ring): Try and wait with a Clean Install until the gap between the available ISO and 'your' latest available preview is small... -ish.

Fare thee well… for now,

Stephen

PS Please feel free to post here should the happy time come and you have issues, questions, …..

[Edit] At the time of this writing one would have to start with build 17127... bbrrrr...

Hi Stephen, 

Yes surely I know how to make a clean install. And I've edited my last reply to give additional info about my machine. You could check it now, and if it's helpful just mentioned that, or just leave it alone.

Thanks.

Nero

Nero,

One thing does draw my attention: that NVIDIA GeForce GTX 1060 video card you have. I remember reading about issues with that card. Not having such a card myself I never really read them, but a forum search might well be worthwhile (and shouldn't take to long |--)

And a minor thing, OneDrive is fine, but has it's uses... I need not say more.

PS Any Overclocking is indeed best undone during installing or upgrading but I'm sure you tried that.

2018-06-01 21:36:24, Error                 SP     Error converting install time 5/4/2018 to structure[gle=0x00000057]
2018-06-01 21:36:24, Error                 SP     Error converting install time 5/4/2018 to structure[gle=0x00000057]
2018-06-01 21:36:24, Error                 SP     Error converting install time 4/5/2018 to structure[gle=0x00000057]

You could probably avoid those by changing your time format to ISO date  yyyy-MM-dd  --  or always do your updates after the 12th day of each month.    <eg>

Who knows?  Maybe that change would change some of the other error symptoms too?

FWIW I don't think that  setuperr.log  will be the right log but I don't know how to find a more significant one.  I would try just finding out where the latest changes had been made and using them as potentially useful clues.

C.f.

https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update-insiderplat_pc/cannot-update-to-latest-insider-preview/7f47e6ca-bdd1-4381-bc9d-86dbfc45c4cc?page=1&msgid=0194d9ca-0cc5-47a9-b252-798b63f1bcc1

<quote>

Edit:   Outside this thread I had to revise the filter to try to deal with unsortable date and time formats.

cd \

$This_Hour = Get-Date -Hour ((Get-Date).Hour -1)  -Format "yyyy-MM-dd HH:MM:ss"

LS -Re -Fi * -Fo -EA:SilentlyContinue | where LastWriteTime -GE ($This_Hour) | sort LastWriteTime | ft LastWriteTime, Length, FullName  -AutoSize -Wrap

</quote>

Windows 10.  Still an Adventure ("Twisty passages, all different.")

HTH

Robert Aldwinckle

---