Solved Cannot Complete Installing Updates, or Check for New Updates

[NoelDP]

I've found all the missing files except 4 - which all relate to an update I can find no record of, to do with graphics. Have you installed any hotfix patches??

Here's the 'fix' for the remainder....



I've uploaded a file - quagxx.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
This should create a folder C:\quagxx
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:\quagxx
hit the enter key - if you get a 'Not Found' error try
DIR D:\quagxx
or
DIR E:\quagxx

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

XCOPY <drive>:\quagxx <drive>:\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 SkyDrive Public folder, and post a new link

 

[QuagsireQing]

https://skydrive.live.com/redir?resid=E4C3B3CFA85B2D3D!229

 

[tom982]

Hello QuagsireQing,

In order to find where those remaining 4 files came from, we need a bit more information. Would you mind uploading this file to your Skydrive for me please?

C:\Windows\system32\config\COMPONENTS (it has no file extension)

Tom

Edit: Temporarily posting this: kb2454826

 

[NoelDP]

Good - SFC completed without throwing any fits (although it's still doing a lot in the background, and generating a lot of errors)
Please now run the CheckSUR tool again, and post the new report.

 

[QuagsireQing]

Components for Tom:
https://skydrive.live.com/redir?resid=E4C3B3CFA85B2D3D!230

CheckSUR log for Noel:

 

[NoelDP]

I'll leave this for Tom -

The CheckSUR shows the following files missing....

Checking Component Store
(f) CSI Payload File Missing 0x00000000 cdd.dll x86_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.20830_none_ac59a14f5dd9e4eb 
(f) CSI Payload File Missing 0x00000000 dxgkrnl.sys x86_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.20830_none_ac59a14f5dd9e4eb 
(f) CSI Payload File Missing 0x00000000 dxgmms1.sys x86_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.20830_none_ac59a14f5dd9e4eb 
(f) CSI Payload File Missing 0x00000000 dxgmms1.sys x86_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.16699_none_ab9825b044e4d3af

 

[tom982]

Those files have completely stumped me! They traced back to KB2454826, yet when I download and extract the files from KB2454826, none of them have a 6.1.7600.20830 version number It is a v2 update, so I'm guessing the files were from the original, which I can't find anywhere other than on torrent websites, and god knows what's been embedded in those files.

The MS download link is dead, so I think it's a lost cause:

http://download.microsoft.com/download/5/E/4/5E404378-9A5D-41AB-AFBA-1AC04F3B2A13/Windows6.1-KB2454826-x86.msu

I think the only way forward would be to do a repair install I'm afraid

http://www.sevenforums.com/tutorials/3413-repair-install.html

Tom

 

[QuagsireQing]

Part of me says, "Just buy a new computer, yours has been on life support for years," and part of me says, "If you're doing an install, why not jump straight into 8?" But this repair install looks like such a quick and simple fix, that even if I were to rebuild my PC or upgrade my OS, I may as well do this for now. If the only difference I'll notice after doing the install is that some device drivers need to be reinstalled, I'll do it in a couple days. (I just did a full file backup last Tuesday.)

 

[NoelDP]

It's not so much the drivers that are likely to need re-updating, - but all the Updates since SP1 will need to be reinstalled.
Take them in batches - I tend to leave all the .NET ones until last, and do the Security ones first.
Do batches of no more than 10 at a time (oldest first), and reboot in between batches at least twice to make sure that everything is properly bedded-in.
Why leave the .NET until last? - they are the most likely to cause problems - so do them no more than 5 at a time, and expect one or two to fail (usually because they are expecting file versions that don't yet exist) but they will usually install on the second or third attempt.

 

[QuagsireQing]

Of course the repair couldn't just go smoothly. It hung at "Gathering files 20%" for nearly two hours before moving on (the entire "gathering files" stage took nearly four hours) and now it's been stuck on "Transferring files 72% (642297 of 642471)" for at least six hours. (It isn't frozen, it just doesn't appear to be progressing, unless it's actually making some secret progress.) All told, I started the upgrade over fourteen hours ago. What should I do at this point?

 

[NoelDP]

Ouch!
That does sound as if it's stalled
The following article may help Solution to Windows 7 Installation Hang at 62% or 72% during Upgrade from Vista
It's written for a Vista>Win7 upgrade, but should still apply for a repair install

 

[QuagsireQing]

I can barely believe it, but I've somehow regained my desktop. Interrupting the stalled installation resulted in an endless loop of Windows 7 setup screens that reported the error and recommended a restart, but a simple adjustment in the regedit persuaded the system to "prepare my desktop for the first time," as if the install had succeeded. Once at the desktop, it took a repair of the .NET framework to be able to be able to activate Windows, but I seem to have an operational machine again. I'll try doing updates and report back with the results.

UPDATE: Checking for updates has been successful so far. In the meantime, one of the final steps in the repair install walkthrough Tom provided was to use Disk Cleanup to remove the C:\Windows.old, C:\$INPLACE.~TR and C:\WINDOWS.~Q folders. When I ran Disk Cleanup, it didn't detect any leftover installation files to delete (presumably because of the way the installation wound up finishing), so C:\$INPLACE.~TR and C:\WINDOWS.~Q are still there (C:\Windows.old doesn't exist), and are accompanied by C:\$UPGRADE.~OS and C:\$WINDOWS.~LS. Is it safe for me to delete those folders manually?

 

[QuagsireQing]

Just a quick bump to confirm that last question in the update of my last post.

 

[NoelDP]

There shouldn't be a problem in manually deleting those folders/files

 

[QuagsireQing]

Alright, then, thanks to all your help, I'll mark this case...solved!