I am unable to pause between updates because I am currently using an ISO to update Windows. Is it possible to send the whole log file instead since I cannot take screenshots?
Unable to update windows.
I cannot update windows because of it fails during installing drivers. This is the code it gives me. I have searched for the driver that is giving the issue but I have not been able to get a result. Can someone please be of assistance? I have run the update troubleshooter, used Dism commands, the Sfc tools and none of these worked.
Windows for home | Windows 11 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
16 answers
Sort by: Most helpful
-
Anonymous
2023-07-05T16:53:43+00:00 -
Anonymous
2023-07-05T16:45:21+00:00 Unfortunately, I didn't have much clarification when analyzing these log entries because some information that would be useful in this case is not recorded in this log. I only found a generic Windows Update error that would lead you to generic procedures that might not help.
A screenshot would be more helpful in this case specifically.
Try pausing the updates, restarting your PC, and unpause. Sometimes this procedure causes driver updates to install correctly.
-
Anonymous
2023-07-05T17:07:06+00:00 Isn't Windows Update giving you the errors?
Please explain to me what exactly you are trying to do.
-
Anonymous
2023-07-05T14:17:01+00:00 Hello David, thank you for your response. I am unable to send a screenshot so I would send the errors I can find in a text format.
2023-07-05 15:04:37, Info DISM API: PID=1608 TID=1612 Input parameters: Session: 2, DriverPath: C:\Windows\System32\DriverStore\FileRepository\nvhmig.inf_amd64_fbd76834fba77a54\nvhmig.inf, Flags: 11, ProcessorArchitecture: 9, PropertyKeysCount: 0 - DismAddDriverInternal
2023-07-05 15:04:37, Info DISM API: PID=1608 TID=1612 Initialized default cancel event - DismAddDriverInternal
2023-07-05 15:04:37, Info DISM API: PID=1608 TID=1612 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2023-07-05 15:04:37, Info DISM API: PID=1608 TID=1692 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2023-07-05 15:04:37, Info DISM API: PID=1608 TID=1692 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2023-07-05 15:04:37, Warning DISM DISM Driver Manager: PID=1708 TID=1736 Failed to find the INF package in the driver store (hr = 0x80070490); falling back to INF file name - CDriverPackage::InitPublishedInfName
2023-07-05 15:04:38, Info DISM DISM Driver Manager: PID=1708 TID=1736 Signature status of driver C:\Windows\System32\DriverStore\FileRepository\nvhmig.inf_amd64_fbd76834fba77a54\nvhmig.inf is: SIGNED - CDriverPackage::InitSignatureStatus
2023-07-05 15:04:39, Info DISM API: PID=1608 TID=1692 Found flag telling us to force unsigned driver. - CAddDriverCommandObject::CheckClientAddDriverScenarios
2023-07-05 15:04:39, Info DISM API: PID=1608 TID=1692 Found Flag telling us not to reflect the driver payload. Install flags: 0x00000001 - CAddDriverCommandObject::AddDriverPackage
2023-07-05 15:04:39, Info DISM API: PID=1608 TID=1692 Found Flag telling us hardlink the driver payload. Install flags: 0x00000003 - CAddDriverCommandObject::AddDriverPackage
2023-07-05 15:04:48, Error DISM DISM Driver Manager: PID=1708 TID=1736 Failed to import driver package 'C:\Windows\System32\DriverStore\FileRepository\nvhmig.inf_amd64_fbd76834fba77a54\nvhmig.inf'. - CDmiDriverStore::Import(hr:0x80070002)
2023-07-05 15:04:48, Error DISM DISM Driver Manager: PID=1708 TID=1736 Failed to install the driver package 'C:\Windows\System32\DriverStore\FileRepository\nvhmig.inf_amd64_fbd76834fba77a54\nvhmig.inf'. - CDriverPackage::InternalInstall(hr:0x80070002)
2023-07-05 15:04:48, Error DISM DISM Driver Manager: PID=1708 TID=1736 onecore\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:384 - CDriverPackage::InstallEx2(hr:0x80070002)
2023-07-05 15:04:48, Error DISM API: PID=1608 TID=1692 Driver package C:\Windows\System32\DriverStore\FileRepository\nvhmig.inf_amd64_fbd76834fba77a54\nvhmig.inf failed to install. (hr:0x80070002) - CAddDriverCommandObject::AddDriverPackage(hr:0x80070002)
2023-07-05 15:04:48, Error DISM API: PID=1608 TID=1692 onecore\base\ntsetup\opktools\dism\api\lib\dmicommandobjects.cpp:172 - CAddDriverCommandObject::InternalExecute(hr:0x80070002)
2023-07-05 15:04:48, Error DISM API: PID=1608 TID=1692 InternalExecute failed - CBaseCommandObject::Execute(hr:0x80070002)
2023-07-05 15:04:48, Error DISM API: PID=1608 TID=1612 CAddDriverCommandObject failed - DismAddDriverInternal(hr:0x80070002)
2023-07-05 15:04:48, Error SP DRVMIG: Failed to inject driver package in the new OS: C:\Windows\System32\DriverStore\FileRepository\nvhmig.inf_amd64_fbd76834fba77a54\nvhmig.inf. Error: 0x80070002[gle=0x0000007a]
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 Input parameters: Session: 2 - DismCloseSessionInternal
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 Refcount for DismSession= 2s 0 - CSessionTable::RemoveSession
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1692 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1692 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1692 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1692 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2023-07-05 15:04:48, Info DISM DISM Manager: PID=1608 TID=1692 Closing session event handle 0x35c - CDISMManager::CleanupImageSessionEntry
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1692 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1688 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1688 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1688 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1688 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1688 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 Deleted g_internalDismSession - DismShutdownInternal
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 Shutdown SessionTable - DismShutdownInternal
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 DismApi.dll: - DismShutdownInternal
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2023-07-05 15:04:48, Info DISM API: PID=1608 TID=1612 DismApi.dll: - DismShutdownInternal
2023-07-05 15:04:48, Info SP SetupPlatform: Global progress: 1, Phase progress: 5
2023-07-05 15:04:48, Info SP <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2023-07-05 15:04:48, Error SP Operation failed: Apply Drivers. Error: 0x80070002[gle=0x000000b7]
2023-07-05 15:04:48, Info SP Operation can retry, we'll attempt to revert its execution.
2023-07-05 15:04:48, Info SP Attempt to revert execution for operation 42
2023-07-05 15:04:48, Info SP The current operation's changes could not be undone, we'll search for operations whose output might have been tainted
2023-07-05 15:04:48, Info SP Will have to revert execution for 47, as its output might have been tainted by the current operation
2023-07-05 15:04:48, Info SP Attempt to revert execution for operation 47
2023-07-05 15:04:48, Info SP Will revert execution for 121, as it needed to be executed after the current operation
2023-07-05 15:04:48, Info SP Will revert execution for 48, as it needed to be executed after the current operation
2023-07-05 15:04:48, Info SP The current operation's changes could not be undone, we'll search for operations whose output might have been tainted
2023-07-05 15:04:48, Info SP Will have to revert execution for 44, as its output might have been tainted by the current operation
2023-07-05 15:04:48, Info SP Attempt to revert execution for operation 121
2023-07-05 15:04:48, Info SP Attempt to revert execution for operation 48
2023-07-05 15:04:48, Error SP Cannot revert execution of operation 48 (Apply EAs for C:$WINDOWS.~BT\NewOS). Execution queue is now compromised.
2023-07-05 15:04:48, Info SP Cannot revert execution in the queue, this is a fatal error.
2023-07-05 15:04:48, Error SP Operation execution failed: 7. hr = 0x80070002
2023-07-05 15:04:48, Error SP ExecuteOperations: Main operation execution failed. Error: 0x80070002
2023-07-05 15:04:48, Error SP ExecuteOperations: Failed execution phase Safe OS. Error: 0x80070002
2023-07-05 15:04:48, Error SP CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x80070002
2023-07-05 15:04:48, Info Persisting diagnostics data to C:$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat
2023-07-05 15:04:48, Info Diagnostics data saved successfully
2023-07-05 15:04:48, Info SP Execution phase [Safe OS] exiting with HRESULT [0x80070002]
-
Anonymous
2023-07-05T14:03:15+00:00 Hi. I'm David, and I'm happy to help you.
Please send a screenshot of the updates failing with the error code being displayed.
Use the shortcut "Windows + Shift + S" to use the screenshot tool.
Be sure to censor any personal information. The Microsoft Community is public.