Problem with wifes notebook ;-)
- Thread starter frankhaas
- Start date
Please try the following command, I wonder if error 126 appears too? If so, please attach the latest DISM log to see if it failed to load drvstore.dll this time.
Code:
DISM /online /get-drivers
Last edited:
Here's the new fix: SFCFix.zip - Shared with pCloud
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards, reboot the system and try DISM again and post the result.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
- Save any work you have open, and close all programs.
- Download the attachment SFCFix.zip and save it to your desktop.
- Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
- SFCFix will launch, let it complete.
- Once done, a file will appear on your desktop, called SFCFix.txt.
- Post the logfile (SFCFix.txt) as attachment in your next reply.
Afterwards, reboot the system and try DISM again and post the result.
Code:
DISM /online /cleanup-image /RestoreHealth
Please run the following command in an elevated command prompt and post the result.
Code:
regsvr32 C:\windows\system32\dism\dismprov.dll
Please try this command as well, just to see if you get the same error?
Code:
%systemroot%\SysWoW64\regsvr32 C:\Windows\SysWOW64\Dism\DismProv.dll
Please try to run DISM again and see what happens now.
Code:
DISM /online /cleanup-image /RestoreHealth
There seems to be something badly wrong with the WOW64 file system redirection. Please try the following commands in an elevated command prompt:
Code:
CD\
CD C:\Windows\SysWOW64
DISM /online /cleanup-image /RestoreHealth
Mmm. this is really interesting. Try this command again in a regular prompt after: C:\Windows\system32>
The command prompt was not started with administrator privileges, sorry with "regular" I meant not using the SysWOW directory....
Please run DISM again with Process Monitor running, there has to be a clue somewhere why it fails?!
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
Hi,
Please run the following commands to check the bam-driver.
Please run the following commands to check the bam-driver.
Code:
sc query bam
sc qc bamHas Sysnative Forums helped you? Please consider donating to help us support the site!