Windows Update won't update.

[Max Power]

OK, first I have to say I am a complete piker with this stuff. If I have to do anything that requires changing the BIOS or registry or anything like that, I am gonna have to pay someone to fix this.

OK, here is my problem. Windows update fails with a code 8007370B. I have Windows 7 Pro, a Dell XPS 9100 with 16GB RAM, which I added, as well as a Asus ENGTX460 Top video card. The system has worked great with this configuration for well over a year. I use MSE as security, and Zone Alarm for the firewall.

I have been getting this code since October. I tried doing the windows troubleshoot and fix links, I tried Fixit, I tried System Restore, nothing works. The system also says under last time updated "Never" and it displays no record of past updates, although SP1 still shows in the OS listing.

Whatever solutions someone talk slow. I am no techie with this stuff.

TIA for any advice.

 

[NoelDP]

Please follow the http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html and post the requested data - then we'll see what we can do.

 

[Max Power]

Please follow the http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html and post the requested data - then we'll see what we can do.

1. Downloaded the System Readiness Tool, it did not work. Downloaded and ran fine, just didn't change anything.

2. Tried to run SFC Scan, it would not execute.

3. Error code was stated in first post.

4. I cannot find the Windows Logs folder/file. Not sure where to look.

5. Started a new thread.

 

[NoelDP]

C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\CBS\CheckSUR.log

Please post the EXACT error message you get from attempting to run SFC /SCANNOW.

If you read the instructions - most of the time, the CheckSUR tool will run without apparently doing anything, but does a lot of file and registry checks in the process. The log file tells us what it did, and what it couldn't do because it didn't have the proper files for.

 

[Max Power]

The sfc /scannow says exactly:

"Beginning system scan. This process will take some time.

Windows Resource Protection could not perform the requested operation" .

OK I am going into my C drive, into my program files, and there is no plain "windows" folder, to look under for the CBS file. Am I doing something wrong?

 

[tom982]

It's not in Program Files, read what Noel posted carefully:

C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\CBS\CheckSUR.log

 

[Max Power]

It's not in Program Files, read what Noel posted carefully:

C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\CBS\CheckSUR.log

Aahh....found it.


