CNBJ2530.DPB corruptions, DISM hangs at 40%...

N

nio102

Member
Joined
Jan 24, 2015
Posts
8
Hi,

I've got the CNBJ2530.DPB corruption problem, but when I'm trying to use SFCFix or directly running DISM, it hangs indefinitely at 40%...

I've seen another thread with the same problem/description, but the fix given through dropbox isn't available anymore, so here I am in a new thread!

Attached is the CBS.log file zipped generated by sfc /scannow.

Thanks in advance for your help !

Regards,

Nicolas.
 

Attachments

Hello Nicolas and welcome to Sysnative :)

This time out issue with DISM is something I have seen a few times over the past few weeks. To get around this we will manually replace the corrupt CNBJ2530.DPB file.

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.
  2. Download 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 - put [CODE][/CODE] tags around the log to break up the text.

SFC /SCANNOW
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Command prompt (Admin) => Press Yes on the prompt
  3. Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW
  4. Please wait for this to Finish before continuing with rest of the steps.
Convert CBS.log to CBS.txt
  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run => Inside the run box copy and paste the following command:
    Code: 
    cmd /c copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  3. Press Enter
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please upload CBS.txt to this thread
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive


Thanks
Alex
 
Hello Nicolas, and welcome to Sysnative!

In addition to the instructions Alex has given you, it would be great if you could help us a little bit by seeing if there's anything you can do to identify what's going wrong on the 40% stall. We'll analyse the data and if we can find a cause we'll feedback that information to Microsoft so that they can potentially create a fix.

So, before you follow Alex's instructions (if you haven't already), can you please try DISM one more time please.

Then, I want you to download this tool from Microsoft: https://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
and start it up. I then need you to make a few changes:

Filter > Reset Filter
Filter > Drop Filtered Events (so there's a tick in the box)
Filter > Filter, then: Process Name is dism.exe then Include > Add > OK
Edit > Clear Display
File > Uncheck Capture Events

I now want you to start dism.exe and let it run until ~37%. Then, go back to Process Monitor, File > tick Capture Events > let dism.exe run until 40% and stall for a little bit, then File > Untick Capture Events.


Finally, File > Save > "Events displayed using current filter" (tick in Also include Profiling Events too) > Dot next to Native Process Monitor Format (PML), then click the "..." button next to Path, and save Logfile.PML on your Desktop > OK > OK.

Then, if you could upload that new file from your Desktop to SkyDrive or any other file sharing website, make it publicly accessible and share the link here, that would be absolutely amazing.


Please know that these steps are completely optional. Alex's instructions are what you need to fix your computer. However, it's people like you who voluntarily help us report back to Microsoft with enough information to give them a chance of fixing the issue that allows these rare issues to be sorted out once and for all. I do completely understand though that everyone's busy at this time of year and you're probably up to your eyes in work right now. So it is completely optional.

Thank you so much.

Richard
 
@Alex:
Thanks for your help!
Here are attached both cbs.log and sfcfix.txt zipped files.

After doing an sfc /scannow with good results, I tried to run sfcfix.exe (alone without any .zip), and dism still kept frozen at 40%...

@Richard:
Sorry, I had already tried Alex's fix before reading your message... : /

But seeing that dism was still hanging at 40%, I did what you asked for and here is attached the resulting log file...

Hope this helps... : /

Thanks again for your help!

Best regards,

Nicolas.
 

Attachments

Hello again Nicolas!

Your CBS.log is now good, just as SFC says it is.


In terms of the DISM issue, I've analysed the result and got quite a bit of useful data, but I'd wonder if you've be willing to do one more ProcMon run with different settings now I've done a preliminary analysis? Again, this is completely optional and I won't ask for a third time. But it would be very helpful if you're willing.

For what it's worth, I am seeing a repeat thread creation with the same call stack each time. This is certainly indicative of some sort of loop condition (doing the same thing again and again and again). I will now dig into the actual call stacks and try to drain them of the last vestiges of useful information. In the meantime though, something I'm not seeing is any file I/Os, and I want to investigate this further.

So, if you are willing this final time, could you please re-configure ProcMon just as you did before. Then, in addition, on the toolbar at the top full of coloured icons, to the very right hand side you should see a block of five. Can you click on each of these as necessary, and make sure that all five have a square around them.

Then start DISM, wait for it to get to a couple of percentage points under 40% again, start ProcMon recording, wait for DISM to hang for a little bit, then stop ProcMon.

Hopefully with these extra data collection options enabled I'll be able to juice this issue a little more :)

Richard
 
Hello Richard,

Here you go: attached is the new log file with the profiling events enabled...

Hope this helps!

Nicolas.
 

Attachments

nio102 said:
Hello Richard,

Here you go: attached is the new log file with the profiling events enabled...

Hope this helps!

Nicolas.
Click to expand...

Thank you so much again for your help :)

I'll analyse the data, collate from other machines if necessary, and will work to find a root cause if I possibly can. It's a difficult process but we've managed to track down and fix similar issues in the past so I am optimistic that with a bit of grit we'll get there in the end. Thank you so much again for your help.


Is there anything else I can do to help you? Other than DISM is anything else not working, anything else need fixing?

Richard
 
Hi,

Despite the dism problem, my windows update seems to install updates again, and that's great news, because I was struggling with it for a long time !

Bringing you those logs was the least I could do to thank you for your help... ;p

Thank you again, and keep up the good work!

Regards,

Nicolas.
 
Hi,

In fact, I managed to install two updates, and now I'm again stuck... The updates won't install, they will stall at 4% or 5%...
No more network activity, but 100% disk activity on my main drive.

SFC reports no problem at all. I have 7GB of free space on this main C: drive.
I've tried every trick I could find, empty cache, scan registry, reset windows update... no luck.
My drive is working fine, and I have no weird problem apart from the windows udpate process.

What do you think I could do to overcome those problems ?
Can I request some support from Microsoft or will they just send me to the very same solutions I've already tried ?

Reinstalling windows is not an option for me now... So much stuff to reinstall and configure...

Thanks for your advice!
 
Hello,

Contacting MS can be a hit and miss depending on who you get, you will most likely go around in circles with generic responses.

Windows Update Log

  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run Inside the Run box copy and paste the following command
    cmd /c copy %windir%\WindowsUpdate.log "%userprofile%\Desktop\WindowsUpdate.txt"
  3. Please go to your desktop and attach WindowsUpdate.txt to your next post
 
They are downloading, installing, and then I get an error message stating that 2 updates could'nt be installed: KB2962409 and KB2967917.
The error code is 800F0900...

I uninstalled panda could antivirus in the hope it would help, but it didn't... No other security program installed...
 
800fXXX error codes refer to CBS errors. Strange that this one is not showing in the CBS log.

Maybe it might be in one of the previous CBS log file. Can you please run Windows updates again, let it fail then provided the following:

Export CBS folder

  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on File Explorer
  3. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
  4. Find and double click on the Logs folder.
  5. Right-click on the CBS folder, and select Copy.
  6. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
  7. Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
  8. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created.
  9. Attach this to your next post please.
Please Note:: if the file is too big to upload to you next post please upload via Dropbox or One Drive

Windows Update Log

  1. Right click on the
    aa922834-ed43-40f1-8830-d5507badb56c_39.jpg
    button
  2. Click on Run Inside the Run box copy and paste the following command
    cmd /c copy %windir%\WindowsUpdate.log "%userprofile%\Desktop\WindowsUpdate.txt"
  3. Please go to your desktop and attach WindowsUpdate.txt to your next post
 
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