Error DISM restorehealth

Page 2 of 8 FirstFirst 1234 ... LastLast

  1. Posts : 5,478
    2004
       #11

    Kyhi said:
    Place the "Image_health" folder on C - you are running the command 9 folders deep...
    Place Image_health-sxs.cmd inside "image_health" folder
    I had to put it on root of D: as I've only 8GB free on C which isn't enough as the copied wim is 3.5 GB and mount directory expands wim to take an additional 10.7GB.

    Kyhi said:
    step 1 delete current dism and cbs log files
    step 2 run Image_Health.cmd - option 1 = scanhealth
    step 3 run Image health - option 2 = restorehealth
    step 4 run image health - option 3 = restorehealth /source
    step 5 post dism.log and cbs.log (note: you can post logs as .txt > cbs.txt dism.txt)
    step 1. OK
    step 2. said repairable.
    step 3. "The operation completed successfully"
    step 4. "The operation completed successfully" (but then there was nothing to repair anymore)
    step 5. Attachment 39345, dism.txt

    sfc /scannow now finishes with no integrity violations.

    Perhaps I was running it in wrong order before jumping straight in at step 3. It seems that option 3 restore-health /source option didn't work as this was the corrupt file:

    amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.10240.16431_none_19399ca28acb6684\MicrosoftEdgeSquare44x44.scale-125_contrast-white.png

    but the only file in D:\IMAGE_HEALTH\Temp\Mount\Windows\WinSxS was

    amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.10240.16384_none_193830228accc4c7

    So like you said from Windows update...

    Does this sound right to you - the /source /limit-access will not fix anything updated by Windows update? So to repair in such a case you'd need to somehow or other track down the correct .msu and add it to D:\IMAGE_HEALTH\Temp\Mount with dism /add-package?

    I don't have a problem any more I'm just curious - and thanks for the script - it is really nice having all the options in one place..
      My Computer


  2. Posts : 7
    Windows 10
    Thread Starter
       #12

    Re


    re


    1) I downloaded the Windows version 10 that corresponds me TechBench
    2) Mounted ISO
    3) Preview: IMAGE_HEALTH.zip on the root C:
    4) Unlocked: IMAGE_HEALTH.CMD
    5) Launched administrator IMAGE_HEALTH.CMD
    6) Selection of Option 3
    For me, everything went well with no errors:
    ===============================================================================
    Dism is restoring the online image health.
    This will take several minutes..
    ===============================================================================

    Outil Gestion et maintenance des images de déploiement
    Version : 10.0.10240.16384

    Version de l’image : 10.0.10240.16384

    [==========================100.0%==========================]
    La restauration a été effectuée.
    L’opération a réussi.

    Outil Gestion et maintenance des images de déploiement
    Version : 10.0.10240.16384

    Démontage de l’image
    [==========================100.0%==========================]
    L’opération a réussi.
    Appuyez sur une touche pour continuer...
    I launched a sfc / Scannow no errors and everything is ok now.


    Thank you for the help that solved the problem in my case.


    Best regards
      My Computer


  3. Posts : 4,131
    Windows 3.1 to Windows 11
       #13

    Glad it finally worked out for the both of you..

    a mounted Windows 10 Pro - install.wim - has 13,038 folders inside the Windows\winsxs folder

    when you use the install.wim as the repair /source = it does not contain any windows updates...

    What I would recommend (now that the corruption is repaired) is make a backup of the WINSXS folder = as that is the actual repair /source for the online OS image...

    /limitacces = prevents the use of the windows update server as a repair /source

    thus in theory removing the /limtaccess - should allow dism to use the windows update server as a repair /source

    So, in fact there are 3 repair /source (s)
    install.wim
    winsxs folder
    MS updates

    what is often found, is that most of the file corruption reports come from windows updates.. thus /limitaccess
      My Computer


  4. Posts : 70
    Windows 10 Home
       #14

    Would it be ok to create my media from courrpt computer system?? ONLY WIN 10 HOME BOX?




    kyhi said:
    here is a program to help users with corrupt windows files..
    This program will run system file checker and dism commands to repair an online windows image
    and will look for the setup media to use as a repair source

    step 1: Download and extract > image_health.zip to a root folder ( c:\image_health )
    step 2: Right-click image_health.cmd > select properties > select unblock
    step 3: Insert your windows setup media ( mounted iso or dvd or usb )
    step 4: Right click on image_health.cmd and run as administrator

    image_health.zip

    the preferred method of use would be to select

    option 1 scanhealth > if shows as repairable,
    then
    option 2 restorehealth > if shows as needing source file,
    then
    option 3 restorehealth /source

    note: Dism uses the component store as it's main source for image repair, and windows updates are placed in the component store, so best to try to use current component store for restorehealth,
    before selecting option 3 and redirecting the repair source, to the windows setup media..

    Option 4 > will analyze the component store, it will tell you if the store can be cleaned up -
    option 5 > will cleanup (remove) superseded windows files over 45 days old in the component store
    option 6 > will cleanup (remove) all superseded windows files in the component store
    option 7 > will run revert pending dism actions (unlock, the locked disk message)

    option 8 > will run system file checker sfc /scannow

    note: Sfc has been known to flag perfectly good files as corrupt, although this does not harm anything other, then the user now thinking the system is corrupt, and resulting in false positive confusion about the corruption

    option 9 > will run disk cleanup manager in extended mode

    note: There are log files to help you and others troubleshoot dism issues,
    c:\windows\logs\cbs\cbs.log
    c:\windows\logs\dism\dism.log

    it is advised to delete those .log files first, then run the program and post the .log(s) as .txt files in forum..
      My Computer


  5. Posts : 29
    Windows 10 (Version 10.0.10240 Build 10240)
       #15

    It did not work for me. I followed all the steps. I got the same error when I run DISM and SFC. Here are the logs

    DISM
    [10 Nov 2015] Dism.txt - Google Drive

    CBS
    [10 Nov 2015] CBS.txt - Google Drive

    Can anybody read them and offer some help? Thanks.
      My Computer


  6. Posts : 4,131
    Windows 3.1 to Windows 11
       #16

    delete current log files
    C:\Windows\Logs\CBS\CBS.log
    C:\Windows\Logs\DISM\dism.log

    Run option 1 and post new log files
      My Computer


  7. Posts : 29
    Windows 10 (Version 10.0.10240 Build 10240)
       #17

    I deleted the old logs.
    I just run Option 1 as you indicated. The result is below.

    Here are the new logs

    CBS
    CBS_2.txt - Google Drive

    DISM
    DISM_2.txt - Google Drive




    ===============================================================================
    Dism is scanning the online image for health.
    Dism will report whether the image is healthy or repairable
    This will take several minutes..
    ===============================================================================


    Deployment Image Servicing and Management tool
    Version: 10.0.10240.16384


    Image Version: 10.0.10240.16384


    [==========================100.0%==========================]
    The component store is repairable.
    The operation completed successfully.
    Press any key to continue . . .

    What else can I do? Thanks.
      My Computer


  8. Posts : 4,131
    Windows 3.1 to Windows 11
       #18

    CSI Payload Corruption: 1

    x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197\adcjavas.inc

    "C:\Windows\WinSxS\x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197"

    here is the folder and the file is inside goes into Winsxs folder
    [removed]
      My Computer


  9. Posts : 29
    Windows 10 (Version 10.0.10240 Build 10240)
       #19

    I find many sites with this issue, but no concrete solution. Can you please tell me what to do? Or can you direct me to site that shows stepy by step how this issue was successfully solved?
      My Computer


  10. Posts : 4,131
    Windows 3.1 to Windows 11
       #20

    adcjavas.inc
    that file is corrupt and the only one pulling the error
    I have unloaded the folder the file is in..
    extract the zip file and place the folder in winsxs folder

    or browse to the folder on your PC and replace the file inside

    then run option 1
    then run option 2
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:54.
Find Us




Windows 10 Forums