New
#11
Here's another try:
Ah, I see I finally got WZ7 to work. Had to add associate wz7 with *.zip
Here's another try:
Ah, I see I finally got WZ7 to work. Had to add associate wz7 with *.zip
Well done!
(If you'd followed the instructions as posted, they should have worked first time. Windows has a very effective built-in compression ability.... back to topic!)
The critical error appears to be this...
This could mean a number of things - one of which is that there's no space on the disk for the install. It requires at least 1.5GB free disk space.Code:04/20/15 18:31:14 DDSet_Status: Reserving disk space by 15782880 in %windir% 04/20/15 18:31:14 DDSet_Warning: MsiViewExecute failed .
one other thing could be a corrupt registry.
Please open an Elevated Command Prompt, and run the following commands
REG QUERY HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msiserver
REG QUERY HKLM\Software\Microsoft\Windows\CurrentVersion\Installer
Post the results,
Then do a full reset of Windows Update - see here https://support.microsoft.com/en-gb/kb/971058
please don't try installing the update until I get a look at the results of the registry checks.
OK, here's the report on the two reg files you asked for. I also then ran the windows reset update. Interestingly, initial report showed several problems that were Fixed; however, the following was reported as Not Fixed: Windows update error: 0x80070057(2015-04-21-T-12_13_37P). But when I selected View Detail Info, the error was reported as Fixed???
The registry output looks normal to me.
How is WIndows Update functioning now?
Do a Check for Updates, then try installing ONLY the oldest found update - post the error message (if any) and the new C:\Windows\windowsupdate.log file
Hate to say this, Noel, but things aren't getting any better. I didn't really understand doing "Only the oldest update," so when I did Check for Updates, 4 new option updates were downloaded and I tried installing one of them. This was a failure with the error code 800F0104.However, I did run the Diagnostics Troubleshooting Wizard that was able to fix most problems, but again it first showed that 0x80070057(2015-04-21-T-5_20_45P) couldn't be fixed and View Details then showed that this was fixed??? Here are some shots of the Diagnostics report. The W7Transfer was also listed in the Wizard and refers to something about Windows transferring...I don't remember, but hope you recognize it.
Last edited by flycaster; 21 Apr 2015 at 17:37.
WinZip7 keeps alerting me that the file is being used by another process and can't be compressed. Probably didn't see this alert when I zipped the file and sent it out. I can't figure out where else this file is being used???
... usually, if the file is in use, you can still copy it elsewhere, and then compress the copy.(max size for the windowsupdate.log file is ~2MB anyhow)
Some interesting results in what you uploaded - but there's just the two obvious patching failures...
I'd hide the NVidia update, and if necessary install updated drivers from the manufacturer's website.Code:Line 12672: 2015-04-21 17:18:55:450 376 161c Report REPORT EVENT: {74B2DCDD-5AD2-44E6-AB96-E76618180EA7} 2015-04-21 17:17:29:293-0400 1 182 101 {7F0C2BAC-713E-43CE-9D51-772DA66E3436} 200 800f0104 AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x800f0104: nVidia - Graphics Adapter WDDM1.1, Other hardware - NVIDIA GeForce 7100 / NVIDIA nForce 630i. Line 13409: 2015-04-21 18:18:02:937 544 8ac Report REPORT EVENT: {B1C9FE5A-0BDD-4DF3-96DA-8654BBD61D28} 2015-04-21 18:17:33:785-0400 1 182 101 {74256EC4-CE5C-46AE-B60F-7BB99C5B0C7D} 200 80070643 AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Microsoft .NET Framework 4.5.2 for Windows 7 x64-based Systems (KB2901983).
If we look at the detail of the .NET install attempt we get
This article and fixit may help.Code:2015-04-21 18:16:10:434 2440 cbc Handler : Updates to install = 1 2015-04-21 18:16:14:726 544 8ac Report REPORT EVENT: {84A43E4B-C579-4EE7-8CC5-5573BE6E4273} 2015-04-21 18:16:09:720-0400 1 181 101 {74256EC4-CE5C-46AE-B60F-7BB99C5B0C7D} 200 0 AutomaticUpdates Success Content Install Installation Started: Windows successfully started the following update: Microsoft .NET Framework 4.5.2 for Windows 7 x64-based Systems (KB2901983) 2015-04-21 18:17:33:783 2440 cbc Handler : WARNING: Command line install completed. Return code = 0x00000643, Result = Failed, Reboot required = false 2015-04-21 18:17:33:784 544 e7c AU >>## RESUMED ## AU: Installing update [UpdateId = {74256EC4-CE5C-46AE-B60F-7BB99C5B0C7D}] 2015-04-21 18:17:33:784 544 e7c AU # WARNING: Install failed, error = 0x80070643 / 0x00000643 2015-04-21 18:17:33:784 2440 cbc Handler : WARNING: Exit code = 0x8024200B 2015-04-21 18:17:33:784 2440 cbc Handler ::::::::: 2015-04-21 18:17:33:784 2440 cbc Handler :: END :: Handler: Command Line Install 2015-04-21 18:17:33:784 2440 cbc Handler ::::::::::::: 2015-04-21 18:17:33:785 544 1050 Agent LogHistory called. idUpdate={74256EC4-CE5C-46AE-B60F-7BB99C5B0C7D}.200, resultMapped=80070643, resultUnMapped=643 2015-04-21 18:17:33:909 544 1050 Agent *********
https://support.microsoft.com/en-us/kb/976982
Followed your suggested help link. Did the Fitit and the recommendation was to fix 4.5.1 (which is onboard) using a MS NET fixer. It didn't work. I was starting to think that my update installer was completely on the fritz because nothing has been updated since 4/15. But then I saw that Windows Defender was updated on 4/21. This was the only update that was successful since 4/15. OK, what happened on 4/15...don't know. Doubt whether I can get back to restore point prior to 4/15 as since I've we've been trying to fix this mess, many, many restore points were done...erasing the previous ones, I believe. Damn, what's next? Anything?
EDIT:
As it seems that 4.5.1 may need some fixing also, and it also seems that I am having problems - in general - with installing updates, I have fears about deleting 4.5.1 and then reinstalling a new 4.5.1...as it may not install. One thought I have around this potential problem is to rename 4.5.1 and then try to install a new 4.5.1. If the new 4.5.1 doesn't install, I can at least bring back the original 4.5.1.
Last edited by flycaster; 24 Apr 2015 at 11:12.