Update has caused corruption

[budegan]

Hi,

Firstly sorry that I can't give a more specific title thread at the moment - I'll explain why below.

Secondly apologies if I have posted in the wrong forum, I had a skim through them and this seemed then most appropriate though I wasn't too sure.

So here's the problem:

Over the last few days I've been getting a whole host of error messages, and lots of strange going ons. I believe -though I'm not entirely sure - it all started when a (Critical) Windows Update automatically run and restarted my laptop on 22nd December.

The first and most noticeable thing to happen was that my desktop picture had disappeared. Then came the error messages - eg when I open iTunes the pop-up message "DDE Server Window: iTunes.exe - Corrupt File...The file or directory C:\users\matt\AppData\Roaming\Microsoft\Windows is corrupt and unreadable. Please run the Chkdsk utility."

I tried to run a scheduled Chkdsk but it did not run at start up. I then learnt that one could be scheduled via Command Prompt, but had problems with this also as many of the suggested ways of getting to the command prompt as none of the methods suggested here: http://www.sevenforums.com/tutorials/947-command-prompt.html would work. Eg if I type CMD into the search box in the start menu I receive the message "Windows cannot find 'search:query=cmd'. Make sure you typed the name correctly, and then try again".

Assuming that this meant that I had really big problems I attempted to try a system restore, but that won't run either as I get the following message: "The disc TI106139W0E (C has errors" and the instruction to run chk disc! Round and round in circles.....

I've had a bit of a look around these forums, but every thing I try doesn't work. Eg:

I was led to try System File Checker (System Files - SFC Command - Vista Forums), and managed to get a command prompt via a download someone had posted on here but when I type SFC /SCANNOW I get the message "Windows Resource Protection could not start the repair service".......so then - as per the tutorial - I attempt to run it in safe mode (Safe Mode - Vista Forums) but this doesn't work either as when I type MSCONFIG into the search box in the start menu I receive the message "Windows cannot find 'search:query=msconfig'. Make sure you typed the name correctly, and then try again".

I had recently run Microsoft Security Essentials - which is reporting to be all up to date, and protected - so assume that's all good.

PLEASE can anyone help at all? You'd really make my Christmas.

Thanks in advance.

 

[NoelDP]

Please follow the instructions in Windows Updates & Activation - Windows 7 Forums and post the requested data.
You may find it better to try running CHKDSK and SFC in offline mode....


Your best option in that case is to run the CHKDSK and SFC in offline mode from a Recovery Environment boot.

Reboot the computer, and tap the F8 key until you get the advanced boot menu up - one option should be 'Repair your computer'. Pick that one.

Log into your normal account.
You'll get a set of options - pick the Command Prompt one.
At the command prompt, type DIR C:\
- if we're lucky this will bring up a listing of your normal C: drive contents, including the Program Files folder(s) and the Windows folder.
If not, try D:\ or E:\ (etc. until you get the right letter)
then type the following command

CHKDSK <drive>: /R

and wait for it to complete - it could take a few hours, depending on the size of the drive.

Once complete, type

sfc /scannow /OFFBOOTDIR=<drive>:\ /OFFWINDIR=<drive>:\Windows

where <drive> is the letter you found above.

Wait for the command to complete. (make a note of the response!).

Once it has, type EXIT and the pick the option to reboot.

then post again, and include the data from the instructions.

 

[budegan]

Hi Noel,

Thanks a billion for your response - you're a good man.

I went through your instructions and was all good up to the point at which I needed to enter CHKDSK <drive>: /R. At this point I got the message: "The system cannot find the file specified" (see attached screenshot).

Can you recommend anything to try next?

Very best wishes,
Matt

 

[Kari]

You have a syntax error there. Replace <drive> on Noels instructions with the drive letter, without less than and greater than tags.

In other words, when instructions tell you to type CHKDSK <drive>: /R and the drive you need to check is C:, your command should be CHKDSK C: /R

Kari

 

[NoelDP]

The command you need is
CHKDSK C: /R

(I see Kari beat me to it - thanks Kari!)

 

[Kari]

Saw OP hanging online, thought he might sit there just waiting an answer and this was so simple even I knew it .

 

[mmkarimi]

also recommend you to make another fresh user and log on to it. sometime this can help...
then for the check disk see the following picture.. after ticking these restart your system and let it check disk you. it takes a big time

 

[budegan]

