onestory151
Member
:banghead:SFC /SCANNOW CANNOT FINISH REPAIRS, FIXED OTHERS, SFC.EXE SEEMS TO HAVE FAILED BUT REPORTS SUCCESS AS SECOND SCAN SAME RESULT STILL A CORRUPTION.
CNBJ2530.DPB and prncacla.inf Corruptions - Windows 8 SFC /scannow cannot repair 2 corruptions, fixed others, DISM failed on the 22nd and said cannot fix 64bit operating system with 32bit cmd.exe nor did the 64bit cmd.exe work, I have not tried that today because Stephen did not mention this in his heads up post on this matter. There was chatter about Windows Resource Protection precluding as well on the 22nd, I did not see that yet today as SFC /scannow did run today and would not on the 22nd but could not finish repairs, SFCfix says that it did but apparently not. Let me backtrack and delve deeper. I firmly believed at the time and still do that the corruption was the result of foul or failed windows updates because that day the 22nd Sept 2015 Windows update failed on both of my computers back to back, this turned out to be a disaster and i want to warn that I tried to do a reset of my computer suspicious that the recovery environment had been affected which research online led me to believe though I wasn't sure nonetheless the reset to factory failed and having failed installed a second operating system on the same drive which would not boot then I used USB set up thru BIOS to get back to RE when I was asked at next boot to choose an OS so since the second had failed to boot after reset I chose the first prior to reset leary because of the drive wipe of course and it tried to boot did better than the other but got stuck in an infinite loop on the WELCOME screen so that was then worst yet, not only that all USB ports were disabled and there was no longer any access to bios nor did bios have CD boot to start with, let me reiterate I wrote that here as fair warning to others experiencing this problem as it's too much of a conincidence for my taste.
I am writing then because my second machine a Toshiba Satellite L875 S7110 had the exact same corruptions as the ASUS, it would seem best to fix this problem first though I say that as a layman speaking from immediate experience. Tonight the 23rd I read Stephen's post that he is aware of the problem affecting many so I did as instructed and ran the file checker then the SFCfix.exe actually twice already and now it seeems I must a third time as the fix did not seem to take the first time but says it has both times with the corrupt seemingly fixed culprit being;
AutoAnalysis::
FIXED: Performed DISM repair on file Amd64\CNBJ2530.DPB of version 6.2.9200.16430.
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
I am running a third and will upload any files that seem pertinent in addition to SFCfix.txt
It seems a human must further analyze the matter. Earlier on of course DISM could not fix the file not even in Safe Mode on the 22nd.
This update has failed 24 times since Sept 9th, (KB3069114), I did a 3rd and final scan on Sept 24th and the result was the same file which shows up twice as corrupted as listed above
I have run SFC.exe one last time though surely the result is identical which says it's repaired but it is not ergo deeper analysis required as you stated. 3 scans, 3 sfcfic, 3 fails showing as
succeeded. 2 corruptions the same file twice found so go figure. Forgive the preponderance especially the ASUS and warning, I am uploading the last scan and last sfcfix files, if you need to
see the others say so though it's a running file it seems and everything the same.
CNBJ2530.DPB and prncacla.inf Corruptions - Windows 8 SFC /scannow cannot repair 2 corruptions, fixed others, DISM failed on the 22nd and said cannot fix 64bit operating system with 32bit cmd.exe nor did the 64bit cmd.exe work, I have not tried that today because Stephen did not mention this in his heads up post on this matter. There was chatter about Windows Resource Protection precluding as well on the 22nd, I did not see that yet today as SFC /scannow did run today and would not on the 22nd but could not finish repairs, SFCfix says that it did but apparently not. Let me backtrack and delve deeper. I firmly believed at the time and still do that the corruption was the result of foul or failed windows updates because that day the 22nd Sept 2015 Windows update failed on both of my computers back to back, this turned out to be a disaster and i want to warn that I tried to do a reset of my computer suspicious that the recovery environment had been affected which research online led me to believe though I wasn't sure nonetheless the reset to factory failed and having failed installed a second operating system on the same drive which would not boot then I used USB set up thru BIOS to get back to RE when I was asked at next boot to choose an OS so since the second had failed to boot after reset I chose the first prior to reset leary because of the drive wipe of course and it tried to boot did better than the other but got stuck in an infinite loop on the WELCOME screen so that was then worst yet, not only that all USB ports were disabled and there was no longer any access to bios nor did bios have CD boot to start with, let me reiterate I wrote that here as fair warning to others experiencing this problem as it's too much of a conincidence for my taste.
I am writing then because my second machine a Toshiba Satellite L875 S7110 had the exact same corruptions as the ASUS, it would seem best to fix this problem first though I say that as a layman speaking from immediate experience. Tonight the 23rd I read Stephen's post that he is aware of the problem affecting many so I did as instructed and ran the file checker then the SFCfix.exe actually twice already and now it seeems I must a third time as the fix did not seem to take the first time but says it has both times with the corrupt seemingly fixed culprit being;
AutoAnalysis::
FIXED: Performed DISM repair on file Amd64\CNBJ2530.DPB of version 6.2.9200.16430.
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
I am running a third and will upload any files that seem pertinent in addition to SFCfix.txt
It seems a human must further analyze the matter. Earlier on of course DISM could not fix the file not even in Safe Mode on the 22nd.
This update has failed 24 times since Sept 9th, (KB3069114), I did a 3rd and final scan on Sept 24th and the result was the same file which shows up twice as corrupted as listed above
I have run SFC.exe one last time though surely the result is identical which says it's repaired but it is not ergo deeper analysis required as you stated. 3 scans, 3 sfcfic, 3 fails showing as
succeeded. 2 corruptions the same file twice found so go figure. Forgive the preponderance especially the ASUS and warning, I am uploading the last scan and last sfcfix files, if you need to
see the others say so though it's a running file it seems and everything the same.
