DISM error 193 and can't run sfc

[swertal]

Hi!
I noticed that I wasn't able to download and install KB5043076
I found out that my DISM is somehow corrupted with error 193 and can't run sfc /scannow either.


Every help will be appreciated

 

[Maxstar]

Hi and welcome to Sysnative,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• 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.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[swertal]

Hi, Sorry haven't opened this forum lately, i tried but the error logs on CMD (attached image)
I attached the following log

Thankyou, Maxtar.

 

[Maxstar]

Hi,

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[swertal]

Hi,

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[Maxstar]

Hi,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• 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.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[swertal]

Hi,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• 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.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

Still the same error i get before.

 

[Maxstar]

Please post also the SFCFix.txt file.

 

[swertal]

Please post also the SFCFix.txt file.

Sorry i forgot, here are the files.

 

[Maxstar]

Hi,

The previous fix failed, so please do the following first.

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[swertal]

Hi,

The previous fix failed, so please do the following first.

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[Maxstar]

Could not move "C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat" => Scheduled to move on reboot.

Result of scheduled files to move (Boot Mode: Normal) (Date&Time: 16-04-2025 16:06:18)

C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat => Could not move

Please open the directory "C:\WINDOWS\Servicing\Packages\" and navigate to the highlighted file and take a screenshot of this window to see if it's a 0 bytes file?

 

[swertal]

Could not move "C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat" => Scheduled to move on reboot.

Result of scheduled files to move (Boot Mode: Normal) (Date&Time: 16-04-2025 16:06:18)

C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat => Could not move

Please open the directory "C:\WINDOWS\Servicing\Packages\" and navigate to the highlighted file and take a screenshot of this window to see if it's a 0 bytes file?

No, it's a 11kb file if i'm not mistaken.

 

[Maxstar]

Failed to read file attributes for file C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat.

Please try the following fix to remove this file so we can replace it.

Start the

Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST64.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[swertal]

Failed to read file attributes for file C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat.

Please try the following fix to remove this file so we can replace it.

Start the

Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST64.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

There is 1 more file named "Addition", should i upload it?

 

[Maxstar]

Yes, but it seems you've pressed the scan button as well?

"C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat" => could not be unlocked
Could not move "C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat" => Scheduled to move on reboot.

Result of scheduled files to move (Boot Mode: Normal) (Date&Time: 16-04-2025 18:34:43)

C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat => Could not move

However, the fix failed again. Do you have an USB-stick to create a bootable Linux environment to delete this file outside of Windows?

 

[swertal]

Yes, but it seems you've pressed the scan button as well?

"C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat" => could not be unlocked
Could not move "C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat" => Scheduled to move on reboot.

Result of scheduled files to move (Boot Mode: Normal) (Date&Time: 16-04-2025 18:34:43)

C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat => Could not move

However, the fix failed again. Do you have an USB-stick to create a bootable Linux environment to delete this file outside of Windows?

Yes, i miss clicked and then i quickly close the program and launch it again. Should i run another without scan?
I do have an usb-stick, is "create a bootable Linux environment to delete this file outside of Windows?" hard to do? I'm afraid if i messed up the system.

 

[Maxstar]

I do have an usb-stick, is "create a bootable Linux environment to delete this file outside of Windows?" hard to do?

No, this is easy to do with the following steps.
1. Download the Linux Mint ISO from here: Linux Mint 22.1 "Xia" - Linux Mint
2. Use the portable version of Rufus to create the USB-stick with the Linux environment.
3. When completed you can boot the system from this stick.
4. Then the only thing you'll need to do is to remove the highlighted *.cat file

C:\WINDOWS\Servicing\Packages\HyperV-VmSerial-Package~31bf3856ad364e35~amd64~en-US~10.0.22621.1.cat