Main Forum > General Computer Support
.dll problems (solved)
Pipsqueak:
Steam throws up a 'steamui.dll not found' error when it tries tostart. Attempted all the usual fixes but none worked.
Went to try SFC but thatrefused to start, at which point I attempted a system restore to the last time it worked (11pm, 24th May) which promptly failed.
Having exausted all the google suggestions to try and fix SFC and System Restore (which, unhelpfully, involve each other working...), I tried the Windows Repair tool, which has given me this log on the pre-scan:
--- Quote ---These Files Are Missing: (Total: 8)
C:\Windows\servicing\Packages\Package_122_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.cat
C:\Windows\servicing\Packages\Package_129_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Package_1_for_KB2515325~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2515325_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
C:\Windows\servicing\Packages\Package_for_KB2515325_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
C:\Windows\servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Base-WinIP-Package~31bf3856ad364e35~amd64~bg-BG~7.1.7601.16492.mum
C:\Windows\servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~amd64~bg-BG~7.1.7601.16492.cat
C:\Windows\servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-WinIP-Package~31bf3856ad364e35~amd64~sk-SK~7.1.7601.16492.cat
These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 2)
C:\Windows\servicing\Packages\Package_122_for_KB2984972~31bf3856ad364e35~amd64~~6.1.1.4.mum
C:\Windows\servicing\Packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~amd64~bg-BG~7.1.7601.16492.mum
--- End quote ---
As they all have 'amd' mentioned this may have something to do with the AMD control suddenly deciding to stop working then switch to german on me when I fixed it a few months back. No idea if thisis actually related though.
OS: Windows 7 professional 6.1.7601 SP1 x64
Boggin:
sfc /scannow relies upon the Windows Module Installer service starting which is found when you press the Windows key, type services.msc - press enter then scroll down to the service.
This is default set to Manual and sfc should fire it up, but you can manually start it by clicking on it and then on Start in the upper left pane.
Have you tried a chkdsk without any parameters to see what that reports ?
There are a couple of ways you could try the restore points and they are when you boot up into the Advanced Boot options by tapping F8 (usually) as you switch on and select Safe Mode to try them, as it could be your AV program that is blocking it.
The other is to select Repair your Computer in the Advanced Boot options, navigate to the Recovery Environment then select the Restore option.
Using the Startup Repair option also gives you a Restore option as it works its way through before going onto the full Startup repair.
If the restore is successful and then sfc, run Windows Repair again to see if it produces the same Package errors.
Pipsqueak:
--- Quote from: Boggin on May 28, 2015, 03:16:16 am ---sfc /scannow relies upon the Windows Module Installer service starting which is found when you press the Windows key, type services.msc - press enter then scroll down to the service.
This is default set to Manual and sfc should fire it up, but you can manually start it by clicking on it and then on Start in the upper left pane.
--- End quote ---
Already tried this. Didn't work.
--- Quote ---Have you tried a chkdsk without any parameters to see what that reports ?
--- End quote ---
chkdsk runs fine, but doesn't fix the problem.
--- Quote ---There are a couple of ways you could try the restore points and they are when you boot up into the Advanced Boot options by tapping F8 (usually) as you switch on and select Safe Mode to try them, as it could be your AV program that is blocking it.
The other is to select Repair your Computer in the Advanced Boot options, navigate to the Recovery Environment then select the Restore option.
Using the Startup Repair option also gives you a Restore option as it works its way through before going onto the full Startup repair.
If the restore is successful and then sfc, run Windows Repair again to see if it produces the same Package errors.
--- End quote ---
None ofthe restores I ran, in safe mode or no, were able to complete.
Boggin:
What did chkdsk report ?
EDIT - Can you also try Last Known Good Configuration to see if that will restore.
chkdsk without any parameters is a read only mode and will not repair but will report or advise what next to run if any errors are found.
Shane:
Those errors in the pre-scan wont keep the repairs from working, just make sure to run all the repairs and run them in safe mode, of course have it do a registry backup first just in case :wink:
Shane
Navigation
[0] Message Index
[#] Next page
Go to full version