daveguitaruno Contributor Joined May 1, 2019 Posts 103 Location United Kingdom Jun 17, 2019 #121 SFCFix version 3.0.2.1 by niemiro. Start time: 2019-06-17 21:20:11.843 Microsoft Windows 7 Service Pack 1 - amd64 Using .txt script file at C:\Users\Dave\Desktop\SFCFix.txt [0] RegistryScript:: Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~pt-PT~0.0.0.0. WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~pt-PT~0.0.0.0. Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~pt-PT~0.0.0.0. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~pt-PT~0.0.0.0. RegistryScript:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 58 datablocks. Finish time: 2019-06-17 21:20:12.185 Script hash: ccXgBcElNuOQMcd+7GM3Wv7STyLQbnRyIFat/BKZrKU= ----------------------EOF-----------------------
SFCFix version 3.0.2.1 by niemiro. Start time: 2019-06-17 21:20:11.843 Microsoft Windows 7 Service Pack 1 - amd64 Using .txt script file at C:\Users\Dave\Desktop\SFCFix.txt [0] RegistryScript:: Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~pt-PT~0.0.0.0. WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~pt-PT~0.0.0.0. Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~pt-PT~0.0.0.0. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~pt-PT~0.0.0.0. RegistryScript:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 58 datablocks. Finish time: 2019-06-17 21:20:12.185 Script hash: ccXgBcElNuOQMcd+7GM3Wv7STyLQbnRyIFat/BKZrKU= ----------------------EOF-----------------------
SleepyDude Windows Update Moderator, Security Analyst Staff member Joined Dec 20, 2013 Posts 3,061 Location Portugal Jun 17, 2019 #122 The chkdsk result looks ok! Run SURT one last time I think it should be clean now.
daveguitaruno Contributor Joined May 1, 2019 Posts 103 Location United Kingdom Jun 17, 2019 #123 ================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2019-06-17 21:25 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-foundation_31bf3856ad364e35_6.1.7601.17514_none_3e8cb52f886c2db2.manifest amd64_microsoft-windows-foundation_31bf3856ad364e35_6.1.7601.17514_none_3e8cb52f886c2db2 (fix) CSI Manifest Failed Catalog Check CSI File Replaced File: amd64_microsoft-windows-foundation_31bf3856ad364e35_6.1.7601.17514_none_3e8cb52f886c2db2.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-neutralcab-v2.cab (f) CSI Payload File Corrupt 0x00000000 cmiadapter.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b Summary: Seconds executed: 547 Found 2 errors Fixed 1 errors CSI Manifest Failed Catalog Check Total count: 1 Fixed: CSI Manifest Failed Catalog Check. Total count: 1 CSI Payload File Corrupt Total count: 1 Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2019-06-17 21:25 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-foundation_31bf3856ad364e35_6.1.7601.17514_none_3e8cb52f886c2db2.manifest amd64_microsoft-windows-foundation_31bf3856ad364e35_6.1.7601.17514_none_3e8cb52f886c2db2 (fix) CSI Manifest Failed Catalog Check CSI File Replaced File: amd64_microsoft-windows-foundation_31bf3856ad364e35_6.1.7601.17514_none_3e8cb52f886c2db2.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-neutralcab-v2.cab (f) CSI Payload File Corrupt 0x00000000 cmiadapter.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b Summary: Seconds executed: 547 Found 2 errors Fixed 1 errors CSI Manifest Failed Catalog Check Total count: 1 Fixed: CSI Manifest Failed Catalog Check. Total count: 1 CSI Payload File Corrupt Total count: 1 Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.
daveguitaruno Contributor Joined May 1, 2019 Posts 103 Location United Kingdom Jun 17, 2019 #124 BTW, what is your opinion on what I said in #106?
SleepyDude Windows Update Moderator, Security Analyst Staff member Joined Dec 20, 2013 Posts 3,061 Location Portugal Jun 18, 2019 #125 I don't think the Advanced Format is the problem, you can check if you have KB982018 installed, I have it on my machine and I don't remember to manually install the update it was offered by Windows Update. SURT found a missing/corrupted file that we need to replace. SFCFix Script !!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems... Download SFCFix.exe (by Niemiro) and save it to the Desktop Download the file SFCFIX.ZIP, attached below, and save this to your Desktop On your Desktop, make sure you have the two files: SFCFix.exe and SFCFIX.zip Drag the file SFCFIX.zip onto the file SFCFix.exe and release it The SFCFix tool will process the script Upon completion, a log file SFCFix.txt should be created on your Desktop Open the SFCFix.txt log and copy & paste the contents to your post You have an old backup that passes the Acronis validation, right? How about restoring from the backup only the system partition? Attachments SFCFix.zip 7.2 MB · Views: 2
I don't think the Advanced Format is the problem, you can check if you have KB982018 installed, I have it on my machine and I don't remember to manually install the update it was offered by Windows Update. SURT found a missing/corrupted file that we need to replace. SFCFix Script !!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems... Download SFCFix.exe (by Niemiro) and save it to the Desktop Download the file SFCFIX.ZIP, attached below, and save this to your Desktop On your Desktop, make sure you have the two files: SFCFix.exe and SFCFIX.zip Drag the file SFCFIX.zip onto the file SFCFix.exe and release it The SFCFix tool will process the script Upon completion, a log file SFCFix.txt should be created on your Desktop Open the SFCFix.txt log and copy & paste the contents to your post You have an old backup that passes the Acronis validation, right? How about restoring from the backup only the system partition?
daveguitaruno Contributor Joined May 1, 2019 Posts 103 Location United Kingdom Jun 19, 2019 #126 Hey SleepyDude SleepyDude said: You have an old backup that passes the Acronis validation, right? Click to expand... SleepyDude said: How about restoring from the backup only the system partition? Click to expand... That's a great idea, I'll try this out tonight when I get back home
Hey SleepyDude SleepyDude said: You have an old backup that passes the Acronis validation, right? Click to expand... SleepyDude said: How about restoring from the backup only the system partition? Click to expand... That's a great idea, I'll try this out tonight when I get back home
daveguitaruno Contributor Joined May 1, 2019 Posts 103 Location United Kingdom Jun 19, 2019 #127 Here's the sfcfix.txt and here's the CheckSUR Attachments SFCFix.txt 62.4 KB · Views: 1 CheckSUR.log 1.2 KB · Views: 2
SleepyDude Windows Update Moderator, Security Analyst Staff member Joined Dec 20, 2013 Posts 3,061 Location Portugal Jun 20, 2019 #128 Hi, SURT found more to fix... SFCFix Script !!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems... Download SFCFix.exe (by Niemiro) and save it to the Desktop Download the file SFCFIX.ZIP, attached below, and save this to your Desktop On your Desktop, make sure you have the two files: SFCFix.exe and SFCFIX.zip Drag the file SFCFIX.zip onto the file SFCFix.exe and release it The SFCFix tool will process the script Upon completion, a log file SFCFix.txt should be created on your Desktop Open the SFCFix.txt log and copy & paste the contents to your post Attachments SFCFix.zip 5.5 MB · Views: 3
Hi, SURT found more to fix... SFCFix Script !!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems... Download SFCFix.exe (by Niemiro) and save it to the Desktop Download the file SFCFIX.ZIP, attached below, and save this to your Desktop On your Desktop, make sure you have the two files: SFCFix.exe and SFCFIX.zip Drag the file SFCFIX.zip onto the file SFCFix.exe and release it The SFCFix tool will process the script Upon completion, a log file SFCFix.txt should be created on your Desktop Open the SFCFix.txt log and copy & paste the contents to your post
daveguitaruno Contributor Joined May 1, 2019 Posts 103 Location United Kingdom Jun 20, 2019 #129 Hi SleepyDude, I did a boot scan yesterday but it didn't detect any viruses. These corruptions seem suspicious to me, it's like the system is fighting back. Here's my latest log file and SURT log Attachments SFCFix.txt 63.7 KB · Views: 1 CheckSUR.log 36.3 KB · Views: 1
Hi SleepyDude, I did a boot scan yesterday but it didn't detect any viruses. These corruptions seem suspicious to me, it's like the system is fighting back. Here's my latest log file and SURT log
SleepyDude Windows Update Moderator, Security Analyst Staff member Joined Dec 20, 2013 Posts 3,061 Location Portugal Jun 20, 2019 #130 Hi, In some situations SURT stops on the first errors it finds and only when those are resolved continues doing more checking... The errors related with avast can be ignored. Run also SFC /scannow to make sure it doesn't report problems.
Hi, In some situations SURT stops on the first errors it finds and only when those are resolved continues doing more checking... The errors related with avast can be ignored. Run also SFC /scannow to make sure it doesn't report problems.
daveguitaruno Contributor Joined May 1, 2019 Posts 103 Location United Kingdom Jun 20, 2019 #131 I'm afraid it does report errors Attachments CBS.7z 123.4 KB · Views: 3
SleepyDude Windows Update Moderator, Security Analyst Staff member Joined Dec 20, 2013 Posts 3,061 Location Portugal Jun 20, 2019 #132 Run SFCFix without any script, let the tool check the system and then post the log SFCFix.txt
daveguitaruno Contributor Joined May 1, 2019 Posts 103 Location United Kingdom Jun 20, 2019 #133 I rebooted and ran SURT tool again here's the CheckSUR log ================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2019-06-20 21:24 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store (f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_5ca6eb17137337f1 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_5ca6eb17137337f1 (f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_9c229ed3ddb17764 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_9c229ed3ddb17764 (f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_4f95660acc611f2b amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_4f95660acc611f2b (f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_a93423e024c3902a x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_a93423e024c3902a (f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_547567fcc9354e5e amd64_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_547567fcc9354e5e (f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_a45421ee27ef60f7 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_a45421ee27ef60f7 (f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_97429ce1e0dd4831 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_97429ce1e0dd4831 (f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_6186ed0910476724 amd64_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_6186ed0910476724 Summary: Seconds executed: 555 Found 8 errors CSI C Mark Deployment Not Marked Total count: 8 Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site. ========================================================================================== Here's the SFCFix.txt SFCFix version 3.0.2.1 by niemiro. Start time: 2019-06-21 00:28:23.311 Microsoft Windows 7 Service Pack 1 - amd64 Not using a script file. AutoAnalysis:: WARNING: Failed to get store name from identity name with return code 2 for component prnhp003.inf and file Amd64\hpj6400t.xml. File is reported as corrupt by SFC. CORRUPT: Amd64\hpj6400t.xml of component prnhp003.inf. WARNING: Failed to get store name from identity name with return code 2 for component prnnr004.inf and file Amd64\NRMPC303.PPD. File is reported as corrupt by SFC. CORRUPT: Amd64\NRMPC303.PPD of component prnnr004.inf. SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com. CBS & SFC total detected corruption count: 2 CBS & SFC total unimportant corruption count: 0 CBS & SFC total fixed corruption count: 0 SURT total detected corruption count: 8 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 AutoAnalysis:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 137 datablocks. Finish time: 2019-06-21 00:29:24.598 ----------------------EOF------------------
I rebooted and ran SURT tool again here's the CheckSUR log ================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2019-06-20 21:24 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store (f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_5ca6eb17137337f1 amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_5ca6eb17137337f1 (f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_9c229ed3ddb17764 x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_9c229ed3ddb17764 (f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_4f95660acc611f2b amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_4f95660acc611f2b (f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_a93423e024c3902a x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_a93423e024c3902a (f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_547567fcc9354e5e amd64_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_547567fcc9354e5e (f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_a45421ee27ef60f7 x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_a45421ee27ef60f7 (f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..t.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_97429ce1e0dd4831 x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.27012.0_none_97429ce1e0dd4831 (f) CSI C Mark Deployment Not Marked 0x00000000 c!avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_6186ed0910476724 amd64_avast.vc140.mfc_fcc99ee6193ebbca_14.0.27012.0_none_6186ed0910476724 Summary: Seconds executed: 555 Found 8 errors CSI C Mark Deployment Not Marked Total count: 8 Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site. ========================================================================================== Here's the SFCFix.txt SFCFix version 3.0.2.1 by niemiro. Start time: 2019-06-21 00:28:23.311 Microsoft Windows 7 Service Pack 1 - amd64 Not using a script file. AutoAnalysis:: WARNING: Failed to get store name from identity name with return code 2 for component prnhp003.inf and file Amd64\hpj6400t.xml. File is reported as corrupt by SFC. CORRUPT: Amd64\hpj6400t.xml of component prnhp003.inf. WARNING: Failed to get store name from identity name with return code 2 for component prnnr004.inf and file Amd64\NRMPC303.PPD. File is reported as corrupt by SFC. CORRUPT: Amd64\NRMPC303.PPD of component prnnr004.inf. SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com. CBS & SFC total detected corruption count: 2 CBS & SFC total unimportant corruption count: 0 CBS & SFC total fixed corruption count: 0 SURT total detected corruption count: 8 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 AutoAnalysis:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 137 datablocks. Finish time: 2019-06-21 00:29:24.598 ----------------------EOF------------------
SleepyDude Windows Update Moderator, Security Analyst Staff member Joined Dec 20, 2013 Posts 3,061 Location Portugal Jun 21, 2019 #134 Hi, The following fix should take care of the corrupted files reported by SFC. SFCFix Script !!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems... Download SFCFix.exe (by Niemiro) and save it to the Desktop Download the file daveguitaruno.zip and save this to your Desktop On your Desktop, make sure you have the two files: SFCFix.exe and daveguitaruno.zip Drag the file daveguitaruno.zip onto the file SFCFix.exe and release it The SFCFix tool will process the script Upon completion, a log file SFCFix.txt should be created on your Desktop Open the SFCFix.txt log and copy & paste the contents to your post
Hi, The following fix should take care of the corrupted files reported by SFC. SFCFix Script !!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems... Download SFCFix.exe (by Niemiro) and save it to the Desktop Download the file daveguitaruno.zip and save this to your Desktop On your Desktop, make sure you have the two files: SFCFix.exe and daveguitaruno.zip Drag the file daveguitaruno.zip onto the file SFCFix.exe and release it The SFCFix tool will process the script Upon completion, a log file SFCFix.txt should be created on your Desktop Open the SFCFix.txt log and copy & paste the contents to your post
daveguitaruno Contributor Joined May 1, 2019 Posts 103 Location United Kingdom Jun 21, 2019 #135 Hi, too big to paste here so attached file instead Attachments SFCFix.txt 452.8 KB · Views: 1
SleepyDude Windows Update Moderator, Security Analyst Staff member Joined Dec 20, 2013 Posts 3,061 Location Portugal Jun 22, 2019 #136 Hi, One file couldn't be replaced lets remove it during boot and copy the file again... Step 1 - Farbar Recovery Scan Fix !!! WARNING !!! The following fix is only relevant for this system and no other, running the script on another computer will not work and may cause problems... Download FRST or FRST x64 and save it to the Desktop. (Please pick the version that matches your operating system's bit type. If you don't know which version matches your system, try FRST if it say that is not compatible with your OS you have to use FRST64) Highlight the contents of the box below, right click on it and select Copy to transfer the script to the Windows Clipboard Start:: C:\Windows\WinSxS\amd64_microsoft-windows-font-truetype-meiryo_31bf3856ad364e35_6.1.7601.24440_none_d2ea7e9a7749baf9 Reboot: End:: Click to expand... Execute FRST/FRST64 right click on the icon and choose Run as Administrator. Make sure all other windows are closed. Press the Fix button just once and Wait, FRST will read the instructions from the Clipboard. After the fix the system needs to restart if the tool does not request it please Restart the computer. The tool will make a log (Fixlog.txt) on the same location as FRST/FRST64 please post it in your next reply. Step 2 - SFCFix Script !!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems... Download SFCFix.exe (by Niemiro) and save it to the Desktop Download the file SFCFIX.ZIP, attached below, and save this to your Desktop On your Desktop, make sure you have the two files: SFCFix.exe and SFCFIX.zip Drag the file SFCFIX.zip onto the file SFCFix.exe and release it The SFCFix tool will process the script Upon completion, a log file SFCFix.txt should be created on your Desktop Open the SFCFix.txt log and copy & paste the contents to your post Attachments SFCFix.zip 5.7 MB · Views: 1
Hi, One file couldn't be replaced lets remove it during boot and copy the file again... Step 1 - Farbar Recovery Scan Fix !!! WARNING !!! The following fix is only relevant for this system and no other, running the script on another computer will not work and may cause problems... Download FRST or FRST x64 and save it to the Desktop. (Please pick the version that matches your operating system's bit type. If you don't know which version matches your system, try FRST if it say that is not compatible with your OS you have to use FRST64) Highlight the contents of the box below, right click on it and select Copy to transfer the script to the Windows Clipboard Start:: C:\Windows\WinSxS\amd64_microsoft-windows-font-truetype-meiryo_31bf3856ad364e35_6.1.7601.24440_none_d2ea7e9a7749baf9 Reboot: End:: Click to expand... Execute FRST/FRST64 right click on the icon and choose Run as Administrator. Make sure all other windows are closed. Press the Fix button just once and Wait, FRST will read the instructions from the Clipboard. After the fix the system needs to restart if the tool does not request it please Restart the computer. The tool will make a log (Fixlog.txt) on the same location as FRST/FRST64 please post it in your next reply. Step 2 - SFCFix Script !!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems... Download SFCFix.exe (by Niemiro) and save it to the Desktop Download the file SFCFIX.ZIP, attached below, and save this to your Desktop On your Desktop, make sure you have the two files: SFCFix.exe and SFCFIX.zip Drag the file SFCFIX.zip onto the file SFCFix.exe and release it The SFCFix tool will process the script Upon completion, a log file SFCFix.txt should be created on your Desktop Open the SFCFix.txt log and copy & paste the contents to your post
daveguitaruno Contributor Joined May 1, 2019 Posts 103 Location United Kingdom Jun 22, 2019 #137 Hi SleepyDude, here you go SFCFix version 3.0.2.1 by niemiro. Start time: 2019-06-22 18:45:11.899 Microsoft Windows 7 Service Pack 1 - amd64 Using .zip script file at C:\Users\Dave\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\WinSxS Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-font-truetype-meiryo_31bf3856ad364e35_6.1.7601.24440_none_d2ea7e9a7749baf9. Failed to find any content under directory "C:\Users\Dave\AppData\Local\niemiro\Archive\Packages" in line ""C:\Users\Dave\AppData\Local\niemiro\Archive\Packages" C:\Windows\Servicing\Packages [DIR]". Failed to find any content under directory "C:\Users\Dave\AppData\Local\niemiro\Archive\Manifests" in line ""C:\Users\Dave\AppData\Local\niemiro\Archive\Manifests" C:\Windows\WinSxS\Manifests [DIR]". Successfully copied file C:\Users\Dave\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-font-truetype-meiryo_31bf3856ad364e35_6.1.7601.24440_none_d2ea7e9a7749baf9\meiryo.ttc to C:\Windows\WinSxS\amd64_microsoft-windows-font-truetype-meiryo_31bf3856ad364e35_6.1.7601.24440_none_d2ea7e9a7749baf9\meiryo.ttc. Successfully restored ownership for C:\Windows\WinSxS Successfully restored permissions on C:\Windows\WinSxS PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 452 datablocks. Finish time: 2019-06-22 18:45:21.892 Script hash: IEGhPXZotw/I4rzoWDeHUY9HVZVxri/hVngwFJwyJa0= ----------------------EOF-----------------------
Hi SleepyDude, here you go SFCFix version 3.0.2.1 by niemiro. Start time: 2019-06-22 18:45:11.899 Microsoft Windows 7 Service Pack 1 - amd64 Using .zip script file at C:\Users\Dave\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\WinSxS Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-font-truetype-meiryo_31bf3856ad364e35_6.1.7601.24440_none_d2ea7e9a7749baf9. Failed to find any content under directory "C:\Users\Dave\AppData\Local\niemiro\Archive\Packages" in line ""C:\Users\Dave\AppData\Local\niemiro\Archive\Packages" C:\Windows\Servicing\Packages [DIR]". Failed to find any content under directory "C:\Users\Dave\AppData\Local\niemiro\Archive\Manifests" in line ""C:\Users\Dave\AppData\Local\niemiro\Archive\Manifests" C:\Windows\WinSxS\Manifests [DIR]". Successfully copied file C:\Users\Dave\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-font-truetype-meiryo_31bf3856ad364e35_6.1.7601.24440_none_d2ea7e9a7749baf9\meiryo.ttc to C:\Windows\WinSxS\amd64_microsoft-windows-font-truetype-meiryo_31bf3856ad364e35_6.1.7601.24440_none_d2ea7e9a7749baf9\meiryo.ttc. Successfully restored ownership for C:\Windows\WinSxS Successfully restored permissions on C:\Windows\WinSxS PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 452 datablocks. Finish time: 2019-06-22 18:45:21.892 Script hash: IEGhPXZotw/I4rzoWDeHUY9HVZVxri/hVngwFJwyJa0= ----------------------EOF-----------------------
SleepyDude Windows Update Moderator, Security Analyst Staff member Joined Dec 20, 2013 Posts 3,061 Location Portugal Jun 22, 2019 #138 Hi, You didn't post the fixlog.txt but it seems it worked... Run SFC /scannow again, lets see if reports no corruptions.
Hi, You didn't post the fixlog.txt but it seems it worked... Run SFC /scannow again, lets see if reports no corruptions.
daveguitaruno Contributor Joined May 1, 2019 Posts 103 Location United Kingdom Jun 22, 2019 #139 Sorry will do Attachments Fixlog.txt 673 bytes · Views: 1
SleepyDude Windows Update Moderator, Security Analyst Staff member Joined Dec 20, 2013 Posts 3,061 Location Portugal Jun 23, 2019 #140 No problem. And SURT.