[SOLVED] DISM Error 1392

[Scooby]

When updating a video driver I found the new one would not install. I am now stuck with the Microsoft Basic Display Adapter. A couple weeks earlier I recognized I could no longer print and found the Spooler service would Stop even if manually started.

I ran MalwareBytes which found 2 minor registry entries.

sfc /scannow verifies to 23% and then reports Windows Resource Protection could not perform the requested operation.

dism /online /cleanup-image /scanhealth returns Error: 1392 The file or directory is corrupted and unreadable. I notice about 7/8 of the way down the log file there are odd ansi characters.

OCZ SSD Utility shows my drive healthy at 96%.

Windows Updates fail to install as well. I am willing to rebuild Windows if I must but am unsure how to this this without Win10 media.

I'm at a loss as to what to do next. Any help is greatly appreciated.

 

[Scooby]

Chkdsk /scan /forceofflinefix ran successfully without issue.

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.


C:\WINDOWS\system32>chkdsk /scan /forceofflinefix
The type of the file system is NTFS.


Stage 1: Examining basic file system structure ...
  506368 file records processed.
File verification completed.
  28142 large file records processed.
  0 bad file records processed.


Stage 2: Examining file name linkage ...
  653046 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.


Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  73340 data files processed.
CHKDSK is verifying Usn Journal...
  40319224 USN bytes processed.
Usn Journal verification completed.


Windows has scanned the file system and found no problems.
No further action is required.


 124469247 KB total disk space.
 106248788 KB in 362118 files.
    248720 KB in 73341 indexes.
         0 KB in bad sectors.
    632435 KB in use by the system.
     65536 KB occupied by the log file.
  17339304 KB available on disk.


      4096 bytes in each allocation unit.
  31117311 total allocation units on disk.
   4334826 allocation units available on disk.


C:\WINDOWS\system32>

 

[BrianDrab]

Welcome to Sysnative. Sorry for the delay. Are you still in need of assistance?

 

[Scooby]

Thanks for the response. I am happy to report that last night I successfully revived my computer after many fruitless days of troubleshooting.

For those reading this thread, I tried a dirty install with media built on a USB thumb drive. It failed, I believe, because I did not have enough drive space. I found you needs ~9G + the current size of your Windows directory in order to reinstall Win 10. I was challenged for some time to remove C:\$Windows.~BT directory which was part of the failed reinstall process. I downloaded a program called Unlocker (unlocker.emptyloop.com) that was able to clear most but not all of the directory. A better method it seems is to use Windows [Disk Cleanup] and select the Windows install files. In my case this did not work either because I had adjusted the permissions on the directory and files attempting to delete them. I was able to rename the folder and then (with the proper free space) ran the Windows Setup from the USB drive and allowed driver updates during the reinstall process. Remarkably everything worked after this. AMD display adapter driver was installed. Windows Updates ran and applied patches. My Print Spooler service stays running. And I all of my applications/data/profiles remained in tact. I'm actually surprised I did not need to perform a clean install.

Overall a very sloppy job on my part but I learned quite a bit about Windows 10 in the process. I really wanted to better understand how to repair the manifest files but the logs were too cryptic for me to use Google-fu effectively.

sfc /scannow successfully verified 100% and "did not find any integrity violations."

Let me know if there are any recommendations for further cleanup and integrity checks.

P.S. After the dirty install whatever was holding onto $Windows.~BT released and allowed me to delete the directory.

 

[BrianDrab]

Thank you for letting us know. Good job!