Page 1 of 2 12 Last
  1. #1

    Question [10v1511b10586 x64] always failed to upgrade.

    I refered to the guide in this forum and ran SFC /scannow, and uploaded the CBS.log to the one drive. (https://1drv.ms/u/s!Ao55nNRDPoC9g1TjC1VCFZ9FL6H4)

    currently behavior is
    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 and again.

    I even tried the solution provided by posting a thread in msdn forum here, but still failed. I want to find the solution here.


    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:E:\win10pro /readonly
    5. Dism /Online /Cleanup-Image /RestoreHealth /Source:E:\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 Configure a Windows Repair Source | Microsoft Docs.

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

    and I uploaded the dism.log to https://1drv.ms/u/s!Ao55nNRDPoC9g1KtpT3JfUlQebwD


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2

    Join Date
    Dec 2014
    Posts
    1,919

    Re: [10v1511b10586 x64] always failed to upgrade.

    Hello and welcome,

    Follow the instructions below please.

    WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.


    • Download SFCFix and move the executable to your desktop.
    • Download the attachment SFCFix.zip and save it on your desktop.
    • Save any work you have open, and close all programs.
    • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    • SFCFix will launch, let it complete.
    • Once done, a file will appear on your desktop, called SFCFix.txt.
    • Open the file, then copy and paste its content in your next reply.
    Attached Files Attached Files

  3. #3

    Re: [10v1511b10586 x64] always failed to upgrade.

    Quote Originally Posted by PeterJ View Post
    Hello and welcome,

    Follow the instructions below please.

    WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.


    • Download SFCFix and move the executable to your desktop.
    • Download the attachment SFCFix.zip and save it on your desktop.
    • Save any work you have open, and close all programs.
    • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    • SFCFix will launch, let it complete.
    • Once done, a file will appear on your desktop, called SFCFix.txt.
    • Open the file, then copy and paste its content in your next reply.
    Hi,Peter,
    thanks for your reply.

    I followed the steps you mentioned, and pasted the result. (from SFCFix.txt)

    Code:
    SFCFix version 3.0.0.0 by niemiro.
    Start time: 2018-01-05 20:25:40.115
    Microsoft Windows 10 Build 10586 (Updates Deferred) - amd64
    Using .zip script file at C:\Users\ALEXYA\Desktop\SFCFix.zip [0]
    
    
    
    
    
    
    
    
    PowerCopy::
    Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-ui-logon-library_31bf3856ad364e35_10.0.10586.1106_none_aa4d36f24ffc5a63\Windows.UI.Logon.pri
    
    
    Successfully copied file C:\Users\ALEXYA\AppData\Local\niemiro\Archive\amd64_microsoft-windows-ui-logon-library_31bf3856ad364e35_10.0.10586.1106_none_aa4d36f24ffc5a63\Windows.UI.Logon.pri to C:\Windows\winsxs\amd64_microsoft-windows-ui-logon-library_31bf3856ad364e35_10.0.10586.1106_none_aa4d36f24ffc5a63\Windows.UI.Logon.pri.
    
    
    Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-ui-logon-library_31bf3856ad364e35_10.0.10586.1106_none_aa4d36f24ffc5a63\Windows.UI.Logon.pri
    Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-ui-logon-library_31bf3856ad364e35_10.0.10586.1106_none_aa4d36f24ffc5a63\Windows.UI.Logon.pri
    PowerCopy:: directive completed successfully.
    
    
    
    
    
    
    
    
    Successfully processed all directives.
    SFCFix version 3.0.0.0 by niemiro has completed.
    Currently storing 2 datablocks.
    Finish time: 2018-01-05 20:25:40.365
    Script hash: szSpAWxWH9G8iWwqwGLXMVSAx9pMctRweGSm5AMJzRg=
    ----------------------EOF-----------------------

  4. #4

    Re: [10v1511b10586 x64] always failed to upgrade.

    [10v1511b10586 x64] always failed to upgrade.-win10-upgrade6-jpg
    [@PeterJ]
    After I did the SFCFix as your steps, the win10 upgrade triggered again automatically on my computer. And it failed with the error (in screenshot above).

  5. #5

    Join Date
    Dec 2014
    Posts
    1,919

    Re: [10v1511b10586 x64] always failed to upgrade.

    Run SFC /SCANNOW again:

    1. Right-click on the Start button and select Command Prompt (administrator).
    2. When command prompt opens, copy and paste the following commands into it, press enter after each.

      Code:
      sfc /scannow
      Wait for this to finish before you continue

      Code:
      copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
    3. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
      Note: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the download link.

  6. #6

    Re: [10v1511b10586 x64] always failed to upgrade.

    Quote Originally Posted by PeterJ View Post
    Run SFC /SCANNOW again:

    1. Right-click on the Start button and select Command Prompt (administrator).
    2. When command prompt opens, copy and paste the following commands into it, press enter after each.

      Code:
      sfc /scannow
      Wait for this to finish before you continue

      Code:
      copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
    3. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
      Note: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the download link.
    I ran sfc/scannow and uploaded the CBS.txt to one drive. From the result and log, it seems that there is no issue. But I still got upgrade failure again today

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

    Code:
    C:\Windows\system32>sfc /scannow
    
    
    Beginning system scan.  This process will take some time.
    
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    
    Windows Resource Protection did not find any integrity violations.
    
    
    C:\Windows\system32>copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
            1 file(s) copied.

  7. #7

    Join Date
    Dec 2014
    Posts
    1,919

    Re: [10v1511b10586 x64] always failed to upgrade.

    Follow the instructions below to run a scan with the DISM tool and provide a log.

    1. Right-click the Start button and click Command prompt(Administrator).
    2. If you get a popup about UserAccountControl, allow the program to run.
    3. When command prompt opens, copy and paste the following commands into it, press enter after each.

      Code:
      dism /Online /Cleanup-Image /RestoreHealth
      Wait for this to finish before you continue

      Code:
      copy %windir%\logs\dism\dism.log "%userprofile%\Desktop\dism.txt"
    4. This will create a file, dism.txt on your Desktop. Please attach this to your next post.
      Note: if the file is too big to upload to your next post please upload via a service such as Filedropper or One Drive or SendSpace and just provide the download link.

  8. #8

    Re: [10v1511b10586 x64] always failed to upgrade.

    Quote Originally Posted by PeterJ View Post
    Follow the instructions below to run a scan with the DISM tool and provide a log.

    1. Right-click the Start button and click Command prompt(Administrator).
    2. If you get a popup about UserAccountControl, allow the program to run.
    3. When command prompt opens, copy and paste the following commands into it, press enter after each.

      Code:
      dism /Online /Cleanup-Image /RestoreHealth
      Wait for this to finish before you continue

      Code:
      copy %windir%\logs\dism\dism.log "%userprofile%\Desktop\dism.txt"
    4. This will create a file, dism.txt on your Desktop. Please attach this to your next post.
      Note: if the file is too big to upload to your next post please upload via a service such as Filedropper or One Drive or SendSpace and just provide the download link.
    I ran dism and uploaded the log to the one drive.
    https://1drv.ms/t/s!Ao55nNRDPoC9g1buBY2beLoUJ4Lc

    Code:
    C:\Windows\system32>dism /Online /Cleanup-Image /RestoreHealth
    
    
    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0
    
    
    Image Version: 10.0.10586.0
    
    
    [==========================100.0%==========================]
    The restore operation completed successfully.
    The operation completed successfully.
    
    
    C:\Windows\system32>copy %windir%\logs\dism\dism.log "%userprofile%\Desktop\dism.txt"
            1 file(s) copied.
    
    
    C:\Windows\system32>
    p.s. my windows upgrade triggered and failed again. e.g.

    Something went wrong
    Microsoft can't install important security updates on your PC.
    [IMG]file:///C:/Windows10Upgrade/resources/ux/lock.png[/IMG]
    To ensure things go smoothly:
    Please contact Microsoft Support for help with this error.
    Please provide the support representative with this error code: 0x80070002

  9. #9

    Join Date
    Dec 2014
    Posts
    1,919

    Re: [10v1511b10586 x64] always failed to upgrade.

    Please do not quote my message in your reply.

    Microsoft can't install important security updates on your PC.
    [IMG]file:///C:/Windows10Upgrade/resources/ux/lock.png[/IMG]
    Upload that image file to a file-sharing site such as Filedropper or SendSpace and post the downloadlink.

  10. #10

    Re: [10v1511b10586 x64] always failed to upgrade.

    [10v1511b10586 x64] always failed to upgrade.-lock-png

    I uploaded the file "C:/Windows10Upgrade/resources/ux/lock.png" which is a 'lock' picture.

  11. #11

    Join Date
    Dec 2014
    Posts
    1,919

    Re: [10v1511b10586 x64] always failed to upgrade.

    Right-click on the Start button and click Run.
    Typ POWERSHELL in the input field, then click OK.
    A blue window appears.
    Typ in the blue window Get-WindowsUpdateLog and press the enter key.
    Some text will appear in the blue window. Wait for the message "WindowsUpdate.log written to C:\Users\<username>\Desktop\WindowsUpdate.log".
    Close the blue window.

    Attach the file C:\Users\<username>\Desktop\Windows\WindowsUpdate.log to your next reply.
    Note: if the file is too big to upload to your next reply please upload via a service such as Filedropper or One Drive or SendSpace and just provide the download link.

  12. #12

    Re: [10v1511b10586 x64] always failed to upgrade.

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

    I took a look at the log, it seems that the time is wrong. I ran the command Get-WindowsUpdateLog twice but got the same result.

    Code:
    C:\Windows\system32> Get-WindowsUpdateLog
    
    
    Converting C:\Windows\logs\WindowsUpdate into C:\Users\ALEXYA\Desktop\WindowsUpdate.log ...
    
    
    Input
    ----------------
    File(s):
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180104.201247.004.2.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180104.210557.040.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180104.210557.040.2.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180104.221302.102.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180104.231539.991.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180105.065452.178.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180105.202208.013.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180105.202208.013.2.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180105.212852.099.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180105.212852.099.2.etl
    
    
    0.00%8.94%17.88%26.82%35.75%44.69%53.63%62.57%71.51%80.45%89.39%98.32%100.00%
    
    
    Output
    ----------------
    DumpFile:           C:\Users\ALEXYA\AppData\Local\Temp\WindowsUpdateLog\wuetl.CSV.tmp.00000
    
    
    The command completed successfully.
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Input
    ----------------
    File(s):
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180105.225245.035.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180106.203802.222.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180106.203802.222.2.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180106.212933.829.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180106.212933.829.2.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180106.223348.020.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180106.224739.954.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180107.151644.972.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180107.151644.972.2.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180107.155354.323.1.etl
    
    
    0.00%10.67%21.33%32.00%42.67%53.33%64.00%74.67%85.33%96.00%100.00%
    
    
    Output
    ----------------
    DumpFile:           C:\Users\ALEXYA\AppData\Local\Temp\WindowsUpdateLog\wuetl.CSV.tmp.00001
    
    
    The command completed successfully.
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Input
    ----------------
    File(s):
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180107.163922.023.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180107.192626.016.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180107.201112.342.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180107.210554.031.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180107.210554.031.2.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180107.223047.032.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180108.195617.096.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180108.195617.096.2.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180108.210345.040.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180108.212732.517.1.etl
    
    
    0.00%10.74%21.48%32.21%42.95%53.69%64.43%75.17%85.91%96.64%100.00%
    
    
    Output
    ----------------
    DumpFile:           C:\Users\ALEXYA\AppData\Local\Temp\WindowsUpdateLog\wuetl.CSV.tmp.00002
    
    
    The command completed successfully.
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Input
    ----------------
    File(s):
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180108.212732.517.2.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180108.220053.611.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180108.223032.033.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180108.230820.126.1.etl
         C:\Windows\logs\WindowsUpdate\WindowsUpdate.20180109.200138.239.1.etl
    
    
    0.00%48.48%96.97%100.00%
    
    
    Output
    ----------------
    DumpFile:           C:\Users\ALEXYA\AppData\Local\Temp\WindowsUpdateLog\wuetl.CSV.tmp.00003
    
    
    The command completed successfully.
    
    
    
    
    
    
    
    
    
    
    WindowsUpdate.log written to C:\Users\ALEXYA\Desktop\WindowsUpdate.log
    
    
    C:\Windows\system32>

  13. #13

    Join Date
    Dec 2014
    Posts
    1,919

    Re: [10v1511b10586 x64] always failed to upgrade.

    1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool

    2. Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
    3. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
    4. Press the Scan button.
    5. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
    6. Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.

  14. #14

    Re: [10v1511b10586 x64] always failed to upgrade.

    I ran the FRST tool and uploaded the log files.

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

  15. #15

    Join Date
    Dec 2014
    Posts
    1,919

    Re: [10v1511b10586 x64] always failed to upgrade.

    Step 1:
    Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

    1. Download the attachment fixlist.txt and save it to your desktop.
    2. Right-click on FRST64.exe and select "Run as administrator".
    3. Press the Fix button.
    4. The tool will now process fixlist.txt.
    5. 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.
    6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
    7. Post the logfile Fixlog.txt as attachment in your next reply.

    Step 2:
    Check Windows Update again.
    If it fails, perform the instructions in message #5 again.
    Attached Files Attached Files

  16. #16

    Unhappy Re: [10v1511b10586 x64] always failed to upgrade.

    FRST64 result
    Code:
    Fix result of Farbar Recovery Scan Tool (x64) Version: 13.01.2018 01
    Ran by ALEXYA (14-01-2018 15:15:18) Run:1
    Running from C:\Users\ALEXYA\Desktop
    Loaded Profiles: ALEXYA (Available Profiles: ALEXYA)
    Boot Mode: Normal
    ==============================================
    
    
    fixlist content:
    *****************
    CloseProcesses:
    EmptyTemp:
    
    
    *****************
    
    
    Processes closed successfully.
    
    
    =========== EmptyTemp: ==========
    
    
    BITS transfer queue => 0 B
    DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 96740133 B
    Java, Flash, Steam htmlcache => 222852624 B
    Windows/system/drivers => 17445200 B
    Edge => 70075098 B
    Chrome => 489073548 B
    Firefox => 198930901 B
    Opera => 0 B
    
    
    Temp, IE cache, history, cookies, recent:
    Default => 0 B
    Users => 0 B
    ProgramData => 0 B
    Public => 0 B
    systemprofile => 128 B
    systemprofile32 => 128 B
    LocalService => 128 B
    NetworkService => 3866570 B
    ALEXYA => 1324339924 B
    
    
    RecycleBin => 2587050112 B
    EmptyTemp: => 4.7 GB temporary data Removed.
    
    
    ================================
    
    
    
    
    The system needed a reboot.
    
    
    ==== End of Fixlog 15:16:28 ====
    I rebooted the machine and ran Windows 10 Update Asistant, sevral hours later, em..... still failed. I uploaded the cbs and windows update logs.

    cbs.log
    https://1drv.ms/u/s!Ao55nNRDPoC9g1no9u3sse3HGKnQ

    dism.log
    https://1drv.ms/u/s!Ao55nNRDPoC9g1ufti7chUW23wrf

    windowsupdate log
    https://1drv.ms/u/s!Ao55nNRDPoC9g1rwg4-hR7WJOQFq

    Code:
    C:\Windows\system32>sfc /scannow
    
    
    Beginning system scan.  This process will take some time.
    
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    
    Windows Resource Protection did not find any integrity violations.
    
    
    C:\Windows\system32>copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
            1 file(s) copied.
    
    
    C:\Windows\system32>dism /Online /Cleanup-Image /RestoreHealth
    
    
    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0
    
    
    Image Version: 10.0.10586.0
    
    
    [==========================100.0%==========================]
    The restore operation completed successfully.
    The operation completed successfully.
    
    
    C:\Windows\system32>

  17. #17

    Join Date
    Dec 2014
    Posts
    1,919

    Re: [10v1511b10586 x64] always failed to upgrade.

    Attach the files C:\$SysReset\Logs\setupact.log and C:\$SysReset\Logs\setuperr.log.

  18. #18

    Re: [10v1511b10586 x64] always failed to upgrade.

    There is no setupact.log and setuperr.log under my C:\$SysReset\Logs\ folder. (see the screenshot)
    Attachment 31840Attachment 31839


    There is a setupact_offline.log (and the record date is wrong, I think, it should not be the one you want), I pasted the content directly here.

    Code:
    2018-01-03 22:04:20, Info                         RjvStartLogging: Started logging to [C:\$SysReset\Logs\SetupAct_offline.log]
    2018-01-03 22:04:20, Info                         Entering RjvFactoryImageAvailable
    2018-01-03 22:04:20, Info                         [systemreset.exe] Enter WinReGetConfig
    2018-01-03 22:04:20, Info                         [systemreset.exe] Parameters: configWinDir: NULL
    2018-01-03 22:04:20, Info                         [systemreset.exe] WinRE config file path: C:\Windows\system32\Recovery\ReAgent.xml
    2018-01-03 22:04:20, Warning                      [systemreset.exe] winreGetWinReGuid BcdOpenSystemStore failed: 0xc000000f
    2018-01-03 22:04:20, Info                         [systemreset.exe] winreGetWinReGuid returning 0X2
    2018-01-03 22:04:20, Info                         [systemreset.exe] ReAgentConfig::ReadBcdInfo WinRE disabled, WinRE Guid could not be determined  (0X2) 
    2018-01-03 22:04:20, Info                         [systemreset.exe] System is WimBoot: FALSE
    2018-01-03 22:04:20, Info                         [systemreset.exe] WinRE image validated
    2018-01-03 22:04:20, Info                         No OEM image specified
    2018-01-03 22:04:20, Error                        Failed to query registry for ESD image index: 0x2
    2018-01-03 22:04:20, Error                        Failed to search for an ESD image. Last error: 0x0
    2018-01-03 22:04:20, Error                        Returning FALSE from RjvFactoryImageAvailable
    2018-01-03 22:04:47, Info                         RjvStopLogging: Stopped logging to [C:\$SysReset\Logs\SetupAct_offline.log]
    2018-01-03 22:06:57, Info                         RjvStartLogging: Started logging to [C:\$SysReset\Logs\SetupAct_offline.log]
    2018-01-03 22:06:57, Info                         Entering RjvFactoryImageAvailable
    2018-01-03 22:06:57, Info                         [systemreset.exe] Enter WinReGetConfig
    2018-01-03 22:06:57, Info                         [systemreset.exe] Parameters: configWinDir: NULL
    2018-01-03 22:06:57, Info                         [systemreset.exe] WinRE config file path: C:\Windows\system32\Recovery\ReAgent.xml
    2018-01-03 22:06:57, Warning                      [systemreset.exe] winreGetWinReGuid BcdOpenSystemStore failed: 0xc000000f
    2018-01-03 22:06:57, Info                         [systemreset.exe] winreGetWinReGuid returning 0X2
    2018-01-03 22:06:57, Info                         [systemreset.exe] ReAgentConfig::ReadBcdInfo WinRE disabled, WinRE Guid could not be determined  (0X2) 
    2018-01-03 22:06:57, Info                         [systemreset.exe] System is WimBoot: FALSE
    2018-01-03 22:06:57, Info                         [systemreset.exe] WinRE image validated
    2018-01-03 22:06:57, Info                         No OEM image specified
    2018-01-03 22:06:57, Error                        Failed to query registry for ESD image index: 0x2
    2018-01-03 22:06:57, Error                        Failed to search for an ESD image. Last error: 0x0
    2018-01-03 22:06:57, Error                        Returning FALSE from RjvFactoryImageAvailable
    2018-01-03 22:07:11, Info                         RjvStopLogging: Stopped logging to [C:\$SysReset\Logs\SetupAct_offline.log]
    I found another the setupact.log under C:\$WINDOWS.~BT\Sources\Panther, and uploaded to onedrive.

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

    or which one setupact.log you need?
    [10v1511b10586 x64] always failed to upgrade.-win10-upgrade8-jpg

  19. #19

    Join Date
    Dec 2014
    Posts
    1,919

    Re: [10v1511b10586 x64] always failed to upgrade.

    Try to run the Windows Update Troubleshooter:
    Windows Update Troubleshooter - Microsoft Community

    Please report the result.

  20. #20

    Re: [10v1511b10586 x64] always failed to upgrade.

    [10v1511b10586 x64] always failed to upgrade.-win10-upgrade9-jpg

    it seems that there is something error to the windows update. It fixed it.
    I will rerun the windows update assistant.

Page 1 of 2 12 Last

Similar Threads

  1. Replies: 8
    Last Post: 12-22-2017, 11:38 AM
  2. [SOLVED] All of Windows updates failed in June restore points failed
    By Joe Tradition in forum Windows Update
    Replies: 4
    Last Post: 07-03-2016, 03:50 PM
  3. Replies: 0
    Last Post: 12-14-2015, 11:41 PM
  4. Replies: 72
    Last Post: 10-14-2015, 03:59 PM

Log in

Log in