gogeek Member Joined Jul 27, 2023 Posts 14 Jun 9, 2024 #1 Hi all, so here is my issue. Windows updates are failing to install and when I run a SFC scannow it errors out at 77%. See below: PS C:\Windows\system32> sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 77% complete. Windows Resource Protection could not perform the requested operation. The CBS.zip and ComponentsScanner.txt files can be found here Thanks in advance for any assistance with this issue
Hi all, so here is my issue. Windows updates are failing to install and when I run a SFC scannow it errors out at 77%. See below: PS C:\Windows\system32> sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 77% complete. Windows Resource Protection could not perform the requested operation. The CBS.zip and ComponentsScanner.txt files can be found here Thanks in advance for any assistance with this issue
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,283 Jun 10, 2024 #2 Looking over your logs now ...... back soon.
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,283 Jun 10, 2024 #3 WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system. Download SFCFix.exe and save it to your desktop. Download the attachment SFCFix.zip and also save it on your desktop. Save any work you have open, and close all programs. Drag the SFCFix.zip 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. Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Attachments SFCFixScript.zip 11.9 KB · Views: 10
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system. Download SFCFix.exe and save it to your desktop. Download the attachment SFCFix.zip and also save it on your desktop. Save any work you have open, and close all programs. Drag the SFCFix.zip 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. Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
gogeek Member Joined Jul 27, 2023 Posts 14 Jun 10, 2024 #4 Hi Gary, Thanks for the reply. I've run the SFCFix tool as described. Please note that the server in question does not have internet access so it was unable to communicate back to your servers. SFCFix results are as follows and CBS log attached: SFCFix version 3.0.2.1 by niemiro. Start time: 2024-06-11 09:47:04.484 Microsoft Windows Server 10 Build 17763 - amd64 Using .zip script file at C:\ESS\SFCFixScript.zip [0] Not using an additional text script file. AutoAnalysis:: ERROR: File Placement Mode failed to identify destinations for all files and folders. SFCFixScript.txt winsxs\ Manifests\ AutoAnalysis:: directive failed to complete successfully. Failed to process all directives successfully. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2024-06-11 09:48:01.160 Script hash: UOQfh329wu2IUvTKcWJ9Yh5Y3RnLKoEq2h7vKPHL2p8= ----------------------EOF----------------------- Attachments CBS.zip 29.8 KB · Views: 0
Hi Gary, Thanks for the reply. I've run the SFCFix tool as described. Please note that the server in question does not have internet access so it was unable to communicate back to your servers. SFCFix results are as follows and CBS log attached: SFCFix version 3.0.2.1 by niemiro. Start time: 2024-06-11 09:47:04.484 Microsoft Windows Server 10 Build 17763 - amd64 Using .zip script file at C:\ESS\SFCFixScript.zip [0] Not using an additional text script file. AutoAnalysis:: ERROR: File Placement Mode failed to identify destinations for all files and folders. SFCFixScript.txt winsxs\ Manifests\ AutoAnalysis:: directive failed to complete successfully. Failed to process all directives successfully. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2024-06-11 09:48:01.160 Script hash: UOQfh329wu2IUvTKcWJ9Yh5Y3RnLKoEq2h7vKPHL2p8= ----------------------EOF-----------------------
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,283 Jun 11, 2024 #5 For some reason SFCFix did not recognise the SFCFixScript.zip when you drag/dropped it onto SFCFix.exe and therefore did not execute the script, and ran in Auto mode. Please try following the instructions in post #3 again.
For some reason SFCFix did not recognise the SFCFixScript.zip when you drag/dropped it onto SFCFix.exe and therefore did not execute the script, and ran in Auto mode. Please try following the instructions in post #3 again.
gogeek Member Joined Jul 27, 2023 Posts 14 Jun 11, 2024 #6 Hi Gary, Yeah I thought that output looked odd too. I've tried it several times now with the same outcome. I've even rebooted the server and tried again - same result. And I've tried it on another test sever which is experiencing the same "SFC Scannow error at 77%" ... it also has the same output in the SFCFix.txt I also checked your zip file and it opens fine (doesn't appear to be corrupt). Any other ideas?
Hi Gary, Yeah I thought that output looked odd too. I've tried it several times now with the same outcome. I've even rebooted the server and tried again - same result. And I've tried it on another test sever which is experiencing the same "SFC Scannow error at 77%" ... it also has the same output in the SFCFix.txt I also checked your zip file and it opens fine (doesn't appear to be corrupt). Any other ideas?
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,283 Jun 12, 2024 #7 Try again with this (I've renamed the fix script, I think that was the problem) .... WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system. Download the attachment SFCFix.zip and save it on your desktop. Save any work you have open, and close all programs. Drag the SFCFix.zip 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. Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Attachments SFCFix.zip 11.9 KB · Views: 2 Last edited: Jun 12, 2024
Try again with this (I've renamed the fix script, I think that was the problem) .... WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system. Download the attachment SFCFix.zip and save it on your desktop. Save any work you have open, and close all programs. Drag the SFCFix.zip 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. Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
gogeek Member Joined Jul 27, 2023 Posts 14 Jun 12, 2024 #8 Hi Gary - I think you are on a winner there. This time the output looks heaps better (see below). I've also attached the CBS.log in case you are interested. But more importantly, the "sfc /scannow" actually completes now and I am able to install Windows updates again. I believe you have fixed the problem. Thank you so much! SFCFix version 3.0.2.1 by niemiro. Start time: 2024-06-13 08:44:02.620 Microsoft Windows Server 10 Build 17763 - amd64 Using .zip script file at C:\ESS\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1 Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.manifest Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1 to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\Manifests\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.manifest to C:\Windows\WinSxS\Manifests\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.manifest. Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1 Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1 Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml Successfully restored ownership for C:\Windows\WinSxS\Manifests\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.manifest Successfully restored permissions on C:\Windows\WinSxS\Manifests\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.manifest PowerCopy:: directive completed successfully. RegistryScript:: Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5. Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\761c81c8e26..850097cd1bf_31bf3856ad364e35_10.0.17763.831_d1adbfc11ed3dfbc. Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5. Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\761c81c8e26..850097cd1bf_31bf3856ad364e35_10.0.17763.831_d1adbfc11ed3dfbc. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\761c81c8e26..850097cd1bf_31bf3856ad364e35_10.0.17763.831_d1adbfc11ed3dfbc. RegistryScript:: directive completed successfully. Attachments CBS.zip 240 KB · Views: 0
Hi Gary - I think you are on a winner there. This time the output looks heaps better (see below). I've also attached the CBS.log in case you are interested. But more importantly, the "sfc /scannow" actually completes now and I am able to install Windows updates again. I believe you have fixed the problem. Thank you so much! SFCFix version 3.0.2.1 by niemiro. Start time: 2024-06-13 08:44:02.620 Microsoft Windows Server 10 Build 17763 - amd64 Using .zip script file at C:\ESS\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1 Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.manifest Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1 to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml to C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml. Successfully copied file C:\Users\blankenb-admin\AppData\Local\niemiro\Archive\Manifests\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.manifest to C:\Windows\WinSxS\Manifests\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.manifest. Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1 Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\Defender.psd1 Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpComputerStatus.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpPreference.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpScan.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpSignature.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreat.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatCatalog.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpThreatDetection.cdxml Successfully restored ownership for C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml Successfully restored permissions on C:\Windows\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5\MSFT_MpWDOScan.cdxml Successfully restored ownership for C:\Windows\WinSxS\Manifests\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.manifest Successfully restored permissions on C:\Windows\WinSxS\Manifests\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5.manifest PowerCopy:: directive completed successfully. RegistryScript:: Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5. Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\761c81c8e26..850097cd1bf_31bf3856ad364e35_10.0.17763.831_d1adbfc11ed3dfbc. Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5. Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\761c81c8e26..850097cd1bf_31bf3856ad364e35_10.0.17763.831_d1adbfc11ed3dfbc. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.831_none_5892c02f26f780e5. Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\761c81c8e26..850097cd1bf_31bf3856ad364e35_10.0.17763.831_d1adbfc11ed3dfbc. RegistryScript:: directive completed successfully.
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,283 Jun 13, 2024 #9 You're welcome. Glad we were able to help. As you're now able to update, I'll mark this topic as solved.
You're welcome. Glad we were able to help. As you're now able to update, I'll mark this topic as solved.