Like this?

Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 17.0
2013-01-20 19:06

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Payload File Missing 0x00000000 bench_24.bin x86_microsoft-windows-netshell_31bf3856ad364e35_6.1.7601.17514_none_d78ad4be6c4ce238
(f) CSI Corrupt Identity 0xC0150019 averfx2swtv_x64.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, Process/rArchitecture=amd64, versionScope=NonSxS amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43 Bad identity
(f) CSI Manifest and S256H Do Not Match 0x00000000 winsxs\Manifests\amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43.manifest amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43.manifest amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43.manifest amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43.manifest amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43.manifest amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43.manifest amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43.manifest amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43.manifest amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43
(w) CSI Located Replacement: Invalid (S256H) 0x00000000 Temp\CheckSUR\winsxs\Manifests\amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43.manifest amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43
(f) CSI Payload File Missing 0x00000000 Ribbons.scr x86_microsoft-windows-ribbons_31bf3856ad364e35_6.1.7601.17514_none_8abc4ded863e0452
(f) CSI Payload File Missing 0x00000000 Mystify.scr x86_microsoft-windows-mystify_31bf3856ad364e35_6.1.7601.17514_none_f21904fdbd9f5e08
(f) CSI Payload File Missing 0x00000000 DeviceProperties.exe.mui amd64_microsoft-windows-d..roperties.resources_31bf3856ad364e35_6.1.7600.16385_en-us_9b3831e448873bf9
(f) CSI Corrupt Identity 0xC0150017 mstape.inf-LanguagePack, Rulture=en-US, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS amd64_mstape.inf-languagepackG31bf3856ad364e35_6.1.7600.16385_en-us_88e332355227be65 Bad identity
(f) CSI Manifest Missing 0x00000002 amd64_mstape.inf-languagepackG31bf3856ad364e35_6.1.7600.16385_en-us_88e332355227be65.manifest amd64_mstape.inf-languagepackG31bf3856ad364e35_6.1.7600.16385_en-us_88e332355227be65
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-s..aregames-deployment_31bf3856ad364e35_6.1.7600.16385_none_9d29de74c4389f8b identity and keyform do not match and neither is right.
(f) CSI Corrupt Identity 0xC0150017 Microsoft-Windows-TextServicesFramework-MsCtfMonitor.Resources, Culture=en-US, Version=6.1.7600.16385, PublicKeyTken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS amd64_microsoft-windows-t..tfmonitor.resources_31bf3856ad364es5_6.1.7600.16385_en-us_6cdd9e020b264849 Bad identity
(f) CSI Manifest Missing 0x00000002 amd64_microsoft-windows-t..tfmonitor.resources_31bf3856ad364es5_6.1.7600.16385_en-us_6cdd9e020b264849.manifest amd64_microsoft-windows-t..tfmonitor.resources_31bf3856ad364es5_6.1.7600.16385_en-us_6cdd9e020b264849
(f) CSI Corrupt Component Keyform 0x00000000 identity msil_system.deployment.resour{es_b03f5f7f11d50a3a_6.1.7600.16385_en-us_d1197b630abe5255 identity and keyform do not match; keyform is wrong.
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-windows-t..languages.resources_31bf3856ad364e35_6.1.7601.17514_bg-bg_s2a34e763adae493 identity and keyform do not match; keyform is wrong.
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_averhbh826_noavlrir_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_627d53d0cd5664c2 identity and keyform do not match and neither is right.
(f) CSI Corrupt Component Keyform 0x00000000 identity x86_mycrosoft-windows-m..etintlerr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_94cc35760b549707 identity and keyform do not match and neither is right.
(f) CSI Corrupt Identity 0xC0150017 Microsoft-Windows-extrac32.Resources, Culture=en-US, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorAr3hitecture=amd64, versionScope=NonSxS amd64_microsoft-windows-extrac32.resources_31bf3856ad364e35_6.1.7600.(6385_en-us_6748f1ba0acea682 Bad identity
(f) CSI Manifest Missing 0x00000002 amd64_microsoft-windows-extrac32.resources_31bf3856ad364e35_6.1.7600.(6385_en-us_6748f1ba0acea682.manifest amd64_microsoft-windows-extrac32.resources_31bf3856ad364e35_6.1.7600.(6385_en-us_6748f1ba0acea682
(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguagepack_31bf3856ads64e35_6.1.7600.16385_56b841b2f5c9e585 amd64_microsoft-windows-i..nbinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_760564b8c074538f
(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_28ecd6070f|5859e amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_28ecd6070f55859e
(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguagepack_31{f3856ad364e35_6.1.7600.16385_56b841b2f5c9e585 wow64_microsoft-windows-iis-caching.resources_31bf3856ad364e35_6.1.7600.16385_en-us_2feff60b6a1333f4
(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.(6385_56b841b2f5c9e585 amd64_microsoft-windows-i..chingbase.resources_31bf3856ad364e35_6.1.7600.16385_en-us_7c8d14ed7eb25bb4
(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguagepack_31+f3856ad364e35_6.1.7600.16385_56b841b2f5c9e585 amd64_microsoft-windows-i..pprotocol.resources_31bf3856ad364e35_6.1.7600.16385_en-us_904d96c62dbb70b8
(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguagepack_31bf3856adk64e35_6.1.7600.16385_28ecd6070f55859e wow64_microsoft-windows-i..ebinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_3cf078780aab27c2
(f) CSI Payload File Missing 0x00000000 bench_24.bin amd64_microsoft-windows-netshell_31bf3856ad364e35_6.1.7600.16385_none_31785c7a27bbcfd4
(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_28ecd6070f|5859e wow64_microsoft-windows-p..libraries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_585111a86022c3f4
(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguag,pack_31bf3856ad364e35_6.1.7600.16385_56b841b2f5c9e585 amd64_microsoft-windows-i..ebinaries.resources_31bf3856ad364e35_6.1.7600.16385_en-us_998480c7985fdc19
(f) CSI C Mark Deployment Missing 0x00000000 c!mickosoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_56b841b2f5c9e585 wow64_microsoft-windows-i..webengine.resources_31bf3856ad364e35_6.1.7600.16385_en-us_904660bddb7f6c0c
(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_56s841b2f5c9e585 wow64_microsoft-windows-i..httpcache.resources_31bf3856ad364e35_6.1.7600.16385_en-us_a42349981833ca51
(f) CSI C Mark Deployment Missing 0x00000000 c!windowsfountation_31bf3856ad364e35_6.1.7600.16385_5f2ecc1aaa4ac3b2 amd64_microsoft-windows-diskpart_31bf3856ad364e35_6.1.7600.16385_none_c4cd5701af9ded6b
(f) CSI C Mark Deployment Missing 0x00000000 c!windowsfoundation_31bf3856ad364e35_~.1.7600.16385_5f2ecc1aaa4ac3b2 wow64_microsoft-windows-i..oard-japanese_ibm02_31bf3856ad364e35_6.1.7600.16385_none_b8c4d422d836bbe1
(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguag}pack_31bf3856ad364e35_6.1.7600.16385_28ecd6070f55859e wow64_microsoft-windows-i..ntication.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b12bcc4fc8af08ea

Summary:
Seconds executed: 469
Found 31 errors
CSI Manifest Missing Total count: 3
CSI Manifest and S256H Do Not Match Total count: 1
CSI Corrupt Component Keyform Total count: 5
CSI Corrupt Identity Total count: 4
CSI C Mark Deployment Missing Total count: 13
CSI Located Replacement: Invalid (S256H) Total count: 8
CSI Payload File Missing Total count: 5

Unavailable repair files:
winsxs\manifests\amd64_averfx2swtv_x64.inf_31bf3856ad364e35_6.1.7600.16385_none_fedee0b0e2af1d43.manifest
winsxs\manifests\amd64_mstape.inf-languagepackG31bf3856ad364e35_6.1.7600.16385_en-us_88e332355227be65.manifest
winsxs\manifests\amd64_microsoft-windows-t..tfmonitor.resources_31bf3856ad364es5_6.1.7600.16385_en-us_6cdd9e020b264849.manifest
winsxs\manifests\amd64_microsoft-windows-extrac32.resources_31bf3856ad364e35_6.1.7600.(6385_en-us_6748f1ba0acea682.manifest

Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.

 

[NoelDP]

(Thanks, Tom!)

Yes - that's the file.
Next time, please attach it (use the paperclip option in the reply box), as it makes it easier to read and manipulate, and we get the whole thing (the file may exceed limitations on post size otherwise).

I think I'd better leave this one for Tom - the file replacements I can do easily, but Tom's the expert on the registry errors that also show in your report

It may be a good idea to run another CheckSUR scan and post the new report - some of the items were claimed fixed, including one which appears in the end not to have been fixed.

 

[tom982]

Hi Max Power,

Yeah, that's the one. Thanks.

Command Prompt

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. Click on the Start
   
   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
   
   del /f /q /s %WinDir%\Temp\CheckSUR

Export COMPONENTS Hive

Please download RegBak (by AceLogix Software) from the link below and save it to your Desktop.

Download Mirror #1​

• Right-click > Extract all... and extract the files to your Desktop
  
  For 32-bit (x86) editions of Windows, double-click on regbak.exe
  For 64-bit (x64) editions of Windows, double-click on regbak64.exe​
  If you are unsure whether you have x86 or x64 Windows, see here
• Without changing any options, click Next. RegBak will now backup all of your registry hives.
• Navigate to C:\Windows\RegBak\{Date}\ and copy the COMPONENTS file (it has no extension) to your Desktop
• Upload this file for me to analyse please, using any of the following options:
  
  Microsoft Skydrive
  Dropbox
  SendSpace (or any other file-sharing site of your preference)​

Tom

 

[Max Power]

Good morning Tom. Heading off to work in a couple of minutes (The high temp is -7F today!)

OK, in your first set of instructions, got through step 3 just fine, but I can't the root folder or a tom982.txt file discussed in step 4.

By the way Tom, I am central time US, so I am 6 hours behind you, just in case there are gaps in communication. Thanks for your help.

 

[tom982]

Hi Max,

Sorry about that, I incorrectly posted about that file when it isn't created. I edited my post, but I must have been too late. Run the SURT again, then upload your log and the COMPONENTS hive using the instructions from the post before.

-7F :shock: Sounds like you need to wrap up!

No problem, thanks for letting me know, I've helped quite a few people in the US before and it usually works out okay.

Tom

 

[NoelDP]

We have lots of white stuff around here today - 32F/0C - despite the forecast saying only 'occasional light snow'
It hasn't stopped since I first looked out the window at 08:55 (it's now 12:52).
It's not all that heavy, but it's constant; and I really don't wanna have to go out in it, but I need food!

 

[Max Power]

Hi Max Power,

Yeah, that's the one. Thanks.

Command Prompt

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. Click on the Start
   
   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
   
   del /f /q /s %WinDir%\Temp\CheckSUR

Export COMPONENTS Hive

Please download RegBak (by AceLogix Software) from the link below and save it to your Desktop.

Download Mirror #1​

• Right-click > Extract all... and extract the files to your Desktop
  For 32-bit (x86) editions of Windows, double-click on regbak.exe
  For 64-bit (x64) editions of Windows, double-click on regbak64.exe​
  If you are unsure whether you have x86 or x64 Windows, see here
• Without changing any options, click Next. RegBak will now backup all of your registry hives.
• Navigate to C:\Windows\RegBak\{Date}\ and copy the COMPONENTS file (it has no extension) to your Desktop
• Upload this file for me to analyse please, using any of the following options:
  Microsoft Skydrive
  Dropbox
  SendSpace (or any other file-sharing site of your preference)​

Tom

OK Tom a little time to work on this before dashing off to work, I will have more time this evening.

I followed the first set of instructions and when I paste your command line and hit enter, it goes straight back to the prompt without appearing to do anything. Is that what it is supposed to do?

Also downloaded Dropbox, no problems there yet.

You second set of instructions for Regbak. I downloaded the free program ad attempted to run it. I don't know what Mirror ! means, but right clicking on the Regbak 64 doesn't give me a menu with extract all on it, so I double clicked it and that did.

I looked in the Regbak folder and did not find a file named Components sh I saved the entire dated folder to my desktop. Never used Dropbox before so not sure how to share with you and I have to leave for work now. Only 10 below zero F today, with is like 1000 below zero Celsius. Brrrr.

 

[tom982]

Hi Max,

Wow, sounds pretty cold! We had -18C (sub zero in your funny measurements ) a few years ago and that was just horrific.

It should be a relatively fast command, so don't be worried about it completing almost instantly.

I'll need to investigate with regbak a little then, because I have the same problem, but I thought it was just me. We'll do it manually instead.

Navigate to: C:\Windows\system32\config

And copy the file COMPONENTS (it has no extension) into the Public folder of your Dropbox. Then right-click on it then Dropbox > Copy Public Link and paste it here please.

Tom

 

[Max Power]

Hi Max,

Wow, sounds pretty cold! We had -18C (sub zero in your funny measurements ) a few years ago and that was just horrific.

It should be a relatively fast command, so don't be worried about it completing almost instantly.

I'll need to investigate with regbak a little then, because I have the same problem, but I thought it was just me. We'll do it manually instead.

Navigate to: C:\Windows\system32\config

And copy the file COMPONENTS (it has no extension) into the Public folder of your Dropbox. Then right-click on it then Dropbox > Copy Public Link and paste it here please.

Tom

OK, will do when I get home tonight.

FYI, I am in publishing and I have Macs at the office. I am not a Mac fanboi by any measure, but this stuff never happens on my Macs. Maybe that is why they have become popular with pikers like me.

Back at ya in 8 or so.

 

[NoelDP]

One of the main reasons that macs don't have problems is that they don't have to deal with the millions of potential variations of hardware that Windows does - basically all Mac hardware is identical, and therefore easy to write for.... and that doesn't account for the difference in the software environment - Windows is relatively open (anyone can write a Windows app and sell it) Mac software is closed - Apple takes a cut of every app sold.

There are large variations in the capability of even large companies in writing 'good' software - two of the worlds largest AV suppliers are particularly prone to writing incompatible programs. (I'll leave to your imagination which ones I'm referring to)

 

[Max Power]

Hi Max,

Wow, sounds pretty cold! We had -18C (sub zero in your funny measurements ) a few years ago and that was just horrific.

It should be a relatively fast command, so don't be worried about it completing almost instantly.

I'll need to investigate with regbak a little then, because I have the same problem, but I thought it was just me. We'll do it manually instead.

Navigate to: C:\Windows\system32\config

And copy the file COMPONENTS (it has no extension) into the Public folder of your Dropbox. Then right-click on it then Dropbox > Copy Public Link and paste it here please.

Tom

https://dl.dropbox.com/u/89504100/components

Can you make sense of this? Looks to be full of wing dings.

 

[tom982]

https://dl.dropbox.com/u/89504100/components

Thanks Max, I'll review your registry hive now.

Also, I've just noticed this from your first post:

OK, first I have to say I am a complete piker with this stuff. If I have to do anything that requires changing the BIOS or registry or anything like that, I am gonna have to pay someone to fix this.
...
Whatever solutions someone talk slow. I am no techie with this stuff.

You've done brilliantly so far, and the only thing that went wrong was due to my poor instructions, so hang in there and we'll have this fixed in no time! I seriously doubt whether an IT technician would be able to fix this to be honest, they'd probably go down the reinstall route. There aren't many people on the web who will deal with this level of corruption - niemiro, Noel and I make up a large proportion of us! Plus us fixing this will save you a few quid, which is always good

But anyway, please stop me and ask if you're ever unsure about anything I say though, and I'll do my best to explain it to you in the clearest way possible.

Tom

 

[tom982]

Hi Max,

Would you mind running the System Update Readiness Tool for me please? You downloaded a few posts back, and if you still have that file, just double click on it to run it again. When it finishes, post the log please:

C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom

 

[Max Power]

Hi Max,

Would you mind running the System Update Readiness Tool for me please? You downloaded a few posts back, and if you still have that file, just double click on it to run it again. When it finishes, post the log please:

C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom

https://dl.dropbox.com/u/89504100/CheckSUR.persist.log

OK, here ya go.

Thanks again for all your help!