New
#31
Hi Aline,
from CCleaner can you run the Registry scan tool post the logs
If it reports 12 missing were getting there
Would also like to see the results from Farbar, FRST
Roy
Hi Aline,
from CCleaner can you run the Registry scan tool post the logs
If it reports 12 missing were getting there
Would also like to see the results from Farbar, FRST
Roy
Yes I had remembered that I forgot to attach the FRST logs. See attached.
In the meantime I tried to install .NET Framework 4.7.1 which only gave me the option to repair. As far as I can tell, it was updated correctly. That alone didn't resolve the issue so I tried installing KB4054856 which I previously referred to and which supposedly worked for that guy, but that didn't work either.
CCleaner found about two dozen Installer Reference Issues related to .NET Framework. I'm not sure if that's along the lines of what you're referring to about 12 missing. Log attached.
Thanks.
Last edited by Thisisaline; 21 Feb 2018 at 08:42.
Thisisaline thank you for the links. I was able to fix the issue on my system. It seems somehow that my .Net Framework 7.1 became corrupted. I also use CCleaner, but I also use Glarysoft registry repair and I am thinking that maybe some entries were removed that caused this. I did the following steps to fix the issue:
1. I went to .NET Framework Cleanup Tool Users WebLog and downloaded the .NET Framework cleanup tool.
2. I created a restore point, then I ran the tool and uninstalled Net Framework 4.7.1, then skipped the reboot and uninstalled Net Framework 4.7, then rebooted.
3. I went again to .NET Framework Cleanup Tool Users WebLog and scrolled down and downloaded the standalone Net Framework 4.7 & 4.7.1 using the links.
4. I then installed 4.7, then installed 4.7.1 and rebooted.
6. I then ran Windows Update and this time the update (KB 4076492) worked without failing.
5. I then went to http://www.thewindowsclub.com/net-fr...ification-tool and downloaded the .NET Framework Setup Verification Tool
6. I ran the tool and verified that all versions of Net Framework are working correctly.
I hope this works for others with a similar issue, but just because it worked for me is no guarantee that it will work for you.
Good luck and thanks again!!
@JoeSkeeRock Glorious, it worked for me too! Thanks a lot for the instructions.
@torchwood So now that Windows Update works, do I still need to be concerned about the apparent IIS failure, the dlls not registering or loading, and log exceptions re the access of TEMP files? Would the IIS failure or dlls have been fixed along with Windows Update? If not, would Windows automatically fix them? Since the scans didn't uncover anything, can I presume the TEMP file exceptions are down to normal processes? Basically, is there anything else I should need to be doing from this point or can I resume normal use?
Thanks!