S SBG Contributor Joined Jun 7, 2017 Posts 81 Jul 22, 2017 #61 Here is the reply: SFCFix version 3.0.0.0 by niemiro. Start time: 2017-07-22 16:35:07.854 Microsoft Windows 10 Build 14393 - amd64 Using .txt script file at C:\Users\subodhan\Desktop\SFCScript.txt [0] RegistryScript:: Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32. Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version. Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32. WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version. Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version. RegistryScript:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 25 datablocks. Finish time: 2017-07-22 16:35:08.107 Script hash: 0Klk0uLV6yTc9P5cUPS7aOy+fyNdTxLDDx8JfDQshBc= ----------------------EOF-----------------------
Here is the reply: SFCFix version 3.0.0.0 by niemiro. Start time: 2017-07-22 16:35:07.854 Microsoft Windows 10 Build 14393 - amd64 Using .txt script file at C:\Users\subodhan\Desktop\SFCScript.txt [0] RegistryScript:: Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32. Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version. Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32. WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version. Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version. RegistryScript:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 25 datablocks. Finish time: 2017-07-22 16:35:08.107 Script hash: 0Klk0uLV6yTc9P5cUPS7aOy+fyNdTxLDDx8JfDQshBc= ----------------------EOF-----------------------
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jul 23, 2017 #62 Repeat the steps in Post#50.
S SBG Contributor Joined Jun 7, 2017 Posts 81 Jul 23, 2017 #63 The command failed: C:\WINDOWS\system32>DISM /Online /Get-Drivers Deployment Image Servicing and Management tool Version: 10.0.14393.0 Error: 3 An initialization error occurred. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> Please find the DISM log below: View attachment dism.zip
The command failed: C:\WINDOWS\system32>DISM /Online /Get-Drivers Deployment Image Servicing and Management tool Version: 10.0.14393.0 Error: 3 An initialization error occurred. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> Please find the DISM log below: View attachment dism.zip
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jul 25, 2017 #64 Please do the following. Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Open an elevated Command Prompt and run DISM /Online /Get-Drivers just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up and attach the LogFile.PML file as well as your CBS.log and DISM.log
Please do the following. Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Open an elevated Command Prompt and run DISM /Online /Get-Drivers just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up and attach the LogFile.PML file as well as your CBS.log and DISM.log
S SBG Contributor Joined Jun 7, 2017 Posts 81 Jul 26, 2017 #65 DISM /Online /Get-Drivers failed: C:\WINDOWS\system32>DISM /Online /Get-Drivers Deployment Image Servicing and Management tool Version: 10.0.14393.0 Error: 3 An initialization error occurred. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> The zip file (dism.log, cbs.log and LogFile.pml) is available at: https://1drv.ms/u/s!AmgYffdSBkYvmHE845KS8Kh9sZQp
DISM /Online /Get-Drivers failed: C:\WINDOWS\system32>DISM /Online /Get-Drivers Deployment Image Servicing and Management tool Version: 10.0.14393.0 Error: 3 An initialization error occurred. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> The zip file (dism.log, cbs.log and LogFile.pml) is available at: https://1drv.ms/u/s!AmgYffdSBkYvmHE845KS8Kh9sZQp
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jul 26, 2017 #66 It doesn't appear the capture was done correctly or it simply didn't work. You want to make sure Process Monitor is running BEFORE you open a command prompt and run the command DISM /Online /Get-Drivers. Then after the error happens go ahead and stop the capture and save the log. Could you try following the instructions again? Thanks.
It doesn't appear the capture was done correctly or it simply didn't work. You want to make sure Process Monitor is running BEFORE you open a command prompt and run the command DISM /Online /Get-Drivers. Then after the error happens go ahead and stop the capture and save the log. Could you try following the instructions again? Thanks.
S SBG Contributor Joined Jun 7, 2017 Posts 81 Jul 26, 2017 #67 DISM failed: C:\WINDOWS\system32>DISM /Online /Get-Drivers Deployment Image Servicing and Management tool Version: 10.0.14393.0 Error: 3 An initialization error occurred. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> The zip file is here: https://1drv.ms/u/s!AmgYffdSBkYvmHLEci3HBKt3gmiv
DISM failed: C:\WINDOWS\system32>DISM /Online /Get-Drivers Deployment Image Servicing and Management tool Version: 10.0.14393.0 Error: 3 An initialization error occurred. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> The zip file is here: https://1drv.ms/u/s!AmgYffdSBkYvmHLEci3HBKt3gmiv
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jul 26, 2017 #68 Good, that's the info I needed. However it doesn't appear that you attached the most recent CBS.log. It appears old.
Good, that's the info I needed. However it doesn't appear that you attached the most recent CBS.log. It appears old.
S SBG Contributor Joined Jun 7, 2017 Posts 81 Jul 26, 2017 #69 Looks like my CBS log is not getting updated: That is the time I executed the DISM in the morning Last edited: Jul 26, 2017
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jul 26, 2017 #70 Got it. OK there are a couple things we can do here. Step#1 - Add File Please download this file and save it to your c:\windows\servicing\version\10.0.14393.0 folder. The file is named amd64_installed with no extension of any kind. Step#2 - 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 2.3 MB · Views: 10
Got it. OK there are a couple things we can do here. Step#1 - Add File Please download this file and save it to your c:\windows\servicing\version\10.0.14393.0 folder. The file is named amd64_installed with no extension of any kind. Step#2 - 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
S SBG Contributor Joined Jun 7, 2017 Posts 81 Jul 26, 2017 #71 I cannot copy the amd64_installed file to the destination folder, since I do not have (write) access to the folder. Also, if you could let me know how to fix the CBS log issue, that would be great.
I cannot copy the amd64_installed file to the destination folder, since I do not have (write) access to the folder. Also, if you could let me know how to fix the CBS log issue, that would be great.
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jul 26, 2017 #72 OK, ignore the previous steps then. Only do the following. Don't worry about the CBS.log for the moment. 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 440 bytes · Views: 3
OK, ignore the previous steps then. Only do the following. Don't worry about the CBS.log for the moment. 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
S SBG Contributor Joined Jun 7, 2017 Posts 81 Jul 26, 2017 #73 SFCFix version 3.0.0.0 by niemiro. Start time: 2017-07-26 22:45:06.357 Microsoft Windows 10 Build 14393 - amd64 Using .zip script file at C:\Users\subodhan\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\WINDOWS\Servicing\version\10.0.14393.0 Successfully copied file C:\Users\subodhan\AppData\Local\niemiro\Archive\amd64_installed to C:\WINDOWS\Servicing\version\10.0.14393.0\amd64_installed. Successfully copied file C:\Users\subodhan\AppData\Local\niemiro\Archive\x86_installed to C:\WINDOWS\Servicing\version\10.0.14393.0\x86_installed. Successfully restored ownership for C:\WINDOWS\Servicing\version\10.0.14393.0 Successfully restored permissions on C:\WINDOWS\Servicing\version\10.0.14393.0 PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 26 datablocks. Finish time: 2017-07-26 22:45:07.328 Script hash: fstTOowxFZ38NMvEwTExFIAdsrS/N6V4z1V+PD7EdDA= ----------------------EOF-----------------------
SFCFix version 3.0.0.0 by niemiro. Start time: 2017-07-26 22:45:06.357 Microsoft Windows 10 Build 14393 - amd64 Using .zip script file at C:\Users\subodhan\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\WINDOWS\Servicing\version\10.0.14393.0 Successfully copied file C:\Users\subodhan\AppData\Local\niemiro\Archive\amd64_installed to C:\WINDOWS\Servicing\version\10.0.14393.0\amd64_installed. Successfully copied file C:\Users\subodhan\AppData\Local\niemiro\Archive\x86_installed to C:\WINDOWS\Servicing\version\10.0.14393.0\x86_installed. Successfully restored ownership for C:\WINDOWS\Servicing\version\10.0.14393.0 Successfully restored permissions on C:\WINDOWS\Servicing\version\10.0.14393.0 PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.0.0 by niemiro has completed. Currently storing 26 datablocks. Finish time: 2017-07-26 22:45:07.328 Script hash: fstTOowxFZ38NMvEwTExFIAdsrS/N6V4z1V+PD7EdDA= ----------------------EOF-----------------------
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jul 26, 2017 #74 Repeat the steps in Post#64.
S SBG Contributor Joined Jun 7, 2017 Posts 81 Jul 26, 2017 #75 The command executed successfully. The output of the DISM, cbs.log (updated), dism.log, LogFile.pml are available in the zip file: https://1drv.ms/u/s!AmgYffdSBkYvmHN946sUyIWUZGfN
The command executed successfully. The output of the DISM, cbs.log (updated), dism.log, LogFile.pml are available in the zip file: https://1drv.ms/u/s!AmgYffdSBkYvmHN946sUyIWUZGfN
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jul 27, 2017 #76 Thanks. Please do the following. Step#1 - DISM /RestoreHealth Scan 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. Right-click on the Start button and select Command Prompt (Admin) When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead. copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread. Please Note:: if the file is too big (over 7MB) 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. Please do the following. Step#1 - DISM /RestoreHealth Scan 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. Right-click on the Start button and select Command Prompt (Admin) When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead. copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt" Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread. Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
S SBG Contributor Joined Jun 7, 2017 Posts 81 Jul 27, 2017 #77 Dism command failed: C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Error: 193 %1 is not a valid Win32 application. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> The Dism and CBS logs are: View attachment dism_cbs.zip
Dism command failed: C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Error: 193 %1 is not a valid Win32 application. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> The Dism and CBS logs are: View attachment dism_cbs.zip
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Jul 30, 2017 #78 OK, please do the following. Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Open an elevated Command Prompt and run Dism /Online /Cleanup-Image /RestoreHealth just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up and attach the LogFile.PML file as well as your CBS.log and DISM.log
OK, please do the following. Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Open an elevated Command Prompt and run Dism /Online /Cleanup-Image /RestoreHealth just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up and attach the LogFile.PML file as well as your CBS.log and DISM.log
S SBG Contributor Joined Jun 7, 2017 Posts 81 Jul 31, 2017 #79 Here is the result: C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Error: 193 %1 is not a valid Win32 application. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> The zip file is below: https://1drv.ms/u/s!AmgYffdSBkYvmHRHsEIaCTjoTXMy
Here is the result: C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Error: 193 %1 is not a valid Win32 application. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> The zip file is below: https://1drv.ms/u/s!AmgYffdSBkYvmHRHsEIaCTjoTXMy
BrianDrab Emeritus Joined Oct 20, 2014 Posts 18,131 Location United States Aug 5, 2017 #80 OK, I have a few more ideas now after going through those logs. 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, SFCScript.txt, and save this to your Desktop. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt. Drag the file SFCScript.txt 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 SFCScript.txt 71 bytes · Views: 9
OK, I have a few more ideas now after going through those logs. 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, SFCScript.txt, and save this to your Desktop. Save any open documents and close all open windows. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt. Drag the file SFCScript.txt 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