Repair damaged files

MY computer laptop windows 7 has some damaged files is there a way to fix it?

Right-click on the file or folder and then click on restore previous versions.

You will see a list of the available versions of previous of the file or folder. The list will include files saved on a backup (if you use Windows backup to back up your files) as well as restore points.

Tags: Windows

Similar Questions

  • Repair damaged adobe photoshop .psd files?

    One of my project files has been removed in a terrible accident. I won't go into it, but I got one of the .psd files using a commercial conservation program (Fast File Undelete data DTI). It did not work (go figure) and whenever I try to open the file .psd photoshop (7.0) shows a message box that says: "there was a problem to read the data in the layer. Read the composite data instead? "When I click on the play button of Composite data another box shows that reads,"cannot open '[file name]' because the file is not compatible with this version of photoshop. »

    It seems as it is very close to work, because there isn't even a vignette. I also got a handful of .jpg and .tga, who are also broke. Does anyone know of a utility that could attempt to repair a .psd, .tga or a .jpg?

    Repair Kit PSD that repairs the Photoshop files and you give image repaired to the original format as well as repaired layers and the corresponding safe bitmap file.

    -Repair of PSD files developed using any color mode of Photoshop

    -Repairs corrupt the PSB ("large document format") files

    -Fix images with the DDP file extension

    -Provides the bitmap of the repaired Photoshop file

    -Takes to load Adobe Photoshop CS5, CS4, CS3, CS2 CS1

    DOWNLOAD SETUP FROM HOMEPAGE: http://www.psd.repair/

    SECOND FREE SOLUTION:

    Photoshop is adding sometimes a few bytes at the beginning of the file when the file is saved, then the same Photoshop gives an error and complained that the files... All you have to do is delete the Group of bytes that unnecessarily.

    Assuming that you know already what is a HEX editor and how to use it I'll write here a few steps, you can do before opening a "corrupt": PSD file

    1. make a backup (copy) of the file before making any changes.

    2 - Open the file "corrupted" in a HEX editor used (text editor NOT!) and look for such groups of fairness at the beginning: 8 bits/s and after a few bytes 8BIM another group of bytes, then 8BIM.

    3 - this succession must be respected strictly: 8BPS... 8BIM... 8BIM. these groups should be very close to each other and it is easy to find.

    4 - remove all the bytes before 8 group BPS (shift + delete) and save the file... =)

    5 - open in Photoshop and have fun.

    Hope this works for you, for wide info click to:- 6851/how-to-make-photoshop-file-recovery?forum=w7itprogeneral http://social.technet.microsoft.com/Forums/exchange/en-US/7041fd54-6d06-466d-9bf0-30845860

  • "sfc/scannow" was not able to repair some files, one or more of which must be in the path of an installation of Vista SP2

    I tried to install the SP2 of Vista for a few days now with no luck. Earlier today, I had a breakthrough and was finally able to install 'patch for Windows", which, after a reboot, enabled me to see the x 64 SP2 update in part"updates"of the control panel. When I tried to install that, he said he failed and gave me an error code. When I looked it up, it says try "sfc/scannow" in an elevated command prompt. The research a ton of lines of logs and errors, and after looking through, I could find these as (the least most) files problem-

    WinSAT.exe
    Amd64\HPF940AL. DLL
    PresentationBuildTasks.dll
    locale.NLS

    My question is, are any of these files required for the installation of Vista SP2 to cross? Thanks in advance for any help offered, and more information is needed, I will gladly provide.

    Extra balls (If I missed a few files problem, I'd appreciate a double check. WinSAT.exe was not who listed there, but it was listed above upward with no sign to be repaired)

    2014-06-08 14:32:54, 000002f0 CSI Info [SR] verification complete
    2014-06-08 14:32:54, 000002f1 CSI Info [SR] repair 8 components
    2014-06-08 14:32:54, CSI Info 000002f2 transaction [SR] beginning verify and repair
    2014-06-08 14:32:55, CSI Info 000002f3 hashes of file members \SystemRoot\WinSxS\amd64_microsoft-windows-i... nal-Core-locale-nls_31bf3856ad364e35_6.0.6001.18000_none_c6d6cc5d61a33307\locale.nls is not actual file [l:20 {10}] "locale.nls": "
    Found: {l:32 b:wmYkySbnNnz5uBFxkqlZYwcQXpJF7VPzM7ezK / KmEmU =} expected: {l:32 b:KTJBpw1awVp4c5LesEXyEM / jfGsI24iQGrROSGLA9Tc =}
    2014-06-08 14:32:55, 000002f4 CSI Info [SR] cannot repair the military record [l:20 {10}] "locale.nls" Microsoft-Windows-International-Core-Locale-NLS, Version 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 = (9), the Culture neutral, VersionScope is 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2014-06-08 14:32:56, CSI Info 000002f5 Member \SystemRoot\WinSxS\amd64_microsoft-windows-newdev_31bf3856ad364e35_6.0.6001.18000_none_6d94e6d8090688e9\newdev.dll file hashes are not actual file [l:20 {10}] "newdev.dll": "
    Found: {l:32 b:lSyVpDkn/cMYwbuVSPH7Zs5/O8nFWBZqM2RQ9Au7lBc =} expected: n. b:KgBvBB/y3DPbBu/sLiebqGDKWCYtcAHle5YbZ1OItbU = l:32}
    2014-06-08 14:32:56, 000002f6 CSI Info [SR] cannot repair the military record [l:20 {10}] "newdev.dll" Microsoft-Windows-NewDev, Version 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 = (9), the Culture neutral, VersionScope is 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2014-06-08 14:33, CSI Info 000002f7 Member \SystemRoot\WinSxS\amd64_prnhp001.inf_31bf3856ad364e35_6.0.6001.18000_none_2eef0719d90dbdd0\Amd64\HPF940AL file hashes. DLL is not actual file [l:36 {18}] "" Amd64\HPF940AL. "» DLL:
    Found: {l:32 b:skEriPi1c9ksB0gEgVdygoY5xO9Ov8GD8 / 0CX4rugB0 =} expected: {l:32 b:mU / ap55UOjxtVzdrgCzt62CW4HxfZ + uALCVLOKOcCtU =}
    2014-06-08 14:33, 000002f8 CSI Info [SR] cannot repair the military record [l:36 {18}] "" Amd64\HPF940AL. "» DLL"prnhp001.inf, Version 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 = (9), the Culture neutral, VersionScope is 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24 {12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-06-08 14:33, CSI Info 000002f9 Member \SystemRoot\WinSxS\msil_presentationbuildtasks_31bf3856ad364e35_6.0.6001.18096_none_9bc52ef038dbf0b3\PresentationBuildTasks.dll file hashes are not actual file [l:52 {26}] "PresentationBuildTasks.dll": "
    Found: {l:32 b:cm3V/Ig0IdNHXGV6tzz8nMN2GvpxC0nujF4j/RbeCW4 =} expected: {l:32 = b:har0YuKv8pbmLU0w7b0vcjKcWyduPIiqUPx5HlaC02E}
    2014-06-08 14:33, 000002fa CSI Info [SR] cannot repair the military record [l:52 {26}] "PresentationBuildTasks.dll" PresentationBuildTasks, Version = 6.0.6001.18096, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2014-06-08 14:33:02, CSI Info 000002fb Member \SystemRoot\WinSxS\amd64_prnhp001.inf_31bf3856ad364e35_6.0.6001.18000_none_2eef0719d90dbdd0\Amd64\HPF940AL file hashes. DLL is not actual file [l:36 {18}] "" Amd64\HPF940AL. "» DLL:
    Found: {l:32 b:skEriPi1c9ksB0gEgVdygoY5xO9Ov8GD8 / 0CX4rugB0 =} expected: {l:32 b:mU / ap55UOjxtVzdrgCzt62CW4HxfZ + uALCVLOKOcCtU =}
    2014-06-08 14:33:02, CSI Info 000002 fc [SR] cannot repair the military record [l:36 {18}] "" Amd64\HPF940AL. "» DLL"prnhp001.inf, Version 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 = (9), the Culture neutral, VersionScope is 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24 {12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-06-08 14:33:02, 000002fd CSI Info [SR] this element is referenced by [l:164 {82}] "' Package_30_for_KB936330 ~ 31bf3856ad364e35 ~ amd64 ~ ~ 6.0.1.18000.936330 - 161_neutral_GDR" "
    2014-06-08 14:33:03, CSI 000002fe hashes for Member file Info? \C:\Windows\Speech\Engines\SR\en-US\af031033.am are not real file [l:22 {11}] "af031033.am": "
    Found: {l:32 b:cq + 1NYUaITMpBYllzFX/LW74KgeL5QGxQ0 + PBG / 4w4 =} expected: {l:32 b:oZ + J3PjqKUUdN1O + pJQYQ8z + 5SccD + uPMQHFfMlQalE =}
    2014-06-08 14:33:03, 000002ff CSI Info [SR] repair corrupted file [ml:520 {260}, l:76 {38}] '------? \C:\Windows\Speech\Engines\SR\en-us"\[l:22{11}]"af031033.am' of the store
    2014-06-08 14:33:03, info CSI 00000300 WARNING: file [l:22 {11}] "af031033.am" in [l:76 {38}] '-? ' "" \C:\Windows\Speech\Engines\SR\en-us' switching property
    Old: Microsoft-Windows - SpeechRecognizerENU.ale, Version = 6.0.6000.16386, 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
    New: Microsoft-Windows - SpeechRecognizerENU.ale, Version = 6.0.6000.16386, 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
    2014-06-08 14:33:03, info CSI 00000301 Member \SystemRoot\WinSxS\msil_presentationbuildtasks_31bf3856ad364e35_6.0.6001.18096_none_9bc52ef038dbf0b3\PresentationBuildTasks.dll file hashes are not actual file [l:52 {26}] "PresentationBuildTasks.dll": "
    Found: {l:32 b:wskm5ChU9DmxqusVLNiJTnb8sdPBBokQ8Eb8nO/P5/Y =} expected: {l:32 = b:har0YuKv8pbmLU0w7b0vcjKcWyduPIiqUPx5HlaC02E}
    2014-06-08 14:33:03, info CSI 00000302 [SR] cannot repair the military record [l:52 {26}] "PresentationBuildTasks.dll" PresentationBuildTasks, Version = 6.0.6001.18096, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2014-06-08 14:33:03, info CSI 00000303 [SR] this element is referenced by [l:166 {83}] "' Package_4_for_KB948610 ~ 31bf3856ad364e35 ~ amd64 ~ ~ 6.0.6001.2123.948610 - 322_neutral_GDR" "
    2014-06-08 14:33:04, repaired Info CSI 00000304 [SR] file \SystemRoot\WinSxS\Manifests\\[l:20{10}]"newdev.dll" by copying from backup
    2014-06-08 14:33:04, info CSI 00000305 hashes for Member file? \C:\Windows\System32\newdev.dll are not real file [l:20 {10}] "newdev.dll": "
    Found: {l:32 b:lSyVpDkn/cMYwbuVSPH7Zs5/O8nFWBZqM2RQ9Au7lBc =} expected: n. b:KgBvBB/y3DPbBu/sLiebqGDKWCYtcAHle5YbZ1OItbU = l:32}
    2014-06-08 14:33:04, info CSI 00000306 [SR] repair file corrupted [ml:520 {260}, l:46 {23}] '------? \C:\Windows\System32"\[l:20{10}]"Newdev.dll' of the store
    2014-06-08 14:33:04, info CSI 00000307 hashes of file members \SystemRoot\WinSxS\amd64_microsoft-windows-i... nal-Core-locale-nls_31bf3856ad364e35_6.0.6001.18000_none_c6d6cc5d61a33307\locale.nls is not actual file [l:20 {10}] "locale.nls": "
    Found: {l:32 b:wmYkySbnNnz5uBFxkqlZYwcQXpJF7VPzM7ezK / KmEmU =} expected: {l:32 b:KTJBpw1awVp4c5LesEXyEM / jfGsI24iQGrROSGLA9Tc =}
    2014-06-08 14:33:04, info CSI 00000308 [SR] cannot repair the military record [l:20 {10}] "locale.nls" Microsoft-Windows-International-Core-Locale-NLS, Version 6.0.6001.18000, pA = PROCESSOR_ARCHITECTURE_AMD64 = (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2014-06-08 14:33:04, info CSI 00000309 [SR] this element is referenced by [l:164 {82}] "' Package_30_for_KB936330 ~ 31bf3856ad364e35 ~ amd64 ~ ~ 6.0.1.18000.936330 - 185_neutral_GDR" "
    2014-06-08 14:33:04, CSI 0000030 has hashes for Member file Info? \C:\Windows\System32\locale.NLS are not real file [l:20 {10}] "locale.nls": "
    Found: {l:32 b:wmYkySbnNnz5uBFxkqlZYwcQXpJF7VPzM7ezK / KmEmU =} expected: {l:32 b:KTJBpw1awVp4c5LesEXyEM / jfGsI24iQGrROSGLA9Tc =}
    2014-06-08 14:33:04, CSI Info 0000030b hashes of file members \SystemRoot\WinSxS\amd64_microsoft-windows-i... nal-Core-locale-nls_31bf3856ad364e35_6.0.6001.18000_none_c6d6cc5d61a33307\locale.nls is not actual file [l:20 {10}] "locale.nls": "
    Found: {l:32 b:wmYkySbnNnz5uBFxkqlZYwcQXpJF7VPzM7ezK / KmEmU =} expected: {l:32 b:KTJBpw1awVp4c5LesEXyEM / jfGsI24iQGrROSGLA9Tc =}
    2014-06-08 14:33:04, CSI Info 0000030 c [SR] could not reproject corrupted file [ml:520 {260}, l:46 {23}] '------? \C:\Windows\System32"\[l:20{10}]"locale.NLS '; source file in the store is also corrupted
    2014-06-08 14:33:04, CSI Info 0000030 d repair results created:
    POQ 114 begins:
    0: move the file: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\8c0159154883cf0125320000380ccc0e._0000000000000000.cdf-ms', Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms'
    1: move the file: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\ac4f59154883cf0126320000380ccc0e.$$.cdf-ms', Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms'
    2: move the file: Source = [l:244{122}]"\SystemRoot\WinSxS\Temp\PendingRenames\2c6a5f154883cf0127320000380ccc0e.$$_speech_engines_sr_en-us_3201cbb7cd315cd0.cdf-ms', Destination = [l:156{78}]"\SystemRoot\WinSxS\FileMaps\$$_speech_engines_sr_en-us_3201cbb7cd315cd0.cdf-ms'
    3: move the file: Source = [l:254{127}]"\SystemRoot\WinSxS\Temp\PendingRenames\3c915f154883cf0128320000380ccc0e.$$_speech_engines_lexicon_en-us_bd71d54bf658e12b.cdf-ms', Destination = [l:166{83}]"\SystemRoot\WinSxS\FileMaps\$$_speech_engines_lexicon_en-us_bd71d54bf658e12b.cdf-ms'
    "4: hard link file: Source = [l:260 {130}] ' \SystemRoot\WinSxS\x86_microsoft-windows-s... chrecognizerenu.ale_31bf3856ad364e35_6.0.6000.16386_en-us_cbfb04a3abf30016\af031033.am', Destination = [l:100 {50}] '------? \C:\Windows\Speech\Engines\SR\en-US\af031033.am ".
    5: create file: file = [l:228{114}]"\SystemRoot\WinSxS\amd64_microsoft-windows-newdev_31bf3856ad364e35_6.0.6001.18000_none_6d94e6d8090688e9\newdev.dll', attributes = 00000080
    6: move the file: Source = [l:164{82}]"\SystemRoot\WinSxS\Temp\PendingRenames\3c6c7a154883cf0129320000380ccc0e.newdev.dll', Destination = [l:228{114}]"\SystemRoot\WinSxS\amd64_microsoft-windows-newdev_31bf3856ad364e35_6.0.6001.18000_none_6d94e6d8090688e9\newdev.dll'
    7: move the file: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\1c09bc154883cf012a320000380ccc0e.$$_system32_21f9a9c4a2f8b514.cdf-ms', Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms'
    8: hard link file: Source = [l:228 {114}] \SystemRoot\WinSxS\amd64_microsoft-windows-«
    2014-06-08 14:33:04, newdev_31bf3856ad364e35_6.0.6001.18000_none_6d94e6d8090688e9\newdev.dll CSI Info", Destination = [l:68 {34}] '------? \C:\Windows\System32\newdev.dll ".
    9: move the file: Source = [l:220{110}]"\SystemRoot\WinSxS\Temp\PendingRenames\fccae2154883cf012b320000380ccc0e.$$_performance_02bd33cc045df684.cdf-ms', Destination = [l:132{66}]"\SystemRoot\WinSxS\FileMaps\$$_performance_02bd33cc045df684.cdf-ms'
    10: move the file: Source = [l:234{117}]"\SystemRoot\WinSxS\Temp\PendingRenames\4cffe5154883cf012c320000380ccc0e.$$_performance_winsat_ac47b36afb2fa68e.cdf-ms', Destination = [l:146{73}]"\SystemRoot\WinSxS\FileMaps\$$_performance_winsat_ac47b36afb2fa68e.cdf-ms'
    11: move the file: Source = [l:254{127}]"\SystemRoot\WinSxS\Temp\PendingRenames\4c70e8154883cf012d320000380ccc0e.$$_performance_winsat_datastore_34fe222e5de27d61.cdf-ms', Destination = [l:166{83}]"\SystemRoot\WinSxS\FileMaps\$$_performance_winsat_datastore_34fe222e5de27d61.cdf-ms'

    Hello

    We look also at the bottom line in the journal of the SFC, not just specific entries along the way.

    He would often have similar entries, but the line of low said unable to fix or repaired successfully.

    _______________________________________

    • Once the process is complete, you may receive one of the following messages:

    • Windows resource protection did not find any breach of integrity.

      This means that you have not all missing or damaged system files.

    • Windows resource protection could not perform the requested operation.

      To resolve this issue, perform the analysis in safe mode System File Checker

      (http://windows.microsoft.com/en-in/windows/start-computer-safe-mode)

      and make sure that the files PendingDeletes and PendingRenames exist under %WinDir% \WinSxS\Temp.

    • Windows resource protection finds files corrupted and managed to fix it. Details are provided in convertible bonds. Newspaper %WinDir% \Logs\CBS\CBS.log.

      To display detailed information on the analysis of system files and restore, go to the display of the details of the System File Checker process.

    • Windows resource protection found corrupt files but was unable to fix some of them. Details are provided in convertible bonds. Newspaper %WinDir% \Logs\CBS\CBS.log.

      To repair the corrupted files manually, see the details of the System File Checker process to find the damaged file, and then manually replace the corrupted file with a good copy of the file.

    If the message failed to fix some files and they are not the settings.ini errors (which can be ignored), you may need to perform a repair upgrade Installation.

    "How to perform a repair for Vista Installation"

    http://www.Vistax64.com/tutorials/88236-repair-install-Vista.html

    ________________________________________

    Is to install Service Pack information:

    Click Start > right click on computer > left click on properties > see if you have Vista 32 bit or Vista 64-bit installed.

    It will also tell you which SP you have installed.

    Then, choose the download of 'bit' OK to use to install Service Packs, installation of SP1 first if it is not already installed.

    Vista SP1 32-bit (x 86): http://www.microsoft.com/en-us/download/details.aspx?id=30

    Vista SP1 64-bit: http://www.microsoft.com/en-us/download/details.aspx?id=21299

    Vista SP2 32-bit (x 86): http://www.microsoft.com/en-us/download/details.aspx?id=16468

    Vista SP2 64-bit: http://www.microsoft.com/en-us/download/details.aspx?id=17669

    This Information Microsoft can help you resolve problems that you encounter during the installation of Service Packs for Vista.

    http://support.Microsoft.com/kb/947366

    See you soon

  • Error message on my Vista computer: missing or damaged file: C:/windows/system32/drivers/ATAPI.sys. (Status: OXC0000098). NO RECOVERY DISK! (lost).

    Missing or damaged file: C:/windows/system32/drivers/ATAPI.sys. (Status: OXC0000098). NO RECOVERY DISK! (lost). How can I recover my system, if possible? It does not even start.

    Do you know when this problem started?  Try a system restore to a point in time BEFORE the problem started.  Here is the procedure: http://www.howtogeek.com/howto/windows-vista/using-windows-vista-system-restore/.  Don't forget to check the box to show more than 5 days of restore points.  If the first attempt fails, then try an earlier point or two.  NOTE: You will need to re - install any software and updates that you have installed between now and the restore point, but you can use Windows Update for updates.

    If the system restore does not work, do a startup repair, boot from the disk Installation of Windows Vista genuine (or one that you can borrow from someone) or a recovery disc.  Here is the procedure: http://www.bleepingcomputer.com/tutorials/tutorial148.html.  The Startup Repair tool can repair atapt.sys.  You may need to change the BIOS to do first the CD drive in the boot sequence to boot from the CD.  To do this, hold the screen that tells you the key F to push to enter the menu start or start of installation.  Push it quickly. Make the changes, save your work and exit.  Put the CD in the drive and reboot.  When you are prompted, press any key to boot from the CD.

    If you do not have a floppy disk, you can make a bootable recovery disk by using http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ with burning software like: http://www.snapfiles.com/get/active-isoburner.html and, of course, a blank CD.

    If this does not work, try to start in safe mode (click on the F8 key during startup and go into safe mode with network - or using the prompt from the disk, if necessary, several times).  Then we will check some of your system files:

    Go to start / all programs / accessories / command prompt and right click on command prompt, and then click Run as administrator (skip thiis step if you use the disk)...

    Type sfc/scannow, go and let it run.  It will scan and try to correct some of your system files.  If all goes well he comes complete with no corruption, it could not repair (if it has these post of corruption here or try to analyze it to find the problem or files using http://support.microsoft.com/kb/928228.  In a best-case scenario, he'll fix Atapi.sys.

    While in the command prompt, type chkdsk /f /r and enter and let it run.  It will scan and try to solve any corruption or bad sectors on your hard drive and remove especially as a cause.

    If it does not, then thanks for posting any repetitive error message in Event Viewer on startup (Start / Control Panel / administrative tools / event viewer - type eventvwr and enter, if do it from the command prompt).  Here's how to use Event Viewer: http://www.bleepingcomputer.com/forums/topic40108.html.

    I hope this helps.  Post back the results of the analysis and attempts to repair if these do not work.

    Good luck! Lorien - a - MCSE/MCSA/network + / A +.

  • damaged files

    Hello everyone.

    My mobile phone (note m.1 meizu) had only enough memory, yesterday I transferred all of the music on the pc that is running Windows 7. This morning, I was check if everything was OK and I saw a lot of songs where whit another name and some of the time could not be read. I deleted the files from the phone... So, what could I do to get the music into the phone or repair the files on the computer?

    Thank you

    Hello

    For us to provide you with a precise solution, let us know the details below:

    1. What is the format of audio file? (.mp3, .m4a, .mp4, .wav, .wma, .4a, .mp4, .mid, .midi, .au, .aiff)

    2. What is the application that you use to run the music files?

    3. What is the error message or error code that you get when you run these files?

    Try the following solutions for damaged files.

    1 System File Checker tool to repair the missing or damaged system files.

    2 try running a virus scan.

    3. you can play the file using Windows Media Player.  Windows Media Player

    4. try to copy and transfer files from your computer to your mobile phone and let us know how it goes.

    Keep us updated with the details.

    Thank you!

  • SFC/scannow found he could not repair corrupted files

    Running Windows7 32 Bit

    Found several Pots every 5 to 7 years in which this issue; hoping that there may be a newer better way to solve the problem... so seconded and fingers crossed.

    * PC froze

    * Powered off / Powered it back on

    * Selected Normal boot started fine on the desktop PC

    Decided to run sfc/scannow.  "At the end it read: Windows resource Protection found damaged, files but was unable to solve some of them.

    Looked at the log CBS.log file.  It might take some time to review and even if I saw it that I would not be able to choose the corrupted files, nor know how to find and replace... and don't know if I was smart enough for that I could even remove and replace the files of the operating system.

    I realize I've read in some real old Posts on this topic, maybe some corrupt files are not really necessary or important... but I'd rather have a good job of OS.

    So is there a way to better\newer to resolve this issue... instead of finding what could be one is necessary in the files of the boot of Hay, then looking for right files to replace those damaged?

    I note an In BONE repair on-site... that worries me, because the software just doesn't do well after a repair on the spot.

    Looking for replacement option, and eager to have a BONE without corrupted files and corrupt files... If on-site repair is my only way to go... What are the actual steps not excluded... I have my original Windows7 DVD...

    Haven't tried using the system restore, given that this feature would not replace the corrupted files back to a previous restore point...

    Very well.

    Marking of my previous response as RESPONSE will officially close your thread.

    PS: Wouldn't mind a USEFUL vote while you're there either.

  • Scan SFC cannot repair the file system

    I did a scan of the file system, the sfc and the following error message will appear.  How can I solve this problem?  Apparently diagnostic research hit some kind of anomaly and the system could not repair store.

    Any help would be appreciated.

    Thank you

    2015-03-15 08:55:07, CSI Info 0000019b transaction [SR] beginning verify and repair
    2015 03-15 08:55:07, CSI Info 0000019 d [SR] cannot repair the military record [l:30 {15}] "DiagPackage.dll" Microsoft-Windows-SearchDiagnostic, Version 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 = (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    2015-03-15 08:55:12, CSI Info 0000019f [SR] cannot repair the military record [l:30 {15}] "DiagPackage.dll" Microsoft-Windows-SearchDiagnostic, Version 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 = (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, type neutral, TypeName neutral, neutral to the public key in the store, hash mismatch "
    ' 2015-03-15 08:55:12, 000001 has 0 CSI Info [SR] this element is referenced by [l:224{112}]"Microsoft-Windows-SearchEngine-Client-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.SearchEngine-Client-Package. '
    2015-03-15 08:55:12, 000001 has 3 CSI Info [SR] could not reproject corrupted file [ml:520 {260}, l:80 {40}] '------? \C:\Windows\diagnostics\system\Search"\[l:30{15}]"DiagPackage.dll '; source file in the store is also corrupted
    2015-03-15 08:55:13, 000001 has 5 CSI Info [SR] full audit

    Hello

    See if that helps you.

    «Use the System File Checker tool to repair missing or corrupted system files»

    http://support.Microsoft.com/kb/929833/en-us

    Windows resource protection found corrupt files but was unable to fix some of them. Details are provided in convertible bonds. Newspaper %WinDir% \Logs\CBS\CBS.log.
    To repair the corrupted files manually, see the details of the System File Checker process to find the damaged file, and then manually replace the corrupted file with a good copy of the file.

    ___________________________________________

    But if SFC detect serious errors in the file system, you may need to do a repair installation as in the instructions in the first part of this answer.

    "How to do a repair installation to repair Windows 7"
    http://www.SevenForums.com/tutorials/3413-repair-install.html

    See you soon.

  • Damaged file Site Muse

    I wonder if there is some way I can repair my damaged file of the Muse site.

    Please send us the .muse file at [email protected] as well as a link to this topic for the context and we'll take a look inside. If the file is larger than 20 MB, you can use a service like Adobe SendNow, Dropbox, WeTransfer, etc.. Thank you.

  • How can I check and repair damaged or weak HD sectors?

    original title: how to check and repair damaged or weak HD sectors? (XP Home, with ntfs)  Start fails inconsistently during startup and after.

    (XP Home, with ntfs)  Often fails to start but incoherently during start-up and the poster. Sometimes after complete loading of Windows, it just turns off. Cold starting when he is not Windows it stalls after part of the desktop icons are and can take 10 minutes or more to complete the implementation of the office.

    Open the command prompt
    Type:
    Chkdsk /f /r

    Once the scan is completed (command line):
    type:
    sfc.exe/scannow

  • Windows XP does not start due to a missing or damaged file.

    When I turn on my laptop, I get this message:

    Windows didn't start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM

    You can try to repair this file by starting Windows Setup using the original Setup CD.  Select 'r' in the first screen to start repair.

    I bought this computer and has not received any documentation or the drive with him.  How can I me things in the market again?  Or how can I get my files on the HARD disk without losing any data?  Nothing works without some sort of operating system, so I can't start a CD or go on the internet with it or anything else.  Someone suggested to remove the HARD disk and connecting it to another computer via a USB cable.  I tried that but didn't have any instructions very thoroughly how to do and not to do anything.  What can I do?

    The question was preceded by a loss of power, aborted reboot or abnormal termination? (This includes the plug pulling, buttons power and removing the battery).

    These can cause corruption in the file system that must be fixed before you do anything else.

    If none of these events occurred (or even if they have not taken place), you must verify the integrity of your file system before anything else (especially "try" things).

    There is zero logic to begin to try to begin to try to modify or copy files to a hard drive that has a corrupted file system, so this must first be fixed using the XP chkdsk program and run chkdsk on your hard drives may solve your problem completely.

    Use the XP Recovery Console to check the file system on your HARD drive and fix the problems and then try to start your system - this may be all you need to do.  Or, you are welcome to just start trying things that might work.

    Boot into the Recovery Console Windows using an XP bootable installation CD.

    If you have no XP bootable media (or aren't sure you have) create a bootable XP Recovery CD of Console and do not forget.

    This is not the same as recovery disks that may have come to a store to purchase the system.

    You can make a bootable Recovery Console CD by downloading an ISO file and burn it to a CD.

    The ISO bootable image file you need to download is called:

    xp_rec_con. ISO

    Download the ISO from here:

    http://www.mediafire.com/?ueyyzfymmig

    Use a new CD and this simple and free program to burn your ISO file and create your bootable CD:

    http://www.ImgBurn.com/

    Here are some instructions for ImgBurn:

    http://Forum.ImgBurn.com/index.php?showtopic=61

    It would be a good idea to test your bootable CD on a computer running.

    You may need to adjust the computer BIOS settings to use the CD-ROM drive as the first device to boot instead of the hard drive.  These adjustments are made before Windows tries to load.  If you miss it, you will need to restart the system again.

    When you start on the CD, follow the instructions:

    Press any key to boot from CD...

    Installing Windows... going to pronounce.

    Press 'R' to enter the Recovery Console.

    Select the installation that you want to access (usually 1: C:\WINDOWS)

    You may be asked to enter the password (usually empty).

    You should be in the folder C:\WINDOWS.  It's the same as the

    C:\Windows folder that you see in Solution Explorer.

    The Recovery Console allows base as file commands: copy, rename, replace, delete, chkdsk, fixboot, fixmbr, cd, etc.

    For a list of the commands in the Recovery Console, type help at the command prompt.

    Start by checking the integrity of your file system by using the chkdsk command.

    In the command prompt window, run the chkdsk command on the drive where Windows is installed to try to fix any problems on the afflicted player.

    Running chkdsk is fine, even if he finds no problem.  It won't hurt anything to run it.

    Assuming your boot drive is C, run the following command:

    CHKDSK C: /r

    Let chkdsk finish to correct the problems, he could find.  It may take a long time for chkdsk complete or they seem to be "stuck".  Be patient.  If the HARD drive led blinks always, chkdsk is something.  Keep an eye on the amount of the percentage to be sure that it is still making progress.  It may even seem to go back sometime.

    You must run chkdsk/r again until it finds no error to correct.

    Remove the CD, and then type "exit" to exit the RC and restart the computer.

    You have not to set the BIOS to boot the disk HARD since the CD won't be.

    Do, or do not. There is no test.

    I decided to implement the points for a new puppy instead of a pony!

  • Cannot start because of missing or damaged file: \Windows\AppPatch\drvmain.sdb.

    Everything was fine when last stopped.  Then this error message.  Cannot get to anything that will open any program or allow me to run a CD.  Cannot start because of missing or damaged file: \Windows\AppPatch\drvmain.sdb.  Cannot run CHKDSK or use reinstall the CD because there is no place to run is.  Cannot get to Norton to uninstall.  Help!

    Hello

    If we can start safe mode?

    If so, we can perform Clean Boot Troubleshooting:

    http://support.Microsoft.com/kb/310353

    http://support.Microsoft.com/kb/316434

    If this isn't the case, then we might need a Windows XP CD in order to move forward.

    Let us know.

    Best regards

    Matthew_Ha

  • Windows cannot start due to a missing or damaged file

    Original title: using a NETBOOK, WINDOWS can NOT START due to a MISSING OR DAMAGED FILE

    error message. Windows\System32\Config\System

    Let me guess that your netbook from brand not specified and the model has no CD/DVD drive and you have no real media installation of XP and before the incident and during the execution of XP, your system suffered a power failure, power failure, aborted restart or an abnormal termination?

    This is not an insurmountable problem in the world today... it happens all the time in these forums.

  • Explorer Windows has stopped working. Name of the damaged file: wmp.dll

    Original title: Windows Explorer has stopped working

    There seems to be a lot of discussion on this issue.  I tired some of the patches, but some of my numbers seem different from what other people have.  The problem is on my laptop.  I try to connect to my router and have internet access.  My office is a new computer with Windows 7 installed.

    When I try to open my network center and sharing on my laptop, the computer thinks for a while, and then I get the Windows Exporer stopped working window.

    ProblemEvent name: InPageCoFire

    Error state code: c000009c

    Type of media loopholes: 00000003

    Name of the damaged file: wmp.dll

    The system version: 6.0.6002.2.2.0.768.3

    Locale ID: 4105

    Additional information 1: fd00

    Add information 2: ea6f5fe8924aaa756324d57f87834160

    Add information 3: fd00

    Add information 4: ea6f5fe8924aaa756324d57f87834160

    I am at a loss!

    Thank you

    Kevin.

    Hey Kevin,

    You will need to run the command above in the elevated command prompt.

    Refer to this step help: How to run a command with elevated privileges?

    After you run the command of high fashion, you should get the message, "" DLLRegisterServer in wmp.dll managed."

    Also, you can run the method 2 regardless of the success or failure of the method 1. Please try these methods first and see how it goes.

    Normally, it is appropriate to fix this problem by running SFC scan and you would not need to copy the file.

    Kind regards

    Shinmila H - Microsoft Support

    Visit our Microsoft answers feedback Forum and let us know what you think.

  • When I connect and the home screen appears I get this message: DLL environment initializeO-multiple Logger could damage files.

    Original title: Logger initialized O

    When I connect and the home screen appears I get this message: DLL environment initializeO-multiple Logger could damage files. What should I do? Thank you - E.Schmidt

    Hello

    1 how long have you been faced with this problem?
    2 did you recent hardware or software changes to your computer before this problem?
       
    Try to perform the clean boot on the computer.
     
    From your computer by using a minimal set of drivers and startup programs so that you can determine if a background program is interfering with your game or program. This type of boot is known as a "clean boot".
     
    Follow the steps provide in the article below to perform the clean boot. http://support.Microsoft.com/kb/929135

    Thanks and greetings
    Umesh P - Microsoft technical support.

    Visit our Microsoft answers feedback Forum and let us know what you think.
    [If this post can help solve your problem, please click the 'Mark as answer' or 'Useful' at the top of this message.] [Marking a post as answer, or relatively useful, you help others find the answer more quickly.]

  • Protection system is unable to repair the file system

    After further investigation, the corrupted file is usbhub.sys.mui

    SFC is unable to solve this problem, whenever I start windows and run SFC, I get this result "filtered for only SR entries:

    2016-08-25 15:33:01, info CSI 00000009 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:01, CSI information 0000000 transaction [SR] beginning verify and repair
    2016 08-25 15:33:01, information 0000000 c [SR] audit CSI complete
    2016-08-25 15:33:01, CSI to 0000000 d [SR] 100 audit information (0 x 0000000000000064) components
    2016-08-25 15:33:01, Info CSI 0000000e transaction [SR] beginning verify and repair
    2016 08-25 15:33:01, info CSI 00000010 [SR] verification complete
    2016-08-25 15:33:01, info CSI 00000011 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:01, transaction Info CSI 00000012 [SR] beginning verify and repair
    2016 08-25 15:33:01, info CSI 00000014 [SR] verification complete
    2016-08-25 15:33:01, info CSI 00000015 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:01, transaction Info CSI 00000016 [SR] beginning verify and repair
    2016 08-25 15:33:01, info CSI 00000018 [SR] verification complete
    2016-08-25 15:33:01, info CSI 00000019 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:01, CSI Info 0000001 a transaction [SR] beginning verify and repair
    2016 08-25 15:33:02, Info CSI 0000001 c [SR] verification complete
    2016-08-25 15:33:02, components of CSI Info 0000001 d [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:33:02, Info CSI 0000001e transaction [SR] beginning verify and repair
    2016 08-25 15:33:02, info CSI 00000020 [SR] verification complete
    2016-08-25 15:33:02, info CSI 00000021 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:02, transaction Info CSI 00000022 [SR] beginning verify and repair
    2016 08-25 15:33:02, info CSI 00000024 [SR] verification complete
    2016-08-25 15:33:02, info CSI 00000025 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:02, transaction Info CSI 00000026 [SR] beginning verify and repair
    2016 08-25 15:33:02, info CSI 00000028 [SR] verification complete
    2016-08-25 15:33:02, info CSI 00000029 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:02, CSI Info 0000002a transaction [SR] beginning verify and repair
    2016 08-25 15:33:02, Info CSI 0000002 c [SR] verification complete
    2016-08-25 15:33:02, info CSI 0000002d [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:02, Info CSI 0000002e transaction [SR] beginning verify and repair
    2016 08-25 15:33:02, info CSI 00000030 [SR] verification complete
    2016-08-25 15:33:02, info CSI 00000031 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:02, transaction Info CSI 00000032 [SR] beginning verify and repair
    2016 08-25 15:33:03, info CSI 00000034 [SR] verification complete
    2016-08-25 15:33:03, info CSI 00000035 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:03, transaction Info CSI 00000036 [SR] beginning verify and repair
    2016 08-25 15:33:03, info CSI 00000038 [SR] verification complete
    2016-08-25 15:33:03, info CSI 00000039 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:03, CSI Info 0000003a transaction [SR] beginning verify and repair
    2016 08-25 15:33:03, CSI Info 0000003 c [SR] verification complete
    2016-08-25 15:33:03, info CSI 0000003d [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:03, Info CSI 0000003e transaction [SR] beginning verify and repair
    2016 08-25 15:33:04, info CSI 00000040 [SR] verification complete
    2016-08-25 15:33:04, info CSI 00000041 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:04, transaction Info CSI 00000042 [SR] beginning verify and repair
    2016 08-25 15:33:04, info CSI 00000044 [SR] verification complete
    2016-08-25 15:33:04, info CSI 00000045 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:04, Info CSI 00000046 [SR] beginning verify and repair
    2016 08-25 15:33:04, info CSI 00000048 [SR] verification complete
    2016-08-25 15:33:04, info CSI 00000049 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:04, CSI Info 0000004a transaction [SR] beginning verify and repair
    2016 08-25 15:33:04, CSI Info 0000004 c [SR] verification complete
    2016-08-25 15:33:04, components of CSI Info 0000004 d [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:33:04, Info CSI 0000004e transaction [SR] beginning verify and repair
    2016 08-25 15:33:04, info CSI 00000050 [SR] verification complete
    2016-08-25 15:33:05, info CSI 00000051 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:05, the transaction Info CSI 00000052 [SR] beginning verify and repair
    2016 08-25 15:33:05, info CSI 00000054 [SR] verification complete
    2016-08-25 15:33:05, info CSI 00000055 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:05, the transaction Info CSI 00000056 [SR] beginning verify and repair
    2016 08-25 15:33:05, info CSI 00000058 [SR] verification complete
    2016-08-25 15:33:05, info CSI 00000059 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:05, CSI Info 0000005a transaction [SR] beginning verify and repair
    2016-08-25 15:33:06, CSI Info 0000005 c [SR] full check
    2016-08-25 15:33:06, components of CSI Info 0000005 d [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:33:06, Info CSI 0000005e transaction [SR] beginning verify and repair
    2016 08-25 15:33:06, info CSI 00000060 [SR] verification complete
    2016-08-25 15:33:06, info CSI 00000061 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:06, transaction Info CSI 00000062 [SR] beginning verify and repair
    2016 08-25 15:33:06, info CSI 00000064 [SR] verification complete
    2016-08-25 15:33:06, info CSI 00000065 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:06, transaction Info CSI 00000066 [SR] beginning verify and repair
    2016 08-25 15:33:07, info CSI 00000069 [SR] verification complete
    2016-08-25 15:33:07, CSI Info 0000006 components [SR] a check 100 (0 x 0000000000000064)
    2016-08-25 15:33:07, CSI Info 0000006b transaction [SR] beginning verify and repair
    2016 08-25 15:33:08, CSI Info 0000006f Verify [SR] full
    2016-08-25 15:33:08, info CSI 00000070 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:08, transaction Info CSI 00000071 [SR] beginning verify and repair
    2016 08-25 15:33:09, info CSI 00000074 [SR] verification complete
    2016-08-25 15:33:09, info CSI 00000075 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:09, transaction Info CSI 00000076 [SR] beginning verify and repair
    2016 08-25 15:33:10, info CSI 00000079 [SR] verification complete
    2016-08-25 15:33:10, CSI Info 0000007 components [SR] a check 100 (0 x 0000000000000064)
    2016-08-25 15:33:10, CSI Info 0000007 b transaction [SR] beginning verify and repair
    2016 08-25 15:33:11, Info CSI 0000007 d [SR] verification complete
    2016-08-25 15:33:11, CSI 0000007e Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:11, CSI Info 0000007f transaction [SR] beginning verify and repair
    2016-08-25 15:33:13, 000000 a 4 CSI Info [SR] verification complete
    2016-08-25 15:33:13, 000000 to 5 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:13, 000000 a 6 CSI Info transaction [SR] beginning verify and repair
    2016-08-25 15:33:14, a 000000, 8 CSI Info [SR] verification complete
    2016-08-25 15:33:14, 000000 a 9 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:14, 000000aa CSI Info transaction [SR] beginning verify and repair
    2016-08-25 15:33:15, 000000ac CSI Info [SR] verification complete
    2016-08-25 15:33:15, 000000ad CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:15, 000000ae CSI Info transaction [SR] beginning verify and repair
    2016-08-25 15:33:16, 000000 b 0 CSI Info [SR] verification complete
    2016-08-25 15:33:16, 000000 b 1 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:16, 000000 b 2 CSI Info transaction [SR] beginning verify and repair
    2016-08-25 15:33:16, 000000 b 4 CSI Info [SR] verification complete
    2016-08-25 15:33:16, 000000 b 5 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:16, 000000 b 6 CSI Info transaction [SR] beginning verify and repair
    2016-08-25 15:33:18, CSI Info 000000 d 9 [SR] check all the
    2016-08-25 15:33:18, 000000da CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:18, 000000db CSI Info transaction [SR] beginning verify and repair
    2016-08-25 15:33:19, 000000dd CSI Info [SR] verification complete
    2016-08-25 15:33:19, CSI 000000de [SR] components Info check 100 (0 x 0000000000000064)
    2016-08-25 15:33:19, CSI Info 000000df transaction [SR] beginning verify and repair
    2016-08-25 15:33:23, 000000e1 CSI Info [SR] verification complete
    2016-08-25 15:33:23, 000000e2 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:23, CSI Info 000000e3 transaction [SR] beginning verify and repair
    2016-08-25 15:33:24, 000000e7 CSI Info [SR] verification complete
    2016-08-25 15:33:24, CSI Info [SR] 000000e8 components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:24, 000000e9 CSI Info transaction [SR] beginning verify and repair
    2016-08-25 15:33:24, 000000eb CSI Info [SR] verification complete
    2016-08-25 15:33:24, CSI Info [SR] 000000ec components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:24, CSI Info 000000ed transaction [SR] beginning verify and repair
    2016-08-25 15:33:24, 000000ef CSI Info [SR] verification complete
    2016-08-25 15:33:24, CSI Info [SR] 000000f0 components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:24, 000000f1 CSI Info transaction [SR] beginning verify and repair
    2016-08-25 15:33:25, 000000f3 CSI Info [SR] verification complete
    2016-08-25 15:33:25, 000000f4 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:25, 000000f5 CSI Info transaction [SR] beginning verify and repair
    2016 08-25 15:33:28, info CSI 00000108 [SR] verification complete
    2016-08-25 15:33:28, info CSI 00000109 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:28, CSI Info 0000010a transaction [SR] beginning verify and repair
    2016 08-25 15:33:28, CSI Info 0000010 c [SR] verification complete
    2016-08-25 15:33:28, components of CSI Info 0000010 d [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:33:28, Info CSI 0000010e transaction [SR] beginning verify and repair
    2016 08-25 15:33:29, info CSI 00000110 [SR] verification complete
    2016-08-25 15:33:29, info CSI 00000111 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:29, Info CSI 00000112 [SR] beginning verify and repair
    2016 08-25 15:33:29, info CSI 00000114 [SR] verification complete
    2016-08-25 15:33:29, info CSI 00000115 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:29, transaction Info CSI 00000116 [SR] beginning verify and repair
    2016 08-25 15:33:30, info CSI 00000119 [SR] verification complete
    2016-08-25 15:33:30, CSI Info 0000011 components [SR] a check 100 (0 x 0000000000000064)
    2016-08-25 15:33:30, CSI Info 0000011b transaction [SR] beginning verify and repair
    2016 08-25 15:33:32, CSI Info 0000011 d [SR] verification complete
    2016-08-25 15:33:32, CSI 0000011e [SR] Info components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:32, CSI Info 0000011f transaction [SR] beginning verify and repair
    2016 08-25 15:33:33, info CSI 00000121 [SR] verification complete
    2016-08-25 15:33:33, info CSI 00000122 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:33, transaction Info CSI 00000123 [SR] beginning verify and repair
    2016 08-25 15:33:33, info CSI 00000125 [SR] verification complete
    2016-08-25 15:33:33, info CSI 00000126 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:33, transaction Info CSI 00000127 [SR] beginning verify and repair
    2016-08-25 15:33:34, Info CSI 00000129 [SR] full check
    2016-08-25 15:33:34, CSI Info 0000012 components [SR] a check 100 (0 x 0000000000000064)
    2016-08-25 15:33:34, CSI Info 0000012b transaction [SR] beginning verify and repair
    2016-08-25 15:33:35, Info CSI 0000012d [SR] full check
    2016-08-25 15:33:35, CSI 0000012e [SR] Info components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:35, CSI Info 0000012f transaction [SR] beginning verify and repair
    2016 08-25 15:33:36, info CSI 00000131 [SR] verification complete
    2016-08-25 15:33:36, info CSI 00000132 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:36, transaction Info CSI 00000133 [SR] beginning verify and repair
    2016-08-25 15:33:39, CSI Info 0000014b Verify [SR] full
    2016-08-25 15:33:39, components of CSI Info 0000014 c [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:33:39, Info CSI 0000014 d [SR] beginning verify and repair transaction
    2016 08-25 15:33:40, Info CSI 0000014f [SR] Verify complete
    2016-08-25 15:33:40, 00000150 CSI info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:40, transaction Info CSI 00000151 [SR] beginning verify and repair
    2016 08-25 15:33:44, info CSI 00000153 [SR] verification complete
    2016-08-25 15:33:44, info CSI 00000154 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:44, transaction Info CSI 00000155 [SR] beginning verify and repair
    2016-08-25 15:33:45, Info CSI 00000157 [SR] check complete
    2016-08-25 15:33:45, info CSI 00000158 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:45, Info CSI 00000159 [SR] beginning verify and repair
    2016-08-25 15:33:46, CSI Info 0000015b Verify [SR] full
    2016-08-25 15:33:46, components of CSI Info 0000015 c [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:33:46, CSI Info 0000015 d [SR] beginning verify and repair transaction
    2016 08-25 15:33:47, Info CSI 0000015f [SR] Verify complete
    2016-08-25 15:33:47, info CSI 00000160 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:47, Info CSI 00000161 [SR] beginning verify and repair
    2016 08-25 15:33:48, info CSI 00000163 [SR] verification complete
    2016-08-25 15:33:48, info CSI 00000164 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:48, Info CSI 00000165 [SR] beginning verify and repair
    2016 08-25 15:33:49, info CSI 00000169 [SR] verification complete
    2016-08-25 15:33:49, CSI Info 0000016 components [SR] a check 100 (0 x 0000000000000064)
    2016-08-25 15:33:49, CSI Info 0000016b transaction [SR] beginning verify and repair
    2016 08-25 15:33:49, Info CSI 0000016 d [SR] verification complete
    2016-08-25 15:33:49, CSI 0000016e [SR] Info components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:49, CSI Info 0000016f transaction [SR] beginning verify and repair
    2016 08-25 15:33:53, info CSI 00000171 [SR] verification complete
    2016-08-25 15:33:53, info CSI 00000172 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:53, transaction Info CSI 00000173 [SR] beginning verify and repair
    2016 08-25 15:33:54, info CSI 00000176 [SR] verification complete
    2016-08-25 15:33:54, info CSI 00000177 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:54, transaction Info CSI 00000178 [SR] beginning verify and repair
    2016-08-25 15:33:55, CSI Info 0000017b Verify [SR] full
    2016-08-25 15:33:55, components of CSI Info 0000017 c [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:33:55, CSI Info 0000017 d [SR] beginning verify and repair transaction
    2016 08-25 15:33:56, Info CSI 0000017f [SR] Verify complete
    2016-08-25 15:33:56, info CSI 00000180 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:56, transaction Info CSI 00000181 [SR] beginning verify and repair
    2016 08-25 15:33:58, info CSI 00000184 [SR] verification complete
    2016-08-25 15:33:58, info CSI 00000185 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:58, transaction Info CSI 00000186 [SR] beginning verify and repair
    2016 08-25 15:33:59, info CSI 00000188 [SR] verification complete
    2016-08-25 15:33:59, info CSI 00000189 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:33:59, CSI Info 0000018a transaction [SR] beginning verify and repair
    2016 08-25 15:33:59, CSI Info 0000018 c [SR] verification complete
    2016-08-25 15:33:59, components of CSI Info 0000018 d [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:33:59, Info CSI 0000018e transaction [SR] beginning verify and repair
    2016-08-25 15:34, Info CSI 00000191 [SR] full check
    2016-08-25 15:34, Info CSI 00000192 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34, transaction Info CSI 00000193 [SR] beginning verify and repair
    2016 08-25 15:34:01, info CSI 00000195 [SR] verification complete
    2016-08-25 15:34:01, info CSI 00000196 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:01, Info CSI 00000197 [SR] beginning verify and repair
    2016 08-25 15:34:02, info CSI 00000199 [SR] verification complete
    2016-08-25 15:34:02, CSI Info 0000019 components [SR] a check 100 (0 x 0000000000000064)
    2016-08-25 15:34:02, CSI Info 0000019b transaction [SR] beginning verify and repair
    2016-08-25 15:34:03, Info CSI 0000019e [SR] full Verify
    2016-08-25 15:34:03, CSI 0000019f [SR] components Info check 100 (0 x 0000000000000064)
    2016-08-25 15:34:03, CSI Info 000001 a 0 transaction [SR] beginning verify and repair
    2016-08-25 15:34:04, 000001 has 3 CSI Info [SR] full audit
    2016-08-25 15:34:04, 000001 has 4 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:04, CSI Info 000001 has 5 transaction [SR] beginning verify and repair
    2016-08-25 15:34:05, 000001 has 8 CSI Info [SR] full audit
    2016-08-25 15:34:05, 000001 has 9 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:05, CSI Info 000001aa transaction [SR] beginning verify and repair
    2016-08-25 15:34:07, 000001ac CSI Info [SR] verification complete
    2016-08-25 15:34:07, 000001ad CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:07, CSI Info 000001ae transaction [SR] beginning verify and repair
    2016-08-25 15:34:08, 000001 b 0 CSI Info [SR] full audit
    2016-08-25 15:34:08, 000001 b 1 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:08, CSI Info 000001 b 2 transaction [SR] beginning verify and repair
    2016-08-25 15:34:08, 000001 b 4 CSI Info [SR] full audit
    2016-08-25 15:34:08, 000001 b 5 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:08, CSI Info 000001 b 6 transaction [SR] beginning verify and repair
    2016-08-25 15:34:09, 000001 b 8 CSI Info [SR] full audit
    2016-08-25 15:34:09, 000001 b 9 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:09, CSI Info 000001ba transaction [SR] beginning verify and repair
    2016-08-25 15:34:10, 000001bc CSI Info [SR] verification complete
    2016-08-25 15:34:10, 000001bd CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:10, CSI Info 000001be transaction [SR] beginning verify and repair
    2016-08-25 15:34:11, CSI Info 000001 c 0 [SR] check all the
    2016-08-25 15:34:11, CSI Info 000001 c 1 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:11, CSI Info 000001 c 2 [SR] beginning operation check and repair
    2016-08-25 15:34:12, CSI Info 000001 c 4 [SR] check all the
    2016-08-25 15:34:12, CSI Info 000001 c 5 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:12, CSI Info 000001 c 6 [SR] beginning operation check and repair
    2016-08-25 15:34:12, CSI Info 000001 c 8 [SR] check all the
    2016-08-25 15:34:12, CSI Info 000001 c 9 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:12, CSI Info 000001 ca transaction [SR] beginning verify and repair
    2016-08-25 15:34:13, 000001cc CSI Info [SR] verification complete
    2016-08-25 15:34:13, components of CSI Info 000001 cd [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:34:13, CSI Info 000001ce transaction [SR] beginning verify and repair
    2016-08-25 15:34:18, CSI Info 000001 d 0 [SR] check all the
    2016-08-25 15:34:18, CSI Info 000001 d 1 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:18, CSI Info 000001 d 2 [SR] beginning operation check and repair
    2016-08-25 15:34:19, CSI Info 000001 d 4 [SR] check all the
    2016-08-25 15:34:19, CSI Info 000001 d 5 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:19, CSI Info 000001 d 6 [SR] beginning operation check and repair
    2016-08-25 15:34:19, CSI Info 000001 d 8 [SR] check all the
    2016-08-25 15:34:20, CSI Info 000001 d 9 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:20, 000001da CSI Info transaction [SR] beginning verify and repair
    2016-08-25 15:34:20, 000001dc CSI Info [SR] verification complete
    2016-08-25 15:34:20, 000001dd CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:20, 000001de CSI Info transaction [SR] beginning verify and repair
    2016 08-25 15:34:20, Info CSI 000001e0 [SR] Verify complete
    2016-08-25 15:34:21, 000001e1 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:21, 000001e2 CSI Info transaction [SR] beginning verify and repair
    2016-08-25 15:34:21, 000001e4 CSI Info [SR] repair corrupted file [ml:520 {260}, l:74 {37}] '------? \C:\Windows\system32\drivers\en-us"\[l:28{14}]"Usbhub.sys.MUI' of the store
    2016-08-25 15:34:21, 000001e7 CSI Info [SR] repair corrupted file [ml:520 {260}, l:74 {37}] '------? \C:\Windows\system32\drivers\en-us"\[l:28{14}]"Usbhub.sys.MUI' of the store
    2016-08-25 15:34:21, 000001ea CSI Info [SR] verification complete
    2016-08-25 15:34:21, 000001eb CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:21, 000001ec CSI Info transaction [SR] beginning verify and repair
    2016 08-25 15:34:22, 000001ee CSI Info [SR] verification complete
    2016-08-25 15:34:22, 000001ef CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:22, 000001f0 CSI Info transaction [SR] beginning verify and repair
    2016-08-25 15:34:23, 000001f8 CSI Info [SR] verification complete
    2016-08-25 15:34:24, 000001f9 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:24, 000001fa CSI Info transaction [SR] beginning verify and repair
    2016 08-25 15:34:24, CSI Info 000001 fc [SR] verification complete
    2016-08-25 15:34:24, 000001fd CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:24, 000001fe CSI Info transaction [SR] beginning verify and repair
    2016 08-25 15:34:25, info CSI 00000200 [SR] verification complete
    2016-08-25 15:34:25, 00000201 CSI info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:25, transaction Info CSI 00000202 [SR] beginning verify and repair
    2016-08-25 15:34:25, Info CSI 00000204 [SR] check complete
    2016-08-25 15:34:25, 00000205 CSI info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:25, transaction Info CSI 00000206 [SR] beginning verify and repair
    2016 08-25 15:34:27, info CSI 00000208 [SR] verification complete
    2016-08-25 15:34:27, info CSI 00000209 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:27, CSI Info 0000020a transaction [SR] beginning verify and repair
    2016 08-25 15:34:28, CSI Info 0000020 c [SR] verification complete
    2016-08-25 15:34:28, components of CSI Info 0000020 d [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:34:28, Info CSI 0000020e transaction [SR] beginning verify and repair
    2016 08-25 15:34:28, info CSI 00000210 [SR] verification complete
    2016-08-25 15:34:28, info CSI 00000211 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:28, transaction Info CSI 00000212 [SR] beginning verify and repair
    2016 08-25 15:34:30, info CSI 00000215 [SR] verification complete
    2016-08-25 15:34:30, info CSI 00000216 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:30, Info CSI 00000217 [SR] beginning verify and repair
    2016-08-25 15:34:32, CSI Info 0000021b Verify [SR] full
    2016-08-25 15:34:32, components of CSI Info 0000021 c [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:34:32, CSI Info 0000021 d [SR] beginning verify and repair transaction
    2016 08-25 15:34:33, info CSI 00000222 [SR] verification complete
    2016-08-25 15:34:33, info CSI 00000223 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:33, transaction Info CSI 00000224 [SR] beginning verify and repair
    2016-08-25 15:34:34, Info CSI 00000231 [SR] full check
    2016-08-25 15:34:34, Info CSI 00000232 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:34, transaction Info CSI 00000233 [SR] beginning verify and repair
    2016-08-25 15:34:36, CSI Info 0000023a Verify [SR] full
    2016-08-25 15:34:36, CSI Info 0000023 components [SR] b check 100 (0 x 0000000000000064)
    2016-08-25 15:34:36, CSI Info 0000023 c [SR] beginning verify and repair operation
    2016-08-25 15:34:37, Info CSI 0000023e [SR] full Verify
    2016-08-25 15:34:37, CSI 0000023f [SR] components Info check 100 (0 x 0000000000000064)
    2016-08-25 15:34:37, transaction Info CSI 00000240 [SR] beginning verify and repair
    2016 08-25 15:34:38, info CSI 00000244 [SR] verification complete
    2016-08-25 15:34:38, info CSI 00000245 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:38, Info CSI 00000246 [SR] beginning verify and repair
    2016 08-25 15:34:38, info CSI 00000248 [SR] verification complete
    2016-08-25 15:34:38, info CSI 00000249 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:38, CSI Info 0000024a transaction [SR] beginning verify and repair
    2016 08-25 15:34:40, Info CSI 0000026f [SR] Verify complete
    2016-08-25 15:34:40, info CSI 00000270 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:40, transaction Info CSI 00000271 [SR] beginning verify and repair
    2016-08-25 15:34:41, Info CSI 00000273 [SR] check complete
    2016-08-25 15:34:41, 00000274 CSI info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:41, transaction Info CSI 00000275 [SR] beginning verify and repair
    2016-08-25 15:34:41, Info CSI 00000277 [SR] check complete
    2016-08-25 15:34:42, info CSI 00000278 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:42, transaction Info CSI 00000279 [SR] beginning verify and repair
    2016-08-25 15:34:42, CSI Info 0000027b Verify [SR] full
    2016-08-25 15:34:42, components of CSI Info 0000027 c [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:34:42, Info CSI 0000027 d [SR] beginning verify and repair transaction
    2016-08-25 15:34:43, CSI Info 0000028b Verify [SR] full
    2016-08-25 15:34:43, components of CSI Info 0000028 c [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:34:43, CSI Info 0000028 d [SR] beginning verify and repair transaction
    2016 08-25 15:34:43, info CSI 00000292 [SR] verification complete
    2016-08-25 15:34:44, info CSI 00000293 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:44, transaction Info CSI 00000294 [SR] beginning verify and repair
    2016 08-25 15:34:45, Info CSI 0000029f [SR] Verify complete
    2016-08-25 15:34:45, 000002 a 0 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:45, CSI Info 000002 a-1 transaction [SR] beginning verify and repair
    2016-08-25 15:34:45, 000002 a 3 CSI Info [SR] verification complete
    2016-08-25 15:34:45, 000002 a 4 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:45, CSI Info 000002a 5 transaction [SR] beginning verify and repair
    2016-08-25 15:34:47, 000002 a 7 CSI Info [SR] verification complete
    2016-08-25 15:34:47, 000002 a 8 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:47, CSI Info 000002a 9 transaction [SR] beginning verify and repair
    2016-08-25 15:34:47, 000002ab CSI Info [SR] verification complete
    2016-08-25 15:34:47, 000002ac CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:47, CSI Info 000002ad transaction [SR] beginning verify and repair
    2016-08-25 15:34:48, 000002af CSI Info [SR] verification complete
    2016-08-25 15:34:48, 000002 b 0 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:48, CSI Info 000002b 1 transaction [SR] beginning verify and repair
    2016-08-25 15:34:48, 000002 b 3 CSI Info [SR] verification complete
    2016-08-25 15:34:48, 000002 b 4 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:48, CSI Info 000002b 5 transaction [SR] beginning verify and repair
    2016-08-25 15:34:49, 000002 b 7 CSI Info [SR] verification complete
    2016-08-25 15:34:49, 000002 b 8 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:49, CSI Info 000002b 9 transaction [SR] beginning verify and repair
    2016-08-25 15:34:51, CSI Info 000002 d 3 [SR] check all the
    2016-08-25 15:34:51, CSI Info 000002 d 4 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:51, CSI Info 000002 d 5 [SR] beginning operation check and repair
    2016-08-25 15:34:55, CSI Info 000002 d 7 [SR] check all the
    2016-08-25 15:34:55, CSI Info 000002 d 8 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:55, CSI Info 000002 d 9 [SR] beginning operation check and repair
    2016-08-25 15:34:56, 000002db CSI Info [SR] verification complete
    2016-08-25 15:34:56, 000002dc CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:56, CSI Info 000002dd transaction [SR] beginning verify and repair
    2016-08-25 15:34:57, 000002df CSI Info [SR] verification complete
    2016-08-25 15:34:57, CSI Info 000002e0 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:57, CSI Info 000002e1 transaction [SR] beginning verify and repair
    2016-08-25 15:34:57, 000002e5 CSI Info [SR] verification complete
    2016-08-25 15:34:57, Info CSI [SR] 000002e6 components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:57, CSI Info 000002e7 transaction [SR] beginning verify and repair
    2016-08-25 15:34:58, 000002e9 CSI Info [SR] verification complete
    2016-08-25 15:34:58, 000002ea CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:58, CSI Info 000002eb transaction [SR] beginning verify and repair
    2016-08-25 15:34:59, 000002ed CSI Info [SR] verification complete
    2016-08-25 15:34:59, 000002ee CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:59, CSI Info 000002ef transaction [SR] beginning verify and repair
    2016-08-25 15:34:59, 000002f1 CSI Info [SR] verification complete
    2016-08-25 15:34:59, 000002f2 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:34:59, CSI Info 000002f3 transaction [SR] beginning verify and repair
    2016-08-25 15:35, 000002f6 CSI Info [SR] verification complete
    2016-08-25 15:35, 000002f7 CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:35, CSI Info 000002f8 transaction [SR] beginning verify and repair
    2016-08-25 15:35:01, 000002fa CSI Info [SR] verification complete
    2016-08-25 15:35:01, 000002fb CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:35:01, CSI Info 000002 fc [SR] beginning verify and repair operation
    2016-08-25 15:35:02, 000002fe CSI Info [SR] verification complete
    2016-08-25 15:35:02, 000002ff CSI Info [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:35:02, transaction Info CSI 00000300 [SR] beginning verify and repair
    2016 08-25 15:35:02, info CSI 00000302 [SR] verification complete
    2016-08-25 15:35:02, info CSI 00000303 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:35:02, Info CSI 00000304 [SR] beginning verify and repair
    2016 08-25 15:35:03, info CSI 00000307 [SR] verification complete
    2016-08-25 15:35:03, info CSI 00000308 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:35:03, Info CSI 00000309 [SR] beginning verify and repair
    2016-08-25 15:35:04, CSI Info 0000030b Verify [SR] full
    2016-08-25 15:35:04, components of CSI Info 0000030 c [SR] 100 audit (0 x 0000000000000064)
    2016-08-25 15:35:04, CSI Info 0000030 d [SR] beginning verify and repair transaction
    2016 08-25 15:35:05, Info CSI 0000030f [SR] Verify complete
    2016-08-25 15:35:05, info CSI 00000310 [SR] components check 100 (0 x 0000000000000064)
    2016-08-25 15:35:05, the transaction Info CSI 00000311 [SR] beginning verify and repair
    2016 08-25 15:35:06, info CSI 00000313 [SR] verification complete
    2016-08-25 15:35:06, info CSI 00000314 [SR] components check 71 (0 x 0000000000000047)
    2016-08-25 15:35:06, transaction Info CSI 00000315 [SR] beginning verify and repair
    2016 08-25 15:35:06, info CSI 00000317 [SR] verification complete
    2016-08-25 15:35:06, info CSI 00000318 [SR] repair 2 components
    2016-08-25 15:35:06, transaction Info CSI 00000319 [SR] beginning verify and repair
    2016-08-25 15:35:06, CSI 0000031b [SR] repair corrupt file Info [ml:520 {260}, l:74 {37}] '------? \C:\Windows\system32\drivers\en-us"\[l:28{14}]"Usbhub.sys.MUI' of the store
    2016 08-25 15:35:06, CSI 0000031e Info [SR] repair complete
    2016-08-25 15:35:06, CSI 0000031f [SR] Committing transaction Info
    2016 08-25 15:35:06, info CSI 00000323 [SR] check and complete repair operation. All of the files and registry keys listed in this operation were repaired successfully

    Well Yes, if its been properly repaired, why do I need the 'fix' after every start?

    Hello

    Please try to run the DISM to correct the error.  Please follow the steps in this link.

    Otherwise, you can do System Restore to restore your computer to its previous state before this error occurs. Remember to backup your files before performing this step.

    If you need assistance, please do not hesitate to contact us.

    Kind regards.

Maybe you are looking for

  • PWM rise/fall detection

    Hello I am programming a read a di in FPGA (OR 9425) PWM, this card does not accept the methods of fpga, so I need to find a way to detect what she up and down, so I can check the tick in which took place with a sequence structure this ascent/descent

  • munmap network drive on ICB

    Hi all Inside a CVI 8.1.1 program, I needed to find out if a logical drive letter, hides a network drive mapped or not. For example, I would like to know if f:\mydir is really a directory of my drive hard f: or if it is \\server\mydir (where \\server

  • My Windows Mail crashes when I get a Facebook notification.

    original title: Windows Mail & Facebook My Windows mail crashes whenever I hear from Facebook. Any ideas? Thank you!

  • I am trying to access my Gmail account, but all of a sudden, it won't open.

    Original title: Sudden Mail problem I am trying to access my Gmail account, but all of a sudden, it won't open.  The search bar flashes back to this--> https://Accounts.google.com/ServiceLogin?service=mail&passive=true&RM=false&continue= this--> is h

  • Failed to start after installation ripple 0.9.1

    I'm new to Blackberry Webworks development (working on my first Playbook application).  I am currently installing the tools and SDKs.  When I try to start waving after installation I get a Windows error "Application failed to initialize...". » I'm on