[SOLVED] DISM hangs at 40% when trying to repair corrupt files

N

Nine

New member
Joined
Sep 26, 2016
Posts
3
Hello,

I just joined the community after trying to find a solution to my problem.

Hopefully you will be able to help me.

I bought a new laptop last winter straight from Microsoft and it came with Windows 10 pre-installed.

I have been having minor issues here and there, trying to fix them when I ran across them (the pen driver had some issues, for instance, and the Device Manager showed a few items with exclamation marks - I don't remember exactly, but I know some where firmware-related). In any case, I fixed all of those and everything seemed fine.

I have been waiting for the Anniversary Update, and, seeing that I was not getting it, I used Microsoft's Upgrade Assistant to "force" the update. All seemed well, until I got the "Restoring your previous version of Windows" message after reboot.

After I did some digging, I ran the sfc /scannow, and I got the "Windows Resource Protection found corrupt files but was unable to fix some of them." message.

Then, I tried running the RestoreHealth command of DISM, but it always hangs at 40%.

Can you please help me with this?

Thank you so much, and I apologize for any language mistakes - I have never used these commands before and English is not my native language.

Best,
Nine
 
Hello and Welcome, Nine!

Let's take a look at the setup log to find out why the upgrade didn't complete.

Please browse to C:\$Windows.~bt\Sources\Panther\
Find the file SetupAct.log
Copy this file to your Desktop, then right click and choose Send To... -> Compressed (zipped) Folder
Attach the SetupAct.zip file from your Desktop with your reply.
 
Hi zcomputerwiz,

First of all, thank you for the reply!

Second, here is the file you asked for. Hopefully it helps!

Let me know what you think.

Thanks again,
Nine
 

Attachments

Code: 
2016-09-26 02:40:19, Info                  SP     Injecting driver package into the new OS (payload hardlinked): C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1108 Enter DismAddDriverInternal - DismAddDriverInternal
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1108 Input parameters: Session: 2, DriverPath: C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf, ForceUnsigned: 1 - DismAddDriverInternal
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1108 Initialized default cancel event - DismAddDriverInternal
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1108 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1660 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1660 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2016-09-26 02:40:19, Info                  DISM   DISM Provider Store: PID=1664 TID=1684 Getting Provider OSServices - CDISMProviderStore::GetProvider
2016-09-26 02:40:19, Info                  DISM   DISM Provider Store: PID=1664 TID=1684 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-09-26 02:40:19, Info                  DISM   DISM Provider Store: PID=1664 TID=1684 Getting Provider DriverManager - CDISMProviderStore::GetProvider
2016-09-26 02:40:19, Info                  DISM   DISM Provider Store: PID=1664 TID=1684 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-09-26 02:40:19, Error                 DISM   DISM Driver Manager: PID=1664 TID=1684 Failed to find the file in driver store. - CDriverPackage::GetPublishedInfName(hr:0x80070490)
2016-09-26 02:40:19, Info                  DISM   DISM Driver Manager: PID=1664 TID=1684 Driver C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf is boot-critical. - CDriverPackage::FillInPackageDetails
2016-09-26 02:40:19, Info                  DISM   DISM Driver Manager: PID=1664 TID=1684 Signature status of driver C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf is: SIGNED - CDriverPackage::InitSignatureStatus
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1660 Found environment variable telling us not to reflect the driver. Install flags: 0x00000001 - CAddDriverCommandObject::AddDriverPackage
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1660 Found environment variable telling us to hardlink the driver payload. Install flags: 0x00000003 - CAddDriverCommandObject::AddDriverPackage
2016-09-26 02:40:19, Info                  DISM   DISM Driver Manager: PID=1664 TID=1684 Found flag telling us to hardlink this driver. - CDmiDriverStore::Import
2016-09-26 02:40:19, Error                 DISM   DISM Driver Manager: PID=1664 TID=1684 Failed to install the driver package 'C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf'. - CDmiDriverStore::Import(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   DISM Driver Manager: PID=1664 TID=1684 Failed to install the driver package 'C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf'. - CDriverPackage::InternalInstall(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   DISM Driver Manager: PID=1664 TID=1684 onecore\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:408 - CDriverPackage::InstallEx(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   API: PID=1104 TID=1660 Driver package C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf failed to install. (hr:0x80070002) - CAddDriverCommandObject::AddDriverPackage(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   API: PID=1104 TID=1660 onecore\base\ntsetup\opktools\dism\api\lib\dmicommandobjects.cpp:160 - CAddDriverCommandObject::InternalExecute(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   API: PID=1104 TID=1660 InternalExecute failed - CBaseCommandObject::Execute(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   API: PID=1104 TID=1108 CAddDriverCommandObject failed - DismAddDriverInternal(hr:0x80070002)
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1108 Leave DismAddDriverInternal - DismAddDriverInternal

Looks like ekbdflt.inf cannot be installed. From what I found, it may be from an ESET antivirus product.

Please try uninstalling your antivirus, then run the upgrade again.
If it fails, zip and attach SetupAct.log again.
 
zcomputerwiz said:
Code: 
2016-09-26 02:40:19, Info                  SP     Injecting driver package into the new OS (payload hardlinked): C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1108 Enter DismAddDriverInternal - DismAddDriverInternal
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1108 Input parameters: Session: 2, DriverPath: C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf, ForceUnsigned: 1 - DismAddDriverInternal
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1108 Initialized default cancel event - DismAddDriverInternal
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1108 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1660 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1660 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2016-09-26 02:40:19, Info                  DISM   DISM Provider Store: PID=1664 TID=1684 Getting Provider OSServices - CDISMProviderStore::GetProvider
2016-09-26 02:40:19, Info                  DISM   DISM Provider Store: PID=1664 TID=1684 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-09-26 02:40:19, Info                  DISM   DISM Provider Store: PID=1664 TID=1684 Getting Provider DriverManager - CDISMProviderStore::GetProvider
2016-09-26 02:40:19, Info                  DISM   DISM Provider Store: PID=1664 TID=1684 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-09-26 02:40:19, Error                 DISM   DISM Driver Manager: PID=1664 TID=1684 Failed to find the file in driver store. - CDriverPackage::GetPublishedInfName(hr:0x80070490)
2016-09-26 02:40:19, Info                  DISM   DISM Driver Manager: PID=1664 TID=1684 Driver C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf is boot-critical. - CDriverPackage::FillInPackageDetails
2016-09-26 02:40:19, Info                  DISM   DISM Driver Manager: PID=1664 TID=1684 Signature status of driver C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf is: SIGNED - CDriverPackage::InitSignatureStatus
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1660 Found environment variable telling us not to reflect the driver. Install flags: 0x00000001 - CAddDriverCommandObject::AddDriverPackage
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1660 Found environment variable telling us to hardlink the driver payload. Install flags: 0x00000003 - CAddDriverCommandObject::AddDriverPackage
2016-09-26 02:40:19, Info                  DISM   DISM Driver Manager: PID=1664 TID=1684 Found flag telling us to hardlink this driver. - CDmiDriverStore::Import
2016-09-26 02:40:19, Error                 DISM   DISM Driver Manager: PID=1664 TID=1684 Failed to install the driver package 'C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf'. - CDmiDriverStore::Import(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   DISM Driver Manager: PID=1664 TID=1684 Failed to install the driver package 'C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf'. - CDriverPackage::InternalInstall(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   DISM Driver Manager: PID=1664 TID=1684 onecore\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:408 - CDriverPackage::InstallEx(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   API: PID=1104 TID=1660 Driver package C:\Windows\System32\DriverStore\FileRepository\ekbdflt.inf_amd64_76e99bfc65290b87\ekbdflt.inf failed to install. (hr:0x80070002) - CAddDriverCommandObject::AddDriverPackage(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   API: PID=1104 TID=1660 onecore\base\ntsetup\opktools\dism\api\lib\dmicommandobjects.cpp:160 - CAddDriverCommandObject::InternalExecute(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   API: PID=1104 TID=1660 InternalExecute failed - CBaseCommandObject::Execute(hr:0x80070002)
2016-09-26 02:40:19, Error                 DISM   API: PID=1104 TID=1108 CAddDriverCommandObject failed - DismAddDriverInternal(hr:0x80070002)
2016-09-26 02:40:19, Info                  DISM   API: PID=1104 TID=1108 Leave DismAddDriverInternal - DismAddDriverInternal

Looks like ekbdflt.inf cannot be installed. From what I found, it may be from an ESET antivirus product.

Please try uninstalling your antivirus, then run the upgrade again.
If it fails, zip and attach SetupAct.log again.
Click to expand...

Thank you so much, that did it! The update was successful! I also scanned the health with DISM and got no corruption! This is great, I'm so excited! Thanks for everything!

All best,
Nine
 
Glad to hear it! :thumbsup2:

I'll mark the thread solved. If you encounter problems, please post back and I'll continue to assist you.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top