Lucky Active member Joined Nov 2, 2015 Posts 26 Nov 2, 2015 #1 Hello There, I am having problems in installing windows 10 updates from few weeks. So, i tried different methods from internet. But my problem didn't get solved. Today only i came to know about this forum and read few posts as well. So, I registered here. And i am briefing my problem below with details. So, Any help from you guys is definitely helpful to me and i would be very grateful. I ran windows update diagnostic and tried installing but no use. 1) I tried running SFC /SCANNOW from Command prompt(by Run as admin). And the result is as follows. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios. 2) After that i tried DISM commands 2a) dism.exe /online /cleanup-image /scanhealth C:\WINDOWS\system32>dism.exe /online /cleanup-image /scanhealth Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 [==========================100.0%==========================] The component store is repairable. The operation completed successfully. 2b) dism.exe /online /cleanup-image /restorehealth C:\WINDOWS\system32>dism.exe /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 [==========================100.0%==========================] Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log For reference the Screenshot of Command prompt. I am providing the CBS & DISM Log files in a Zip file below. Please check those and Guide me on this. If any further details is needed just let me know, i will provide with those. View attachment CBS & DISM LOGS.zip
Hello There, I am having problems in installing windows 10 updates from few weeks. So, i tried different methods from internet. But my problem didn't get solved. Today only i came to know about this forum and read few posts as well. So, I registered here. And i am briefing my problem below with details. So, Any help from you guys is definitely helpful to me and i would be very grateful. I ran windows update diagnostic and tried installing but no use. 1) I tried running SFC /SCANNOW from Command prompt(by Run as admin). And the result is as follows. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios. 2) After that i tried DISM commands 2a) dism.exe /online /cleanup-image /scanhealth C:\WINDOWS\system32>dism.exe /online /cleanup-image /scanhealth Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 [==========================100.0%==========================] The component store is repairable. The operation completed successfully. 2b) dism.exe /online /cleanup-image /restorehealth C:\WINDOWS\system32>dism.exe /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 [==========================100.0%==========================] Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log For reference the Screenshot of Command prompt. I am providing the CBS & DISM Log files in a Zip file below. Please check those and Guide me on this. If any further details is needed just let me know, i will provide with those. View attachment CBS & DISM LOGS.zip
Aura Sysnative Staff, Security Analyst Staff member Joined Mar 16, 2015 Posts 8,061 Nov 4, 2015 #2 Hi Lucky :) I'll be assisting you with your issue since you sent me a PM. I'll take a look at it tonight once I get home since I don't have access to a Windows 10 computer or .iso at work.
Hi Lucky :) I'll be assisting you with your issue since you sent me a PM. I'll take a look at it tonight once I get home since I don't have access to a Windows 10 computer or .iso at work.
Lucky Active member Joined Nov 2, 2015 Posts 26 Nov 4, 2015 #3 Hi Aura, Thanks very much for the quick response.:smile9:
Aura Sysnative Staff, Security Analyst Staff member Joined Mar 16, 2015 Posts 8,061 Nov 4, 2015 #4 Alright, do you have your Windows 10 installation media or .iso?
Lucky Active member Joined Nov 2, 2015 Posts 26 Nov 5, 2015 #5 No i don't have. I have upgraded from windows 7.
Lucky Active member Joined Nov 2, 2015 Posts 26 Nov 5, 2015 #6 But i have this "$Windows.~WS" in my C folder. and there it contains all data which usually be in Installation Media. will that be any helpful?
But i have this "$Windows.~WS" in my C folder. and there it contains all data which usually be in Installation Media. will that be any helpful?
Aura Sysnative Staff, Security Analyst Staff member Joined Mar 16, 2015 Posts 8,061 Nov 5, 2015 #7 Is it complete? What's the size of it?
Aura Sysnative Staff, Security Analyst Staff member Joined Mar 16, 2015 Posts 8,061 Nov 5, 2015 #9 Looks a bit small. Alright here's what you can do. Download the Windows 10 Media Creation Tool for your version of Windows (32 or 64-bit). https://www.microsoft.com/en-us/software-download/windows10 Once done, launch it and select the second option (create an installation media for another computer), this will make you download a Windows 10 .iso on your system. Select your version and edition and proceed to download it. Let me know once the download is complete.
Looks a bit small. Alright here's what you can do. Download the Windows 10 Media Creation Tool for your version of Windows (32 or 64-bit). https://www.microsoft.com/en-us/software-download/windows10 Once done, launch it and select the second option (create an installation media for another computer), this will make you download a Windows 10 .iso on your system. Select your version and edition and proceed to download it. Let me know once the download is complete.
Lucky Active member Joined Nov 2, 2015 Posts 26 Nov 5, 2015 #10 Actually the size of "$Windows.~WS" is 4.47 Gb. I have just told you the size of Windows folder which is in"$Windows.~WS" and then in "Sources". Do you still suggest me to download?
Actually the size of "$Windows.~WS" is 4.47 Gb. I have just told you the size of Windows folder which is in"$Windows.~WS" and then in "Sources". Do you still suggest me to download?
Aura Sysnative Staff, Security Analyst Staff member Joined Mar 16, 2015 Posts 8,061 Nov 5, 2015 #11 Alright that's a good size for the folder. We'll run DISM using the "Sources" folder of the "$Windows.~WS" folder grab the files. Open a command prompt as Admin, and enter the following command: Code: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1 Replace the "Full Path to install.wim file" for the path to the install.wim file (eg: C:\$Windows.~WS\Sources\install.wim). Once done, upload the logs below for me to review. C:\Windows\Logs\CBS\CBS.log C:\Windows\Logs\DISM\DISM.log
Alright that's a good size for the folder. We'll run DISM using the "Sources" folder of the "$Windows.~WS" folder grab the files. Open a command prompt as Admin, and enter the following command: Code: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1 Replace the "Full Path to install.wim file" for the path to the install.wim file (eg: C:\$Windows.~WS\Sources\install.wim). Once done, upload the logs below for me to review. C:\Windows\Logs\CBS\CBS.log C:\Windows\Logs\DISM\DISM.log
Lucky Active member Joined Nov 2, 2015 Posts 26 Nov 5, 2015 #12 Hello Aura, I am not sure whether i did performed as you explained or not. But i am explaining what i did. Please have a look. I opened command prompt as Admin and entered this command. Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:C:\$Windows.~WS\Sources\install.wim:1 not sure that above command is just as you said or not(i am little confused and just replaced "Full Path to install.wim file" with "C:\$Windows.~WS\Sources\install.wim") The results are: Here are the files you just asked. View attachment cbs and dism.zip If i did anything wrong then please let me know. I will do as you suggest again.:smile9:
Hello Aura, I am not sure whether i did performed as you explained or not. But i am explaining what i did. Please have a look. I opened command prompt as Admin and entered this command. Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:C:\$Windows.~WS\Sources\install.wim:1 not sure that above command is just as you said or not(i am little confused and just replaced "Full Path to install.wim file" with "C:\$Windows.~WS\Sources\install.wim") The results are: Here are the files you just asked. View attachment cbs and dism.zip If i did anything wrong then please let me know. I will do as you suggest again.:smile9:
Aura Sysnative Staff, Security Analyst Staff member Joined Mar 16, 2015 Posts 8,061 Nov 5, 2015 #13 All good :) I wanted to use that method because it's hard to use a SURT log from DISM with one of our tool to source files when it's manifest files, but it seems like I'll have to take the time to format it and such. I'll post a reply tonight at home, since I don't have access to a Windows 10 computer here.
All good :) I wanted to use that method because it's hard to use a SURT log from DISM with one of our tool to source files when it's manifest files, but it seems like I'll have to take the time to format it and such. I'll post a reply tonight at home, since I don't have access to a Windows 10 computer here.
Aura Sysnative Staff, Security Analyst Staff member Joined Mar 16, 2015 Posts 8,061 Nov 5, 2015 #14 What edition of Windows 10 are you running? Also, are you running Windows 10 32 or 64-bit? It seems that I only have a few of your missing files on my Windows 10 system. We'll start by replacing them. SFCFix - Fix Time WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly. Follow the instructions below to download and execute a SFCFix fix, and provide the log. Download SFCFix and move the executable on your Desktop; Download the attached SFCFix.zip and move the archive to your Desktop; Note: Make sure that the file is named SFCFix.zip, do not rename it. Save any work you have open, and close every programs; Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it; SFCFix will launch, let it complete; Once done, a file will appear on your Desktop, called SFCFix.txt; Open the file, then copy and paste its content in your next reply; SFCFix.zip
What edition of Windows 10 are you running? Also, are you running Windows 10 32 or 64-bit? It seems that I only have a few of your missing files on my Windows 10 system. We'll start by replacing them. SFCFix - Fix Time WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly. Follow the instructions below to download and execute a SFCFix fix, and provide the log. Download SFCFix and move the executable on your Desktop; Download the attached SFCFix.zip and move the archive to your Desktop; Note: Make sure that the file is named SFCFix.zip, do not rename it. Save any work you have open, and close every programs; Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it; SFCFix will launch, let it complete; Once done, a file will appear on your Desktop, called SFCFix.txt; Open the file, then copy and paste its content in your next reply; SFCFix.zip
Lucky Active member Joined Nov 2, 2015 Posts 26 Nov 5, 2015 #15 Hello Aura, My Windows edition : Windows 10 Pro, and System type : 32-bit OS, & Below is the content, SFCFix version 2.4.5.0 by niemiro. Start time: 2015-11-06 09:40:38.681 Microsoft Windows 8.1 - x86 Using .zip script file at C:\Users\G.POSI\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\WINDOWS\winsxs\x86_fdssdp_31bf3856ad364e35_10.0.10240.16384_none_e6bfc8c2568e3acf\fdSSDP.mof Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..istfolder.resources_31bf3856ad364e35_10.0.10240.16384_en-us_aeed5a2358acfa89.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..leshooter.resources_31bf3856ad364e35_10.0.10240.16384_en-us_30d38a44a27b584b.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..ommunicationsupport_31bf3856ad364e35_10.0.10240.16384_none_c6cdeac3d5fe6707.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..orkclient.resources_31bf3856ad364e35_10.0.10240.16384_en-us_656ee9a799000201.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..owershell.resources_31bf3856ad364e35_10.0.10240.16384_en-us_97131b4e98990984.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeeradmin_31bf3856ad364e35_10.0.10240.16384_none_f32b4066b2372a1a.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeerdrt-events_31bf3856ad364e35_10.0.10240.16384_none_bd652f123e27f459.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeergraphing_31bf3856ad364e35_10.0.10240.16384_none_0ea4b0ffcc0e6377.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfnet-events_31bf3856ad364e35_10.0.10240.16384_none_8858c7858d50c00e.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfos-events_31bf3856ad364e35_10.0.10240.16384_none_3a486edb8ff337fb.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfproc-events_31bf3856ad364e35_10.0.10240.16384_none_cbc94d7d8947d30d.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photo-printing-wizard_31bf3856ad364e35_10.0.10240.16384_none_00caa676bf61a652.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoacquire_31bf3856ad364e35_10.0.10240.16384_none_e0183ac1ef122f82.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoviewer_31bf3856ad364e35_10.0.10240.16384_none_88206167b208129e.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-pla-events_31bf3856ad364e35_10.0.10240.16384_none_0f8072be4f41d577.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-playtostatusprovider_31bf3856ad364e35_10.0.10240.16384_none_96c28f461d6a65fe.manifest Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\x86_fdssdp_31bf3856ad364e35_10.0.10240.16384_none_e6bfc8c2568e3acf\fdSSDP.mof to C:\WINDOWS\winsxs\x86_fdssdp_31bf3856ad364e35_10.0.10240.16384_none_e6bfc8c2568e3acf\fdSSDP.mof. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-p..istfolder.resources_31bf3856ad364e35_10.0.10240.16384_en-us_aeed5a2358acfa89.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..istfolder.resources_31bf3856ad364e35_10.0.10240.16384_en-us_aeed5a2358acfa89.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-p..leshooter.resources_31bf3856ad364e35_10.0.10240.16384_en-us_30d38a44a27b584b.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..leshooter.resources_31bf3856ad364e35_10.0.10240.16384_en-us_30d38a44a27b584b.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-p..ommunicationsupport_31bf3856ad364e35_10.0.10240.16384_none_c6cdeac3d5fe6707.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..ommunicationsupport_31bf3856ad364e35_10.0.10240.16384_none_c6cdeac3d5fe6707.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-p..orkclient.resources_31bf3856ad364e35_10.0.10240.16384_en-us_656ee9a799000201.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..orkclient.resources_31bf3856ad364e35_10.0.10240.16384_en-us_656ee9a799000201.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-p..owershell.resources_31bf3856ad364e35_10.0.10240.16384_en-us_97131b4e98990984.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..owershell.resources_31bf3856ad364e35_10.0.10240.16384_en-us_97131b4e98990984.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-peertopeeradmin_31bf3856ad364e35_10.0.10240.16384_none_f32b4066b2372a1a.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeeradmin_31bf3856ad364e35_10.0.10240.16384_none_f32b4066b2372a1a.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-peertopeerdrt-events_31bf3856ad364e35_10.0.10240.16384_none_bd652f123e27f459.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeerdrt-events_31bf3856ad364e35_10.0.10240.16384_none_bd652f123e27f459.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-peertopeergraphing_31bf3856ad364e35_10.0.10240.16384_none_0ea4b0ffcc0e6377.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeergraphing_31bf3856ad364e35_10.0.10240.16384_none_0ea4b0ffcc0e6377.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-perfnet-events_31bf3856ad364e35_10.0.10240.16384_none_8858c7858d50c00e.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfnet-events_31bf3856ad364e35_10.0.10240.16384_none_8858c7858d50c00e.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-perfos-events_31bf3856ad364e35_10.0.10240.16384_none_3a486edb8ff337fb.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfos-events_31bf3856ad364e35_10.0.10240.16384_none_3a486edb8ff337fb.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-perfproc-events_31bf3856ad364e35_10.0.10240.16384_none_cbc94d7d8947d30d.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfproc-events_31bf3856ad364e35_10.0.10240.16384_none_cbc94d7d8947d30d.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-photo-printing-wizard_31bf3856ad364e35_10.0.10240.16384_none_00caa676bf61a652.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photo-printing-wizard_31bf3856ad364e35_10.0.10240.16384_none_00caa676bf61a652.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-photoacquire_31bf3856ad364e35_10.0.10240.16384_none_e0183ac1ef122f82.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoacquire_31bf3856ad364e35_10.0.10240.16384_none_e0183ac1ef122f82.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-photoviewer_31bf3856ad364e35_10.0.10240.16384_none_88206167b208129e.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoviewer_31bf3856ad364e35_10.0.10240.16384_none_88206167b208129e.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-pla-events_31bf3856ad364e35_10.0.10240.16384_none_0f8072be4f41d577.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-pla-events_31bf3856ad364e35_10.0.10240.16384_none_0f8072be4f41d577.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-playtostatusprovider_31bf3856ad364e35_10.0.10240.16384_none_96c28f461d6a65fe.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-playtostatusprovider_31bf3856ad364e35_10.0.10240.16384_none_96c28f461d6a65fe.manifest. Successfully restored ownership for C:\WINDOWS\winsxs\x86_fdssdp_31bf3856ad364e35_10.0.10240.16384_none_e6bfc8c2568e3acf\fdSSDP.mof Successfully restored permissions on C:\WINDOWS\winsxs\x86_fdssdp_31bf3856ad364e35_10.0.10240.16384_none_e6bfc8c2568e3acf\fdSSDP.mof Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..istfolder.resources_31bf3856ad364e35_10.0.10240.16384_en-us_aeed5a2358acfa89.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..istfolder.resources_31bf3856ad364e35_10.0.10240.16384_en-us_aeed5a2358acfa89.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..leshooter.resources_31bf3856ad364e35_10.0.10240.16384_en-us_30d38a44a27b584b.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..leshooter.resources_31bf3856ad364e35_10.0.10240.16384_en-us_30d38a44a27b584b.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..ommunicationsupport_31bf3856ad364e35_10.0.10240.16384_none_c6cdeac3d5fe6707.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..ommunicationsupport_31bf3856ad364e35_10.0.10240.16384_none_c6cdeac3d5fe6707.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..orkclient.resources_31bf3856ad364e35_10.0.10240.16384_en-us_656ee9a799000201.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..orkclient.resources_31bf3856ad364e35_10.0.10240.16384_en-us_656ee9a799000201.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..owershell.resources_31bf3856ad364e35_10.0.10240.16384_en-us_97131b4e98990984.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..owershell.resources_31bf3856ad364e35_10.0.10240.16384_en-us_97131b4e98990984.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeeradmin_31bf3856ad364e35_10.0.10240.16384_none_f32b4066b2372a1a.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeeradmin_31bf3856ad364e35_10.0.10240.16384_none_f32b4066b2372a1a.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeerdrt-events_31bf3856ad364e35_10.0.10240.16384_none_bd652f123e27f459.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeerdrt-events_31bf3856ad364e35_10.0.10240.16384_none_bd652f123e27f459.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeergraphing_31bf3856ad364e35_10.0.10240.16384_none_0ea4b0ffcc0e6377.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeergraphing_31bf3856ad364e35_10.0.10240.16384_none_0ea4b0ffcc0e6377.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfnet-events_31bf3856ad364e35_10.0.10240.16384_none_8858c7858d50c00e.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfnet-events_31bf3856ad364e35_10.0.10240.16384_none_8858c7858d50c00e.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfos-events_31bf3856ad364e35_10.0.10240.16384_none_3a486edb8ff337fb.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfos-events_31bf3856ad364e35_10.0.10240.16384_none_3a486edb8ff337fb.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfproc-events_31bf3856ad364e35_10.0.10240.16384_none_cbc94d7d8947d30d.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfproc-events_31bf3856ad364e35_10.0.10240.16384_none_cbc94d7d8947d30d.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photo-printing-wizard_31bf3856ad364e35_10.0.10240.16384_none_00caa676bf61a652.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photo-printing-wizard_31bf3856ad364e35_10.0.10240.16384_none_00caa676bf61a652.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoacquire_31bf3856ad364e35_10.0.10240.16384_none_e0183ac1ef122f82.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoacquire_31bf3856ad364e35_10.0.10240.16384_none_e0183ac1ef122f82.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoviewer_31bf3856ad364e35_10.0.10240.16384_none_88206167b208129e.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoviewer_31bf3856ad364e35_10.0.10240.16384_none_88206167b208129e.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-pla-events_31bf3856ad364e35_10.0.10240.16384_none_0f8072be4f41d577.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-pla-events_31bf3856ad364e35_10.0.10240.16384_none_0f8072be4f41d577.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-playtostatusprovider_31bf3856ad364e35_10.0.10240.16384_none_96c28f461d6a65fe.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-playtostatusprovider_31bf3856ad364e35_10.0.10240.16384_none_96c28f461d6a65fe.manifest PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 2.4.5.0 by niemiro has completed. Currently storing 17 datablocks. Finish time: 2015-11-06 09:40:43.032 Script hash: YIG73GC0ORkIevz/hKkeLC5Ae+Z861iJpyZydV9SgrU= ----------------------EOF-----------------------
Hello Aura, My Windows edition : Windows 10 Pro, and System type : 32-bit OS, & Below is the content, SFCFix version 2.4.5.0 by niemiro. Start time: 2015-11-06 09:40:38.681 Microsoft Windows 8.1 - x86 Using .zip script file at C:\Users\G.POSI\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\WINDOWS\winsxs\x86_fdssdp_31bf3856ad364e35_10.0.10240.16384_none_e6bfc8c2568e3acf\fdSSDP.mof Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..istfolder.resources_31bf3856ad364e35_10.0.10240.16384_en-us_aeed5a2358acfa89.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..leshooter.resources_31bf3856ad364e35_10.0.10240.16384_en-us_30d38a44a27b584b.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..ommunicationsupport_31bf3856ad364e35_10.0.10240.16384_none_c6cdeac3d5fe6707.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..orkclient.resources_31bf3856ad364e35_10.0.10240.16384_en-us_656ee9a799000201.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..owershell.resources_31bf3856ad364e35_10.0.10240.16384_en-us_97131b4e98990984.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeeradmin_31bf3856ad364e35_10.0.10240.16384_none_f32b4066b2372a1a.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeerdrt-events_31bf3856ad364e35_10.0.10240.16384_none_bd652f123e27f459.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeergraphing_31bf3856ad364e35_10.0.10240.16384_none_0ea4b0ffcc0e6377.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfnet-events_31bf3856ad364e35_10.0.10240.16384_none_8858c7858d50c00e.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfos-events_31bf3856ad364e35_10.0.10240.16384_none_3a486edb8ff337fb.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfproc-events_31bf3856ad364e35_10.0.10240.16384_none_cbc94d7d8947d30d.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photo-printing-wizard_31bf3856ad364e35_10.0.10240.16384_none_00caa676bf61a652.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoacquire_31bf3856ad364e35_10.0.10240.16384_none_e0183ac1ef122f82.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoviewer_31bf3856ad364e35_10.0.10240.16384_none_88206167b208129e.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-pla-events_31bf3856ad364e35_10.0.10240.16384_none_0f8072be4f41d577.manifest Successfully took permissions for file or folder C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-playtostatusprovider_31bf3856ad364e35_10.0.10240.16384_none_96c28f461d6a65fe.manifest Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\x86_fdssdp_31bf3856ad364e35_10.0.10240.16384_none_e6bfc8c2568e3acf\fdSSDP.mof to C:\WINDOWS\winsxs\x86_fdssdp_31bf3856ad364e35_10.0.10240.16384_none_e6bfc8c2568e3acf\fdSSDP.mof. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-p..istfolder.resources_31bf3856ad364e35_10.0.10240.16384_en-us_aeed5a2358acfa89.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..istfolder.resources_31bf3856ad364e35_10.0.10240.16384_en-us_aeed5a2358acfa89.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-p..leshooter.resources_31bf3856ad364e35_10.0.10240.16384_en-us_30d38a44a27b584b.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..leshooter.resources_31bf3856ad364e35_10.0.10240.16384_en-us_30d38a44a27b584b.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-p..ommunicationsupport_31bf3856ad364e35_10.0.10240.16384_none_c6cdeac3d5fe6707.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..ommunicationsupport_31bf3856ad364e35_10.0.10240.16384_none_c6cdeac3d5fe6707.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-p..orkclient.resources_31bf3856ad364e35_10.0.10240.16384_en-us_656ee9a799000201.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..orkclient.resources_31bf3856ad364e35_10.0.10240.16384_en-us_656ee9a799000201.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-p..owershell.resources_31bf3856ad364e35_10.0.10240.16384_en-us_97131b4e98990984.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..owershell.resources_31bf3856ad364e35_10.0.10240.16384_en-us_97131b4e98990984.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-peertopeeradmin_31bf3856ad364e35_10.0.10240.16384_none_f32b4066b2372a1a.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeeradmin_31bf3856ad364e35_10.0.10240.16384_none_f32b4066b2372a1a.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-peertopeerdrt-events_31bf3856ad364e35_10.0.10240.16384_none_bd652f123e27f459.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeerdrt-events_31bf3856ad364e35_10.0.10240.16384_none_bd652f123e27f459.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-peertopeergraphing_31bf3856ad364e35_10.0.10240.16384_none_0ea4b0ffcc0e6377.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeergraphing_31bf3856ad364e35_10.0.10240.16384_none_0ea4b0ffcc0e6377.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-perfnet-events_31bf3856ad364e35_10.0.10240.16384_none_8858c7858d50c00e.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfnet-events_31bf3856ad364e35_10.0.10240.16384_none_8858c7858d50c00e.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-perfos-events_31bf3856ad364e35_10.0.10240.16384_none_3a486edb8ff337fb.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfos-events_31bf3856ad364e35_10.0.10240.16384_none_3a486edb8ff337fb.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-perfproc-events_31bf3856ad364e35_10.0.10240.16384_none_cbc94d7d8947d30d.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfproc-events_31bf3856ad364e35_10.0.10240.16384_none_cbc94d7d8947d30d.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-photo-printing-wizard_31bf3856ad364e35_10.0.10240.16384_none_00caa676bf61a652.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photo-printing-wizard_31bf3856ad364e35_10.0.10240.16384_none_00caa676bf61a652.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-photoacquire_31bf3856ad364e35_10.0.10240.16384_none_e0183ac1ef122f82.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoacquire_31bf3856ad364e35_10.0.10240.16384_none_e0183ac1ef122f82.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-photoviewer_31bf3856ad364e35_10.0.10240.16384_none_88206167b208129e.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoviewer_31bf3856ad364e35_10.0.10240.16384_none_88206167b208129e.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-pla-events_31bf3856ad364e35_10.0.10240.16384_none_0f8072be4f41d577.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-pla-events_31bf3856ad364e35_10.0.10240.16384_none_0f8072be4f41d577.manifest. Successfully copied file C:\Users\G.POSI\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-playtostatusprovider_31bf3856ad364e35_10.0.10240.16384_none_96c28f461d6a65fe.manifest to C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-playtostatusprovider_31bf3856ad364e35_10.0.10240.16384_none_96c28f461d6a65fe.manifest. Successfully restored ownership for C:\WINDOWS\winsxs\x86_fdssdp_31bf3856ad364e35_10.0.10240.16384_none_e6bfc8c2568e3acf\fdSSDP.mof Successfully restored permissions on C:\WINDOWS\winsxs\x86_fdssdp_31bf3856ad364e35_10.0.10240.16384_none_e6bfc8c2568e3acf\fdSSDP.mof Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..istfolder.resources_31bf3856ad364e35_10.0.10240.16384_en-us_aeed5a2358acfa89.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..istfolder.resources_31bf3856ad364e35_10.0.10240.16384_en-us_aeed5a2358acfa89.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..leshooter.resources_31bf3856ad364e35_10.0.10240.16384_en-us_30d38a44a27b584b.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..leshooter.resources_31bf3856ad364e35_10.0.10240.16384_en-us_30d38a44a27b584b.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..ommunicationsupport_31bf3856ad364e35_10.0.10240.16384_none_c6cdeac3d5fe6707.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..ommunicationsupport_31bf3856ad364e35_10.0.10240.16384_none_c6cdeac3d5fe6707.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..orkclient.resources_31bf3856ad364e35_10.0.10240.16384_en-us_656ee9a799000201.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..orkclient.resources_31bf3856ad364e35_10.0.10240.16384_en-us_656ee9a799000201.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..owershell.resources_31bf3856ad364e35_10.0.10240.16384_en-us_97131b4e98990984.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-p..owershell.resources_31bf3856ad364e35_10.0.10240.16384_en-us_97131b4e98990984.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeeradmin_31bf3856ad364e35_10.0.10240.16384_none_f32b4066b2372a1a.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeeradmin_31bf3856ad364e35_10.0.10240.16384_none_f32b4066b2372a1a.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeerdrt-events_31bf3856ad364e35_10.0.10240.16384_none_bd652f123e27f459.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeerdrt-events_31bf3856ad364e35_10.0.10240.16384_none_bd652f123e27f459.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeergraphing_31bf3856ad364e35_10.0.10240.16384_none_0ea4b0ffcc0e6377.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-peertopeergraphing_31bf3856ad364e35_10.0.10240.16384_none_0ea4b0ffcc0e6377.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfnet-events_31bf3856ad364e35_10.0.10240.16384_none_8858c7858d50c00e.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfnet-events_31bf3856ad364e35_10.0.10240.16384_none_8858c7858d50c00e.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfos-events_31bf3856ad364e35_10.0.10240.16384_none_3a486edb8ff337fb.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfos-events_31bf3856ad364e35_10.0.10240.16384_none_3a486edb8ff337fb.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfproc-events_31bf3856ad364e35_10.0.10240.16384_none_cbc94d7d8947d30d.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-perfproc-events_31bf3856ad364e35_10.0.10240.16384_none_cbc94d7d8947d30d.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photo-printing-wizard_31bf3856ad364e35_10.0.10240.16384_none_00caa676bf61a652.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photo-printing-wizard_31bf3856ad364e35_10.0.10240.16384_none_00caa676bf61a652.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoacquire_31bf3856ad364e35_10.0.10240.16384_none_e0183ac1ef122f82.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoacquire_31bf3856ad364e35_10.0.10240.16384_none_e0183ac1ef122f82.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoviewer_31bf3856ad364e35_10.0.10240.16384_none_88206167b208129e.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-photoviewer_31bf3856ad364e35_10.0.10240.16384_none_88206167b208129e.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-pla-events_31bf3856ad364e35_10.0.10240.16384_none_0f8072be4f41d577.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-pla-events_31bf3856ad364e35_10.0.10240.16384_none_0f8072be4f41d577.manifest Successfully restored ownership for C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-playtostatusprovider_31bf3856ad364e35_10.0.10240.16384_none_96c28f461d6a65fe.manifest Successfully restored permissions on C:\WINDOWS\winsxs\Manifests\x86_microsoft-windows-playtostatusprovider_31bf3856ad364e35_10.0.10240.16384_none_96c28f461d6a65fe.manifest PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 2.4.5.0 by niemiro has completed. Currently storing 17 datablocks. Finish time: 2015-11-06 09:40:43.032 Script hash: YIG73GC0ORkIevz/hKkeLC5Ae+Z861iJpyZydV9SgrU= ----------------------EOF-----------------------
Aura Sysnative Staff, Security Analyst Staff member Joined Mar 16, 2015 Posts 8,061 Nov 6, 2015 #16 32-bit, that's probably why I couldn't find all your files. I'll download a Windows 10 32-bit .iso tonight and source the files from it. Let's run SFC to see if the changes are accepted meanwhile, and DISM after that so I can get an updated list of the files I need to source. System File Checker (SFC) Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply; On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select Run as Administrator On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin); On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin); Enter the command below and press on Enter; Code: sfc /scannow Note: There's a space between "sfc" and "/scannow"; Once the scan is complete, enter the command below and press on Enter Code: copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here; Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't have the information from the scan anymore. So archive it and upload it as soon as you can.
32-bit, that's probably why I couldn't find all your files. I'll download a Windows 10 32-bit .iso tonight and source the files from it. Let's run SFC to see if the changes are accepted meanwhile, and DISM after that so I can get an updated list of the files I need to source. System File Checker (SFC) Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply; On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select Run as Administrator On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin); On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin); Enter the command below and press on Enter; Code: sfc /scannow Note: There's a space between "sfc" and "/scannow"; Once the scan is complete, enter the command below and press on Enter Code: copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here; Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't have the information from the scan anymore. So archive it and upload it as soon as you can.
Lucky Active member Joined Nov 2, 2015 Posts 26 Nov 6, 2015 #17 Hello Aura, I just did as you suggested. Here are the details, From the CMD prompt content, Microsoft Windows [Version 10.0.10240] (c) 2015 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios. C:\WINDOWS\system32>copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" 1 file(s) copied. C:\WINDOWS\system32> And Below is link of Cbs.txt file on Google Drive, https://drive.google.com/file/d/0B94a6vWfom5MRm5YUDI0MlhyVE0/view?usp=sharing
Hello Aura, I just did as you suggested. Here are the details, From the CMD prompt content, Microsoft Windows [Version 10.0.10240] (c) 2015 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios. C:\WINDOWS\system32>copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" 1 file(s) copied. C:\WINDOWS\system32> And Below is link of Cbs.txt file on Google Drive, https://drive.google.com/file/d/0B94a6vWfom5MRm5YUDI0MlhyVE0/view?usp=sharing
Aura Sysnative Staff, Security Analyst Staff member Joined Mar 16, 2015 Posts 8,061 Nov 6, 2015 #18 All good, let's run DISM again to get a new SURT log, and I'll work on that tonight :) I really need to transfer Windows 10 .iso on my work laptop! DISM - Fixing Component Store Corruption Follow the instructions below to run a DISM operation on your system. On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin); On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin); Enter the command below and press on Enter; Code: DISM /Online /Cleanup-Image /RestoreHealth Let the scan run until the end (100%). Depending on your system, it can take some time; Copy the C:\Windows\Logs\DISM folder and C:\Windows\Logs\CBS\CBS.log file on your Desktop, then right-click on it, go to Send to... and select Compressed .zip archive; Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here; Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the DISM scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.
All good, let's run DISM again to get a new SURT log, and I'll work on that tonight :) I really need to transfer Windows 10 .iso on my work laptop! DISM - Fixing Component Store Corruption Follow the instructions below to run a DISM operation on your system. On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin); On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin); Enter the command below and press on Enter; Code: DISM /Online /Cleanup-Image /RestoreHealth Let the scan run until the end (100%). Depending on your system, it can take some time; Copy the C:\Windows\Logs\DISM folder and C:\Windows\Logs\CBS\CBS.log file on your Desktop, then right-click on it, go to Send to... and select Compressed .zip archive; Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here; Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the DISM scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.
Lucky Active member Joined Nov 2, 2015 Posts 26 Nov 6, 2015 #19 Hello Aura, This is CMD prompt content, Microsoft Windows [Version 10.0.10240] (c) 2015 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>DISM /Online /Cleanup-Image /RestoreHealth Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 [==========================100.0%==========================] Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> And below is the link for compressed zip of both cbs and dism log files, https://drive.google.com/file/d/0B94a6vWfom5MX2I2WV9fbUVmRUU/view?usp=sharing
Hello Aura, This is CMD prompt content, Microsoft Windows [Version 10.0.10240] (c) 2015 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>DISM /Online /Cleanup-Image /RestoreHealth Deployment Image Servicing and Management tool Version: 10.0.10240.16384 Image Version: 10.0.10240.16384 [==========================100.0%==========================] Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> And below is the link for compressed zip of both cbs and dism log files, https://drive.google.com/file/d/0B94a6vWfom5MX2I2WV9fbUVmRUU/view?usp=sharing
Aura Sysnative Staff, Security Analyst Staff member Joined Mar 16, 2015 Posts 8,061 Nov 6, 2015 #20 That was it, sourced all the files from a Windows 10 x86 RTM .iso. Follow the instructions below please. SFCFix - Fix Time WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly. Follow the instructions below to download and execute a SFCFix fix, and provide the log. Download SFCFix and move the executable on your Desktop; Download the attached SFCFix.zip and move the archive to your Desktop; Note: Make sure that the file is named SFCFix.zip, do not rename it. Save any work you have open, and close every programs; Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it; SFCFix will launch, let it complete; Once done, a file will appear on your Desktop, called SFCFix.txt; Open the file, then copy and paste its content in your next reply; SFCFix.zip
That was it, sourced all the files from a Windows 10 x86 RTM .iso. Follow the instructions below please. SFCFix - Fix Time WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly. Follow the instructions below to download and execute a SFCFix fix, and provide the log. Download SFCFix and move the executable on your Desktop; Download the attached SFCFix.zip and move the archive to your Desktop; Note: Make sure that the file is named SFCFix.zip, do not rename it. Save any work you have open, and close every programs; Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it; SFCFix will launch, let it complete; Once done, a file will appear on your Desktop, called SFCFix.txt; Open the file, then copy and paste its content in your next reply; SFCFix.zip
