Update has caused corruption

Page 2 of 3 FirstFirst 123 LastLast

  1. Lee
    Posts : 1,796
    Win 7 Pro x64, VM Win XP, Win7 Pro Sandbox, Kubuntu 11
       #11

    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. . .:)
      My Computer


  2. Posts : 279
    Windows 7 Ultimate x64
       #12

    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..
      My Computer


  3. Posts : 7
    Windows Home 7 Home Premium 64bit
    Thread Starter
       #13

    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
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #14

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

    Follow the instructions in Windows Update Posting Instructions and post the results - we can then see what sort of a mess your system is still in :)
      My Computer


  5. Posts : 7
    Windows Home 7 Home Premium 64bit
    Thread Starter
       #15

    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
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #16

    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......
    Code:
    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:
      My Computer


  7. Posts : 7
    Windows Home 7 Home Premium 64bit
    Thread Starter
       #17

    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
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #18

    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.
      My Computer


  9. Posts : 279
    Windows 7 Ultimate x64
       #19

    NoelDP said:
    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?
      My Computer


  10. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #20

    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.
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:28.
Find Us