New
#11
Sorry Roy, my bad. CBS log attached.
Thanks again.
Sorry Roy, my bad. CBS log attached.
Thanks again.
Hi Aline,
stranger and stranger
Both logs are clean,
there is a prerequisite for this KB, check for KB4019990 please
can you try the stand-alone package installers for both
REBOOT between them please
silly question is it being offered
Roy
Ah, that must be to do with the required d3dcompiler_47.dll. I must admit that I had earlier wondered if the issue had something to do with it, but with troubleshooting not too far along, I wasn't yet prepared to make that conclusion or ask about it.
As it turns out though, according to the update history, KB4019990 was not installed. I suppose I'll try to install it like you suggest.
I'm not sure I get your question 'is it being offered?' but KB4019990 is NOT listed as an available update, but KB4076492 is.
Thanks Roy.
Ok, so even though I can't find KB4019990 in the Windows Update history, when I try the stand-alone package installer, it says it is already installed.
So I tried the stand-alone package installer for KB4076492 and what I got was:-
KB4054998: Already Installed
msiregpatchfix: Image 1
KB4054981: Image 2, KB4054981_Log attached below
KB4019990: Already Installed as above
KB4054992: Image 3
Thanks.
Hi Aline,
can you try the NF repair tool,
Download Microsoft .NET Framework Repair Tool from Official Microsoft Download Center
Roy
Hmmmm
the 1st capture showed as an IIS failure - DONT know why
according to your specs your running Home premium like me
whats showing here - see screenshot
Roy
Admittedly this is pushing the boundaries of my understanding.
NF repair tool reregistered and restarted Windows Installer service but the error persisted so it just submitted a bunch of logs to Microsoft for analysis.
NF Windows Feature is the same as yours, IIS unchecked, see attached.
Thanks
Last edited by Thisisaline; 17 Feb 2018 at 15:21.
I had posted the same query on the Microsoft Community forum at the same time as I did here. I've just noticed that a mod responded a few hours ago. I've attached the response. I'll have to give it a go later on, need to hit the sack for now. Maybe you can let me know what you think in the meantime if you see this.
Thanks Roy.
So I tried disabling my AV and a clean boot but it didn't help either.
The only options I have in mind next are resetting the Windows Update components manually and trying to create a restore point manually and seeing what happens.
I'll wait for advice.
Thank you.
So I did more searching and found this post about an issue that's the most similar, though not identical, to mine that I've found so far - failed windows updates after replacing CMOS battery. The user was able to resolve the issue after resetting Windows Update twice, though it is unclear why it only worked after the second try. Since I had not received any further feedback over the past couple of days, based on this I decided to proceed to try to reset Windows Update. However the method to do so linked from the thread uses a script and is only based on another post by the community mod - there is no dedicated support page and write up for this method that I could find. So I decided to follow the method on this page which I previously alluded to in my original post and my previous post as well.
When reregistering the BITS files, some loaded with the message that the entry-point DIIRegisterServer was not found, while some failed to load. I'm not sure how much of an issue this is. I backed up my registry so I am wondering if I should restore it. (If it works that is. The last time I tried to restore my registry, it didn't work. However I knew what changes I had made previously so just had to undo it manually.)
When I tried to run Windows Update again, the notable difference was that unlike all the previous attempts except the first, it started 'afresh', in that it started by downloading the update again. I thought that I may have got it working again, but once again, when it got to creating a restore point, it failed.
Based on what happened, I'm more convinced now, though still far from certain, that resetting the CMOS battery has messed up the process of creating a restore point. In fact, expanding on what I already said about resetting the date and time in BIOS/UEFI, this pc was a friend's pc that I took over, and when I previously went into the BIOS/UEFI, I vaguely remember that the date/time may have been wrong, though I can't remember for certain.
With that said, I keenly await any further advice.
Thank you.