I'm not stupid...honestly!

Will try again right now. Thanks both.

 

[budegan]

Oh Lordy.

So I entered the check disc command correctly and it begun to run - wey hey! As you warned it took time, lots of time; so I figured I'd do some stuff (I had a bath and watched some TV, relaxing not just in hot water but also in the knowledge that I'd return to a completed disk check).

I've just come back to the computer and instead of finding it in the command prompty thing it was turned off. Now I've rebooted to turn it on it's in the same state as it was before the CHKDSK - ie no change, no fix.

What do you think happened and what do you suggest I do next? Do I need to run CHKDSK again but not be tempted by a relaxing bath and instead wait for the process to complete so I can immediately pounce on it and complete your suggested actions? Or should I pick up from the CHKDSK (ie run the Scandsk from offline mode)?

Thanks all - it's genuinely appreciated.

 

[NoelDP]

It sounds as if you may have some hardware problems - try running the less intensive test

Same procedure, but this time use the command

CHKDSK C: /F

see if that completes properly, then try the SFC /SCANNOW

 

[Lee]

There are a couple of possible things that could be wrong. The first thing that comes to my mind is that there is a possibility that the HDD is going bad, and if so that means you could lose all your data. To avoid this if you have the ability to make a Linux run disc then do that; once done run it to see if your HDD is available, and if so backup all your data, music and whatever else you want to keep.

Once that is done then reinstall the OS, or using your install disc see if you can restore your system to a date prior to the 22 Dec update (you can attempt this prior to making a Linux run disc).

Oh, and BTW how old is your system; this information would be nice to help determine what the problem might be.

Good Luck. . .

 

[mmkarimi]

after the check disk, it logs into the windows. if you don't do anything after maybe 15 min it turns your computer off. which is because of your power managing task.
its important to know if it logs on to the win for sure.

if so, your HDD is fine and the problem is with your software, as i said try a new user ( a fresh one, it may help). if no change re install your software, or finally your os..

 

[budegan]

HA! JOY!

It seems to have worked!

I followed Noel's instruction (he was first - thanks to the other guys who offered advice) of trying CHKDSK C:/F which ran quickly and completed (see attachment screengrab_1).

I then entered SFC /SCANNOW. This also ran quickly and completed (see attachment screengrab_2).

I rebooted and things seem to be back to normal - desktop picture is back, and no error messages.

A BIG thank you!

Hopefully my last question: should I do anything further? Should I try and run a full CHKDSK?

Thanks again!

Matt

 

[NoelDP]

Yes - there's still a fair amount of fixing likely to be necessary

Follow the instructions in http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html and post the results - we can then see what sort of a mess your system is still in

 

[budegan]

Good evening Noel,

Thanks once again for that. I followed all the instructions in the link you provided, and everything worked without a hitch.

I'm assuming it's the (attached) zipped CBS file that you need to look at to see the extent of my woes.

Fingers crossed things aren't too bad I guess.

I look forward to your response, with thanks as always.

Matt

 

[NoelDP]

There is indeed a fair amount to be fixed - but I'm in the pub, so now is not thtime to attempt it.
for the record, here are the known problems......

2012-12-29 18:19:21, Info                  CSI    000002f5 [SR] Repairing 2 components
2012-12-29 18:19:21, Info                  CSI    000002f6 [SR] Beginning Verify and Repair transaction
2012-12-29 18:19:21, Info                  CSI    000002f7 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:m38S6QqjUzzDzsYd6NdBgVBOts1dZBL5BBvm7oHrL4I=} Expected: {l:32 b:e8hHzmwtKcM08NFgC7veOTP/Rfa+5RhvRC5icKP57E4=}
2012-12-29 18:19:21, Info                  CSI    000002f8 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7601.17514, 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
2012-12-29 18:19:21, Info                  CSI    000002f9 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-w..ctionflow.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6f232ab0cfb511fa\WLanConn.dll.mui do not match actual file [l:32{16}]"WLanConn.dll.mui" :
  Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:AeL9/EJVS35x6IAuIgHCidg5L5tpIrQ+AuisWXwQbso=}
