Attachment 245716Hi, If anyone can help with this error I would appreciate being able to use the Windows Update function. I have tried other forums for this error code but no luck so far. Screen shot is attached for identification of the error code. Also tried the Microsoft site FixIt and other options on their site but still have found nothing that would allow the Update to run.
Thank you NoelD I have followed the instructions and have attached the zipped CBS log file as requested. The windows error code is that stipulated in the thread title. Part of the message from the cmd prompt run of scf /scannow was that there were some corrupted files that could not be fixed so I hope this shows in the logs. Here's hoping you are able to find a solution it would be greatly appreciated.
Thanks again.
(Sorry for the delay - ISP problems!)
Shows your problems as far as SFC is concerned....Code:Line 49765: 2012-12-16 16:52:42, Info CSI 000001c4 [SR] Cannot repair member file [l:48{24}]"System.Data.Services.dll" of System.Data.Services, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch Line 49768: 2012-12-16 16:52:42, Info CSI 000001c6 [SR] Cannot repair member file [l:24{12}]"NAPCLCFG.MSC" of Microsoft-Windows-Networking-NapClientConfigUI.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch Line 49771: 2012-12-16 16:52:42, Info CSI 000001c8 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"Utilman.exe" from store Line 49774: 2012-12-16 16:52:42, Info CSI 000001ca [SR] Cannot repair member file [l:48{24}]"System.Data.Services.dll" of System.Data.Services, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b77a5c561934e089}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch Line 49775: 2012-12-16 16:52:42, Info CSI 000001cb [SR] This component was referenced by [l:158{79}]"Microsoft-Windows-NetFx3-OC-Package~31bf3856ad364e35~x86~~6.1.7601.17514.NetFx3" Line 49778: 2012-12-16 16:52:42, Info CSI 000001cd [SR] Cannot repair member file [l:24{12}]"NAPCLCFG.MSC" of Microsoft-Windows-Networking-NapClientConfigUI.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch Line 49779: 2012-12-16 16:52:42, Info CSI 000001ce [SR] This component was referenced by [l:262{131}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~x86~en-US~6.1.7601.17514.Windows Foundation Language Pack" Line 49784: 2012-12-16 16:52:42, Info CSI 000001d1 [SR] Could not reproject corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:24{12}]"NAPCLCFG.MSC"; source file in store is also corrupted
I'm a little confused by your CheckSUR log, though - there appears to be an unfixed error, but it's not logged in teh summary.
Please run both SFC and CheckSUR again, and post a new set of results - we'll then see what has really happened.
Hi NoelDP
Sorry I think my reply went to tom by mistake. Here is the info you requested my apologies for the
delay, I hope it provides what you need. Kind regards mumsy
No problem.
The two unfixed errors in SFC are still there (as expected) and the new CheckSUR is clear.
I'll work up a fix for them today and get back to you with it
I've uploaded a file - mumsy.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:\mumsy
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:\mumsy hit the enter key - if you get a 'Not Found' error try
DIR D:\mumsy
or
DIR E:\mumsy
The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...
XCOPY <drive>:\mumsy <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
Also run a new MGADiag report, and post the result.
Hi NoelDP,
Thank you for the instructions. I have tried to implement but get this response at the cmd prompt on the Repair your computer window:
x:\windows\system32\DIR C:\mumsy
Volume in drive C is System Reserved
Volume serial number is B267-D66B
Directory of C:\
File not found
Volume in drive X is Boot
Volume Serial Number is D60A - 0DC2
Directory of x:\windows\system32
File not found
x:\windows\system32\_
Each time I try to search on a different drive (as per your instructions) I get the same response.
Volume in drive C is System Reserved etc.
I have even tried putting the file in the C:\Users\Mandy\mumsy (which is actually where it is sitting now which is another try out) and I still get the same response.
So I have not been able to complete your instructions yet.
Any ideas?
In normal Windows - open a Command prompt, and type the command
DIR C:\mumsy
If that comes back 'Not found' then you possibly don't have proper permissions.
run the following command, and post the results.
ICACLS C:\
Hi NoelDP
I have ran the first command and you are correct. As it comes through from the users
path, it doesnt carry the correct permissions over the C drive as the Administrator (which
is what I am supposed to be) so I will rectify that and have another go then report results.
Many thanks
Mumsy
Quote