Windows Vista SP1: unable to install updates, SP2 or SURT

N

NJamesD

Active member
Joined
Jan 12, 2014
Posts
29
Location
Harrogate, England
Hello,
This is my first post although I have been following the forum for a little while _ I hope those of you who have had exams have done as well as you hoped.

I have a number of issues with installing Windows updates on my PC - I can install Microsoft Office 2010 updates with no problems.

I have 93 updates that will download but will not install. The latest attempt today produced error codes 80080005 and 80070057.

I have tried to download SP2 but cannot install - error code 0x80070246.

I have tried installing SURT. It downloads but then sticks on the box that reads, Initialising installation - done. Installing Hotfix for Windows (KB947821)(Update 1 of 1).

I have also tried the cmd prompt sfc/scannow but this would not complete.

I have attached the CBS zip file to this message.

Regards,
Noel

I would be most grateful for any help you can offer as I have spent months trying to sort this.
 

Attachments

Hello and welcome to Sysnative Forums,

I need to get the SURT logs from you. You say you tried SURT, but it got stuck.

Please try downloading a fresh copy of SURT, ensuring you get the correct version for your operating system. SURT can take over an hour to run in some cases, so please be patient. Give it some time - it can appear to be frozen but actually running.

Stephen
 
Hi Stephen,

Thanks for your prompt reply.
I tried to install SURT again from your site and it installed! I have tried numerous times before without luck so hopefully that's minor progress.

Could you advise me how I can get the SURT logs please.

Thanks,
Noel
 
Hi,

That's great news. The SURT logs can be found in the CBS folder:

Export CBS folder


  1. Click the Start button :startorb: then click Computer.
  2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
  3. Find and double click on the Logs folder.
  4. Right-click on the CBS folder, and select Copy.
  5. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
  6. Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
  7. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created.
  8. Attach this new file to your next post.


Stephen
 
Hi,

For some reason, the SURT logs aren't there.... The CBS folder is the same as before.

Are you sure it installed properly? Please try again (sorry, I know you've tried lots of times, but there's not much else I can advice without the SURT logs).

If SURT runs successfully, then there will be two new logs in the CBS folder - CheckSUR.log and CheckSUR.persist.log.

Stephen
 
Hi Stephen

The checkSUR log and CheckSUR.persist.log are in my CBS folder.

I have tried to attach again.

Sorry, not sure what went wrong.

Noel
 

Attachments

Hi Stephen,
I appreciate that you are really busy so not chasing a detailed response. Just wanted to check that the file I sent last night contains the information you need.

Thanks,
Noel
 
Hi,

SURT ran successfully, but no errors are reported:

Code: 
=================================
Checking System Update Readiness.
Binary Version 6.0.6002.23186
Package Version 22.0
2014-01-21 18:53

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 1047
 No errors detected

Checking CoreOS key for repairing corruptions.
Winner version: 6.0.6001.18000.
Processor architecture: x86.
Check key to be repaired: wcm://Microsoft-Windows-CoreOS?version=6.0.6001.18000&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers\metadata\elements\ComputerName
Recreated value: @_type.
Recreated value: @dataOnly.
Recreated value: @default.
Recreated value: @description.
Recreated value: @displayName.
Recreated value: @handler.
Recreated value: @legacyName.
Recreated value: @legacyType.
Recreated value: @migrate.
Recreated value: @scope.
Recreated value: @xsd:type.

That's either a good or a bad thing, depending on how you look at it :p

I've been skimming through your CBS log, and we have some interesting stuff going on there. All sorts funky things!

I would like to see a fresh log. This will ensure the last thing in the log is the thing I want.

SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.


Stephen
 
Hi Stephen

The process stops at 16% of the verification and will not complete.

I get the following message, "Windows resource protection could not perform the requested operation."

I have had this problem when I have tried to run sfc /scannow before.

Regards,
Noel
 
Eugh... This is gonna be fun! :p


  1. Download SFCFix.exe and save this to your Desktop.
  2. Save any open documents and close all open windows.
  3. Double click on SFCFix.exe to open it.
  4. Follow all on screen instructions and upon completion, a file should be created on your Desktop: SFCFix.txt.
  5. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please.


Stephen
 
No need to keep apologising, you're doing perfect!

That's looking fine. I forgot to ask for the cbs.txt file you made earlier, can you attach that to your next post?

Stephen
 
Sorry, my bad. I didn't make myself clear. When I asked you to do another SFC scan (that stopped at 16%), I then asked you to run a command to create a cbs.txt file on your desktop. Since SFC didn't finish, you understandably didn't run the command. Can you please do the following:

SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 
Perfect, I now have plenty of information.

This is going to be a good learning experience for me, because I've not seen this before. I may have to call in another expert, we shall see.

I have to go for tonight, but I will hopefully have another look tomorrow.

Stephen

Notes
Code: 
2014-01-22 20:49:55, Error                 CSI    00000034@2014/1/22:20:49:55.831 (F) d:\longhorn\base\lstring\lblob.cpp(2217): Error STATUS_ILLEGAL_CHARACTER originated in function RtlTranscodeLBlobs expression: __rv.UcsCharacter != (0xffffffff)
[gle=0x80004005]
2014-01-22 20:50:21, Error                 CSI    00000035 (F) STATUS_ILLEGAL_CHARACTER #891850# from CFileInstaller::CommitChanges(...)[gle=0xd0000161]
2014-01-22 20:50:21, Error                 CSI    00000036 (F) STATUS_ILLEGAL_CHARACTER #891849# from PrimitiveInstaller::CCoordinator::FinalizeChanges(...)[gle=0xd0000161]
2014-01-22 20:59:17, Info                  CBS    Scavenge: Package store indicates there is no component to scavenge, skipping.
 
Hi Stephen
Thank you very much for looking into this for me, it is really appreciated.
I will be around tomorrow evening if you do get chance to have a further look.
Have a good day.

Regards,
Noel
 
Hi Stephen,

When we last communicated you suggested that you might have to call in a fellow expert to look at my issue. I was just wondering if you had yet had the opportunity to do this.

Regards,
Noel
 
Good evening Noel,

I have indeed heard back from another expert. After some discussion, we feel that this issue may stem further than initially thought.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFix.txt, and save this to your Desktop. Ensure that this file is named SFCFix.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.txt.
  5. Drag the file SFCFix.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.


https://www.dropbox.com/s/asnu6btqcorq04u/SFCFix.txt

Stephen
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top