DISM Error 1392

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[============================100%=========================]

Error: 1392

The file or directory is corrupted and unreadable.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

The readable portions of the Log file:

[1696] Caller did not request sparse mount
[1696] Mounting new image.
Wim:         [\\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim]
Image Index: [1]
Mount Path:  [C:\WINDOWS\TEMP\9b7451a8-9817-4b54-85ad-ac6f9cdab01b]
[1696] Wimserv process started for guid d192a7f0-1dfb-4a7a-913e-5ba362358f33.  Id is 1020
[1020] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[1020] Mounted image at C:\WINDOWS\TEMP\9b7451a8-9817-4b54-85ad-ac6f9cdab01b.
[1696] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[1696] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[1696] [0xc142011c] WIMGetMountedImageHandle:(2568)
[1696] [0x8007007b] FIOReadFileIntoBuffer:(1415): The filename, directory name, or volume label syntax is incorrect.
[1696] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[1696] [0xc142011c] WIMGetMountedImageHandle:(2568)
[1696] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[1696] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[1696] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[1696] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[1696] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[1696] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[1696] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE\Winre.wim.
[1020] Received unmount request for image with guid d192a7f0-1dfb-4a7a-913e-5ba362358f33.
[1020] Unmount for image at C:\WINDOWS\TEMP\9b7451a8-9817-4b54-85ad-ac6f9cdab01b complete.

 

Question Info


Last updated November 9, 2018 Views 37,347 Applies to:

Hi,

This issue might occur if the Windows image file is corrupt.

I would suggest you to repair the image file using the DISM command. Refer to the link and follow the steps from the link:

http://technet.microsoft.com/en-us/library/hh824869.aspx

First of all, check if the image is repairable. DISM tool will report whether the image is healthy, repairable, or non-repairable. If the image is non-repairable, you should discard the image and start again. If the image is repairable, you can use the /RestoreHealth argument to repair the image. Refer to the next section "To repair an image".

Please let us know the status of this issue.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Since no browser seems to be willing to let me upload pictures, I'm including a link to a photo doing just as you described. It's a screen shot of Windows in safe mode trying to see if safe mode might make any kind of difference. http://1drv.ms/1eOwSqh

I've also tried using the "Refresh" option available in the update and recovery section of 8.1, but it asks for a disc, to which, I only have the original Windows 8 disc, and that won't be recognized. If feels kind of like Windows has gone back to having to be re-installed like it did up until Windows 7.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

This error message could occur due to presence of bad sectors on the hard drive.

I would suggest you to run check disk and check if it fixes the issue.

  • Follow the steps below to run the check disk:
  • Press Windows+X keys and select Command Prompt (admin).
  • Type the following command and check for the errors:

chkdsk  /F /R”

Important:  Data available on bad sectors might be lost when chkdsk tries to repair your hard disc.

Please let us know the status of this issue.

27 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

This issue might occur if the Windows image file is corrupt.

I would suggest you to repair the image file using the DISM command. Refer to the link and follow the steps from the link:

http://technet.microsoft.com/en-us/library/hh824869.aspx

First of all, check if the image is repairable. DISM tool will report whether the image is healthy, repairable, or non-repairable. If the image is non-repairable, you should discard the image and start again. If the image is repairable, you can use the /RestoreHealth argument to repair the image. Refer to the next section "To repair an image".

Please let us know the status of this issue.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

This issue might occur if the Windows image file is corrupt.

I would suggest you to repair the image file using the DISM command. Refer to the link and follow the steps from the link:

http://technet.microsoft.com/en-us/library/hh824869.aspx

First of all, check if the image is repairable. DISM tool will report whether the image is healthy, repairable, or non-repairable. If the image is non-repairable, you should discard the image and start again. If the image is repairable, you can use the /RestoreHealth argument to repair the image. Refer to the next section "To repair an image".

Please let us know the status of this issue.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

http://www.tenforums.com/tutorials/7808-dism-repair-windows-10-image-15.html
"Everybody has a plan until they get punched in the mouth." - Mike Tyson

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

No bad sectors but my disk was not clean.

After Sysprep, I rebooted and missed the bios to boot into windows PE.

I Forced power off and suspect this caused the issue.

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

This issue might occur if the Windows image file is corrupt.

I would suggest you to repair the image file using the DISM command. Refer to the link and follow the steps from the link:

http://technet.microsoft.com/en-us/library/hh824869.aspx

First of all, check if the image is repairable. DISM tool will report whether the image is healthy, repairable, or non-repairable. If the image is non-repairable, you should discard the image and start again. If the image is repairable, you can use the /RestoreHealth argument to repair the image. Refer to the next section "To repair an image".

Please let us know the status of this issue.

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks.

This issue is solved. Working fine so far. 

sanfrid

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.