Solved windows 7 update not working

[NoelDP]

...it means I goofed!

I've uploaded a new copy of the cjdac.zip file with the proper structure - try the whole procedure again.

(it's what comes of doing this before finishing the first cup of coffee of the day!)

 

[catchjudo]

Thanks NoelDP, ok this time have attached the CBS log file.

 

[NoelDP]

I must be losing my touch!...

 Line 14598: 2015-03-03 19:39:10, Info                  CSI    00000359 [SR] Repairing 3 components
 Line 14599: 2015-03-03 19:39:10, Info                  CSI    0000035a [SR] Beginning Verify and Repair transaction
 Line 14602: 2015-03-03 19:39:10, Info                  CSI    0000035c [SR] Cannot repair member file [l:42{21}]"getevent.types.ps1xml" of Microsoft-Windows-PowerShell, Version = 7.1.7601.16398, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 14605: 2015-03-03 19:39:10, Info                  CSI    0000035e [SR] Cannot repair member file [l:58{29}]"PowerShellTrace.format.ps1xml" of Microsoft-Windows-PowerShell, Version = 7.1.7601.16398, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 14608: 2015-03-03 19:39:10, Info                  CSI    00000360 [SR] Cannot repair member file [l:22{11}]"acppage.dll" of Microsoft-Windows-Application-Experience-Tools, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 14611: 2015-03-03 19:39:10, Info                  CSI    00000362 [SR] Cannot repair member file [l:24{12}]"services.msc" of Microsoft-Windows-ServicesSnapIn, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'l check through the details and see if I can work out why those replacements didn't work and get back to you.

 

[NoelDP]

Definitely a case of me losing my touch! - plus one of the patches required is quite obscure...


I've uploaded a file - cjdad.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\cjdad
hit the enter key - if you get a 'Not Found' error try
DIR D:\cjdad
or
DIR E:\cjdad



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\cjdad <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[catchjudo]

thanks NoelDP all done have attached the cbs file

 

[NoelDP]

SFC is clear - are you still having problems with WU?

 

[catchjudo]

Hi NoelDP , windows update is working fine now thanks to your input.

 

[NoelDP]

Great!
Good luck.

 

[ElBanko]

red x on update win 7 pro laptop .

Hi Noel, sorry to continue this old thread BUT your victory heartened me since I have spent 4 full days rebuilding, upgrading from home to pro and testing my Sony VAIO laptop (2009). I have tried many, many things without success.

The last major thing to note is I upgraded Win 7 Home to Win 7 Pro using a custom install. Win 7 Home is now rolled up into windows.old folder. Doing that upgrade resolved other related issues but now I have the big red X on the update page. Whenever I trigger Windows updates it just shows it is searching for updates but never completes and both CPU and memory creep into extreme high usage.

When I did the upgrade it looked all normal UNTIL updates were installed. Updates were several Security updates and a ton of .NET 4 updates. I knew I would have lots of updates since the upgrade disk is a few years old. Anyway, after windows updated the problem with updates returned and persists no matter what I do.

I add that the original Win 7 home problems (can provide more details if needed) started in late June but I was able to continue using the laptop. After upgrading to Win Pro many problems were resolved but a new one arose - the dreaded RED "X" on the update page; updates stopped working; CPU and Memory usage crept up eventually CPU usage shows 68-99% and memory fluctuates from 80-100%.

Soon as I stop Windows update service they both return to normal (about 2-5% for CPU at idle and memory about 20% - (seen using Gadget meters).

I went to your above referenced site to locate your zip file but it seems to not be there now so I write you asking for mercy and some of your time to help resolve this misery. Pretty please

Just so you know I am a PC Tech. and have pursued at least 20 potential solutions so far. The upgrade came closest to resolution but I remain perplexed as I have run out of options. Thanks for any assistance you may offer.

If we cannot resolve this I am considering buying a retail Win 7 Pro, formatting the disk and doing a clean install - however I fear the problem may return during updates.

Thanks in advance for your time and interest. Larry

 

[NoelDP]

This is unfortunately a common problem at the moment - the good news is simply that you need to give WU time to do its job. Others have found that just leaving the system searching for updates for up to 24 hours (or more) does the trick - and after the first batch of updates, it works much more quickly

 

[ElBanko]

Good to hear from you Noel - will follow your advice

Thanks for the reply. So, let it sit and try for a day and see what happens? Since you have helped others with your magic zip file I will heed your advice - what have I got to lose at this point, right?

Hopefully the old laptop doesn't flame out from overheating as the CPU and Memory stay high. Time will tell.

Best regards,
Larry

 

[ElBanko]

Neal, You are the Man!!

Neal, I did leave it scanning for about 1.5 hours and finally it came through with 222 Important updates and several optional ones. In progress now downloading and installing the Important ones.

I cannot thank you enough. As mentioned I have been like a dog on a bone for going on 5 days with this laptop, upgraded to W10, restored partition image, upgrading to Win 7 Pro, troubleshooting and on and on.

The upgrade to Win 7 Pro (from W7 Home) got me almost home but the updates was the last dragon to slay! I had let it run before for about an hour and never got anything BUT letting it go longer did the trick.

Now I am holding my breath and all updates and reboots will not put it back in the ditch but I wanted to thank you straight away for your confident suggestion ( and all your efforts with prior posters that led me to trust in you).

You are my Hero for the day pal!
Best Regards,
Larry

 

[ElBanko]

Neal, well so much for the good news! :-( SVCHOST or TrustedInstaller continue to hold CPU @ 50%+ and Memory about 60%! The 222 updates largely FAILED but finally I did get a dozen or two Important updates so all Important updates are done for now.

I tried to download and install some Optional updates - let it run for a long while without joy. I then picked a very small Optional update - 168KB and let that run for a long, long while without success. It is a very small update for an external standard mouse.

For now I changed to manual and stopped the Win Update service and everything immediately drops to normal range (CPU @ 2-7% when idle). I changed updates to Sunday @ 0300 and so far the laptop runs normal. Obviously this is a temporary fix.

In your opinion if I buy a Win 7 Pro RETAIL FULL VERSION, wipe the drive and do a clean install will this problem go away? I am ready to do that since everything else (about 90% anyway) is working well and the laptop is responsive so I am convinced this is a software issue. My concern is that if I do that and the problem returns I am out of options and may have to get a new laptop. Know that I support Windows users but for the first time I am thinking Apple may be in my life soon! ARGH&^$@#

 

[NoelDP]

Here's my preferred methodology for installing the 200+ windows Updates in Vista and Win7...

Note - between each of the below batches of updates, reboot at least once, even if the machine auto-rebooted during the updates. After teh update, do a new Check for Updates. Add any remaining updates or failed updates to the next batch.




1) Install all 'Security Update for Windows'
Reboot
Check for Updates
(some will have failed, and some new ones will have appeared)
2) Install the remaining/new 'Security Update for Windows'
Reboot
Check for Updates
3) Install all ordinary 'Update for Windows'
Reboot
Check for Updates
4) install updates for IE8 - but NOT IE 9/10/11
Reboot
Check for Updates
5) install all other updates EXCEPT .NET ones and IE9/10/11
Reboot
Check for Updates
repeat 5 until there's nothing left in the main window except the .NET and IE upgrades

