Error 4448, DISM stoped at 73 %, ISO repair failed

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it 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
 
softwaremaniac said:
Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps.2. Try updating the system just like you have in the past. 3. Stop Process Monitor as soon as it 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
Click to expand...
Dropbox - Logfile_08_11.rar
Dropbox - cbs08_11.txt
 
Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

softwaremaniac said:
Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
Click to expand...

Well, I did it, whole process took about couple of seconds, not more than 30, and no restart was asked for or was initiated.

View attachment Fixlog.txt
 
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 the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - 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 SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

OK, here you go

Code: 
[/COLOR]SFCFix version 3.0.0.0 by niemiro.Start time: 2018-11-11 17:48:31.704
Microsoft Windows 10 Build 17134 - amd64
Using .txt script file at C:\Users\Zlatko\Desktop\SFCFixScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-t..iprovider.resources_31bf3856ad364e35_10.0.17134.1_en-us_2a43f5abf3791b4c.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-t..iprovider.resources_31bf3856ad364e35_10.0.17134.1_en-us_2a43f5abf3791b4c.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2018-11-11 17:48:32.062
Script hash: rEGs6KaLZEB3JGzXLVDrT2HOBXRqiHQn0yDJkhEwIVA=
----------------------EOF-----------------------[COLOR=#3E3E3E]
 
Here you can find Windows update proceed with, but without problem, cause there is no update available in this moment for my comp, cause recently I update it, after i flush completely windup history, and after I perform again update, it did it successfully, meanwhile I was waiting for your further direction. so what to do next?
So, procmonitor cant capture anything in side this WU proces.
 

Attachments

  • WU_fine.PNG
    WU_fine.PNG
    272.3 KB · Views: 3
  • WU history.PNG
    WU history.PNG
    14.1 KB · Views: 2
Is there anyone else on this forum with some constructive idea to solve this issue beside that one clean install, I know that one too, long time before I ask for help here? Or, the best maybe is to direct me to reliable another/other forum where members are more interested in more chalenging issues?
Thank you in front
 
There's nothing constructive about this. Hardware issues can only be resolved by replacing the faulty part for a brand new one. Then, and only then can the issue be fully resolved. As we have confirmed by several tools, you do have indeed have a faulty drive. I've personally been through several hundreds of these issues and I know what I'm talking about.
 
softwaremaniac said:
There's nothing constructive about this. Hardware issues can only be resolved by replacing the faulty part for a brand new one. Then, and only then can the issue be fully resolved. As we have confirmed by several tools, you do have indeed have a faulty drive. I've personally been through several hundreds of these issues and I know what I'm talking about.
Click to expand...


OK, lets say I take you serous, you talk about this truly, I have my next SSD drive, and I will use it for clean install for my PC where mine <faulty>> drive was, and <<faulty>> one will use to install in side other hardware, notebook, how I can check that he is really is bad? How can I confirm your claim/theory??
 
Several tools have confirmed it as you have seen by the screenshots. You could also put it in another machine and see that you will get errors (maybe not right away, but very soon).
 
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