none
My windows always failed to update to new version windows

    Question

  • 1. I tried to use the "Windows 10 Update Assistant" shortcut in my desktop

    2. download new version of windows 10 ISO, extract to a folder and run setup, choose "upgrade"

    3. or use the media create tool to createa a USB windows 10, use it to boot machine and choose "upgrade"

    all the methods I tried failed.

    So, now, everyday, when I opened my computer, it will try to upgrade once, and failed agian ang again. 

    I don't know how to handle it and upgrade my windows 10. 

    I uploaded the related logs to onedrive, could u please help to analysis it? thx. 

    https://1drv.ms/f/s!Ao55nNRDPoC9aXawUF9wKFLbNuE

    Monday, January 01, 2018 12:04 PM

All replies

  • Fix Windows Update errors by using the DISM or System Update Readiness tool

    You may go for a clean install with the  Windows 10 ISO created and  thereafter try to update to the latest version.


    S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP


    Tuesday, January 02, 2018 1:44 AM
  • Fix Windows Update errors by using the DISM or System Update Readiness tool

    You may go for a clean install with the  Windows 10 ISO created and  thereafter try to update to the latest version.


    S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP


    No, I don't want to re-install a clean windows 10. There are too many software and settings in it. 

    (update:  I noticed that there is a way to "refresh" windows, which means re-install windows with keeping personal files and settings, but it seems win10 doesn't support "refresh" PC)

     

    unfortunately, I followed the link you provided but can't make it run. 

    my steps were:

    1. run winver on command prompt, my OS version is 1511 (build 10586.1176)

    2. download ISO en_windows_10_multiple_editions_version_1511_updated_feb_2016_x64_dvd_8379634

    3. mount it to G drive and get that the index 1 is the winpro.

    dism /Get-WimInfo /WimFile:G:\sources\install.wim

    4. DISM /Mount-Wim /WimFile:G:\sources\install.wim /Index:1 /MountDir:D:\win10pro /readonly

    5. Dism /Online /Cleanup-Image /RestoreHealth /Source:D:\win10pro

    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0

    Image Version: 10.0.10586.0

    [==========================100.0%==========================]

    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 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

    I uploaded the DISM.log file to one drive and you can get it from 

    https://1drv.ms/u/s!Ao55nNRDPoC9g1KtpT3JfUlQebwD


    2018-01-02 21:34:58, Error                 DISM   DISM Package Manager: PID=2176 TID=5368 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
    2018-01-02 21:34:58, Error                 DISM   DISM Package Manager: PID=2176 TID=5368 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
    2018-01-02 21:34:58, Error                 DISM   DISM Package Manager: PID=2176 TID=5368 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
    2018-01-02 21:34:58, Error                 DISM   DISM Package Manager: PID=2176 TID=5368 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
    2018-01-02 21:34:58, Error                 DISM   DISM Package Manager: PID=2176 TID=5368 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
    2018-01-02 21:34:58, Error                 DISM   DISM Package Manager: PID=2176 TID=5368 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)











    • Edited by Alex Ya Wednesday, January 03, 2018 2:09 PM
    Tuesday, January 02, 2018 9:17 AM
  • from your setuperr.log:
    2018-01-01 18:23:26, Error                 SP     CDownloadDUUpdates::DoExecuteInternal: Did not find hard disk space needed, when update cab files will not be extracted. This is unexpected! hr = 0x8000ffff

    so looks like you don't have enough free space.
    Tuesday, January 02, 2018 12:23 PM
  • from your setuperr.log:
    2018-01-01 18:23:26, Error                 SP     CDownloadDUUpdates::DoExecuteInternal: Did not find hard disk space needed, when update cab files will not be extracted. This is unexpected! hr = 0x8000ffff

    so looks like you don't have enough free space.

    I don't know why there was the "incorrect" message, in fact, my drive C has 200GB free size. 


    • Edited by Alex Ya Tuesday, January 02, 2018 2:40 PM typo
    Tuesday, January 02, 2018 2:39 PM
  • Hi,

    I am experiencing the exact same issue, however I am trying to upgrade from 1607 to 1709. I have over 600gigs free but the error says CDownloadDUUpdates::DoExecuteInternal: Did not find hard disk space needed, when update cab files will not be extracted. This is unexpected! hr = 0x8000ffff.

    I have a hybrid HD though, where 8 gigs is SSD, and the rest is a standard HD. This (on paper) is transparent to the user. Could the fact that it is a hybrid HD that is causing the issue? I.e., it sees an 8gig SSD and thinks there's not enough space?

    C

    Friday, January 05, 2018 3:07 PM