Thanks mate . I do hope Robert reads this.
Feature update to Windows 10, version 1709 fails to install
Hi, I am trying to install the Creators Update on my computer, but it fails and has to recover every time I try. What system information should I post to help troubleshoot why the update continues to fail?
Thanks!
-Andrew
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
153 answers
Sort by: Oldest
-
Anonymous
2018-02-18T02:58:57+00:00 -
Anonymous
2018-02-18T03:01:29+00:00 so as I have been following along with the troubleshooting, one of the solutions posted that I tried seemed to have fixed the install issue. sadly I don't know which one it was, as I had tried so many. I was to the point that I was going to clean install windows this morning, but when I turned on the pc to back up stuff, the 1709 update finally decided to install with out errors. probably scared the pc with a clean install lol
thanks to all that posted stuff to try
-
Anonymous
2018-02-18T03:14:26+00:00 Glad to hear it. 😊. That proves it can be done.
It is sad 😢you can't recall exactly what the cure was, though. I'm sure if you did a BCDBoot you'd remember that. So, it couldn't be that.
-
Anonymous
2018-02-18T05:05:41+00:00 I managed to create the things as you requested.
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>MD C:\BU
C:\WINDOWS\system32>BCDEdit /Export "C:\BU\BCD Backup
The operation completed successfully.
C:\WINDOWS\system32>
-
Anonymous
2018-02-18T05:34:02+00:00 2018-02-18 10:19:49, Error DISM DISM Package Manager: PID=14140 TID=11644 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
2018-02-18 10:19:49, Info DISM DISM Package Manager: PID=14140 TID=11644 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
Try to find the CBS.log for that time and just before. You may have to look at the archived bits to find one for that. Otherwise, do it again and then you would be able to see the relevant logging in the current CBS.log
HTH
Robert