6) Install all Security Updates for .NET - but nothing else
Reboot
Check for Updates
7) Install all other .NET updates
Reboot
Check for Updates
8) Install IE10 if offered - IE11 should wait if it's still an Optional update.
9) Install the IE10 updates, then install IE11 and update that.

 

[NoelDP]

So - please post the C:\Windows\windowsupdate.log file, and I'll see if I can work out what the sticking-point is.

 

[ElBanko]

Windowsupdate.log attached

Thank you for your kind offer.

I'm stunned with this problem. Everything works normal on the laptop now with updates as exception.

I download non-update files at full speed online.

I even attempted to upgrade to Win 10 - the Win 10 file downloaded without issue form the MS Create Media site. It asked what I wanted to - Update This PC - that started but in the next step or two it wants to get updates needed for Win 10 and so I waited and waited but finally gave up and closed it out.

Since my other computers update fine (XP set as retail so I still get updates, Win 8.1, Win 10) and at normal speed. Thus I conclude it indicates either a missing file or a corruption on this laptop only.

Oh, yesterday I downloaded KB947821- a HOTFIX for Win 7 64 updates - it was 559MB that downloaded fine (not from update site) and ran it. From description I expected it to completely replace or repair updater. No joy from that either! ARGH!! SFC, Chkdsk, etc. all ran clean as did virus scan, JRT, TDSS Killer and on and on...

Perhaps you will see something repairable but if not I have identified a source for Win 7 Pro 64 Full Version.

If you need anything else please let me know. Wish I could send you a beer online - haha.

 

[NoelDP]

Hmmm - the wu log is a bit of a mess
Please post the C:\Windows\Logs\CBS\CheckSUR.log file

 

[ElBanko]

Neal, At one point I deleted CBS logs per some site recommendation. I have attached as requested. This may be an "AHA" moment - the deletion of logs was controversial on the help site as some said never do that while others had done it over a year prior with good results. In any event - here it is...

If you review and think this is going to be a long and difficult resolution please know I will have a Win 7 Pro. Retail CD next week and stand ready to wipe and clean install.

If you see a way to repair this that would be great. If not, a clean install should take care of it.

Thanks much for your time and efforts.

 

[NoelDP]

CheckSUR found nothing wrong anyhow

There's nothing wrong with deleting old logs as a rule - but there is almost never any good reason for doing so either, and sometimes it's the old logs which give us the clue/history we need to identify the problem.

I need to have a look at the event logs...
Open Event Viewer
click on the Windows logs entry in the left pane to expand it.
Now click on the Application entry - wait while it loads.
Click on 'File' in the menu bar and select Save...
Save the file as Appevt.evtx
Repeat for the System log
then zip both, and upload them.

 

[ElBanko]

A while back the CBS log was almost 100GB so I had to do something! No idea why it grew so large back then. That was the reason to delete it and allow a new one to be created by Windows.

Anyway, I hope I did this correctly for you - two zip files (made with 7zip). 7Zip uses 7z as extension and I changed that to .zip.

Cheers