Windows 10: DISM error 1060

Discus and support DISM error 1060 in Windows 10 Installation and Upgrade to solve the problem; hii, I got window update error is like: There were some problems installing updates, but we'll try again later. If you keep seeing this and want to... Discussion in 'Windows 10 Installation and Upgrade' started by Gurpalsingh3, Jan 16, 2020.

  1. GURPALSINGH3
    Gurpalsingh3 Win User

    DISM error 1060


    hii,

    I got window update error is like:

    There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: 0x80070424

    I also did SFC scan but it can't repair all files and shows following error in sfcdetails text file


    2020-01-16 19:33:30, Info CSI 0000416b [SR] Beginning Verify and Repair transaction

    2020-01-16 19:33:35, Info CSI 0000416d [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:35, Info CSI 0000416f [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:35, Info CSI 00004171 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:35, Info CSI 00004173 [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:35, Info CSI 00004175 [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:35, Info CSI 00004177 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:35, Info CSI 00004179 [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:35, Info CSI 0000417b [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:35, Info CSI 0000417d [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:36, Info CSI 00004194 [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:36, Info CSI 00004195 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2020-01-16 19:33:36, Info CSI 00004197 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:36, Info CSI 00004198 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2020-01-16 19:33:36, Info CSI 0000419a [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:36, Info CSI 0000419b [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2020-01-16 19:33:36, Info CSI 0000419d [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:36, Info CSI 0000419e [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2020-01-16 19:33:36, Info CSI 000041a0 [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:36, Info CSI 000041a1 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2020-01-16 19:33:36, Info CSI 000041a3 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:36, Info CSI 000041a4 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2020-01-16 19:33:36, Info CSI 000041a6 [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:36, Info CSI 000041a7 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2020-01-16 19:33:36, Info CSI 000041a9 [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:36, Info CSI 000041aa [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2020-01-16 19:33:36, Info CSI 000041ac [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    2020-01-16 19:33:36, Info CSI 000041ad [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e6e595ade1abc2bd0ca651b4908a'

    2020-01-16 19:33:36, Info CSI 000041b0 [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpComputerStatus.cdxml; source file in store is also corrupted

    2020-01-16 19:33:36, Info CSI 000041b3 [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreat.cdxml; source file in store is also corrupted

    2020-01-16 19:33:36, Info CSI 000041b6 [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatCatalog.cdxml; source file in store is also corrupted

    2020-01-16 19:33:36, Info CSI 000041b9 [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatDetection.cdxml; source file in store is also corrupted

    2020-01-16 19:33:36, Info CSI 000041bc [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpPreference.cdxml; source file in store is also corrupted

    2020-01-16 19:33:36, Info CSI 000041bf [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpScan.cdxml; source file in store is also corrupted

    2020-01-16 19:33:36, Info CSI 000041c2 [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpWDOScan.cdxml; source file in store is also corrupted

    2020-01-16 19:33:36, Info CSI 000041c5 [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpSignature.cdxml; source file in store is also corrupted

    2020-01-16 19:33:36, Info CSI 000041c8 [SR] Could not reproject corrupted file \??\C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender\\Defender.psd1; source file in store is also corrupted


    it seems to be problem in microsoft security defender but it looks ok when i open microsoft defender and also it shows

    threat found every time start my pc but didn't found any virus after full scanning


    So i used this command in cmd:


    dism /online /cleanup-image /restorehealth

    but after around 74% it shows following error:


    Error: 1060

    The specified service does not exist as an installed service.

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


    My pc is freezing so much i need help with this problem

    :)
     
    Gurpalsingh3, Jan 16, 2020
    #1
  2. JERALDINE ASE
    Jeraldine Ase Win User

    how to repair "Error 1060

    Hi,

    For step-by-step instructions on troubleshooting error 1060, kindly refer to the post of Mohammad _ Imran on this

    link    .

    You may also visit this
    link     to know more about Windows 10 errors. For more information on Windows 10 upgrade and installation error, visit this

    link    .

    Let us know if you need further help.

    Best regards,
     
    Jeraldine Ase, Jan 16, 2020
    #2
  3. STEPHANIE SAL
    Stephanie Sal Win User
    DISM - Parameter "Cleanup-Image" is not known (error 87)

    Hello Eric,

    To troubleshoot your concern, we suggest that you run DISM Restore Health command. Refer to the steps provided below:

    • Open Command Prompt (Administrator).
    • Type the following command:
    DISM /Online /Cleanup-Image /RestoreHealth

    3. Press Enter.

    Let us know how it goes.

    Thank you.
     
    Stephanie Sal, Jan 16, 2020
    #3
  4. ZBOOK
    zbook Win User

    DISM error 1060

    Programs not working


    In post 26 there were steps listed to fix the operating system corruption.
    Are you able to follow them?
    In post 29 was the suggested dism repair command.
     
    zbook, Jan 16, 2020
    #4
Thema:

DISM error 1060

Loading...

  1. DISM error 1060 - Similar Threads - DISM error 1060

  2. DISM error

    in Windows 10 Gaming
    DISM error: Hello,during last days, this message has kept appearing on my screen.Is there anything else to do besides following process, which sadly hasn't solved the problem?Open an elevated command prompt window, then type the following and hit Enter.sfc/scannowOnce done, type the...

  3. DISM error

    in Windows 10 Software and Apps
    DISM error: Whats causing my dism to not find source files? CBS and DISM log: logss https://answers.microsoft.com/en-us/windows/forum/all/dism-error/4bc2be8c-cdd4-48dd-9e7c-c1353c0e028e

  4. How to fix DISM error code 1060?

    in Windows 10 Gaming
    How to fix DISM error code 1060?: Hi! Im facing a problem with DISM tool, it fails a lot with error code 1060. How can i fix it???? I have done: sfc.exe /scannowDISM /online /cleanup-image /StartComponentcleanup -> Fails about 4, 5 times until start and end at 20%.DISM /Online /Cleanup-image /ScanHealth ->...

  5. How to fix DISM error code 1060?

    in Windows 10 Software and Apps
    How to fix DISM error code 1060?: Hi! Im facing a problem with DISM tool, it fails a lot with error code 1060. How can i fix it???? I have done: sfc.exe /scannowDISM /online /cleanup-image /StartComponentcleanup -> Fails about 4, 5 times until start and end at 20%.DISM /Online /Cleanup-image /ScanHealth ->...

  6. Dism Error

    in Windows 10 BSOD Crashes and Debugging
    Dism Error: Hi, i need help with this, I have an Acer swift 314, when I run sfc /scan now, it says :Windows Resource Protection found corrupt files but was unable to fix some of them.For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For...

  7. Error 1060 - Microsoft Gaming Services

    in Microsoft Windows 10 Store
    Error 1060 - Microsoft Gaming Services: It will not start, I have powershell removed it, and powershell installed it. I assume I will get a copy paste to do that again, to failure Ive done it 15 times with 15 different scrips and restarts. Anyone have a real fix?...

  8. DISM ERROR

    in Windows 10 BSOD Crashes and Debugging
    DISM ERROR: Hi, i did an sfc /scannow and got an error saying some components cant be fixed. So i did a Dism check health and scan health, both said there are no errors. Then i did a dism restorehealth but the operation is completed at 84.9%. Please help i am experiencing a lot of issues...

  9. DISM error

    in Windows 10 BSOD Crashes and Debugging
    DISM error: My laptop had a lot of corrupted files after I accidentally switched off the wrong switch. I ran DISM restore health, the following was returned. C:\WINDOWS\system32>dism /Online /Cleanup-image /RestoreHealth Deployment Image Servicing and Management tool Version:...

  10. help error 1060

    in Windows 10 Support
    help error 1060: ok so i am looking into my programs and their is this one called "chrome search" which is just kinda blank and i want to remove it but everytime i go to try and uninstall it i get an error 1060 after my cmd pops up talking about a dispatch file their is no version or size to...

Users found this page by searching for:

  1. error 1060 in restorehealth cmd

    ,

  2. windows service management error #1060