DISM WOF driver corruption

J

Jack Diamond

Member
Joined
May 26, 2020
Posts
9
I've had some intermittent computer issues - 3 disk errors (one of which restarted the computer for me with no warning), separately 3 blue screens from memory issues (Stop code: MEMORY_MANAGEMENT), apps or the whole computer freezing for 30-120 seconds; I have been working through them.

Chkdsk came up clear on the main drive (though with 54,830 reparse records, not sure if that's a lot or not); error in one directory on my e: drive was repaired, but that's non-essential, otherwise fine, and f: drive fine.
Windows Memory Diagnostic came up clear. SFC fails, DISM fails:

>SFC /SCANNOW Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 30% complete. Windows Resource Protection could not perform the requested operation. >DISM /Online /Cleanup-Image /ScanHealth Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18363.778 [=== 6.3% ] Error: 4448 The WOF driver encountered a corruption in the compressed file's Resource Table. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Downloaded the correct ISO, then ran the following per Restoring Windows 10 to an earlier point in time
>DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim

Same error.

In truth, this SFC and DISM issue has been around for a few months. Last time I tried to fix it, I did some research, tried a few things (including running them from safe mode) but nothing worked. I did a big upgrade to Windows 10 v1909, but that didn't help either. You guys are the only ones I've found who seem to consistently fix this, and now it's getting urgent. Can you help? I'm very keen not to lose my installed apps, which seems like the next step if you guys can't fix this up... I'd be deeply grateful!
 

Attachments

Forgot to say: Windows 10 Pro 1909

Also: I've checked Smart Status, all HD passed.
Ran AVG and Malwarebytes - nothing serious found, removed the new PUPs etc. that they found.
Updated a few drivers that AVG's Driver Updater found, but not all of them (I couldn't find the suggested updates at legit sources since Intel has discontinued support, and the names of some of them are cut off by AVG, but they were Realtek HD Audio, Intel Management Engine Interface, XEON processor E3-1200 v2/3rd Gen Core processor x 2, Intel Chipset USB x 2, Intel Chipset LPC Interface, Intel Chipset PCI Express x 3, Intel Chipset SMBus). BIOS is up to date.

Also - I was having a problem a couple months back with my Windows Explorer font (and Taskmanager) disappearing very occasionally, at times of high computer usage - a restart would fix it for a while. I checked and I had a font missing, which is why I got started on this whole SFC thing, but while the font never got fixed that error stopped happening.
 
Please perform a clean installation of Windows 10 May 2020 update on a known good HDD. This is damaged and can no longer be trusted or properly salvaged.
 
Thanks softwaremaniac.

The C hard disk for Windows is fine as far as I know. It's a new disk, comes up clear on chkdsk and smart, and has never had errors that I know about.
The problem disk was the E drive...

The windows install is more of an issue... I've been keeping this thing going for years now. But I was kind of hoping to get SFC working and so fix up the Windows install - I've seen in other cases where you guys managed to fix 'WOF driver encountered a corruption in the compressed file's Resource Table.'

Is there really no hope? A fresh install is going to be a huge problem, if nothing else in terms of finding apps to reinstall.
 
Yes, that in itself can sometimes be fixed, but the bigger problems are the consequences like the start menu or the right-click not working properly once fixed, so I'd still heartily recommend a reinstall.
 
Why should that be? If the DISM is fixed, then the SFC is fixed, then the windows install should subsequently be fixed too? Why would it get worse when SFC was fixed and useable?

Not meaning to disagree, so much as seeking to understand.
 
Unfortunately, I do not know what exactly causes the Start Menu/Right-click or other underlying things to stop working, but it can be the result of a sudden power loss, corrupt file system structure, bad blocks or similar.
 
OK. But then if my Start Menu/Right-click are still working fine, and you do not know what causes Start Menu/Right-click issues, then what makes you think that fixing my WOF corruption, and thus my SFC, and thus my Windows 10 install, will lead to it? Does it happen every time you fix WOF corruption?
 
Huh. Well fair enough. That answers that.

Mind you, I'd be willing to give it a go - I'd set up a Windows installer USB first, and probably deactivate my Windows (so that if I install it elsewhere I can use the same install), ready to install on a blank disk if need be... after that I'd be more than happy to roll the dice and see what happens - if it works, great, no new install; if it doesn't work then I have to do a fresh install anyway... Would you be willing?
 
I could try a few files and then see how we are progressing before I decide whether this is fixable or not, but like I said, this is a scenario where your best bet is a fresh install.
 
That sounds great (the 'try a few files') - if you are willing, I know this is a pain!
Believe me, I have considered long and hard about the fresh install, or a refresh. But finding the software is going to be a major problem in many cases (I've moved a few times...) that I'd like to avoid if at all possible.
Up to you - if you are willing then I will take a day or so to make sure I have the windows installer ready, the windows key, the office key, and as much software as I can, and a few other things I can prepare - most personal stuff is backed up to the cloud ready to be restored.
 
Hi Softwaremaniac, it's the darnedest thing!

First, sorry I disappeared on you - I got Dengue Fever, and spent the last 9 days flattened by that. So sorry.

Second, when I came back to my computer near the end of that time, to get ready for the above procedure, it seemed if anything a little worse - during normal use (OK, a LOT of tabs open in Chrome, but otherwise...) first Chrome then everything ground to a halt completely, with 100% disk use despite almost no apps showing disk usage in TaskManager. Closing the tabs, and various apps, did not help; on restart it took >30 minutes to restart, and when it came back it was slow (and something weird happened with the font in some apps).

But there was a new update out (2004?), and I thought I would have one last try. So I did an install/upgrade in place (which installed but failed to fix the problem the last two times I tried it), and would you believe it has fixed the problem?! DISM works, SFC works, and so far no weirdness at all. So I'm going to mirror this over to another hard disk (just in case I am having disk issues) and then keep testing it... in the meantime I am calling this provisionally closed, with an update after another week or two (or less if bad things happen!).

Thanks again so much for being willing to have a go at this, I really appreciated it; I hope I have now averted that need...
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top