Hi All
Download • 2017-12 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4054517) I've tried 6 times and still will not download first one ever for me.
I've run Security Norton, Malware, adware etc but still NIL response even re installed windows!!
I`m now totally brain dead from it all.
Xmas wishes to all
Rich
Regarding seeing the results of CHKDSK, rather than the procedure in the above link, I find it easier to just open Event Viewer from a right-click on the Start Button, focus on the Application Log and it will be there as an Informational Event - thus: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/
A quick reply, as I'm just not into much serious computing today; the NY and LA Times Sunday Crossword puzzles are more interesting.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:
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.
Last edited by IronZorg89; 17 Dec 2017 at 14:30.
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.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
Version 1709, OS Build 16299.64That'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 command 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
[
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.
Lastly, maybe it would 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.
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.
Last edited by Not Myself; 17 Dec 2017 at 15:52.
@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.@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
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....
Quote