2012-12-29 18:19:21, Info                  CSI    000002fa [SR] Cannot repair member file [l:32{16}]"WLanConn.dll.mui" of Microsoft-Windows-WLANConnectionFlow.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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
2012-12-29 18:19:21, Info                  CSI    000002fb Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:m38S6QqjUzzDzsYd6NdBgVBOts1dZBL5BBvm7oHrL4I=} Expected: {l:32 b:e8hHzmwtKcM08NFgC7veOTP/Rfa+5RhvRC5icKP57E4=}
2012-12-29 18:19:21, Info                  CSI    000002fc [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7601.17514, 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
2012-12-29 18:19:21, Info                  CSI    000002fd [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2012-12-29 18:19:21, Info                  CSI    000002fe Hashes for file member \??\C:\windows\System32\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:m38S6QqjUzzDzsYd6NdBgVBOts1dZBL5BBvm7oHrL4I=} Expected: {l:32 b:e8hHzmwtKcM08NFgC7veOTP/Rfa+5RhvRC5icKP57E4=}
2012-12-29 18:19:21, Info                  CSI    000002ff Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe do not match actual file [l:22{11}]"autochk.exe" :
  Found: {l:32 b:m38S6QqjUzzDzsYd6NdBgVBOts1dZBL5BBvm7oHrL4I=} Expected: {l:32 b:e8hHzmwtKcM08NFgC7veOTP/Rfa+5RhvRC5icKP57E4=}
2012-12-29 18:19:21, Info                  CSI    00000300 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:22{11}]"autochk.exe"; source file in store is also corrupted
2012-12-29 18:19:21, Info                  CSI    00000301 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-w..ctionflow.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6f232ab0cfb511fa\WLanConn.dll.mui do not match actual file [l:32{16}]"WLanConn.dll.mui" :
  Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:AeL9/EJVS35x6IAuIgHCidg5L5tpIrQ+AuisWXwQbso=}
2012-12-29 18:19:21, Info                  CSI    00000302 [SR] Cannot repair member file [l:32{16}]"WLanConn.dll.mui" of Microsoft-Windows-WLANConnectionFlow.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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
2012-12-29 18:19:21, Info                  CSI    00000303 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.Microsoft-Windows-Client-Features-Language-Pack"
2012-12-29 18:19:21, Info                  CSI    00000304 Hashes for file member \??\C:\windows\System32\en-US\WLanConn.dll.mui do not match actual file [l:32{16}]"WLanConn.dll.mui" :
  Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:AeL9/EJVS35x6IAuIgHCidg5L5tpIrQ+AuisWXwQbso=}
2012-12-29 18:19:21, Info                  CSI    00000305 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-w..ctionflow.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6f232ab0cfb511fa\WLanConn.dll.mui do not match actual file [l:32{16}]"WLanConn.dll.mui" :
  Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:AeL9/EJVS35x6IAuIgHCidg5L5tpIrQ+AuisWXwQbso=}
2012-12-29 18:19:21, Info                  CSI    00000306 [SR] Could not reproject corrupted file [ml:520{260},l:58{29}]"\??\C:\windows\System32\en-US"\[l:32{16}]"WLanConn.dll.mui"; source file in store is also corrupted
2012-12-29 18:19:21, Info                  CSI    00000307 Repair results created:

 

[budegan]

Oh no - and I thought it was job done earlier today.

Enjoy the pub and have a pint on me - it's deserved. I assume from your profile that you're somewhere in Wales. I'm originally from Port Talbot but haven't drank around there for awhile.

Best,
Matt

 

[NoelDP]

Sorry about the wait!
It seems I created the fix - and promptly forgot to post it!
here it is now, anyway....


I've uploaded a file - budxx.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:\budxx
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:\budxx
hit the enter key - if you get a 'Not Found' error try
DIR D:\budxx
or
DIR E:\budxx

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

XCOPY <drive>:\budxx <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.

 

[mmkarimi]

Sorry about the wait!
It seems I created the fix - and promptly forgot to post it!
here it is now, anyway....


I've uploaded a file - budxx.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:\budxx
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:\budxx
hit the enter key - if you get a 'Not Found' error try
DIR D:\budxx
or
DIR E:\budxx

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

XCOPY <drive>:\budxx <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.

would you explain more where budxx can be used for! and what is it going to do?

 

[NoelDP]

budxx.zip is a personalised file containing the missing files that SFC complained about.
the 'fix' places those files in their proper places, and the SFC run checks that they are correct, and if necessary replaces the working copy in the System32 structure - the CBS.log then shows us whether the fix did what it was supposed to do.
We can then move on to any further repairs that may be indicated.