Windows 10: Cumulative Update KB4054517 Windows 10 v1709 Build 16299.125

Page 9 of 16 FirstFirst ... 7891011 ... LastLast
  1.    17 Dec 2017 #81

    Win7ine said: View Post
    I have 3 machines here which fail with the same error and the last definition version on these is from yesterday 1.259.151.0.
    Win7ine said: View Post
    I get Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.259.221.0) - Error 0x80070643

    Several other machines updated ok to 1.259.221.0 and I guess they must have had another definition version as base.
    Click image for larger version. 

Name:	Capture.PNG 
Views:	6 
Size:	31.9 KB 
ID:	168613
    Just DO IT! It worked for me!
    Link here: KB4051963 t install after restart. - Microsoft Community
      My ComputerSystem Spec

  2.    18 Dec 2017 #82

    Not Myself said: View Post
    I would thank you, but you just ruined my day. Took me a moment to figure out what you were looking at, went to C:\, to properties, to Error Checking, which took me to the notification that I don't need to scan the disk, as no problems have been found. I am going to assume that that information is a result of my having recently run chkdsk /r, and, therefore, am not going to run it again to try to find the related entry in the Event Viewer.

    That means that I will have to find something much less boring to do this evening.

    So, I think that you can see that you really did ruin my day, for not only don't I need to rerun chkdsk /r and Event Viewer, but I even have to thank you for the fascinating tip you provided....
    @Not Myself Lol! I must admit that when I first read your post, I didn't pick up the flippancy - luckily I did second time through.

    Just to confirm, when you see "the notification that I don't need to scan the disk, as no problems have been found......"

    That is exactly what it means - I always interpret it as "no problems have been found in regular use, so don't bother scanning the disk"

    However, if you do still hit the Scan drive button, it should perform the scan and log the oft-mentioned Application Event whether it finds problems or not.

    Glance back at my earlier screenshot (post #72) and you'll see that the drive I scanned had no problems but the Event was still created to confirm that fact.

    Remember, it's an Event Viewer NOT an Error log - as such, Errors are a sort of Event, so events good and bad are logged, unless you apply some filters.

    I've never known scanning a drive in this way to cause any issues other than the fact that, as you infer, it is slightly less thrilling than watching grass grow.
    You could at least try it someday when its raining and there's nothing on tele.
    That would at least confirm that the event is being logged.
      My ComputerSystem Spec

  3.    18 Dec 2017 #83

    IronZorg89 said: View Post

    Lastly, maybe it would be a good idea to completely uninstall Macrium Reflect and reinstall it to see if it can work. You definitely need your backup software to work.
    The weirdness continues: Around 0530 local this date, I got an email from Macrium that the KB about troubleshooting, which only went through version 6 of Reflect also applies to version 7, which latter version I am using.

    At 0820 local this date, I got a notification that my weekly Monday morning full backup, which had failed twice last Monday, had completed successfully today. I had not even started to follow the instructions in the Macrium KB, which I intended to do later today, so what whatever caused the failures last Monday appears to have been fixed. I wonder if perhaps something I had done in my quest to fix the Windows Update problem might have fixed the Macrium Reflect full backup malady; if so, I doubt that I will ever know.
      My ComputerSystem Spec

  4.    18 Dec 2017 #84

    Not Myself said: View Post
    The weirdness continues: Around 0530 local this date, I got an email from Macrium that the KB about troubleshooting, which only went through version 6 of Reflect also applies to version 7, which latter version I am using.

    At 0820 local this date, I got a notification that my weekly Monday morning full backup, which had failed twice last Monday, had completed successfully today. I had not even started to follow the instructions in the Macrium KB, which I intended to do later today, so what whatever caused the failures last Monday appears to have been fixed. I wonder if perhaps something I had done in my quest to fix the Windows Update problem might have fixed the Macrium Reflect full backup malady; if so, I doubt that I will ever know.
    I looked at your dism.log file and did a bit of research on it. All they say online is to try to reset Windows Update component with regard to the first error: "Failed to create the dismhost.exe servicing process". I know for a fact you have tried that already and it didn't work. Next they say to try it (Reset Windows Update component) in a clean boot state, for some non Microsoft app might be preventing the dism.exe command to run properly.

    Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

    With regard to Macrium Reflect, I think it is acting up and I wouldn't worry too much about it for now. That is until you get version build of your OS to 16299.125.
      My ComputerSystem Spec

  5.    18 Dec 2017 #85

    IronZorg89 said: View Post
    I looked at your dism.log file and did a bit of research on it. All they say online is to try to reset Windows Update component with regard to the first error: "Failed to create the dismhost.exe servicing process". I know for a fact you have tried that already and it didn't work. Next they say to try it (Reset Windows Update component) in a clean boot state, for some non Microsoft app might be preventing the dism.exe command to run properly.

    Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

    With regard to Macrium Reflect, I think it is acting up and I wouldn't worry too much about it for now. That is until you get version build of your OS to 16299.125.
    Thanks for looking at the file Please do NOT take this as being argumentative: I have several times run the Windows Update Troubleshooter successfully. I did that a few minutes ago, tried dism.exe, got the same failure as before.

    I had seen at least one reference to trying a Clean Boot troubleshooting session yesterday, but did not followup on it. Using your kindly provided link to the tutorial, I have printed the six pages of instructions (the rest of the document being comments and the like) and will spend some time with this function tomorrow, in the (obvious) hope that somehow it can find and fix matters.
      My ComputerSystem Spec

  6.    18 Dec 2017 #86

    Not Myself said: View Post
    Thanks for looking at the file Please do NOT take this as being argumentative: I have several times run the Windows Update Troubleshooter successfully. I did that a few minutes ago, tried dism.exe, got the same failure as before.

    I had seen at least one reference to trying a Clean Boot troubleshooting session yesterday, but did not followup on it. Using your kindly provided link to the tutorial, I have printed the six pages of instructions (the rest of the document being comments and the like) and will spend some time with this function tomorrow, in the (obvious) hope that somehow it can find and fix matters.
    Honestly, I am eager to seeing you resolve this problem. A clean boot state can be your last resort, since whatever (App or anti-virus Sotware) is in interfering with your dism.exe command lines won't be in your way. Really looking forward to seeing the results of your attempts tomorrow.
      My ComputerSystem Spec

  7.    19 Dec 2017 #87

    A re-start solved the problem for me! However I found you have to be patient because the updates can take some time to start installing/downloading?
      My ComputerSystem Spec

  8.    19 Dec 2017 #88

    Willabong said: View Post
    A re-start solved the problem for me! However I found you have to be patient because the updates can take some time to start installing/downloading?
    And, I've found in the past that if you do a restart too soon (before the Restart button appears) Windows can sometimes announce that the upgrade failed because the device was powered down. (I don't remember the exact phrasing, but that was the gist of it)
      My ComputerSystem Spec

  9.    19 Dec 2017 #89

    IronZorg89 said: View Post
    I That is until you get version build of your OS to 16299.125. .
    I am now officially confused; in the past, I was simply confused....

    1. I tried three times to do a Clean Boot; each time, the Microsoft Services which I had hidden and disabled were reset during the restart to get to Clean Boot, so it did not work.

    2. I used the MS Support system to get a very patient, and clearly knowledgeable technician. She deleted lots of files, for example, then I unblocked KB4054517, and she ran an update search. When that KB appeared, she rebooted my computer through her remote support connection.

    Due to all the gyrations going on, I am not clear as to exactly when, in terms of during which reboot, this strange event took place. At any rate, during one reboot, after a rather lengthy period of nothing but a blank screen, the usual `working on update' screen appeared, except that it stated that it was at step 2 of 2, although I had never seen step oneWhen the progress reached 30%, the computer rebooted, and after a while, resumed updating. When it reached 100% it appeared to stop.

    We waited for a long interval, and she had me turn off the computer and restart it. It was not entirely happy with that, but did eventually restart. Returning to Windows Update, KB4058043 showed up again, and required a reboot--or at least I think that it did, and KB405417 said that it did. Rebooted, 43 was installed, 17 not.

    She started a new download of the ISO process, and we ended the call after a while, as I had both a case number and a direct phone number. I happened to look at the monitor as the verification process was starting, but the next time, there was only a small pop-up which said that it could not start something , and to reboot and resume. I restarted,, could not find anything to resume.

    As I still had the desktop shortcut to the ISO-creating program, I clicked on, which stated that I had the latest version of Windows 10, which, as KB4054517 had apparently not been installed, just added to my lack of understanding of what was going on.

    I tried to run dism.exe, which failed, so I logged on here to report my latest shenanigans, where I found your comment about OS Build 16299.125. I had seen that just before logging on, and was quite certain that it was not a number I had seen before. Apparently, I have an up-to-date version of Windows, but which continues to be corrupt, and which insists that KB 4054517 has not been installed, and which leaves me wondering about future update success.
      My ComputerSystem Spec

  10.    19 Dec 2017 #90

    Hi,

    and which insists that KB 4054517 has not been installed, and which leaves me wondering about future update success.
    Since these updates are cumulative you don't need 043 to be installed.
    If it were me I'd run sfc /scannow instead of dism first.

    Cheers,
      My ComputersSystem Spec


 
Page 9 of 16 FirstFirst ... 7891011 ... LastLast

Related Threads
UPDATE 12/12: Cumulative Update KB4054517 Windows 10 v1709 Build 16299.125 - Windows 10 Forums Source: https://support.microsoft.com/en-us/help/4051963/windows-10-update-kb4051963 See also: Servicing stack update KB4054022 for...
UPDATE 11/30: Cumulative Update KB4051963 Windows 10 v1709 Build 16299.98 - Windows 10 Forums Source: https://support.microsoft.com/en-us/help/4048955 163809
UPDATE 11/14: Cumulative Update KB4048955 Windows 10 v1709 Build 16299.64 - Windows 10 Forums Source: https://support.microsoft.com/en-us/help/4043961 Find Windows 10 Version Number
918929244553482240 917827916217516032 915698213587361792 Source: Announcing Windows 10 Insider Preview Build 16299 for PC - Windows Experience Blog
Update: December 9th 2016 Cumulative Update KB3201845 had now been released to general public. Update: December 2nd 2016 Source: Feedback Hub
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 15:18.
Find Us