B bro Active member Joined Jan 7, 2017 Posts 33 Jan 7, 2017 #1 Every time I run sfcfix after the first time I no longer get the communication question of y/n. First time I ran sfcfix I put 'N' just to see if it would work, all I got was this: SFCFix version 3.0.0.0 by niemiro. Start time: 2017-01-07 14:24:28.029 Microsoft Windows 7 Service Pack 1 - amd64 Not using a script file. AutoAnalysis:: SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com. CBS & SFC total detected corruption count: 4 CBS & SFC total unimportant corruption count: 0 CBS & SFC total fixed corruption count: 0 SURT total detected corruption count: 0 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 AutoAnalysis:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2017-01-07 14:25:07.637 ----------------------EOF----------------------- Click to expand... I tried running it again to answer Y, but no longer get the question screen. how do i reset it? or does it matter?
Every time I run sfcfix after the first time I no longer get the communication question of y/n. First time I ran sfcfix I put 'N' just to see if it would work, all I got was this: SFCFix version 3.0.0.0 by niemiro. Start time: 2017-01-07 14:24:28.029 Microsoft Windows 7 Service Pack 1 - amd64 Not using a script file. AutoAnalysis:: SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com. CBS & SFC total detected corruption count: 4 CBS & SFC total unimportant corruption count: 0 CBS & SFC total fixed corruption count: 0 SURT total detected corruption count: 0 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 AutoAnalysis:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2017-01-07 14:25:07.637 ----------------------EOF----------------------- Click to expand... I tried running it again to answer Y, but no longer get the question screen. how do i reset it? or does it matter?
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,670 Location World, Europe, Italy Jan 7, 2017 #2 Hi bro. :welcome: If you refer to this message: Read More: Will you allow SFCFix to communicate with Sysnative servers? Most file system and registry corruptions cannot be repaired when this tool works standalone. Sysnative's central servers can be used to give direction on repairing registry corruptions and finding good replacements for damaged files using aggregate data compiled over thousands of computers. Details of your Windows Update configuration may be transmitted to our servers for furtheranalysis as part of this process. No personally identifiable information will becollected. Although the process is entirely opt-in, if you choose not to accept this transmission the tool can operate only in a reduced function mode and the majority of corruptions will not be repaired automatically. Would you like this communication to take place? Type "y" for yes or "n" for no and press enter to continue: You can re-get it removing completely %localappdata%\niemiro folder (c:\users\%username%\appdata\local\niemiro). Sfcfix should be closed when you do it.
Hi bro. :welcome: If you refer to this message: Read More: Will you allow SFCFix to communicate with Sysnative servers? Most file system and registry corruptions cannot be repaired when this tool works standalone. Sysnative's central servers can be used to give direction on repairing registry corruptions and finding good replacements for damaged files using aggregate data compiled over thousands of computers. Details of your Windows Update configuration may be transmitted to our servers for furtheranalysis as part of this process. No personally identifiable information will becollected. Although the process is entirely opt-in, if you choose not to accept this transmission the tool can operate only in a reduced function mode and the majority of corruptions will not be repaired automatically. Would you like this communication to take place? Type "y" for yes or "n" for no and press enter to continue: You can re-get it removing completely %localappdata%\niemiro folder (c:\users\%username%\appdata\local\niemiro). Sfcfix should be closed when you do it.
B bro Active member Joined Jan 7, 2017 Posts 33 Jan 11, 2017 #3 xilolee said: Hi bro. :welcome: If you refer to this message: Read More: Will you allow SFCFix to communicate with Sysnative servers? Most file system and registry corruptions cannot be repaired when this tool works standalone. Sysnative's central servers can be used to give direction on repairing registry corruptions and finding good replacements for damaged files using aggregate data compiled over thousands of computers. Details of your Windows Update configuration may be transmitted to our servers for furtheranalysis as part of this process. No personally identifiable information will becollected. Although the process is entirely opt-in, if you choose not to accept this transmission the tool can operate only in a reduced function mode and the majority of corruptions will not be repaired automatically. Would you like this communication to take place? Type "y" for yes or "n" for no and press enter to continue: You can re-get it removing completely %localappdata%\niemiro folder (c:\users\%username%\appdata\local\niemiro). Sfcfix should be closed when you do it. Click to expand... Yes that is the screen i'm referring to. But I cannot locate the appdata folder.
xilolee said: Hi bro. :welcome: If you refer to this message: Read More: Will you allow SFCFix to communicate with Sysnative servers? Most file system and registry corruptions cannot be repaired when this tool works standalone. Sysnative's central servers can be used to give direction on repairing registry corruptions and finding good replacements for damaged files using aggregate data compiled over thousands of computers. Details of your Windows Update configuration may be transmitted to our servers for furtheranalysis as part of this process. No personally identifiable information will becollected. Although the process is entirely opt-in, if you choose not to accept this transmission the tool can operate only in a reduced function mode and the majority of corruptions will not be repaired automatically. Would you like this communication to take place? Type "y" for yes or "n" for no and press enter to continue: You can re-get it removing completely %localappdata%\niemiro folder (c:\users\%username%\appdata\local\niemiro). Sfcfix should be closed when you do it. Click to expand... Yes that is the screen i'm referring to. But I cannot locate the appdata folder.
B bro Active member Joined Jan 7, 2017 Posts 33 Jan 11, 2017 #4 OK I found the folder through dos and deleted it, ran scffix to hit y this time (Thanks!) Now my problem is that I still no further than before. It scanned some windows update registry (said stage 1 failed on server) and after stage 5, it said "failed to create zip file with errno 2" 4 times and this is all that is shown in the new log: SFCFix version 3.0.0.0 by niemiro. Start time: 2017-01-11 09:54:28.883 Microsoft Windows 7 Service Pack 1 - amd64 Not using a script file. AutoAnalysis:: SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com. CBS & SFC total detected corruption count: 4 CBS & SFC total unimportant corruption count: 0 CBS & SFC total fixed corruption count: 0 SURT total detected corruption count: 0 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 AutoAnalysis:: directive completed successfully. Successfully processed all directives. Failed to generate a complete zip file. Upload aborted. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2017-01-11 09:56:35.520 ----------------------EOF----------------------- Click to expand... Also, this folder needs deleted every time to answer yes to communicate with servers.
OK I found the folder through dos and deleted it, ran scffix to hit y this time (Thanks!) Now my problem is that I still no further than before. It scanned some windows update registry (said stage 1 failed on server) and after stage 5, it said "failed to create zip file with errno 2" 4 times and this is all that is shown in the new log: SFCFix version 3.0.0.0 by niemiro. Start time: 2017-01-11 09:54:28.883 Microsoft Windows 7 Service Pack 1 - amd64 Not using a script file. AutoAnalysis:: SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com. CBS & SFC total detected corruption count: 4 CBS & SFC total unimportant corruption count: 0 CBS & SFC total fixed corruption count: 0 SURT total detected corruption count: 0 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 AutoAnalysis:: directive completed successfully. Successfully processed all directives. Failed to generate a complete zip file. Upload aborted. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2017-01-11 09:56:35.520 ----------------------EOF----------------------- Click to expand... Also, this folder needs deleted every time to answer yes to communicate with servers.
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jan 11, 2017 #5 Hi and welcome to Sysnative. Please do the following. SFC Scan Click on the Start button and in the search box, type Command Prompt When you see Command Prompt on the list, right-click on it and select Run as administrator When command prompt opens, copy and paste the following commands into it, press enter after each sfc /scannow Wait for this to finish before you continue copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt This will create a file, cbs.txt on your Desktop. Please attach this to your next post. Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Hi and welcome to Sysnative. Please do the following. SFC Scan Click on the Start button and in the search box, type Command Prompt When you see Command Prompt on the list, right-click on it and select Run as administrator When command prompt opens, copy and paste the following commands into it, press enter after each sfc /scannow Wait for this to finish before you continue copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt This will create a file, cbs.txt on your Desktop. Please attach this to your next post. Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
B bro Active member Joined Jan 7, 2017 Posts 33 Jan 12, 2017 #6 BrianDrab said: ...... This will create a file, cbs.txt on your Desktop. Please attach this to your next post. Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link. Click to expand... Hello, main reason I'm doing this is because I'm getting SXS errors with trying to start a couple of games and Event Viewer pane that refuse to load from mmc snap in failure, which all (games and event viewer) seem to get fixed and randomly fail simultaneously (everything else works fine afaik). First fix was from updating graphics drivers, that no longer works, then everything failed again randomly, second fix was from running Tron script, then everything failed randomly again, no longer works. So now I'm doing this. When event viewer was working, I found invalid syntax on line 0 of one of the amd64 sxs xml files, for whatever that is worth. Dropbox - CBS (2).log
BrianDrab said: ...... This will create a file, cbs.txt on your Desktop. Please attach this to your next post. Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link. Click to expand... Hello, main reason I'm doing this is because I'm getting SXS errors with trying to start a couple of games and Event Viewer pane that refuse to load from mmc snap in failure, which all (games and event viewer) seem to get fixed and randomly fail simultaneously (everything else works fine afaik). First fix was from updating graphics drivers, that no longer works, then everything failed again randomly, second fix was from running Tron script, then everything failed randomly again, no longer works. So now I'm doing this. When event viewer was working, I found invalid syntax on line 0 of one of the amd64 sxs xml files, for whatever that is worth. Dropbox - CBS (2).log
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jan 12, 2017 #7 Thanks for the info. Please do the following. Step#1 - System Update Readiness Tool (SUR) 1. Download and run the following file. 2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel. 3. You will get an Installation Complete screen when it's done running. 4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Thanks for the info. Please do the following. Step#1 - System Update Readiness Tool (SUR) 1. Download and run the following file. 2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel. 3. You will get an Installation Complete screen when it's done running. 4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
B bro Active member Joined Jan 7, 2017 Posts 33 Jan 12, 2017 #8 These files sound familiar from when event log was working (viewing the file that fails when trying to launch game that was failing to open) ================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2017-01-12 21:27 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_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd Summary: Seconds executed: 54 Found 1 errors CSI Manifest Failed Catalog Check Total count: 1 Unavailable repair files: winsxs\manifests\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest Click to expand...
These files sound familiar from when event log was working (viewing the file that fails when trying to launch game that was failing to open) ================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2017-01-12 21:27 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_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd Summary: Seconds executed: 54 Found 1 errors CSI Manifest Failed Catalog Check Total count: 1 Unavailable repair files: winsxs\manifests\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest Click to expand...
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jan 13, 2017 #9 Please do the following. Step#1 - SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip. Drag the file SFCFix.zip onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a file should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please Attachments SFCFix.zip 850 bytes · Views: 24
Please do the following. Step#1 - SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip. Drag the file SFCFix.zip onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a file should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
B bro Active member Joined Jan 7, 2017 Posts 33 Jan 13, 2017 #10 sweet, looks good? SFCFix version 3.0.0.0 by niemiro. Start time: 2017-01-13 21:10:53.805 Microsoft Windows 7 Service Pack 1 - amd64 Using .zip script file at C:\Users\User Name\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\Temp\CheckSur\Winsxs\Manifests Successfully copied file C:\Users\User Name\AppData\Local\niemiro\Archive\Manifests\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest to C:\Windows\Temp\CheckSur\Winsxs\Manifests\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest. Successfully restored ownership for C:\Windows\Temp\CheckSur\Winsxs\Manifests Successfully restored permissions on C:\Windows\Temp\CheckSur\Winsxs\Manifests PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 1 datablocks. Finish time: 2017-01-13 21:10:53.955 Script hash: H045KAm31keJfaWEpLOF2HMP4JW7E5HWCyloFf+MjAU= ----------------------EOF----------------------- Click to expand...
sweet, looks good? SFCFix version 3.0.0.0 by niemiro. Start time: 2017-01-13 21:10:53.805 Microsoft Windows 7 Service Pack 1 - amd64 Using .zip script file at C:\Users\User Name\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\Temp\CheckSur\Winsxs\Manifests Successfully copied file C:\Users\User Name\AppData\Local\niemiro\Archive\Manifests\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest to C:\Windows\Temp\CheckSur\Winsxs\Manifests\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest. Successfully restored ownership for C:\Windows\Temp\CheckSur\Winsxs\Manifests Successfully restored permissions on C:\Windows\Temp\CheckSur\Winsxs\Manifests PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 1 datablocks. Finish time: 2017-01-13 21:10:53.955 Script hash: H045KAm31keJfaWEpLOF2HMP4JW7E5HWCyloFf+MjAU= ----------------------EOF----------------------- Click to expand...
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jan 13, 2017 #11 Looks good. Do the following again to confirm. Step#1 - System Update Readiness Tool (SUR) 1. Download and run the following file. 2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel. 3. You will get an Installation Complete screen when it's done running. 4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Looks good. Do the following again to confirm. Step#1 - System Update Readiness Tool (SUR) 1. Download and run the following file. 2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel. 3. You will get an Installation Complete screen when it's done running. 4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
B bro Active member Joined Jan 7, 2017 Posts 33 Jan 14, 2017 #12 ================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2017-01-13 23:27 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_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd (fix) CSI Manifest Failed Catalog Check CSI File Replaced File: amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439 Summary: Seconds executed: 52 Found 2 errors Fixed 1 errors CSI Manifest Failed Catalog Check Total count: 2 Fixed: CSI Manifest Failed Catalog Check. Total count: 1 Unavailable repair files: winsxs\manifests\amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest Click to expand...
================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2017-01-13 23:27 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_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd (fix) CSI Manifest Failed Catalog Check CSI File Replaced File: amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_09c4cec9fac927dd.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439 Summary: Seconds executed: 52 Found 2 errors Fixed 1 errors CSI Manifest Failed Catalog Check Total count: 2 Fixed: CSI Manifest Failed Catalog Check. Total count: 1 Unavailable repair files: winsxs\manifests\amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest Click to expand...
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jan 14, 2017 #13 That one was fixed but we have another one to fix. Please do the following. Step#1 - SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip. Drag the file SFCFix.zip onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a file should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please Attachments SFCFix.zip 850 bytes · Views: 9
That one was fixed but we have another one to fix. Please do the following. Step#1 - SFCFix Script Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip. Drag the file SFCFix.zip onto the file SFCFix.exe and release it. SFCFix will now process the script. Upon completion, a file should be created on your Desktop: SFCFix.txt. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
B bro Active member Joined Jan 7, 2017 Posts 33 Jan 14, 2017 #14 SFCfix: SFCFix version 3.0.0.0 by niemiro. Start time: 2017-01-14 11:31:31.583 Microsoft Windows 7 Service Pack 1 - amd64 Using .zip script file at C:\Users\User Name\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\Temp\CheckSur\Winsxs\Manifests Successfully copied file C:\Users\User Name\AppData\Local\niemiro\Archive\Manifests\amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest to C:\Windows\Temp\CheckSur\Winsxs\Manifests\amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest. Successfully restored ownership for C:\Windows\Temp\CheckSur\Winsxs\Manifests Successfully restored permissions on C:\Windows\Temp\CheckSur\Winsxs\Manifests PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 1 datablocks. Finish time: 2017-01-14 11:31:31.739 Script hash: hOrKf7zOGh+vmhy+gaheL7jKXrc7jRnW7q+IS0GXxp8= ----------------------EOF----------------------- Click to expand... CheckSUR: ================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2017-01-14 11:35 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_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439 (fix) CSI Manifest Failed Catalog Check CSI File Replaced File: amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab Summary: Seconds executed: 54 Found 1 errors Fixed 1 errors CSI Manifest Failed Catalog Check Total count: 1 Fixed: CSI Manifest Failed Catalog Check. Total count: 1 Click to expand... Looks like the first file was what was causing my problems, good to see the other file fixed too. Why do these specific files go bad, go good, then bad again? I feel like I'll have to do this over again in the future.
SFCfix: SFCFix version 3.0.0.0 by niemiro. Start time: 2017-01-14 11:31:31.583 Microsoft Windows 7 Service Pack 1 - amd64 Using .zip script file at C:\Users\User Name\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\Temp\CheckSur\Winsxs\Manifests Successfully copied file C:\Users\User Name\AppData\Local\niemiro\Archive\Manifests\amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest to C:\Windows\Temp\CheckSur\Winsxs\Manifests\amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest. Successfully restored ownership for C:\Windows\Temp\CheckSur\Winsxs\Manifests Successfully restored permissions on C:\Windows\Temp\CheckSur\Winsxs\Manifests PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 1 datablocks. Finish time: 2017-01-14 11:31:31.739 Script hash: hOrKf7zOGh+vmhy+gaheL7jKXrc7jRnW7q+IS0GXxp8= ----------------------EOF----------------------- Click to expand... CheckSUR: ================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2017-01-14 11:35 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_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439 (fix) CSI Manifest Failed Catalog Check CSI File Replaced File: amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.6195_none_06366735fd130439.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab Summary: Seconds executed: 54 Found 1 errors Fixed 1 errors CSI Manifest Failed Catalog Check Total count: 1 Fixed: CSI Manifest Failed Catalog Check. Total count: 1 Click to expand... Looks like the first file was what was causing my problems, good to see the other file fixed too. Why do these specific files go bad, go good, then bad again? I feel like I'll have to do this over again in the future.
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jan 14, 2017 #15 Looks like you are good to go now. Corruption can happen for all sorts of reasons. Computer is powered off without cleanly shutting down first (i.e. pulling the plug), conflicts with Antivirus Software, bad update and on and on. You shouldn't have to do this very often at all. If you do you likely have bad RAM, disk or processor. Is there anything else I can assist with?
Looks like you are good to go now. Corruption can happen for all sorts of reasons. Computer is powered off without cleanly shutting down first (i.e. pulling the plug), conflicts with Antivirus Software, bad update and on and on. You shouldn't have to do this very often at all. If you do you likely have bad RAM, disk or processor. Is there anything else I can assist with?
B bro Active member Joined Jan 7, 2017 Posts 33 Jan 15, 2017 #16 Unless these files are susceptible to some specific common issue I can focus on and prevent then I think that's it. A relief it's fixable without total overhaul. Thanks for all the help!!!
Unless these files are susceptible to some specific common issue I can focus on and prevent then I think that's it. A relief it's fixable without total overhaul. Thanks for all the help!!!
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jan 16, 2017 #17 No problem. Take care.