DISM, unexpected behavior

Page 2 of 9 FirstFirst 1234 ... LastLast

  1. Posts : 41
    Windows 10
    Thread Starter
       #11

    DISM /Get-Wiminfo /WimFile:E:\sources\install.wim /index:1
    ...result: "
    Version : 10.0.10586"

    winver opens "About WIndows" that I posted previously: "10586.713"


    DISM /Online /Cleanup-Image /RestoreHealh /source:WIM:E:\sources\install.wim:1
    ...results:

    "Deployment Image Servicing and Management tool
    Version: 10.0.10586.0

    Image Version: 10.0.10586.0

    Error: 87

    The restorehealh option is not recognized in this context.For more information, refer to the help.The source option is not recognized in this context.For more information, refer to the help.

    The DISM log file can be found at C:\windows\Logs\DISM\dism.log"
      My Computer


  2. Posts : 41
    Windows 10 Pro x64
       #12

    After i had problem with DISM and mount install.wim i tested somethign else...

    I mounted Windows 10 Client Insider Preview - Build 15042 English iso with Daemon Tools, i mounted install.wim with VDISM tool but DISM still doesn't work,,,

    PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\ISO\Windows /limitaccess

    Deployment Image Servicing and Management tool
    Version: 10.0.15048.0

    Image Version: 10.0.15048.0

    [===========================89.8%==================== ]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more informat
    ion on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    PS C:\WINDOWS\system32>
    SFC /scannow didn't reported error BUT:

    Log Name: Setup
    Source: Microsoft-Windows-Servicing
    Date: 14/03/2017 17:32:09
    Event ID: 1015
    Task Category: None
    Level: Warning
    Keywords:
    User: SYSTEM
    Computer: Pz-DESKTOP
    Description:
    0 of 1 instances of system store corruption have been repaired. Unrepaired corruptions may lead to failures in future system servicing.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Servicing" Guid="{BD12F3B8-FC40-4A61-A307-B7A013A069C1}" />
    <EventID>1015</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2017-03-14T16:32:09.710897800Z" />
    <EventRecordID>21</EventRecordID>
    <Correlation />
    <Execution ProcessID="2812" ThreadID="4276" />
    <Channel>Setup</Channel>
    <Computer>Pz-DESKTOP</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <UserData>
    <CbsStoreCorruptionRepairFinish xmlns="http://manifests.microsoft.com/win/2004/08/windows/setup_provider">
    <Repaired>0x0</Repaired>
    <TotalCorruption>0</TotalCorruption>
    </CbsStoreCorruptionRepairFinish>
    </UserData>
    </Event>
      My Computer


  3. Posts : 251
    Windows 10 Pro
       #13

    First of all, when you mount the ISO, right click on the ISO file and select mount. Enter the command below from an admin command prompt substituting that assigned drive letter for H in the command below:

    Dism /online /cleanup-image /restorehealth /source:wim:H: \sources\install.wim:1 /limitaccess

    Blank before each /

      My Computer


  4. Posts : 41
    Windows 10 Pro x64
       #14

    @TexasBandit

    Thank you but WIM solution didn't worked...now and then... i started to tjink it's a problem related to Insider
    10.0.15048.0 with MISSING Microsoft-Windows-TestRoot-and-FlightSigning-package~31bf3856ad364e35~amd64~~10.0.15048.0

    CBS Failed to look for file Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15048.0.mum in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]2017-03-14 22:12:03, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
    2017-03-14 22:12:03, Error CBS Failed to look for file Servicing\Packages\update.mum in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
    2017-03-14 22:12:03, Info CBS Repr: Not able to find replacement manifests for package Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15048.0 from any local source
    2017-03-14 22:12:03, Info CBS Exec: Download qualification evaluation, business scenario: Manual Corruption Repair
    2017-03-14 22:12:03, Info CBS Exec: Clients specified using local source only.
    2017-03-14 22:12:03, Info CBS Repr: The system configuration is not qualified for Windows Update download, skip WU.

    2017-03-14 22:12:03, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081


    Here's results:

    PS C:\WINDOWS\system32> Dism /online /cleanup-image /restorehealth /source:wim:H:\sources\install.wim:1 /limitaccessDeployment Image Servicing and Management toolVersion: 10.0.15048.0Image Version: 10.0.15048.0[===========================89.6%=================== ]Error: 0x800f081fThe source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logPS C:\WINDOWS\system32>


    Same problem....If you read carefully i've ALSO tested with a MOUNTED Install.wim and..failed...
    Last edited by PzSniper; 14 Mar 2017 at 16:36.
      My Computer


  5. Posts : 41
    Windows 10
    Thread Starter
       #15

    When I put Dism /online /cleanup-image /restorehealth /source:wim:e: \sources\install.wim:1 /limitaccess (mounted e: ) this is what happens:
    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0
    Image Version: 10.0.10586.0
    [==========================100.0%==========================]
    Error: 0x800f081fThe source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.The DISM log file can be found at C:\windows\Logs\DISM\dism.log

    Why will this not work?
      My Computer


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

    If the Install.wim ( mounted or not) does not contain the original copy of the corrupted file or package..

    The source file will not be found...

    Image-Health creates Detailed txt file on your desktop - detailing the corrupt files names

    If it really bothers you - you can do an in-place repair, upgrade or a system Refresh..

    Just run the setup.exe of your windows setup media from within your current OS.

    Windows will upgrade itself with a fresh copy of the windows OS, keeping your files and settings..
    And placing the corrupted windows OS in the windows.old folder
      My Computer


  7. Posts : 41
    Windows 10 Pro x64
       #17

    I've read on latest Insider builds it's MISSING Microsoft-Windows-TestRoot-and-FlightSigning-package
      My Computer


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

    PzSniper said:
    I've read on latest Insider builds it's MISSING Microsoft-Windows-TestRoot-and-FlightSigning-package
    Thus source file not found...

    Problem is, you hijacked this support thread with your insider preview issues...
    Your issue is not the same, you are using Testing Software...
    He is using Retail Release Software...
      My Computer


  9. Posts : 41
    Windows 10 Pro x64
       #19

    Oh k, sorry...
      My Computer


  10. Posts : 41
    Windows 10
    Thread Starter
       #20

    kyhi: are you saying that even though my installed version and the iso version are both 10.0.10586.0, they still do not match?
      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 08:15.
Find Us




Windows 10 Forums