Windows 10: Cumulative Update KB4054517 Windows 10 v1709 Build 16299.125

Page 7 of 16 FirstFirst ... 56789 ... LastLast
  1.    15 Dec 2017 #60

    IronZorg89 said: View Post
    @ Not Myself

    I am still thinking about your case.
    As you have been so very kind to keep posting for me, rather than my going back to find the earlier post with your suggestion to try certain things, I am going to use this recent message from you to inform you as to what transpired yesterday.

    You had suggested a series of things to do:

    1. Run sfc /scanow again. I did that, nothing found.

    2. Run chkdsk /r. I did that, which was a bit scary at first. The computer seemed to be locked up, with three or four items that I had never seen before preventing the restart, with the mouse inactive, the enter key doing nothing. I was close to losing patience and turning the computer off, but thought that was not a good idea so I waited a while. Eventually, whatever it was got sorted out and chkdsk started to run. My best guess is that the attempt to install the update and the request to run chkdsk were in contention. Chkdsk quickly went to 10%, which I have seen before, and remained there for at least a few hours; the next thing that I saw was the lock screen, so I assume that chkdsk had finished.

    3. After the startup finished, I twice ran dism /online /cleanup-image /restorehealth. Both times, it failed, with notification as to where the log could be found. The log is very long, very complex, and I did not even try to understand the entries, but did find this:

    Host machine information: OS Version=10.0.16299, Running architecture=amd64, Number of processors=8
    2017-12-14 18:07:06, Error DISM DISM.EXE: Failed validating command line: "C:\Windows\system32\Dism.exe" /online
    2017-12-14 18:07:06, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

    After the second failure, I decided to throw myself on the mercy of the court and/or on your amazing patience, and ask your advice as to what I ought to do next. I did not run the fourth item in your list, to again run Windows Updates troubleshooter.
      My ComputerSystem Spec

  2.    15 Dec 2017 #61

    I have not had any issues installing any updates on my PC. All windows defender updates work too. Hope all problems get sorted out
      My ComputerSystem Spec

  3.    15 Dec 2017 #62

    Not Myself said: View Post
    As you have been so very kind to keep posting for me, rather than my going back to find the earlier post with your suggestion to try certain things, I am going to use this recent message from you to inform you as to what transpired yesterday.

    You had suggested a series of things to do:

    1. Run sfc /scanow again. I did that, nothing found.

    2. Run chkdsk /r. I did that, which was a bit scary at first. The computer seemed to be locked up, with three or four items that I had never seen before preventing the restart, with the mouse inactive, the enter key doing nothing. I was close to losing patience and turning the computer off, but thought that was not a good idea so I waited a while. Eventually, whatever it was got sorted out and chkdsk started to run. My best guess is that the attempt to install the update and the request to run chkdsk were in contention. Chkdsk quickly went to 10%, which I have seen before, and remained there for at least a few hours; the next thing that I saw was the lock screen, so I assume that chkdsk had finished.

    3. After the startup finished, I twice ran dism /online /cleanup-image /restorehealth. Both times, it failed, with notification as to where the log could be found. The log is very long, very complex, and I did not even try to understand the entries, but did find this:

    Host machine information: OS Version=10.0.16299, Running architecture=amd64, Number of processors=8
    2017-12-14 18:07:06, Error DISM DISM.EXE: Failed validating command line: "C:\Windows\system32\Dism.exe" /online
    2017-12-14 18:07:06, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

    After the second failure, I decided to throw myself on the mercy of the court and/or on your amazing patience, and ask your advice as to what I ought to do next. I did not run the fourth item in your list, to again run Windows Updates troubleshooter.
    For not finding any integrity violations after running sfc /scannow is a good sign.
    When running chkdsk it is normal that it stays at 10% or 11% until it is over. Mine always stays at 11%. I don't really know the reason for that. The thing about chkdsk is that when it has finished, one never sees the results to know whether or not there was a problem. But there is a way to find the results:

    https://askleo.com/how_do_i_see_the_...t_ran_on_boot/

    Now, with regard to dism.exe failure, all I can see from what you wrote is probably the command line was not written properly. That's my guess since I am not tech-savvy enough when it comes to Windows Kernel and the way it works. Maybe you should try it again and making sure that is written in a Command Prompt (Admin) with respect for the space between each command:
    dism.exe /online/ cleanup-image /restorehealth.

    I don't doubt that you know how to do it, but sometimes with all the frustrations a typo can usually make the difference.

    Last thing I would like to know is whether or not you have tried to delete everything in the Software Distribution folder instead of only the Download folder, rerun the Windows Update troubleshooter, and recheck Windows updates as suggested in my last post. If after that, things are still not working, I would suggest a repair install (It seems that you have tried it already and it couldn't work according to your previous posts)

    I really wish you could resolve this issue before going nuclear with a refresh or reset.
      My ComputerSystem Spec

  4.    16 Dec 2017 #63

    I love this blog statement! The issue was that MS had not ACTUALLY implemented the standard touch keyboard for all but a few languages (was recently fixed in Insider versions).



    • Addresses issue where the touch keyboard doesnít support the standard layout for 88 languages.


    Edit - just found a bug with Edge and standard touch keyboard - F12 does not invoke developer mode yet it works fine on Chrome.
      My ComputerSystem Spec

  5.    16 Dec 2017 #64

    I got a notification that an update failed to install.

    I checked the update screen and it showed several installed correctly on December 12th, but 4054517 "failed to install".

    I forced an update check. "Your computer is fully up to date" (or something similar).

    I manually downloaded the 510mb file from microsoft's update catalogue and then ran it: "This update is already installed".

    I then checked my OS build version: 16299.125

    That build version is the correct, updated, version which KB4054517 installs. I'm puzzled why my computer had a message that it failed to install but it had installed.

    All solved, but wanted to toss more information out there.
      My ComputerSystem Spec

  6.    16 Dec 2017 #65

    IronZorg89 said: View Post
    Now, with regard to dism.exe failure, all I can see from what you wrote is probably the command line was not written properly. That's my guess since I am not tech-savvy enough when it comes to Windows Kernel and the way it works. Maybe you should try it again and making sure that is written in a Command Prompt (Admin) with respect for the space between each command:
    dism.exe /online/ cleanup-image /restorehealth.

    I don't doubt that you know how to do it, but sometimes with all the frustrations a typo can usually make the difference.
    Ironically, the DISM that you posted won't work, as it has to be /online /cleanup-image /restorehealth. I had been running dism properly, as shown by the lengthy log, with the failures being shown at the end of each session in the log. In addition, earlier today, I tried at least of two the dism options in the ResetWUENG.cmd script, which failed for reasons other than when trying the code in this paragraph.

    Before I did that, I ran Option 2, "Resets the Windows Update Components." That did all sorts of things, one of which I wish it had done, namely remove the block I had on the KB, so that Windows Update would keep giving more problems.

    Last thing I would like to know is whether or not you have tried to delete everything in the Software Distribution folder instead of only the Download folder, rerun the Windows Update troubleshooter, and recheck Windows updates as suggested in my last post. If after that, things are still not working, I would suggest a repair install (It seems that you have tried it already and it couldn't work according to your previous posts)

    I really wish you could resolve this issue before going nuclear with a refresh or reset.
    Just before posting this, I managed to delete everything in the Software Distribution folder, which, has become the normal, was not easy. The first problem was that something could not be deleted as it was active in one of the services (name already forgotten,) which would not complete the stop process, so I had to reboot to get that done. Then another service had to be stopped, and a third, but now the folder is empty, and the KB block has been reestablished.

    I then once more ran the Windows Update troubleshooter, which had at least once or twice cleaned up the database, but was failing to do so the last few times I tried; it is now restored.

    Given that dism.exe will not work, I am loathe to try updating yet again. This is based entirely on my complete lack of knowledge or information as to why it won't work, and, thus, what might be wrong with Windows 10, things that might still prevent a successful update.

    I have a Macrium Reflect full backup which was created the Monday before the KB was issued, and I have a System Restore Point dated 07Dec2017. 9 (There are a few later ones, that apparently were created on 12Dec when I first tried to update, and on 12DEc and 15Dec for "Windows Module Installer," whatever that means.

    In sum, I seem to have three possible ways of fixing this before applying drastic measures. Oh, hold on, I just scrolled up and saw that you suggested trying a repair install again. I don't see how, even if it were to fail, that it could make matters worse, so I will do that after finding and restarting the services I had to stop as they might interfere with the ISO attempt.

    However, as the adage has it in my version, "Multiple times bitten, multiple times shy," so before I do anything about the KB problem, I am once again going to wait for advice; as far as I have seen since the KB fiasco started, everything else is working correctly, although I've not tried many programs, so waiting is not likely to cause any further consternation.

    ===
    A few minutes later: There are no services stopped, but the Software Distribution folder, that I fought with to empty is now again full. I suspect that that was caused by my running the Windows Update troubleshooter to fix the database. If so, I am apparently stuck in a moebius strip conundrum.

    ===
    Continuing My Flailing

    Two other possibilities:

    1. I have the KB downloaded directly from MS, and wonder what might happen were I to run it; any ideas?

    2. Having had my weekly Macrium Reflect full-disk backup fail twice on the Monday after the KB release, I started a support ticket, which eventuated in a link to a Macrium troubleshooting procedure. I finally got to that yesterday, only to find that it is for version 4 and 5/6, while I have 7. I am waiting for a reply to my question as to how to proceed. I wonder if, once I run the procedure, which I am fairly certain creates a log, and were I to submit it to Macrium, if they might see something on my computer that not only caused the backup failures but might also be related to the update failures. Perhaps it would be a good idea for me to wait for this to take place before I try any of my other techniques as listed above in this conglomerated what ever it is?
    Last edited by Not Myself; 16 Dec 2017 at 15:29.
      My ComputerSystem Spec

  7. storageman's Avatar
    Posts : 428
    Windows 10 Pro 1803 17134.137
       16 Dec 2017 #66

    I have to laugh looking at all of the issues people. We should never have to worry, MS will have another CU available in a short period of time. W10 is a work in progress and will continue on this course for the next (n) years. !!!
      My ComputersSystem Spec

  8.    16 Dec 2017 #67

    my desktop updated yesterday when i left it running and went outside and came back to find i had to log in again.
    thought it strange as normally doesn't do that till i looked on here and saw update.
    did a sfc /scannow which came back saying a few corrupt file have been fixed so rescanned it and came back clean.
    so far everything seams to be working.
      My ComputerSystem Spec


  9. Posts : 57
    Windows 10 Home 64-bit (1803)
       16 Dec 2017 #68

    Not Myself said: View Post
    Ironically, the DISM that you posted won't work, as it has to be /online /cleanup-image /restorehealth. I had been running dism properly, as shown by the lengthy log, with the failures being shown at the end of each session in the log. In addition, earlier today, I tried at least of two the dism options in the ResetWUENG.cmd script, which failed for reasons other than when trying the code in this paragraph.

    Before I did that, I ran Option 2, "Resets the Windows Update Components." That did all sorts of things, one of which I wish it had done, namely remove the block I had on the KB, so that Windows Update would keep giving more problems.



    Just before posting this, I managed to delete everything in the Software Distribution folder, which, has become the normal, was not easy. The first problem was that something could not be deleted as it was active in one of the services (name already forgotten,) which would not complete the stop process, so I had to reboot to get that done. Then another service had to be stopped, and a third, but now the folder is empty, and the KB block has been reestablished.

    I then once more ran the Windows Update troubleshooter, which had at least once or twice cleaned up the database, but was failing to do so the last few times I tried; it is now restored.

    Given that dism.exe will not work, I am loathe to try updating yet again. This is based entirely on my complete lack of knowledge or information as to why it won't work, and, thus, what might be wrong with Windows 10, things that might still prevent a successful update.

    I have a Macrium Reflect full backup which was created the Monday before the KB was issued, and I have a System Restore Point dated 07Dec2017. 9 (There are a few later ones, that apparently were created on 12Dec when I first tried to update, and on 12DEc and 15Dec for "Windows Module Installer," whatever that means.

    In sum, I seem to have three possible ways of fixing this before applying drastic measures. Oh, hold on, I just scrolled up and saw that you suggested trying a repair install again. I don't see how, even if it were to fail, that it could make matters worse, so I will do that after finding and restarting the services I had to stop as they might interfere with the ISO attempt.

    However, as the adage has it in my version, "Multiple times bitten, multiple times shy," so before I do anything about the KB problem, I am once again going to wait for advice; as far as I have seen since the KB fiasco started, everything else is working correctly, although I've not tried many programs, so waiting is not likely to cause any further consternation.

    ===
    A few minutes later: There are no services stopped, but the Software Distribution folder, that I fought with to empty is now again full. I suspect that that was caused by my running the Windows Update troubleshooter to fix the database. If so, I am apparently stuck in a moebius strip conundrum.

    ===
    Continuing My Flailing

    Two other possibilities:

    1. I have the KB downloaded directly from MS, and wonder what might happen were I to run it; any ideas?

    2. Having had my weekly Macrium Reflect full-disk backup fail twice on the Monday after the KB release, I started a support ticket, which eventuated in a link to a Macrium troubleshooting procedure. I finally got to that yesterday, only to find that it is for version 4 and 5/6, while I have 7. I am waiting for a reply to my question as to how to proceed. I wonder if, once I run the procedure, which I am fairly certain creates a log, and were I to submit it to Macrium, if they might see something on my computer that not only caused the backup failures but might also be related to the update failures. Perhaps it would be a good idea for me to wait for this to take place before I try any of my other techniques as listed above in this conglomerated what ever it is?
    I donít know how to fix your problem. I can only say what I would try on my own system if I were in a similar situation. First, I would determine the last time Windows Update applied an update successfully. Then, beginning with that date, I would check the Event Viewer logs and the Reliability History, looking for errors that may indicate when the problem started. If I found something, I would restore the Macrium Reflect image that I took prior to that date and try the update again. If I didnít find anything in the logs, then I would restore the Macrium Reflect image that I took prior to the last successful windows update. Then I would let the latest Windows update install again. The update itself would be different this time because it would include two updates and could possibly produce a different result. Incidentally, I always back up my personal data before I restore an image. I also make sure my rescue media works. Again, this isnít a recommendation. Iím just saying what additional steps I would try on my own system in a similar situation before resorting to a complete Windows 10 reinstall.
    Last edited by radiowaves; 16 Dec 2017 at 21:19.
      My ComputerSystem Spec

  10.    17 Dec 2017 #69

    Ironically, the DISM that you posted won't work, as it has to be /online /cleanup-image /restorehealth. I had been running dism properly, as shown by the lengthy log, with the failures being shown at the end of each session in the log. In addition, earlier today, I tried at least of two the dism options in the ResetWUENG.cmd script, which failed for reasons other than when trying the code in this paragraph.

    Before I did that, I ran Option 2, "Resets the Windows Update Components." That did all sorts of things, one of which I wish it had done, namely remove the block I had on the KB, so that Windows Update would keep giving more problems.



    Just before posting this, I managed to delete everything in the Software Distribution folder, which, has become the normal, was not easy. The first problem was that something could not be deleted as it was active in one of the services (name already forgotten,) which would not complete the stop process, so I had to reboot to get that done. Then another service had to be stopped, and a third, but now the folder is empty, and the KB block has been reestablished.

    I then once more ran the Windows Update troubleshooter, which had at least once or twice cleaned up the database, but was failing to do so the last few times I tried; it is now restored.

    Given that dism.exe will not work, I am loathe to try updating yet again. This is based entirely on my complete lack of knowledge or information as to why it won't work, and, thus, what might be wrong with Windows 10, things that might still prevent a successful update.

    I have a Macrium Reflect full backup which was created the Monday before the KB was issued, and I have a System Restore Point dated 07Dec2017. 9 (There are a few later ones, that apparently were created on 12Dec when I first tried to update, and on 12DEc and 15Dec for "Windows Module Installer," whatever that means.

    In sum, I seem to have three possible ways of fixing this before applying drastic measures. Oh, hold on, I just scrolled up and saw that you suggested trying a repair install again. I don't see how, even if it were to fail, that it could make matters worse, so I will do that after finding and restarting the services I had to stop as they might interfere with the ISO attempt.

    However, as the adage has it in my version, "Multiple times bitten, multiple times shy," so before I do anything about the KB problem, I am once again going to wait for advice; as far as I have seen since the KB fiasco started, everything else is working correctly, although I've not tried many programs, so waiting is not likely to cause any further consternation.

    ===
    A few minutes later: There are no services stopped, but the Software Distribution folder, that I fought with to empty is now again full. I suspect that that was caused by my running the Windows Update troubleshooter to fix the database. If so, I am apparently stuck in a moebius strip conundrum.

    ===
    Continuing My Flailing

    Two other possibilities:

    Not Myself said: View Post
    1. I have the KB downloaded directly from MS, and wonder what might happen were I to run it; any ideas?

    2. Having had my weekly Macrium Reflect full-disk backup fail twice on the Monday after the KB release, I started a support ticket, which eventuated in a link to a Macrium troubleshooting procedure. I finally got to that yesterday, only to find that it is for version 4 and 5/6, while I have 7. I am waiting for a reply to my question as to how to proceed. I wonder if, once I run the procedure, which I am fairly certain creates a log, and were I to submit it to Macrium, if they might see something on my computer that not only caused the backup failures but might also be related to the update failures. Perhaps it would be a good idea for me to wait for this to take place before I try any of my other techniques as listed above in this conglomerated what ever it is?
    One thing for sure is that your Windows update database is corrupted and that can be one of the reasons why dism.exe is failing. Normally the tutorial on "How to reset Windows update in Windows 10" (link is in the post #57) should be able to fix the issue. I don't understand why it cannot work in your case. Something else is preventing your machine from installing the updates normally. Can you check your system for malware or virus by running adwCleaner or your anti-virus program:

    https://toolslib.net/downloads/viewd.../1-adwcleaner/


    With regard to the KB you have downloaded from Microsoft Update Catalog, you can always try to install it. The worst that can happen it will roll back if it cannot install. Or, it can get stuck in which case you could run the Windows Update Troubleshooter while it is stuck instead of shutting down or rebooting your machine.

    A couple of questions I have for your:
    1) Have you tried to see the results of the chkdsk you made by going to EventViewer according to the tutorial (link in post #63)?. That would give you a good idea about whether or not chkdsk has repaired or failed to repair something.
    2) Have you tried to see if your display adapter driver is up-to-date?

    My final suggestions would be to try do the same attempts in SafeMode with Windows Networking or open a new account as Administrator and tried everything again in this new account that you can either keep if things have been fixed or discarded thereafter if things are still not working.
      My ComputerSystem Spec


 
Page 7 of 16 FirstFirst ... 56789 ... 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 13:05.
Find Us