Windows 10: Cumulative Update KB4054517 Windows 10 v1709 Build 16299.125

I disagree. Look at my screenshot above (post #72) - it's Chkdsk in the Source column, not Wininit

 

I disagree. Look at my screenshot above (post #72) - it's Chkdsk in the Source column, not Wininit Now I see your point. So, you are right about saying it is different. I have just learned something new. Thanks! *Smile

 

A quick reply, as I'm just not into much serious computing today; the NY and LA Times Sunday Crossword puzzles are more interesting.

1. There does not appear to be any Event View entry for chkdsk. I did a Custom View, entered that code, and got a zero reply. I note that I posted about my having run chkdsk /r the morning of 15Dec . and I am rather certain that I ran chkdsk the previous evening. I went through the Event Viewer for that time span, never saw a chkdsk entry.

Why that should be, I have not the slightest idea.

2. Also, I believe that I have run the Windows Update Troubleshooter at least ten to twelve times; sometimes it has worked, other times not. It did indicate that it was okay earlier today, after I got rid of the supposedly-blocked KB. Curiously, there was a second KB shown as ready to install today, one I've never seen before, and which did not appear in the .cab used to block individual updates.

However, even after I had successfully run the troubleshooter, it soon enough has again indicated that the database is again corrupt. I don't have any specific idea as to when that happens, nor what might have triggered it.

 

It is not for "chkdsk" you have to look for but "Wininit" under the Source column in the Application log of the EventViewer interface. Have a second look at the tutorial

You haven't mentioned the KB number. There was a new KB4058043 (out of band update) that I have installed just this morning. I don't know if it is the one you are talking about

That's a fact. Your Windows Update database is corrupted. What I don't understand is that you have run successfully the Windows Update troubleshooter and then again it got corrupted. That's a bit weird. Things that I really would like to know are:
- the build version you are at right now after putting "Winver" in the run box (Windows key + R)
- the results of you chkdsk
I have also made some suggestions in the last paragraph of my post # 70 to which I would add:
Open an elevated command prompt and run the following commands one after the other:

- Dism.exe /online /Cleanup-Image /StartComponentCleanup

- Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

After that, restart your PC and open again an elevated command prompt and run:

- Dism.exe /online /Cleanup-Image /RestoreHealth

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.

 

Another message said to look for chkdsk, not winit, but I looked for both, found none. I think that I will run chkdsk /r this evening, so that I ought to be able to find any entry in the Event Viewer.

I don't know: As I had an unwelcome download of 17, along with another, I went into Software Distribution, where there was only one entry, which I deleted. Opened the .cab I use to block updates, which only offered 17. I will likely see the newer one next time I run an update search.

Version 1709, OS Build 16299.64

I have run many dism attempts, not a single one works. I know I tried all of the your original suggestions, have likely tried the two new ones, will see if they will run.

My daily Macrium non-full backup works; did so at 0900 this date. We return you now to trying to solve today's NY Times crossword puzzle, as I have many cross words to share over this horribly confusing, frustrating, time-consuming computer puzzle.

Ran the first of the two dism links above, which (as expected) failed. For your entertainment, I have attached the log of that session; perhaps you can figure out why dism fails.

 

@Not Myself

Just "FYI" That was my message about the Event Viewer (Post #72)

I usually run chkdsk from the GUI thus:




But whether I do that or run it from an elevated command prompt (not a regular one), I still get the Application Event I referred to in #72. The detail varies as to whether I run chkdsk or chkdsk /r but I always get the Application Event and have as far back as I can recall

 

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

 

Just DO IT! It worked for me!
Link here: KB4051963 t install after restart. - Microsoft Community

 

@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. *092

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. *Sleepy That would at least confirm that the event is being logged.

 

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.

*Arrow 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.

 

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. *Smile

 

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)