KB 4076492 Fail - Unknown Error

[Thisisaline]

Since I can't edit my last post:

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.

I was concerned that I was remembering the BIOS version instead for some reason so I just went to check the BIOS/UEFI again, and now I'm even more sure that it was the date that was set to sometime in 2012 when I was in there no more than a few week ago, though I had no reason to bother with it at the time.

 

[torchwood]

Hi Aline,
Was celebrating nippers 40'th, sorry bout the delay, the head took longer to return to normal.

Please ensure that the Bios date is correct, check the system date and time zones as well, either being wrong will stop updates.
If you had to change any of them then
REBOOT
try the update again

Im not too hopefull based on your comments about the dll's not registering or being loaded

If it still fails to install, please do the following

1. Download Windows Repair (All-in-One) Portable to your desktop.
http://www.tweaking.com/files/setups...repair_aio.zip


2. Once the file is downloaded, right-click on the file on your desktop and choose Extract All...
3. Keep the defaults and click the Extract button.
4. A folder named tweaking.com_windows_repair_aio will be extracted to the desktop. Once the extraction is complete the folder will open.
5. Inside this folder, there is a folder named Tweaking.com - Windows Repair. Open this folder as well.
6. Double-click on Repair_Windows.exe to open. Note: Please make sure all of your programs are closed and anything you were working on is saved as we will be rebooting.
7. When the program opens, click the Reboot to Safe Mode button at the bottom of the screen. Answer Yes to allow.

8. Once rebooted into Safe Mode, open the program again. When the program opens, click the Repairs tab and click the Open Repairs button.

9. A backup of your registry will be made. After a few moments you will have many options from which you can choose.
10. Please click the Unselect All button and then click to enable only the following ones:

01 - Reset Registry Permissions
02 - Reset File Permissions
03 - Reset Service Permissions
04 - Register System Files
10 - Remove Policies Set By Infection
14 - Remove Temp Files
15 - Repair Proxy Settings
17 - Repair Windows Updates
21 - Repair MSI (Windows Installer)


11. Ensure the Restart check box is selected and click the Start Repairs button in the lower right of the screen. This may take some time to run so be patient.

once complete try updating, if it fails please post the tweaking log


When was the last successfull upate installed.

Roy

 

[Thisisaline]

Hi Aline,
Was celebrating nippers 40'th, sorry bout the delay, the head took longer to return to normal.

No worries mate, happy birthday to him, and it does take a couple days to recover from knocking back the pints, but I knew you'd be back

Please ensure that the Bios date is correct, check the system date and time zones as well, either being wrong will stop updates.
If you had to change any of them then
REBOOT
try the update again

Well the BIOS date is definitely correct now.. and I've checked the system date, time and time zone which are still correct since I started using this pc.

Im not too hopefull based on your comments about the dll's not registering or being loaded

May I ask what you mean by this? Should I restore the saved registry? Do you think I'm probably not going to be able to resolve the issue and that I'll have to reformat the pc and reinstall Windows? I would admit that for a few months since I took over the pc just under a year ago, I used to clear the registry with CCleaner every so often, though I've since, for the past few months, decided it best to go with the advice not to clear the registry if you don't have to. This is the only thing that I think could have broken anything if that is indeed what happened.

I have to hit the hay for now so I'll have to take on the rest of your advised course of action later on.

Thanks again Roy.

 

[Thisisaline]

So after running repair, apart from taking awhile to check for updates, the outcome was the same. I've attached all the logs.

When was the last successfull upate installed.

Resetting Windows Update has cleared my update history, but I can say that a couple of other updates have installed since KB4076492 first tried to install. Otherwise, before then, I would say within the last couple of weeks, no longer.

 

[torchwood]

Hi Aline,

there are some odd exceptions in the logs - unable to access file in use !!! there TEMP files
This could be because of Malware
could also cause certain dll's not to run -(my not to hopefull comment re post#20 para 2)

please run
Malwarebytes free
Eset on line - dissable your current AV during the scan
Farbar - FRST post both logs
Download Farbar Recovery Scan Tool

Roy

 

[Thisisaline]

Hi Roy,

I had already decided to do a scan with Malwarebytes which came out clean. I'll try Eset and Farbar soonest.

Thanks.

 

[JoeSkeeRock]

I have the exact same issue with KB 4076492. I have a dual boot of Win7 Ultimate and on my other Win7 Ultimate, the update installed fine. I can't seem to figure out why it wont install on the other one. It says creating a restore point, then after that it fails. All other updates installed fine. This one has me scratching my head.....

 

[Thisisaline]

So ESET only removed the bundled Google toolbars from CCleaner installers v5.39 and v5.40.

FRST seems to have flagged driver ALSysIO64.sys, but apparently that is a component of Core Temp software which I'm using.

I have the exact same issue with KB 4076492. I have a dual boot of Win7 Ultimate and on my other Win7 Ultimate, the update installed fine. I can't seem to figure out why it wont install on the other one. It says creating a restore point, then after that it fails. All other updates installed fine. This one has me scratching my head.....

I'm sorry you're facing the same problem, but admittedly it's good to know that I'm not the only one facing this issue. Are you getting a Code 2 Unknown Error as well? Do you notice any similarities to my situation - replacing CMOS battery, etc.? Have you tried any of the solutions mentioned e.g. stand-alone package installer?

 

[JoeSkeeRock]

I'm sorry you're facing the same problem, but admittedly it's good to know that I'm not the only one facing this issue. Are you getting a Code 2 Unknown Error as well? Do you notice any similarities to my situation - replacing CMOS battery, etc.? Have you tried any of the solutions mentioned e.g. stand-alone package installer?

Yes code 2 error, but I never replaced CMOS battery or anything like that. I downloaded the update from Microsoft Update catalog and tried to manually install, but got an error "Final Result: Installation failed with error code: (0x80070002), "The system cannot find the file specified. "

 

[Thisisaline]

Doing more searching I found this, (using Google Translate) apparently someone else who failed to install the update, who found a resolution through here, the outcome of which was an update to .NET Framework 4.7.1 here.

The thing is though that the problem as described and resolved is based in 4.7.1, however I am still on 4.7.0.
So I'm wondering if the root cause of my issue is different, or if it is similar and could be resolved by updating .NET Framework to 4.7.1..?

JoeSkeeRock maybe you could check the .NET Framework versions of both your Windows installs

 

[torchwood]

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

 

[Thisisaline]

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.

 

[JoeSkeeRock]

Doing more searching I found this, (using Google Translate) apparently someone else who failed to install the update, who found a resolution through here, the outcome of which was an update to .NET Framework 4.7.1 here.

The thing is though that the problem as described and resolved is based in 4.7.1, however I am still on 4.7.0.
So I'm wondering if the root cause of my issue is different, or if it is similar and could be resolved by updating .NET Framework to 4.7.1..?

JoeSkeeRock maybe you could check the .NET Framework versions of both your Windows installs

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-framework-setup-verification-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!!

 

[Thisisaline]

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!