- May 7, 2013
- 10,396
Could you please run SFC again then provide the CBS log if it fails.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Hello thank you for your care..Could you please run SFC again then provide the CBS log if it fails.
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-02-21 12:40:37.125
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.
AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 1
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2022-02-21 13:18:09.792
----------------------EOF-----------------------
sfc /scannow
Please run the SFCFix script from previous post (post #15), if you get the successfully replaced message then please open command prompt and then the following command:
Rich (BB code):sfc /scannow
If it fails i.e. gives an error message, then please attach the latest CBS log.
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-02-21 18:41:02.185
Microsoft Windows 8.1 Update 3 - amd64
Using .zip script file at C:\Users\Adm\Desktop\SFCFix.zip [1]
PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys
WARNING: File C:\Windows\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys was not backed up as that would replace the current backup.
Successfully copied file C:\Users\Adm\AppData\Local\niemiro\Archive\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys to C:\Windows\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys.
Successfully restored ownership for C:\Windows\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys
Successfully restored permissions on C:\Windows\WinSxS\amd64_mshdc.inf_31bf3856ad364e35_6.3.9600.16384_none_cdf68824f580d510\pciidex.sys
PowerCopy:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2022-02-21 18:41:02.811
Script hash: /T44zTpWwTslFRJXmAw7CVquhRLKcQ8E2w4gIzIU3yQ=
----------------------EOF-----------------------
It's because you haven't put the correct opening tag, it should be [QUOTE] but you've put [/QUOTE] instead. I've fixed it now.I do not know why the bb code is not working it was supposed to be in quotes..
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
The CBS log looks fine, did SFC complete without any errors or with the message that it was able to successfully repair them? If it didn't, then please run DISM using the following command from an elevated command prompt:
Rich (BB code):DISM /Online /Cleanup-Image /RestoreHealth
" A recent hardware or software change might be the cause"
...
Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎22/‎02/‎2022 18:55:16 (GMT)
Number of repair attempts: 1
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = F:\Windows
AutoChk Run = 0
Number of root causes = 1
Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms
Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 78 ms
Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms
Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms
Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Root cause found:
---------------------------
Boot status indicates that the OS booted successfully.
---------------------------
---------------------------
yes.. it only happens when i try to boot into Safe Mode@dokha can you not boot into Windows?
diskpart
list disk
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/pciidex.sys
%systemroot%/Inf
Do you remember if this is a GPT or MBR disk? Please boot into Windows normally and then the following commands sequentially in an elevated Command Prompt:
Rich (BB code):diskpart list disk
Please provide a screenshot or copy/paste the output in your next post. Just looking back over this thread, I noticed that you mentioned that the Driver Store directory was missing for the said driver.
Could you please open the registry editor and then navigate to the following key path:
Rich (BB code):HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/pciidex.sys
Please copy/paste the Source value in your next post as well. You also wish to attach the setupapi.dev.log too, which can be found in the following directory:
Rich (BB code):%systemroot%/Inf
Here is everything.. I thought I should mention that there are two other "setupapi.dev" files but the have a string of numbers after the name..Do you remember if this is a GPT or MBR disk? Please boot into Windows normally and then the following commands sequentially in an elevated Command Prompt:
Rich (BB code):diskpart list disk
Please provide a screenshot or copy/paste the output in your next post. Just looking back over this thread, I noticed that you mentioned that the Driver Store directory was missing for the said driver.
Could you please open the registry editor and then navigate to the following key path:
Rich (BB code):HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/System32/drivers/pciidex.sys
Please copy/paste the Source value in your next post as well. You also wish to attach the setupapi.dev.log too, which can be found in the following directory:
Rich (BB code):%systemroot%/Inf
The System Reserved Partition is usually hidden to prevent users from making any modifications to it. Most of the files will be hidden and inaccessible in File Explorer as well. Let's focus on trying to resolve what appears to be the imminent problem and that is the pciidex.sys driver:I then found that the Recovery folder inside the partition is empty, and I also cannot access it telling me: "It is not accessible , access denied"
Is this normal?
Where did you replace it from though?I have replaced it in the first directory no problem,
Has Sysnative Forums helped you? Please consider donating to help us support the site!