[WinServer2012Standard x64] Unsuccessful reparation of file CNBJ2530.DPB

V

voice

Member
Joined
Mar 3, 2017
Posts
12
Unsuccessful reparation of file CNBJ2530.DPB

Hi

I have read myself through the different topics and threads, but there wasn't a solution for my specific case. I have run the SFCFix several times and tried different ways, but no one helped. Probably you can help me to solved this issue. Here is my log. It's says, the problem is fixed, but if I run "sfc /scannow", it tels me about the "Windows Resource Protection found corrupt files but was unable to fix some of them....". IAttached you will find the cbs.log as well.

Thanks a lot for any suggestions.

Patrick


=============================
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-03-06 11:12:44.264
Microsoft Windows Server 2012 - amd64
Not using a script file.




AutoAnalysis::
FIXED: Performed DISM repair on file Amd64\CNBJ2530.DPB of version 6.2.9200.16384.




SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-03-06 13:27:54.210
----------------------EOF-----------------------



Update: I tried to attach a zip file, but it seems it doesn't work with the upload through the upload manager. Also with the automatic uploading through SFCFix, it doesn't show this log file here in this thread. How can I provide the cbs log file? By the way, the server which has this issue, is running Windows Server 2012 Standard.
 
Hi and welcome to Sysnative. Please do the following.

SFC Scan
1. Right-click on the Start
w8start.png
button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
 sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

4. Once this has completed please go to your Desktop and you will find CBS.txt => Right-click on this file and choose Send To...Compressed (zipped folder). Please upload this zipped file CBS.zip to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
This should get you fixed up.

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
 

Attachments

Hi

I followed your suggestion and the output seems to be fine, the problem should be fixed. Great, thank you very much.

-----------------------------------------------------------------
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-03-10 14:23:49.932
Microsoft Windows Server 2012 - amd64
Using .zip script file at C:\Users\Administrator\Desktop\SFCFix.zip [0]


PowerCopy::
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16384_none_fd9c01be8b864efc\Amd64\CNBJ2530.DPB


Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16384_none_fd9c01be8b864efc\Amd64\CNBJ2530.DPB to C:\Windows\Winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16384_none_fd9c01be8b864efc\Amd64\CNBJ2530.DPB.


Successfully restored ownership for C:\Windows\Winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16384_none_fd9c01be8b864efc\Amd64\CNBJ2530.DPB
Successfully restored permissions on C:\Windows\Winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16384_none_fd9c01be8b864efc\Amd64\CNBJ2530.DPB
PowerCopy:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2017-03-10 14:23:50.556
Script hash: Ksscvdy8oBCHMPv1OwkCN4gbo2lWkuv4NH8wfcO7ofE=
-----------------------------------------------------------------
 
Good Morning,

After I had the fix applied, I ran "sfc /scannow", which was ok, then I ran "Dism /Online /Cleanup-Image /RestoreHealth". After a while it had completed, and still complained about an error. So, somehow the fix didn't helped in overall.

------------------------------------------
C:\Users\Administrator>Dism /Online /Cleanup-Image /RestoreHealth


Deployment Image Servicing and Management tool
Version: 6.2.9200.16384


Image Version: 6.2.9200.16384


[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the comp
onent store cannot be repaired.


Error: 0x800f081f


DISM failed. No operation was performed.
For more information, review the log file.


The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


C:\Users\Administrator>
------------------------------------------

Please find the part of dism.log zipped and attached. Is there anything else I can try?


Best regards

Patrick
 

Attachments

Hi Brian

Please find attached the current cbs.log.

I appreciate your time, thank you.

Patrick
 

Attachments

Can you zip up and attach the following file please?
C:\windows\servicing\sessions\30579678_3328763254.xml (note: you may not see the .xml extension)
 
OK, thanks. Please do the following.

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run Dism /Online /Cleanup-Image /RestoreHealth just like you have in the past.
3. Stop Process Monitor as soon as DISM fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 and attach the LogFile.PML file as well as your CBS.log.
 
That's really odd. Please do the following.

ChkDsk
1. Point your mouse to the lower left of your computer screen and click on the Start screen. Type cmd on the Start Screen.
2. Once the Command Prompt program is found, right-click on it with your mouse and select Run as administrator.
3. Answer Yes when asked to allow.
4. You should now have a black window open that you can type in to.
5. Please type chkdsk and then press enter.
6. An online checkdisk will begin. Let it complete.
7. Download ListChkdskResult.exe by SleepyDude and save it on your desktop.
8. Right-click this file and select Run as administrator (Allow if prompted)and a text file will open (and also be saved on the desktop as ListChkdskResult.txt).
Please copy the contents of this file and paste into your next post.
 
Thanks, her the results:

ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013


------< Log generate on 15.03.2017 14:02:32 >------
Category: 0
Computer Name: IVR2
Event Code: 26212
Record Number: 19444
Source Name: Chkdsk
Time Written: 03-15-2017 @ 13:02:15
Event Type: Information
User:
Message: Chkdsk was executed in read-only mode on a volume snapshot.


Checking file system on C:
The type of the file system is NTFS.


WARNING! F parameter not specified.
Running CHKDSK in read-only mode.


CHKDSK is verifying files (stage 1 of 3)...
177920 file records processed.


File verification completed.
4361 large file records processed.


0 bad file records processed.




CHKDSK is verifying indexes (stage 2 of 3)...
242234 index entries processed.


Index verification completed.
0 unindexed files scanned.


0 unindexed files recovered.




CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
32158 data files processed.


CHKDSK is verifying Usn Journal...
34312520 USN bytes processed.


Usn Journal verification completed.


Windows has scanned the file system and found no problems.
No further action is required.


104497151 KB total disk space.
45911432 KB in 114717 files.
91880 KB in 32159 indexes.
0 KB in bad sectors.
282739 KB in use by the system.
65536 KB occupied by the log file.
58211100 KB available on disk.


4096 bytes in each allocation unit.
26124287 total allocation units on disk.
14552775 allocation units available on disk.


-----------------------------------------------------------------------
 
I installed the kb, but still it fails. Attached you will find the dism log.

-------------------------------------------------------------------
Deployment Image Servicing and Management tool
Version: 6.2.9200.16384


Image Version: 6.2.9200.16384


[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the comp
onent store cannot be repaired.


Error: 0x800f081f


DISM failed. No operation was performed.
For more information, review the log file.


The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 

Attachments

Unfortunately I have not idea why it is reporting a failure. It doesn't appear to stop you from getting Windows Updates correct?
 
That's not correct. I'm not able to get any windows updates. As soon as I start the windows update to received the newest updates, the process starts and never stops (I had it once run for 4 days). Also during this time, the CPU goes to 100% and the machine is very slow. I shows that the computer is searching for new updates, but nothing else happens. I thought, it has something to do with this error. I will give a try to install all the updates since last October (last time the updates were regularly installed, without any issues) manually. It's a time consuming thing, but probably it solves the issue. I will let you know, otherwise I also don't have any further ideas.
 
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